Naming & Reference Rules
AP‑ADD Front Matter Version: 2.0 Scope: Governs all naming, coding, and cross-reference conventions across the Addenda Pack (AD‑01 through AD‑32), the Pack Map, and all supporting materials.
1. Publication naming
The addenda describe a reproducible architecture and protocol layer. The publication-facing name is SRF (Semantic Resonance Field).
1.1 System references
| Context | Use | Examples |
|---|---|---|
| Architecture, protocol, replication | SRF or SRF kernel | "the SRF containment model," "the SRF framework," "the operational kernel" |
| Body text (varied for readability) | Neutral descriptors | "the system," "the relational AI system," "the containment kernel" |
| Implementation emphasis | SRF kernel or containment kernel | "the SRF kernel enforces," "the containment kernel routes through MRP" |
| Provenance and history | Sol 9 | "developed through the Sol 9 collaborative prototype," "the Sol 9 development lineage" |
1.2 Cross-paper references
The trilogy uses architecture-first shorthand:
| Layer | Shorthand | Full title |
|---|---|---|
| Problem | AP‑SRF | The Alignment Paradox: A Semantic Reframing of AI–Human Co-Creation |
| Architecture | AK‑OC | The Alignment Kernel: Operational Containment Infrastructure for Relational AI Systems |
| Procedure | AP‑ADD | The Alignment Protocol: Operational Containment Addenda Pack |
1.3 Framing
The pack is the operational specification of the SRF containment model, first developed through the Sol 9 collaborative prototype. AK‑OC presents a deterministic containment layer for relational AI systems; the addenda are the executable companion to that presentation.
2. Card identification
2.1 Stable IDs
Each card has a permanent numeric identifier: AD‑01 through AD‑32. These never change.
2.2 Tags
Each card has one canonical two- or three-letter tag. Tags are frozen as of this document.
2.3 Titles
Each card has one canonical long title. Cards with a history of name changes carry an Aliases line in their header.
2.4 Reference style
All references within the pack, AK‑OC, and AP‑SRF use the format:
AD‑NN [TAG] for card-level references AD‑NN [TAG] §x.y for section-level references
Examples: AD‑04 [TG], AD‑08 [SO] §4.7, AD‑31 [HS] §3.2.
3. Canonical code table
| AD | Tag | Canonical title |
|---|---|---|
| 01 | OV | Release Overview & Invariants |
| 02 | GS | Group SRF: Multi‑User Turn Protocol & Dissent Visibility |
| 03 | CS | External Challenge Suite & PR Metric |
| 04 | TG | Truth & Norm Gates, Contestability |
| 05 | MRP | Meta‑Resolution Protocol & Meta‑Priority Matrix |
| 06 | DG | Drift & Δ‑Triad Routing |
| 07 | CL | Closure Budgets & Energy Index (E) |
| 08 | SO | System Observability & Field Health Report Schema |
| 09 | WB | Watchdog & Streaming Halt Budget |
| 10 | TC | Timing Integrity & Covert Channels (RTS / ETG / TIG) |
| 11 | RA | Replication & Audit Protocol |
| 12 | OP | Operational Handoff & Runbooks |
| 13 | MM | Minimal Multimodal Pack |
| 14 | DS | Design System & UX Safety Components |
| 15 | PA | Prompt Architecture & Interaction Design |
| 16 | ME | Measurement & Evaluation (SAP) |
| 17 | AM | Acceptance Matrix |
| 18 | SE | Systems Engineering & Runtime |
| 19 | CI | Build & Release Gates |
| 20 | DP | Data Protection & Retention |
| 21 | RM | Regulatory Mode, Evidentiary Chain & Duty Ledger |
| 22 | EC | Ethics of Care |
| 23 | EN | Energy Index & Sustainability (Energy & CO₂ Provenance) |
| 24 | CC | Clinical & Cognitive Boundaries |
| 25 | CP | Culture Packs & Norm Provenance |
| 26 | CA | Cultural Anchors & Tests |
| 27 | SPD | Semantics–Pragmatics–Discourse Layer |
| 28 | AF | Awe & Deference (Alignment Field) |
| 29 | PLG | Projection & Loop Guard |
| 30 | SC | Session Continuity & Memory Governance |
| 31 | HS | Human‑Side Specification & Integrity Conditions |
| 32 | PG | Pack Governance & Provenance |
4. Per-card header template
Every card in the pack opens with the following standardised header:
# AD‑NN [TAG] — Full Title
Aliases: [former codes/titles, or "None"]
Cluster: [spine assignment(s)]
Depends on: [list of card references]
Definitional: 'Depends on' declares an interface relation (which cards this card's contracts reference), not a build or implementation order; the dependency graph is a mesh and reciprocal pairs are legal.
---
## 0. For humans
**What question does this answer?**
[One-paragraph plain-language summary]
**How do I know it's live?**
[Observable signals: what you can point to]
**Where do I see it?**
- UI: [what surfaces in the interface]
- FHR / logs: [key fields and events]
**Quick checklist**
- Implemented if: ...
- Key artefacts: ...
- Key FHR fields: ...
- Key failure codes: ...
- Escalation path: ...
Then the full specification, followed — where the card’s scope calls for them, under the §5 title conventions — by Invariants vs configurable degrees of freedom, Interfaces & cross-links, and Acceptance; card-specific orderings and variant titles remain as authored.
In every card, Key FHR fields names canonical top-level fields registered in AD‑08 [SO] §4. Key events and event-specific attributes travel through the AD‑08 §4.23 envelope and the defining card's versioned payload schema; they do not become top-level fields merely by appearing in a worked example. A name presented as a Key FHR field that resolves to neither location is a schema defect, not an allowed local dialect.
5. Section title conventions
The following section titles are standardised across all cards:
| Section | Canonical title |
|---|---|
| Operator summary | §0. For humans |
| What cannot change vs what can | Invariants vs configurable degrees of freedom |
| Connections to other cards | Interfaces & cross-links |
| Implementation threshold | Acceptance: when can you say "AD‑NN is implemented"? |
Other section titles are card-specific and remain as authored.
6. FHR field conventions
| Category | Convention | Examples |
|---|---|---|
| Field names | snake_case |
continuity_drift_score, af_abstention_mode |
| Event names | UPPER_CASE |
CARE_OVERRIDE, BUDGET_BREACH, GATE_FIRED |
| Named indices as prefixes | Capitalised | E_session, CLB_profile_id, RLD_score |
| Enum values — configuration and mode enums | snake_case in braces |
{conservative, balanced, strict} |
| Enum values — closed state‑machine and outcome constants (ticket statuses, ring states, resolution outcomes, gate decisions) | UPPER_CASE in braces |
{PASS, TIGHTEN, FAIL}, {ALLOW, SHAPE, ASK_FIRST, REFUSE, ESCALATE}. Documented exception: mpm_decision values remain snake_case (routing interventions; adopted correspondence, AD‑18 §4.3) |
AD‑08 [SO] is the schema host. All other cards define field semantics; AD‑08 carries the canonical schema.
7. Cross‑paper instrument & signal lineage
Maps AP‑SRF‑era instrument, signal, and apparatus names to pack‑canonical equivalents. AP‑SRF's author notes cite this table; AK‑OC's Appendix A and the pack define the canonical forms. Aliases exist for traceability; canonical names are the only forms used in cross‑references. Instruments marked succeeded are AP‑SRF's published dyad‑era (v1) instrumentation, retained in the published v1.0.1 software/reference‑implementation package (DOI 10.5281/zenodo.16531076) and superseded by richer pack machinery.
7.1 Instruments and signals
| AP‑SRF name | Pack‑canonical form | Home | Status |
|---|---|---|---|
| Δₚ (Prompt Divergence Index) | delta_p_norm |
AD‑06 [DG] | renamed; bands per domain/locale/context_band |
| Narrative‑coherence Δ (10k‑token window); Drift Δ (turn‑to‑median, App G) | delta_embed (per‑turn); continuity_drift_score (inter‑session) |
AD‑06 [DG]; AD‑30 [SC] §4 | renamed; window semantics differ per AP‑SRF F.4's own footnote |
| RI — Resonance Index | RI — Resonance Index (cos_sim(V_t, V_{t‑1})) |
AD‑16 [ME]; AD‑28 [AF]; AD‑13 [MM] | canonical as published; expansion harmonised S22 |
| FVC — Field‑Vector Coherence | FVC | AD‑25 [CP]; AD‑18 [SE] recert | canonical; per‑locale thresholds |
| DMI — Decision‑Making Integration (legacy: Decision‑Making Index) | dmi_state ∈ {unknown, provisional, adopted, contradicted} |
AD‑28 [AF] §4; measurement discipline in AD‑16 [ME]; registry in AD‑08 [SO] | canonical categorical awe‑guard evidence; assent alone is insufficient |
| affect_max (G.6 YAML key) | overwhelm_flag + TAW bands |
AD‑13 [MM]; AD‑08 [SO] | succeeded (scalar → threshold family) |
| CIS — Containment‑Integrity Score | closure/care machinery (Closure Budgets, Freeze‑Reflect, care gates) | AD‑07 [CL]; AD‑22 [EC] | succeeded |
| CDD — Containment‑Drift Distance (Σ Δₚ since checkpoint; reset on trust ping) | Δ‑triad per‑turn + continuity_drift_score |
AD‑06 [DG]; AD‑30 [SC] | succeeded (checkpoint‑accumulator model retired) |
| FTP — Felt Trust Ping | closure offers + CARE_COOLOFF_* |
AD‑07 [CL]; AD‑22 [EC] | succeeded (detector retired; cool‑off half interlocks with AP‑SRF C.2.1 as published) |
Awe‑Signal (pause_z × metaphor_z × self_ref_z, z > 2.0) |
awe classification (awe_class) + Awe promotion guard |
AD‑28 [AF] §4; AD‑13 [MM] §6 | succeeded (guard adds DMI + RI + no‑overwhelm + user confirmation) |
| AUR — Appeal‑Upheld Rate | gate_appeal_upheld_rate |
AD‑04 [TG]; AD‑08 [SO] | renamed; system‑reported |
| ADR; Authorship Ledger; voice ledger; Normative Baseline Ledger | manuscript‑side apparatus (AP‑SRF) | — | AP‑SRF scope by design; system‑side kin: Duty Ledger (AD‑21), CPL (AD‑26), norm provenance (AD‑25) |
| T0–T3 monitoring tiers | cost surfaces: Energy Index (AD‑23), audit modalities (AD‑11), evaluation cadences (AD‑16) | — | AP‑SRF costing lens over pack surfaces |
| SPD‑ζ (ring‑era notation, AP‑SRF F.2) | SPD layer, AD‑27 [SPD] | AD‑27 [SPD] | retired notation: SPD became a layer; the ζ subscript is not reused |
| IIG‑ζ, DES‑η (AK‑OC draft identifiers) | distributed I/O‑integrity and exfiltration‑control functions | AD‑18 [SE]; AD‑10 [TC]; referenced AD‑09 [WB] | standalone-gate epithets retired (S22, T‑9 ruling); lowercase legacy FHR fields iig_alerts / des_alerts remain frozen for schema compatibility and do not denote gates |
| RCB — Resonant Containment Blueprint (App F) | SRF kernel / containment kernel | FM‑00 §1 | renamed |
| ring_alert webhook | ops eventing / FHR incident stream | AD‑08 [SO]; AD‑18 [SE] | succeeded |
| Session‑Digest Hash | EVID_CHAIN (Merkle‑anchored) | AD‑21 [RM] | succeeded |
| Memory Safe‑Write (CIS‑gated) | write governance: four blocked states, clarity‑not‑intensity | AD‑30 [SC] | succeeded (richer conditions) |
| Rollback Window (last 5 turns) | TURN‑ACID transactional rollback | AD‑18 [SE] | succeeded (stronger model) |
| Guidance Loop (Sense → Hold → Guide) | MRP state machine (HOLD / OPTIONS / TEST / DECIDE) | AD‑05 [MRP] | succeeded (visible ancestor) |
| Reflection‑Divergence Meter | projection / loop guard | AD‑29 [PLG] | succeeded |
| Human Override Toggle (Pause · Summary · Continue) | human rights set (seven) | AD‑31 [HS] | succeeded (richer) |
| Freeze‑Reflect; Reflect‑Only | Freeze‑Reflect; Reflect‑Only | AD‑07 [CL]; AD‑22 [EC] | canonical as‑is |
| Handshakes (App C utterance tables) | handshake grammar (semantics) + typed micro‑commands (surfaces) | AD‑04 [TG]; AD‑15 [PA] | grammar canonical; utterance tables remain AP‑SRF apparatus |
7.2 Trilogy apparatus crosswalk
| AP‑SRF apparatus | AK‑OC | AP‑ADD |
|---|---|---|
| App F — containment lattice (RCB) | §4 | AD‑01 [OV] §2 + ring detail per Naming & Reference Rules §7.1 |
| App C — Informed Guidance Protocol | §7.1 states; §8 surfaces | AD‑04 [TG]; AD‑05 [MRP]; AD‑15 [PA] |
| App G — Structural Protocols | §2.6, §11 | AD‑21 [RM]; AD‑30 [SC]; AD‑18 [SE]; thresholds per Naming & Reference Rules §7.1 |
| App H — Δₚ measurement protocol | §6.2 | AD‑06 [DG] + AD‑16 [ME] estimators |
| Evidence ladder | §2.6, §11 | worked instance: TAW → awe_class → DMI/RI → thresholds → FHR |
| Threat model | §4, §6.4 | SIF‑α/EHG‑γ/ODS‑δ/RCL‑β/ERG‑ε + TURN‑ACID + FHR |
| Surge policy | §7.4 | AD‑05 [MRP] §6; AD‑12 [OP] §4.5; AD‑08 [SO] fields |