system-architecture-capture

Compute and optionally write blast-radius analysis for a service or concept through the SAC graph.

C4 model integration for the architecture second brain. Map System/Person/ SoftwareContainer/Component/Code, generate L1–L4 Mermaid views, import Structurizr DSL, and avoid Docker vs C4 Container confusion.

Materialize a scan (or live scan) into SAC OKF concepts under the knowledge bundle.

Capture wireframes and architecture diagrams into the SAC second brain as OKF concepts with Mermaid or PlantUML listings embedded in Markdown. Covers wireframes (PlantUML salt), architecture, component, sequence, activity, state machine, class, ERD, deployment, C4, and data-flow diagrams. Also use when authoring Module/Class/Method/Function concepts.

Use the SAC architecture second brain when designing new features, services, APIs, mobile apps, web apps, or infra. Loads progressive-disclosure packs (blast radius, contracts, deps, environments) so design work reuses existing topology instead of inventing in a vacuum. Trigger on design, new service, new API, new feature, architecture impact, or "how should we build".

One-screen health check for SAC knowledge bundles (types, thin concepts, broken links).

Export the architecture dependency graph as JSON or Mermaid from a SAC knowledge bundle.

Ingest Jira/Linear/Azure DevOps/GitHub Issues JSON exports into TicketLink and Feature concepts.

Ingest Confluence/Notion/wiki Markdown exports into ADRs, glossary terms, runbooks, and discoveries.

Scaffold a System Architecture Capture knowledge bundle with SAC + PKC catalogs for reverse-engineering systems into OKF. Use when starting architecture capture in a repo.

Add typed architecture edges between SAC concepts (calls, exposes_api, deploys_to, secured_by, …).

Build progressive disclosure context packs (default 2-hop) for precise LLM queries over architecture knowledge.

Breadth-first reverse-engineering plan — map monorepo/multi-repo roots, rank focus areas, emit deep-dive checklists. Pause here before spawning area walkers. Not query-time retrieve.

Query-time retrieval of SAC architecture context without contaminating the parent. Spawn architecture-retriever for topology (Service, ApiContract, Package, Runtime, Pipeline, IdentityProvider, blast radius). Do not run sac_search or sac_pack in the parent. Consume only the retrieval card.

End-to-end reverse-engineer one or more git repositories into a SAC architecture knowledge graph (packages, services, IaC, CI/CD, IAM, identity, topology). Plan breadth-first, then fan out area walkers. Primary entry skill for SAC.

Run deterministic architecture scanners (packages, containers, IaC, K8s, CI/CD, identity) against a code root without writing knowledge.

Full-text search over SAC architecture knowledge concepts.

Open or close an isolated second-brain write session (worktree + PR). Use before scanning or materializing architecture when multiple agents share one knowledge remote.