nejimakibird_model-weave/Templates
2026-07-09 10:00:36 +09:00
..
app_process feat: add app process local domains 2026-06-11 15:41:05 +09:00
class chore: polish docs and templates for 0.1.13 2026-06-12 15:29:44 +09:00
codeset Refresh V0.7 docs samples and templates 2026-04-29 23:14:07 +09:00
data Refresh V0.7 docs samples and templates 2026-04-29 23:14:07 +09:00
dfd chore: polish docs and templates for 0.1.13 2026-06-12 15:29:44 +09:00
er chore: polish docs and templates for 0.1.13 2026-06-12 15:29:44 +09:00
mapping feat: prefer target-first mapping format 2026-07-09 10:00:36 +09:00
message Refresh V0.7 docs samples and templates 2026-04-29 23:14:07 +09:00
rule feat: add V0.8 codeset state usage support 2026-05-31 08:32:36 +09:00
screen feat: add V0.8 codeset state usage support 2026-05-31 08:32:36 +09:00
README.md feat: resolve dfd domain sources 2026-06-11 18:37:06 +09:00

Model Weave Templates

This directory contains V0.7-aligned Markdown templates for Model Weave.

Model Weave uses Markdown model files as the source of truth. Diagrams, previews, diagnostics, Mermaid output, and PNG exports are derived from Markdown.

Template policy

  • Templates are starting points, not generated outputs.
  • Keep Markdown as the canonical design asset.
  • Fill in IDs, names, references, and notes for your project.
  • Avoid leaving placeholder IDs in real design files.
  • Prefer wikilinks for cross-file references when possible.

Format groups

Stable / primary formats

Experimental / evolving formats

Important V0.7 notes

  • dfd_diagram uses the Mermaid runtime path in V0.7.
  • dfd_diagram.Objects should use id / label / kind / ref / domain / notes.
  • dfd_diagram.Domain Sources can reuse type: domains files for Domain grouping.
  • screen transitions should be written in Actions.transition.
  • New screen templates do not use an independent Transitions section.
  • class.Relations starts from the current class file; it does not use a from column.
  • class_diagram.Relations still uses both from and to.