FREE · prove

Private Project Assistant

Answer from current local evidence and say unknown, stale, or observation-limited when support is missing.

01 · THE SITUATION

“A new engineer asks why refunds above the approval threshold need two approvers, and you need an answer that can admit uncertainty.”

Project questions keep returning to the delivery team because the repository cannot explain itself with evidence.

REPOSITORY → ACTION → ARTIFACT → OUTCOME

02 · WHAT IT READS

acme-support-agent/fictional fixture

outputs/blueprint.jsonThe system surfaces that an answer may refer to.
outputs/decisions.jsonEvidence-backed rationale for the approval rule.
outputs/bindings.jsonThe trace from an answer to its system referents.
outputs/freshness.json + outputs/coverage-boundary.mdWhether the evidence is current and safe to use.

03 · WHAT THE FDE DOES

cliVerified public-main primitive

                      adopt agent check --adapter fake_recorded --json

Available adapter-construction check using the recorded test adapter; grounded question answering remains planned.

workbenchIllustrative planned interaction

Planned local assistant — illustrative.

01Interpret the project question without widening its scope.
02Retrieve only evidence bound to relevant system identities.
03Check freshness and the observation boundary before returning a cited known, unknown, or stale result.

04 · WHAT GETS PRODUCED

outputs/answers.jsonIllustrative fixture

Answer with provenance and knowledge state

A supported answer citing PR-184, ACME-91, and routing configuration, with an explicit current-state label.

05 · WORK AVOIDED

Routine project questions start with inspectable evidence instead of returning immediately to you.

06 · CREDIBILITY BOUNDARY

The assistant is not a generic chatbot or support desk; it refuses unsupported, stale, or out-of-bound questions.

07 · NEXT STEP

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