Public terminology taxonomy
Customer-facing website and docs copy must use public capability names, not internal task IDs (ST-003, N086, FLOW-0x, HELPER###, H###, checkpoint/blocker IDs).
Machine-readable source
- public-terminology-taxonomy.json on the marketing site
- Human guide
Policy
| Use in public copy | Do not use in customer summaries |
|---|---|
| Runtime workload identity (SVID) rotation | ST-003 |
| DeliveryPolicy TLS/trust-chain controls | N086 |
| Sandbox delivery validation (direct / egress / relay) | FLOW-01, FLOW-02, FLOW-03, FLOW123 |
| Planes management UI (T1) | L1 /planes T1 as internal shorthand |
| Hash-chain integrity comparison | HELPER### / H### task labels |
internal_ref fields in non-claims.json may retain internal linkage for machines only.
Proof boundaries
- Blogs —
narrative_contextonly; see narrative-context.json - Proof — manifest.json and hash-chain receipts
- Merkle — integrity/tamper-evidence only; not authentication, identity, encryption, or replay prevention
Validators
Run on zen-mesh.io before publish:
python3 scripts/validation/public_terminology_taxonomy_check.py
python3 scripts/validation/public_copy_internal_id_guard.py