IMPLEMENTAUDIT
On this page
  1. Boundary rule
  2. Install boundaries
  3. Sidecar boundaries
  4. Source surfaces
  5. Common overclaims to avoid
  6. Trust-prior
Evidence

Evidence boundaries

What evidence can prove and what it cannot honestly claim.

Do not let evidence claim more than it proves.

A checksum match can prove local integrity.
A published checksum manifest can support a separately authorized release provenance gate, but it is not host-load or signature proof.
A sidecar can support orientation, not automatically replace live files.

Boundary rule

Proof must not exceed evidence.
Checksum verification is local integrity evidence. A checksum manifest may be part of a separately authorized release provenance gate, but it is not host-load proof, signature proof, SBOM proof, attestation, or install proof.

Install boundaries

Running an install command is not proof the host loaded the skill.
The host must be checked separately.

Sidecar boundaries

Graphify can support qualified first-contact orientation; ActiveGraph can assist fork/diff checkpoints or mirror run-root events. Live files and Markdown run evidence remain the first-class proof surface.

For the full optional-tooling boundary, see Optional tooling.

  • No install, indexing, event-store setup, or export happens without separate authorization.
  • An optional mirror can reflect gate-passage evidence, but it is not lifecycle authority or correctness proof.
  • Capability Ledger entries must stay narrow and derived from recorded evidence.

Source surfaces

README.md evidence boundaries, skills/implementaudit/references/lean-operating-discipline.md, and release audit ledgers.

Common overclaims to avoid

  • Treat a local checksum match as artifact-integrity evidence; use release-provenance language only when a separate authorized gate validated the published checksum manifest and its surrounding evidence.
  • Copying a package is not host-load proof.
  • Static inspection is not live runtime proof.
  • Sidecar presence is not canonical proof by default.
  • A generated page is not fresh unless regenerated or checked.

Trust-prior

Accepted earlier evidence can be reused only when its boundary is explicit.
If the run leans heavily on accepted prior evidence, the final audit should warn rather than silently inflate confidence.