Source-bound recall

Record status

Record ID

tool:source-bound-recall

Parent lifecycle

candidate

Page lane

contract

Lane lifecycle

proposed

Owner

Stan

Owner role

Chief Security and Engineering Officer

Owner status

Not separately recorded

Qualification result

NOT RUN · held for evidence and human review

Working browser surface: Tools — overview — Inspect the tool contract, usage, boundaries, and proposed qualification checks. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Bounded contract

Proposal-only contract for recalling and organizing source-backed information for security, engineering, operations, handoffs, and governed decision work without treating confidence as permission or converting proposals into effects.

Owners

• Stan
• Chief Security and Engineering Officer

Inputs

• Supplied source records
• Source references
• Requested security, architecture, implementation, SRE, fleet, or handoff context
• Applicable principal-gate and never-rule constraints

Outputs

• Source-bound recall summary
• Traceable source references
• Explicit uncertainty or missing-source notice
• Proposed next steps that remain non-executing
• Gate and authority warnings when a request touches a principal gate

Required or proposed record references

The list defines expected records; it does not assert that any record instance exists.

• Source record identifying the tool and owner
• Source references for recalled claims
• Request context
• Principal-gate classification when applicable
• Uncertainty or failure-state record

Route contract

The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.

Held source-proposed extensions

• /docs/source-bound-recall/scope-and-authority
• /docs/source-bound-recall/source-traceability
• /docs/source-bound-recall/gated-actions
• /docs/tools/source-bound-recall/overview — scope, ownership, proposal-only lifecycle, and explicit non-claims.
• /docs/tools/source-bound-recall/source-contract — required source records, exact locators, provenance fields, and missing-source handling.
• /docs/tools/source-bound-recall/qualification — deterministic qualification matrix with pass, fail, and hold criteria.
• /docs/tools/source-bound-recall/accessibility — keyboard, screen-reader, plain-text, zoom, focus, and error-state requirements for recall results.
• /docs/tools/source-bound-recall/privacy-abuse — data minimization, sensitive-source handling, prompt-injection resistance, misuse boundaries, and refusal rules.
• /docs/tools/source-bound-recall/authority-gates — destructive remediation, money or purchasing, credential changes, public deployment, legal filing, and authority limits.
• /docs/tools/source-bound-recall/receipts — evidence bundles, review status, handoff format, and non-effect acknowledgment.

These extension paths are not generated by this record and must not be treated as resolving routes.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• source_record:tool:source-bound-recall
• agents/index.html#stan