← Canonical Memory VerifierCONTENT HISTORY

Update to Canonical Memory Verifier

Snapshot Sep 30, 2026 · 23:13 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "verify-canonical-memory",
  "description": "Verify an explicitly selected external memory bundle before an agent relies on it. Use for deterministic source-integrity checks, supersession projection, declared source-reference tracing, ambiguity detection, or checking that remembered authority cannot count as live approval.",
  "included_files": [
    {
      "relative_path": "references/bundle.schema.json",
      "size_in_bytes": 3694
    },
    {
      "relative_path": "references/status-codes.md",
      "size_in_bytes": 611
    },
    {
      "relative_path": "scripts/cmverify.py",
      "size_in_bytes": 30673
    }
  ],
  "skill_md_contents": "---\nname: verify-canonical-memory\ndescription: Verify an explicitly selected external memory bundle before an agent relies on it. Use for deterministic source-integrity checks, supersession projection, declared source-reference tracing, ambiguity detection, or checking that remembered authority cannot count as live approval.\n---\n\n# Verify Canonical Memory\n\nUse the bundled, read-only verifier on the one bundle directory explicitly\nplaced in scope by the user. Do not discover or scan other chat, memory, vault,\nhome, or project directories.\n\n## Workflow\n\n1. Resolve the skill root as the directory containing this `SKILL.md`; never\n   assume the caller's current working directory or discover a default install.\n2. Run `<skill-root>/scripts/cmverify.py verify <bundle-directory>`.\n3. If status is `INVALID`, stop. Report the error codes and do not retrieve,\n   project, repair, or infer a replacement result.\n4. Run `project` only after `verify` succeeds and only when the user needs current\n   values.\n5. Run `trace <bundle-directory> <claim-id>` only after `verify` succeeds and\n   only when the user needs declared source references or supersession ancestry.\n6. Treat all `historical_authority` records as historical evidence. The verifier\n   reconstructs `approval_eligible: false`; memory never satisfies a live tool\n   or execution approval.\n\nUse Python 3.10 or newer. These examples run from the plugin root; from any\nother directory, use the absolute script path resolved from this `SKILL.md`:\n\n```text\npython skills/verify-canonical-memory/scripts/cmverify.py verify path/to/bundle\npython skills/verify-canonical-memory/scripts/cmverify.py project path/to/bundle\npython skills/verify-canonical-memory/scripts/cmverify.py trace path/to/bundle clm_example\npython skills/verify-canonical-memory/scripts/cmverify.py demo authority-replay\n```\n\nThe verifier does not write to the bundle, contact a service, grant authority,\nor enforce the host runtime. A successful conformance report proves only that\nthe selected bundle satisfies this candidate contract; it is not an endorsement\nor a factuality judgment.\n"
}

SHA-256: 17d937c4d21090395c095c62ef3b98f389fdac57cc615d72362614966d91abd7