THE POST-IMPLEMENTATION LAYER
Built during implementation. Operated after go-live.
Onboard UX turns the evidence around a custom software or AI delivery into an inspectable system memory—so routine questions, handover work, and knowledge upkeep stop pulling the FDE back into completed engagements.
Alpha Public CLI foundation is source-only. Product experiences are qualified where prototype or planned.
blueprint.jsondecisions.jsonbaseline.jsoncoverage-boundary.mdEvidence stays inspectable
THE UNMANAGED TAIL
Completed engagements keep consuming scarce delivery capacity because the system has no durable knowledge and ownership layer.
WHAT HAPPENS AFTER INSTALL
One fictional delivery stays visible throughout: acme-support-agent. The planned Local Workbench and qualified CLI paths tell the same story.
01 Repository input
02 Verified foundation
03 Concrete output
Coverage and gap table
Review three gaps instead of every document.
LOCAL WORKBENCH · NOT SOLUTION 0
Choose a job, see what evidence it would inspect, review the artifact, and copy an equivalent CLI command where a verified primitive exists. adopt ui itself is planned—not a public command.
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.BUILD THE LAYER DURING DELIVERY · FREE FIRST
These are jobs inside the same local layer, not eight separate SaaS products. Each experience shows its real availability and boundary.
Understand
Map what shipped and preserve why it works that way.
Prove
Record behavior, answer with evidence, and make gaps explicit.
Package
Turn the verified record into reviewable handover material.
ONE CONTINUOUS RECORD
Go-live is the responsibility boundary in the middle—not the point where the product starts.
Map evidence and preserve decisions during delivery.
Record behavior, coverage, limitations, and unknowns.
Package knowledge, owners, and open work at go-live.
Keep answers, freshness, transitions, and governance useful.
AFTER GO-LIVE · PLANNED OPERATED SERVICES
Adoption knowledge only—not observability, incident response, ITSM, production support, or application maintenance.
TRUST NEEDS STATUS, NOT SUPERLATIVES
CHOOSE YOUR NEXT QUESTION
FOR THE FDE
See the first local session, qualified commands, artifacts, and honest unknowns.
Follow the FDE pathFOR THE DELIVERY LEADER
See how one durable layer can make ownership and knowledge debt visible.
Follow the leader path