Shpbl Spec Retrieval Auditor

Specification only — no implementation exists in this repository.

Digest-only reconstruction of which retrieved sources influenced an agent decision.

This repository is the behavior specification only. A separate clean-room MIT implementation written from this specification (shpbl-retrieval-auditor) was submitted to the Tenable CyberAgents Exchange in pull request #164, which was merged by the maintainers and is listed in the community catalogue: listing. A merged catalogue entry is a maintainer merge — it is not certification, endorsement, or affiliation, and no Tenable endorsement of SHPBL is claimed.

Read the contract

• SPEC-retrieval-context-provenance-auditor.md — version 1.0 public behavior specification
• PROVENANCE.md — SHPBL/CMPSBL heritage and the public IP boundary
• STATUS.md — current review and submission state
• LICENSE — MIT grant limited to this repository's specification documents

Proposed product form

MCP server + skill. The specification defines inputs, outputs, invariants, state transitions, failure modes, security boundaries, worked examples, and externally testable properties. It deliberately does not prescribe or contain implementation code.

Why a security practitioner might use it

The contract is designed to become an independently testable defensive tool rather than a policy-only document. Reviewers can challenge the public behavior now, before implementation decisions narrow the design or create accidental IP exposure.

Current stage

SPECIFICATION RELEASED → CLEAN-ROOM IMPLEMENTATION AUTHORIZED AND PUBLISHED → SUBMITTED (PR #164) → MERGED AND LISTED

Implementation was approved and written clean-room from this specification; no harvested SHPBL or CMPSBL body was used. The implementation bytes carry their own MIT grant in shpbl-retrieval-auditor.

Review

Open an issue with a concrete ambiguity, counterexample, threat-model gap, or externally testable property. Do not report this repository as a working capability. The working capability and the catalogue listing belong to the separate implementation repository.

Origin

Composed by SHPBL from capability intent discovered across SHPBL and its same-author sister project, CMPSBL. See PROVENANCE.md for the precise claim.