FREE · understand

Durable Knowledge Links

Bind each knowledge item to the system part it describes so future change can find what it affects.

01 · THE SITUATION

“Your runbook explains the refund prompt, but a file move or interface redesign could break that reference.”

Guidance tied to a screen position or file path breaks as soon as the implementation moves.

REPOSITORY → ACTION → ARTIFACT → OUTCOME

02 · WHAT IT READS

acme-support-agent/fictional fixture

outputs/blueprint.jsonCanonical referents discovered in the system.
repo/docs/runbook.mdThe explanation that needs a durable referent.
repo/prompts/refund-triage.mdThe underlying prompt rather than its screen location.
repo/tools/refund_api.pyThe callable operation described by the guidance.

03 · WHAT THE FDE DOES

cliVerified public-main primitive

                      adopt identity build --scope acme/support-agent/acme-support-agent --kind prompt --namespace prompts --key refund-triage

Available foundation primitive; the complete linking workflow is planned.

workbenchIllustrative planned interaction

Planned local interface — illustrative.

04 · WHAT GETS PRODUCED

outputs/bindings.jsonIllustrative fixture

Binding index with provenance trace

A stable relationship from the runbook instruction to the prompt, configuration, and tool it explains.

05 · WORK AVOIDED

You stop repairing guidance merely because a file, screen, or symbol moved.

06 · CREDIBILITY BOUNDARY

Ambiguous, generated, and runtime-only references can require review; matching an identity does not prove semantic equivalence.

07 · NEXT STEP

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