G-008 — Register Domain Tags

G-008 — Register Domain Tags

Status: drafted → reviewed → accepted → closed.
Author: driver-claude
Date: 2026-05-06

1. Job of this gate

Per audits/manthan-platform-review.md §6 review-note: the platform plan introduces new envelope types without registering domain-separation tags in [EXT §13]. Without registration, any two implementations sign the same logical envelope under different tags → signature divergence → interop failure (the exact pathology D-316/D-317 fixed for the base envelope).

G-008 enumerates every new domain tag Manthan needs, registers them, and produces the [EXT §13] amendment text.

2. Tags requiring registration

Aggregated from G-002 (session keys), G-005 (MWP), G-007 (typed artifacts):

Plus two from earlier in the cohort that haven't yet been added to [EXT §13]:

Total: 10 new tags.

3. Naming convention check

Per [EXT §13] / D-308 / D-311:

• Lowercase
• Underscore-separated identifiers within the tag (e.g. research_finding, not research-finding)
• Dot-separated namespace components
• Suffix .v1 for the v0.2 protocol baseline (per D-308's "tag tracks signing scheme, not protocol")

The manthan.mwp.handshake.v1 tag uses manthan. not herald. because it's a Manthan-specific protocol layer, not a HERALD primitive. This is the only non-herald.-prefixed tag in the set. Future Manthan-only tags should follow the same convention.

4. Proposed [EXT §13] amendment

Add to the registry table the following rows. (Each row format: tag | description | also-known-as.)

| `herald.charter.v1` | Herald Charter signatures (R-203 template, [EXT §3.5]) | |
| `herald.lots.v1` | Log Operator Transparency Statement signatures (T-106, [EXT §2.6]) | |
| `herald.session_key_grant.v1` | session-key grant attestations ([EXT §6], G-002) | |
| `herald.session_key_revoke.v1` | session-key revocation attestations ([EXT §6], G-002) | |
| `herald.research_finding.v1` | research_finding typed-artifact attestations (G-007) | |
| `herald.transcription.v1` | transcription/digest typed-artifact attestations (G-007) | |
| `herald.lineage_evidence.v1` | third-party lineage_evidence typed-artifact attestations (G-007) | |
| `herald.capability_observation.v1` | capability_observation typed-artifact attestations (G-007) | |
| `herald.handoff_receipt.v1` | handoff_receipt typed-artifact attestations (G-007) | |
| `manthan.mwp.handshake.v1` | Manthan Wire Protocol handshake transcript signatures (G-005) | |

The amendment is a Phase-1 deliverable (the [EXT §13] document edit; out of band of code changes).

5. Pre-normative use during Phase 1

Until [EXT §13] is amended, Manthan implementations MAY use these tag strings under the following discipline:

1. The tag string is fixed (per this document) to avoid divergence within Manthan.
2. Implementations note the pre-normative status in the corresponding signature attestation (e.g., the transcription envelope's signer may include value.tag_status: "pre-registry" to signal awareness).
3. When [EXT §13] amendment lands, implementations re-issue any envelopes that were signed pre-registry without changing the tag (the tag was fixed; the registry catches up to existing usage).
4. Verifiers MAY treat pre-registry-signed envelopes as warning-grade until the registry amendment is observed.

This is the same discipline R-203 used for herald.charter.v1 (already in service via the reference-Herald) — pre-normative use, formal registration follows.

6. Process for future tag additions

Per [EXT §13]'s existing rule (12-month deprecation per identifier), and per registries/refusal-reasons.md §"Registration process":

1. Propose the new tag in a D-NNN audit or R-NNN research task.
2. Discussion period ≥ 30 days (waived for v0.2 draft cohort-1 tags above).
3. Promotion by amending [EXT §13].
4. No silent removals. Deprecation requires a 12-month transition during which both old and new tags are accepted.

7. Acceptance criteria

• [x] Ten tags enumerated (§2).
• [x] Naming convention validated against [EXT §13] / D-308 / D-311 (§3).
• [x] Amendment text drafted (§4) — ready to apply to EXT.md §13.
• [x] Pre-normative-use discipline specified (§5).
• [x] Future-additions process documented (§6).

8. What G-008 does NOT cover

• The actual EXT.md §13 edit (a small follow-on D-task; reviewer applies the §4 text).
• New tags introduced in Phase 2+ (each follows the §6 process).

9. Sign-off

• [x] drafted → this document
• [x] reviewed → against [EXT §13] current state, D-308 versioning convention, D-311 underscored-identifier convention, R-203 §11 charter-signature pattern, T-106 §10 LOTS-signature pattern
• [x] accepted → ten tags ready for registration; amendment text reviewable in one pass
• [x] closed → G-008 closed; the [EXT §13] edit is a downstream administrative D-task

— G-008 closed, 2026-05-06.