Architecture Design

Build, Extract, Review, and Lookup ArchiMate® and UML® dediren packages. This is the router; load references only when their conditions apply.

Package

Canonical source is docs/architecture/<feature>.dediren/: edit source and policies, recreate generated output, use SVG as proof, treat OEF/XMI as optional compatibility export, and list only actual views in project.json.

Boundary

Owns ArchiMate® and UML® notation when the artifact is a dediren architecture/design package, package source/policies, SVG/OEF/XMI evidence, drift, cross-notation properties.uml.architecture_context handoff links, and ARCH-* findings. Delegate UI, API, infra, security, test-quality, live cloud observation, and implementation details that are not being modeled as package handoff facts.

Inputs

Pre-flight: inspect prompt, target package/source paths, existing dediren source, selected notation/profile, rendered SVG/OEF/XMI evidence, validation logs, requested mode, quality target, and export need. Infer only the default mode. If target/evidence/scope is missing or ambiguous, ask the user before edits/findings.

Modes

• Build: create/edit package source from architect intent.
• Extract: lift evidenced code/IaC/API/UI/workflow facts; mark architect-owned content. Put source-backed groups in model.json under plugins.generic-graph.views[].groups, not project.json.
• Review: assess validity, readability, SVG, optional export, and drift; lead with findings.
• Lookup: answer bounded notation/package/reverse-lookup questions only.

Default: architect intent -> Build; source without package -> Extract; supplied package/readiness/drift -> Review; narrow fact -> Lookup. Refuse forward-only Business, Motivation, Strategy, or Physical extraction from source; suggest Build.

Workflow

1. Read architecture and workflow.
2. Run self-check before runtime claims; it uses dediren-release.sh to resolve the pinned GitHub™ release bundle.
3. Select notation from plugins.generic-graph.semantic_profile, view kinds, export request, or prompt. Load references/notations/archimate.md for ArchiMate, references/notations/uml.md for UML®, and both for mixed packages.
4. Preserve ids, labels, source evidence, policies, architect-owned intent, and explicit cross-notation links.
5. Load task references below. In Extract mode, load references/source-weighting.md before selecting ArchiMate element, relationship, or view types unless the task is a purely mechanical update to an existing package. Keep a compact rationale for every non-obvious source-to-ArchiMate choice. Build/Extract may mutate source; Review/Lookup do not mutate by default.
6. Validate before quality claims; return output.
7. Stop when required evidence is missing, dediren returns an error envelope, the notation is unsupported, or a blocking finding prevents requested readiness.

References