Skip to content

Source Registry Standard

  • Status: CANONICAL
  • Physical owner: new-system/catalog/sources/**
  • Implementation Task: NS1-004

1. Purpose

Source references use exact paths and a revision/checksum when generated or externally verified. On a code move or public-symbol change, update inbound catalog relations, mark stale entries and regenerate disposable graphs/context packs; never preserve a false path for compatibility. CONFIRMED, INFERRED, UNKNOWN and CONFLICT remain distinct until the Task review/verification owner resolves them.

The Source Registry records what information exists, where it is, who owns it, how authoritative/fresh it is and what it may support.

Without this registry, old Legacy documents, generated summaries and current target decisions can be retrieved together without precedence or freshness.

2. Required Fields

id: source.new-system.context
type: document
canonical_location: new-system/docs/requirements/CTC_NEW_SYSTEM_CONTEXT.md
owner: new-system-program
scope:
  repository: kylejang1/ctc
  paths:
    - new-system/**
authority: durable-context
classification: internal
revision: <git-sha-or-content-hash>
valid_from: 2026-08-14
valid_until: null
supersedes: []
consumers:
  - agent-startup
  - task-context
checksum: <sha256-or-git-blob>
verification:
  status: CONFIRMED
  method: repository-readback
  last_verified_at: <timestamp>
freshness:
  update_trigger:
    - context-change
notes: []

Additional fields when applicable:

environment
tenant/profile/role
schema/table/object
tool/version
access/redaction
retention/deletion
conflicts
unknowns

3. Authority Classes

Suggested classes:

durable-context
product-target
target-design
development-standard
live-roadmap
task-contract
approved-process
current-runtime-source
current-runtime-evidence
decision
runbook
research
generated-projection
historical

A generated projection never outranks its source.

4. Source Precedence By Question

For Product target:

explicit user decision
-> New Context/Product
-> accepted Decision
-> Task input

For target architecture:

New Context/Design/architecture standards
-> accepted Decision
-> exact Task

For current Legacy behavior:

current source/environment/DB/role/provider evidence
-> current Legacy technical owner/runbook
-> dated reconstruction
-> historical Task

For Process meaning:

approved New Process contract
-> operationally verified current Process evidence
-> source-reconciled candidate
-> inference/unknown

A conflict is reported, not flattened.

5. Registry Operations

  • create on first durable use;
  • update revision/checksum/freshness after source change;
  • mark STALE when verification expires or path changes;
  • mark SUPERSEDED rather than silently deleting unique provenance;
  • delete derived index entries when the source is removed;
  • preserve ACL/classification/redaction boundaries.

6. Task Gate

A Task may not claim complete context when a required source is missing, stale beyond its declared requirement, conflicting without disposition, or generated-only where canonical evidence is required.

---

Source: new-system/docs/knowledge/SOURCE_REGISTRY_STANDARD.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.