FREE · package

Handover Generator

Assemble a dated, source-linked handover draft from the same system memory created during delivery.

01 · THE SITUATION

“Handover is next week, but the map, decisions, behavior checks, owners, and gaps are still scattered.”

The map, rationale, tests, owners, and gaps are scattered when the FDE needs to produce a client handover.

REPOSITORY → ACTION → ARTIFACT → OUTCOME

02 · WHAT IT READS

acme-support-agent/fictional fixture

outputs/blueprint.json + outputs/decisions.jsonWhat shipped and why it was built that way.
outputs/baseline.jsonApproved probes and the delivered behavior snapshot.
outputs/gaps.json + outputs/coverage-boundary.mdKnown gaps and the limits of the evidence.
outputs/handover/transition-record.jsonNamed responsibilities and review state for each section.

03 · WHAT THE FDE DOES

cliVerified public-main primitive

                      adopt export ./onboard-export

Available export foundation; client-ready handover generation remains planned.

workbenchIllustrative planned interaction

Planned workflow — illustrative.

04 · WHAT GETS PRODUCED

outputs/handover/index.mdIllustrative fixture

Dated handover and runbook package

A reviewable handover draft containing the system map, rationale, operating steps, probes, gaps, and boundaries.

05 · WORK AVOIDED

You review a generated handover instead of authoring a deck and runbook from scratch.

06 · CREDIBILITY BOUNDARY

The generated package is a reviewable draft; it cannot fill unknowns or transfer operational accountability by itself.

07 · NEXT STEP

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