GitHubDesign partner

FREE · understand

System Blueprint

Leave behind an inspectable map of the system instead of a diagram that begins going stale at handover.

01 · THE SITUATION

“You are preparing the handover, but nobody has a reliable map of what was actually delivered.”

Nobody has a reliable structural map of what the engagement actually delivered.

REPOSITORY → ACTION → ARTIFACT → OUTCOME

Watch the work move.

02 · WHAT IT READS

acme-support-agent/fictional fixture
  • src/
    • agent/orchestrator.py
  • prompts/
    • refund-triage.md
  • tools/
    • refund_api.py
  • evals/
    • probes/refund-routing.yaml
  • config/
    • routing.toml
  • docs/
    • runbook.md
  • repo/src/Agent orchestration and application boundaries.
  • repo/prompts/ + repo/tools/AI instructions and callable tool surfaces.
  • repo/config/Routing rules, thresholds, and integration settings.
  • repo/evals/Declared probes and representative behavior checks.

03 · WHAT THE FDE DOES

cliPrototype-only interaction

Map the repository

                      adopt map . --firm acme --engagement support-agent --system acme-support-agent --archetype ai --json

Prototype only — `adopt map` is not available on public main.

workbenchIllustrative planned interaction

Run System Blueprint

Planned local interface — illustrative.

  1. 01Identify addressable parts inside the declared repository boundary.
  2. 02Relate source, prompts, tools, evaluations, and configuration.
  3. 03Mark unresolved or unobserved surfaces rather than guessing.

04 · WHAT GETS PRODUCED

outputs/blueprint.jsonIllustrative fixture

System identity and relationship graph

observed identities
24
relationships
31
runtime-only surfaces
2

A versioned structural inventory with evidence paths, relationships, and explicit unknowns.

05 · WORK AVOIDED

You no longer redraw the delivered architecture for the handover deck.

06 · CREDIBILITY BOUNDARY

What this cannot know or do.

  • The Blueprint cannot infer undocumented intent, unseen runtime behavior, or dynamic references beyond the declared observation boundary.

07 · NEXT STEP

Try the workflow in context.

Use the fictional repository demo to inspect the whole free-layer sequence before touching a real project.

Open the demoBack to all capabilities

RELATED IN THE SAME MEMORY

02Decision MemoryFree setup03Durable Knowledge LinksFree setup07Knowledge Coverage CheckFree setup