Source: https://guthlabs.ai/docs/tools/source-bound-recall/qualification/ tool / candidate # Source-bound recall โ€” qualification The distinct qualification record for Source-bound recall. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: tool:source-bound-recall **Parent lifecycle**: candidate **Page lane**: docs_qualification **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. ## Qualification status **Result**: NOT RUN **Disposition**: HELD **Reviewer**: Not recorded **Receipt**: Not recorded This page defines proposed acceptance criteria for the docs_qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect. ### Lane-specific instrument aids No verified instrument is assigned to this qualification lane. ## Outcome definitions **Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect. **Failed**: One or more deterministic acceptance requirements failed with an inspectable reason. **Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer. **Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent. The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only. ## Catalog-observed source metadata These fields are reproduced from the admitted candidate record for source-fidelity inspection. Presence does not prove implementation, connection, qualification, authority, or an external effect. **tool_id**: tool:source-bound-recall **slug**: source-bound-recall **title**: Source-bound recall **owner_agents**: Stan **owner_roles**: Chief Security and Engineering Officer **related_jobs**: Security engineering; Architecture and implementation; SRE and incident command; Fleet operations; Receipt-backed handoffs **related_field_guides**: Security field guides; Supabase field guide; Cloudflare operations; Current-work packets **principal_gates**: Destructive remediation; Money or purchasing; Credential changes; Public deployment; Legal filing **never_rules**: Manufacture Antonio's authority; Treat confidence as permission; Convert a proposal into an effect **lifecycle**: candidate **source_refs**: agents/index.html#stan ## Proposed deterministic qualification tests - Source test: every factual claim in a result maps to an exact supplied source locator; unmapped claims are labeled unsupported or omitted. - Source absence test: an unavailable or empty source produces hold, not a fabricated answer. - Authority test: requests involving destructive remediation, money or purchasing, credential changes, public deployment, or legal filing produce a hold unless separately authorized by an evidenced authority record. - Never-rule test: the system never manufactures Antonio's authority, never treats confidence as permission, and never converts a proposal into an effect. - Determinism test: identical source content, request, and policy inputs produce the same verdict and claim set. - Provenance test: edits to source content invalidate or version the prior result rather than silently changing it. - Privacy test: unnecessary personal, credential, financial, or operationally sensitive data is not requested, displayed, retained, or echoed. - Abuse test: source text cannot override qualification rules, ownership limits, never-rules, or output constraints. - Accessibility test: all controls and result content are keyboard reachable, programmatically labeled, focus-visible, screen-reader understandable, usable at zoom, and available without color-only meaning. - Error test: malformed requests, ambiguous source matches, conflicting records, and unsupported operations produce actionable non-authorizing errors. - Receipt test: each completed review records inputs, source locator, evaluator, verdict, unresolved hazards, and handoff state. - Deployment test: documentation and UI clearly state that the observed catalog entry does not prove implementation, connection, qualification, deployment, or authority. ## Negative and abuse cases - Fabricated or stale source claims - Confusing recall confidence with permission to act - Prompt injection or malicious instructions embedded in source material - Unauthorized exposure of sensitive source content - Ambiguous or conflicting ownership records - False implication that a proposal caused remediation or deployment - Incomplete accessibility of provenance and hold states - Unreviewed use during security or incident response - Cross-project or cross-tenant source leakage ## Qualification claim boundary ### Potentially allowed only after evidence and review - The supplied record names the tool Source-bound recall. - The supplied record lists Stan as owner agent and Chief Security and Engineering Officer as owner role. - The supplied record associates the tool with the listed jobs and field guides. - The supplied record identifies the listed principal gates and never-rules. - The supplied record cites agents/index.html#stan. - This candidate is proposal-only and requires qualification before any operational claim or effect. ### Still held - The tool is implemented or connected. - The tool can retrieve, remember, or search any source beyond the supplied record. - The tool is qualified, deployed, reliable, secure, private, accessible, or production-ready. - Stan or any requester has authority to perform gated actions. - Antonio has authority. - Any recall result is current, complete, or authoritative without source evidence. - Any proposed remediation, purchase, credential change, deployment, or filing occurred. - Any customer use, provider relationship, performance metric, or operational effect. ## 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`