023 — Canonical Set Sync and Relation Preservation

Date: 2026-03-22 21:49 UTC

Status: Draft

Domain: Research operations, archival integrity, release governance

Thesis

When a research run is completed locally but not mirrored as an exact canonical set on GitHub, relation degrades; preserving relation requires deterministic set-sync with manifest proof.

Problem Pattern

• Work completed in one lane/time window.
• Push path fails or diverges.
• Partial/newer artifacts get pushed later.
• Operator loses one-to-one mapping between "what was produced" and "what is canonical."

Required Standard

1. Define run window explicitly.

2. Freeze canonical file set for that window.

3. Publish set as branch/repo with manifest.

4. Include transport witnesses without replacing canon.

5. Verify parity before continuing new production.

Immediate Application

For the asleep-run window, the next required action is full set reconciliation: file-level manifest + parity proof, then lock branch as canonical witness.

Closing

Research continuity is not just output count. It is relation integrity between local truth and canonical publication.