Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/XxYouDeaDPunKxX/canon-boundary-guard-for-gpt-project/llms.txt

Use this file to discover all available pages before exploring further.

Installing Canon Boundary Guard means two things: uploading the zipped canon-boundary-guard-gpt/ bundle to your ChatGPT Project’s files or sources, and pasting the contents of PROJECT_CUSTOM_INSTRUCTIONS.txt into the Project Instructions field. The zip provides the frame — the skill definition, reference files, schemas, and optional scripts. The Project Instructions tell ChatGPT to locate the bundle at session start, inspect it, and use it as the operating frame before producing any substantive output. Together, the two pieces form the stable anchor that prevents chat messages, drafts, and model assumptions from being silently promoted into accepted project truth.

Bundle structure

The canon-boundary-guard-gpt/ folder is the complete published unit. The tree below shows every file included when you zip it for upload:
canon-boundary-guard-gpt/
|-- SKILL.md
|-- references/
|   |-- gpt-project-adapter.md
|   |-- proof-of-read.md
|   |-- protocol.md
|   |-- scratch-canon.md
|   `-- state-and-recovery.md
|-- schemas/
|   |-- CANON_STATE_DELTA.schema.json
|   `-- SESSION_STATE.schema.json
`-- scripts/
    |-- artifact_fingerprint.py
    |-- extract_proof.py
    `-- validate_state.py
SKILL.md is the primary skill definition and the first file ChatGPT inspects during bootstrap. The references/ files define provenance layers, the GPT Project persistence boundary, state and recovery rules, scratch-to-canon promotion rules, and proof-of-read requirements. The schemas/ files are used to validate session state and snapshot deltas. The scripts/ files are optional Python helpers for mechanical validation — they are not hooks and do not make provenance decisions.
A ChatGPT Project is the recommended container for running Canon Boundary Guard. Uploading the bundle as a Project Source means it is available at the start of every chat inside the Project, giving the frame a stable and persistent home. Manual chat use is possible but provides weaker continuity.

Build docs developers (and LLMs) love