# GCS-REGISTER-001 - Specification Register

Register ID  : GCS-REGISTER-001
Title        : Specification Register
Status       : Active
Version      : v1.0
Owner        : Phil
Updated      : 2026-07-08
Owns         : specification identity, dependency order, status, implementation gates

## 1. Rule

This is the document of record for Global Control Structures contracts.
Implementation order is derived from this register. No application code,
container, queue, API, data model, module, environment variable, or test may be
introduced unless it is governed by a Settled contract row here.

Contract IDs are stable and citable:

```text
GCS-<DOMAIN>-<NNN>
```

The ID says which contract. The version says which revision. IDs do not change
when titles change.

## 2. Status Lifecycle

| Status | Meaning | Implementation eligible |
| --- | --- | --- |
| Owed | Named, dependency-known, not written. | No |
| Drafted | Written for review. | No |
| Settled | Approved and binding. | Yes |
| Superseded | Replaced by a later contract. | No |

## 3. Domain Tokens

| Token | Domain | Covers |
| --- | --- | --- |
| SYS | System | Demonstration standard, scope, epistemic boundaries |
| NAME | Naming | Casing, vocabulary, folder/module boundaries, source headers |
| STACK | Architecture | Runtime shape, package ownership, external boundaries |
| DATA | Data | Acquisition, persistence, point-in-time storage |
| SIG | Signal | Inference, causality, validation of analytical claims |
| API | Transport | Wire keys, public/private endpoints, DTO rules |
| RUNTIME | Runtime | Async delivery, queues, schedulers, workers |
| DEPLOY | Deployment | Local containers, managed runtime, env vars, ports |
| SEC | Security | Lawful data, authority tiers, secrets, leakage controls |
| TEST | Test & CI | Executable conformance gates |
| IMPL | Implementation | Sequencing and phase gates |
| AUDIT | Audit | Contract-to-implementation status |
| REGISTER | Register | Specification identity, status, and dependency order |

## 4. Register

| # | Contract ID | Domain | Version | Status | Title | Artifact | Implementation gate |
| --- | --- | --- | --- | --- | --- | --- | --- |
| 0 | GCS-REGISTER-001 | REGISTER | v1.0 | Active | Specification Register | `contracts/GCS-REGISTER-001_Specification_Register.md` | Every contract artifact is registered here |
| 1 | GCS-SYS-001 | SYS | v1.0 | Settled | System Contract | `contracts/GCS-SYS-001_System_Contract.md` | Every claim traces to primary records, concordance, and uncertainty |
| 2 | GCS-NAME-001 | NAME | v1.0 | Settled | Naming and Structure | `contracts/GCS-NAME-001_Naming_and_Structure_Contract.md` | `python3 -m tools.check_contracts --check` |
| 3 | GCS-NAME-002 | NAME | v1.0 | Settled | Master Vocabulary | `contracts/GCS-NAME-002_Master_Vocabulary.md` | Vocabulary terms exist before code names use them |
| 4 | GCS-STACK-001 | STACK | v1.0 | Settled | Stack Architecture | `contracts/GCS-STACK-001_Stack_Architecture_Contract.md` | New runtime folders are contract-owned |
| 5 | GCS-DATA-002 | DATA | v1.0 | Settled | Data Acquisition | `contracts/GCS-DATA-002_Data_Acquisition_Contract.md` | Tiered source register, native clocks, point-in-time ingestion |
| 6 | GCS-DATA-003 | DATA | v1.0 | Settled | Persistence | `contracts/GCS-DATA-003_Persistence_Contract.md` | DB/migrations cannot appear without model and drift gates |
| 7 | GCS-SIG-003 | SIG | v1.0 | Settled | Signal and Inference | `contracts/GCS-SIG-003_Signal_and_Inference_Contract.md` | No causal claim from correlation; out-of-sample validation |
| 8 | GCS-API-001 | API | v1.0 | Settled | API and Wire | `contracts/GCS-API-001_API_and_Wire_Contract.md` | API/DTO inventory must precede implementation |
| 9 | GCS-RUNTIME-001 | RUNTIME | v1.0 | Settled | No Async Queue | `contracts/GCS-RUNTIME-001_No_Async_Queue_Contract.md` | Queue/broker/worker tokens fail until amended |
| 10 | GCS-DEPLOY-001 | DEPLOY | v1.0 | Settled | Runtime and Deployment | `contracts/GCS-DEPLOY-001_Runtime_and_Deployment_Contract.md` | Managed runtime must be single-target and CI-gated |
| 11 | GCS-DEPLOY-002 | DEPLOY | v1.0 | Settled | Local Container Runtime | `contracts/GCS-DEPLOY-002_Local_Container_Runtime_Contract.md` | No active Compose unless namespace/service rules pass |
| 12 | GCS-SEC-001 | SEC | v1.0 | Settled | Security, Source Authority, and Evidence Integrity | `contracts/GCS-SEC-001_Security_Source_Authority_Contract.md` | Public lawful data only; source authority and leak gates |
| 13 | GCS-TEST-001 | TEST | v1.0 | Settled | Test and CI Enforcement | `contracts/GCS-TEST-001_Test_and_CI_Contract.md` | CI and local check run the same validator |
| 14 | GCS-IMPL-004 | IMPL | v1.0 | Settled | Implementation Plan | `contracts/GCS-IMPL-004_Implementation_Plan.md` | Phase gates block analytics until the spine passes |
| 15 | GCS-OVERVIEW-001 | SYS | v1.0 | Settled | Specification Overview | `contracts/GCS-OVERVIEW-001_Specification_Overview.md` | Human-readable dependency and build map stays current |
| 16 | GCS-AUDIT-001 | AUDIT | v1.0 | Settled | Contract Implementation Audit | `contracts/GCS-AUDIT-001_Contract_Implementation_Audit.md` | Audit table is updated after contract/gate changes |
| 17 | GCS-IMPL-005 | IMPL | v1.0 | Settled | Implementation Sequence | `contracts/GCS-IMPL-005_Implementation_Sequence.md` | Exact phase order and blockers are contract-owned |

## 5. Dependency Order

1. GCS-SYS-001 fixes the claim boundary and demonstration standard.
2. GCS-NAME-001 and GCS-NAME-002 fix names before implementation.
3. GCS-STACK-001 fixes package/runtime ownership.
4. GCS-DATA-002 and GCS-DATA-003 fix source and persistence rules.
5. GCS-API-001 and GCS-RUNTIME-001 fix transport and async boundaries.
6. GCS-DEPLOY-001, GCS-DEPLOY-002, and GCS-SEC-001 fix operational safety.
7. GCS-TEST-001 makes the preceding clauses executable.
8. GCS-IMPL-004 sequences implementation.
9. GCS-IMPL-005 fixes the exact legal implementation order.

## 6. Acceptance

The register is conformant only when:

- Every `contracts/GCS-*.md` artifact has a registered ID.
- Every registered Settled artifact exists.
- Every Settled artifact names at least one executable or inspectable gate.
- `python3 -m tools.check_contracts --check` passes.