`architect` — guides

Get an evidence-backed view of the architecture before deciding whether to harden, optimize, scale, modernize, replace, or retain it. You can begin without knowing a skill name:

Assess architecture and provide an action plan.

The first result is a current-state model you can correct, not a verdict. After you accept the map, the agent shows attention hotspots and asks where to drill down. Inspection is read-only by default. You approve private enterprise retrieval, executable checks, runtime evidence, experiments, and file writes.

Choose your task

• Assess a repository when you need a map, evidence coverage, hotspots, findings, and an action plan.
• Shape an architecture concept when the current-state evidence is clear and you need a future-state choice.
• Diagram a system when the picture is the main outcome.
• Review an architecture artifact when you already have an assessment, design doc, diagram, RFC, or ADR.
• Establish a reference architecture when the repository needs a normative golden path for future work.

Start here

• Your first architecture session — run a bounded survey and finish with a corrected current-state map, evidence ledger, attention heat map, and selected next investigation.
• Create and use your reference.md — separately capture one real engineering standard and use it to steer design.
• Hand an intent to build — move shaped work into the build loop.

Look up behavior

• Architecture assessment reference — modes, evidence surfaces, reads, permission gates, output, confidence, and limits.
• reference.md sections and stack-pack contract — the normative repository foundation and delivery rules.

Understand the choices

• Why the diagram workflow works this way — notation, layout, encoding, grounding, and portability.

Installing and upgrading live in ../_shared/.