Archie Architecture Assistant
Review evidence, create artifacts, and propose controlled architecture changes
Archie is the project-aware architecture assistant. Its context follows the current project, selected version, page, focused resource, attached Decision, and approved knowledge.
Conversations And Context
Use Archie to inspect dependencies, compare evidence, explain analysis, draft documentation, or explore a future state. Navigating to a different page changes the context available to new messages, so name the target resource when ambiguity matters.
Examples:
- “Explain the external blast radius for Checkout in the context lens.”
- “Compare this workflow with the declared Relationships.”
- “Draft a security posture document using the current View and Data Model.”
- “Start an architecture simulation for separating payment orchestration.”
Workbench Artifacts
Archie can return structured artifacts rather than only prose. Depending on the task, the workbench can show diagrams, lists, spotlights, document drafts, Data Model proposals, or simulation state.
Inspect the artifact and its evidence before acting. Story mode can walk through a sequence of focused views, while the reader still controls the active lens where supported.
Approval Cards
Changes proposed inside the Archflow chat use explicit approval cards for supported mutations. Review names, stable resources, selected version, and downstream effects before applying.
An interrupted application can require reconciliation. Resume the existing operation safely rather than asking Archie to create a duplicate change.
Focused Modes
- A focused Architecture Document gives Archie the canonical document and its version context.
- A Decision discussion attaches the finding and affected resources.
- Architecture Simulation mode maintains a durable objective, expected outcome, change set, and revision history.
- Page-specific capability packs expose only the tools relevant to the current work.
Memory And Knowledge
| Scope | Use it for |
|---|---|
| Account memory | Cross-project preferences and communication style |
| Project Knowledge | Sources, approved memories, and reviewed insights for one project |
Uploaded sources are evidence, not automatically accepted truth. Approved memories and insights are the durable project knowledge Archie can reuse.
Safe Use
- Confirm the active architecture version.
- Ask Archie to cite the project evidence behind a conclusion.
- Keep product-facing names readable and implementation references in descriptions.
- Treat analysis and generated content as review material.
- Use Architecture Simulations for durable what-if changes instead of editing the baseline through conversation.