- one node per decision (tag coloured by status) with decides links to its elements and supersedes links
- one node per registry file with defines links to its elements
- own legend chips, side panels (Open decision, Open registry), type:decision and type:registry
- walks and paths follow the diagrams' connections only; attached nodes follow their elements into a result
- Model | Graph switch on main.archify (Diagram | Graph on diagram pages, narrowed to that diagram)
- union graph of every element and connection, registry and inline, built from the model index
- query box: text, type:, diagram:, decision:, uses:, near:, from: to:, unused, shared, -shared
- side panel per element and connection with diagrams, registry line and decisions one click away
- legend chips, Fit, Layout, Labels, Export PNG; Cytoscape.js bundled as dist/graph.js
- command Archify | Open Model Graph; integration check; unit tests for graph and queries
- *.archify-decision files: id (unique, words), title, status, date,
elements, diagrams, supersedes, and prose; parsed, merged and link-checked
in the model index; diagnostics on the file
- diagrams point at decisions with decisions: [...] on the diagram, nodes
and edges; stripped before Archify, unknown ids reported, completion,
hover and go-to-definition for the ids and for elements/diagrams/
supersedes in decision files
- Decisions panel on the main.archify page; Decisions rail panel under a
diagram (hover lights up the node or connection); decisions on element
cards and in the element dialog; decision view for the file, with a
lost-model note outside a model
- Archify | New Decision… command and template; editor schemas; the three
New Model examples carry decisions; docs, changelog, 0.8.0
- resolveRefs no longer adds cards to a diagram; it returns node id →
description, which the page sets as the tooltip of the matching row in
Archify's Elements panel
- hand-written cards pass through unchanged; docs and changelog
- model page: registry elements are rendered as Archify info cards (type
colour dot, label, id · type, description, used-in chips that open the
diagram), replacing the table
- resolveRefs: a diagram without cards of its own gets one card per drawn
shared element that has a description, so the registry text shows under
every model diagram as it does on hand-written diagrams
- unit tests for generated cards, own cards winning and no cards without
refs; docs and changelog
- templates/models: C4 - Standard Web App, C4 - E-Shop, C4 - Event-Based
Integration; each a complete model (main.archify, registry, context,
containers, components) that validates
- archify.newModel: pick an example and a folder name, copy it, name the
model after the folder, open the model page
- Explorer menu: New Model… on folders, Open Model on .archify and
.archify-registry files; File → New File… lists New Model…
- unit test validates every example end to end; integration test runs the
command; README, CHANGELOG, docs/model.md
A folder with main.archify at its top is a model, a set of diagrams
that belong together. Opening main.archify shows the model page: the
model's name and description, its own overview diagram when the file
has one, the diagrams grouped by folder (click to open), and the
registry with where each element is used. The page is built by
traversing the folder tree and refreshes when files change.
*.archify-registry files define shared elements once; diagrams draw
them with `ref: <id>` plus position and may override label, sublabel
and tag. References are resolved before Archify runs, so Archify is
unchanged. Hover, go-to-definition and completion on ref; unknown
names, forbidden overrides, duplicate ids and broken registries in
Problems; registry edits re-render open diagrams. `diagram:` links on
elements and components open the linked diagram on double-click.
New command Archify | Open Model, a Model template for New Diagram…,
editor schemas for the new keys and for registries, docs/model.md and
examples/online-shop. Single diagrams behave exactly as before.