FOR FORWARD-DEPLOYED ENGINEERS
Build a reviewable record from the repository while you can still verify it. Package what shipped, expose what is unknown, and stop redrawing the same context for every handover and later question.
adopt map is prototype-only and absent from public main.A CAREFUL FIRST SESSION
The commands below illustrate a safe evaluation path. Consult the public source and command help before using an Alpha tool on a real repository.
BOUNDARY
This website fixture is inert. It does not connect to a repository, send data, or execute product code.
./acme-support-agentDETECT
Keep detection separate from comprehension. An archetype result does not mean every system surface is understood.
adopt detect ./acme-support-agent --jsonCHOOSE
Check whether the page says public-main, prototype-only, or illustrative before copying any command.
REVIEW
A useful result says what evidence supports it, what stayed outside the boundary, and who must confirm the rest.
outputs/…TWO EQUIVALENT PATHS
The planned Workbench would make the free capability suite discoverable. Its CLI view preserves the same repository, selected job, artifact, outcome, and limit.
You no longer redraw the delivered architecture for the handover deck.
Action status: Planned local interface — illustrative.
Limit: The Blueprint cannot infer undocumented intent, unseen runtime behavior, or dynamic references beyond the declared observation boundary.
You no longer reconstruct the decision from memory or old chat threads months later.
Action status: Planned workflow — illustrative.
Limit: When recoverable evidence does not explain the rationale, Decision Memory marks it unknown and asks a human to confirm it.
You stop repairing guidance merely because a file, screen, or symbol moved.
Action status: Planned local interface — illustrative.
Limit: Ambiguous, generated, and runtime-only references can require review; matching an identity does not prove semantic equivalence.
You leave a repeatable reference for detecting behavior change instead of relying on memory.
Action status: Planned workflow — illustrative.
Limit: A baseline is not production monitoring or proof of correctness; it covers only approved probes and cannot trigger real side effects.
Routine project questions start with inspectable evidence instead of returning immediately to you.
Action status: Planned local assistant — illustrative.
Limit: The assistant is not a generic chatbot or support desk; it refuses unsupported, stale, or out-of-bound questions.
You review a generated handover instead of authoring a deck and runbook from scratch.
Action status: Planned workflow — illustrative.
Limit: The generated package is a reviewable draft; it cannot fill unknowns or transfer operational accountability by itself.
You spend scarce subject-matter-expert time correcting missing areas instead of reviewing everything.
Action status: Planned local interface — illustrative.
Limit: Completeness is relative to the observed inventory and declared boundary, never a claim that the whole real-world system is documented.
You can state the evidence boundary clearly instead of letting confidence imply coverage.
Action status: Planned local interface — illustrative.
Limit: The statement reflects declared access and current observations; it is not a certification, compliance attestation, or proof about unseen systems.
adopt map . --firm acme --engagement support-agent --system acme-support-agent --archetype ai --jsonLimit: The Blueprint cannot infer undocumented intent, unseen runtime behavior, or dynamic references beyond the declared observation boundary.
# No public CLI workflow for the planned Decision Memory experienceLimit: When recoverable evidence does not explain the rationale, Decision Memory marks it unknown and asks a human to confirm it.
adopt identity build --scope acme/support-agent/acme-support-agent --kind prompt --namespace prompts --key refund-triageLimit: Ambiguous, generated, and runtime-only references can require review; matching an identity does not prove semantic equivalence.
adopt probe manifest validate evals/probes/refund-routing.yamlLimit: A baseline is not production monitoring or proof of correctness; it covers only approved probes and cannot trigger real side effects.
adopt agent check --adapter fake_recorded --jsonLimit: The assistant is not a generic chatbot or support desk; it refuses unsupported, stale, or out-of-bound questions.
adopt export ./onboard-exportLimit: The generated package is a reviewable draft; it cannot fill unknowns or transfer operational accountability by itself.
adopt coverage recompute --system acme-support-agent --jsonLimit: Completeness is relative to the observed inventory and declared boundary, never a claim that the whole real-world system is documented.
adopt boundary --answers adopt/boundary-answers.json --archetype ai --write-statement ./onboard-output/coverage-boundary.mdLimit: The statement reflects declared access and current observations; it is not a certification, compliance attestation, or proof about unseen systems.
Inspect this repository using the public adopt CLI. Start with `adopt detect ./acme-support-agent --json`. Report what the command verifies, what remains unknown, and every local artifact created. Do not send repository content over the network.
adopt ui is not a public command. The browser Workbench shown here is a planned experience. Verified commands are labelled separately.VERIFIED LOWER-LEVEL PRIMITIVES
These commands were verified in public main as foundations for planned workflows. Their adjacent notes keep that distinction explicit.
adopt identity build --scope acme/support-agent/acme-support-agent --kind prompt --namespace prompts --key refund-triageAvailable foundation primitive; the complete linking workflow is planned.
adopt probe manifest validate evals/probes/refund-routing.yamlAvailable validation primitive; baseline recording remains planned.
adopt agent check --adapter fake_recorded --jsonAvailable adapter-construction check using the recorded test adapter; grounded question answering remains planned.
adopt export ./onboard-exportAvailable export foundation; client-ready handover generation remains planned.
adopt coverage recompute --system acme-support-agent --jsonAvailable deterministic coverage primitive; the visual gap workflow is planned.
adopt boundary --answers adopt/boundary-answers.json --archetype ai --write-statement ./onboard-output/coverage-boundary.mdAvailable boundary primitive; the guided Workbench review is planned.
CODING-AGENT PATH
A useful instruction asks the agent to separate verified output from inference and announce writes before they happen.
Inspect ./acme-support-agent using only the public adopt CLI. Begin with `adopt detect ./acme-support-agent --json`. Before any command that may write, state the target path. Separate verified output from inference, list every unknown, and do not transmit repository content.