Research-Stack/0-Core-Formalism/otom/specs/SCW-8192.md

SCW-8192: Salted Causal Witness Identifier

Status

BEAUTIFUL_PROVISIONAL until the encoding, parser, and receipt validation tests exist.

This specification defines an 8192-bit salted causal witness identifier for OTOM / ENE / AMMR / AVMR / NUVMAP workflows.

SCW-8192 is intentionally longer than standard UUIDs and observability trace IDs. It is not merely an ID. It is a causal witness envelope.

---

One-sentence definition

SCW-8192 is an 8192-bit salted causal witness identifier whose leading salt establishes the causal namespace, quarantine boundary, and decoding domain for the remaining witness envelope.

---

Why this exists

A normal 128-bit trace ID is sufficient for industrial distributed tracing because it provides a low-collision causal namespace for ordinary service telemetry.

SCW-8192 targets a different threat model:

• false lineage merges,
• stale artifact resurrection,
• semantic projection contamination,
• connector/source ambiguity,
• legacy-pattern infection,
• cross-domain namespace bleed,
• mixed evidence receipts,
• adapter-induced ambiguity,
• long-lived research artifacts crossing repositories, documents, simulations, and memory systems.

This project does not merely route logs. It routes, extracts, filters, re-attests, simulates, projects, compresses, and commits structured research artifacts across multiple mathematical and computational layers.

So the answer to “why in Euler's name is it that long?” is:

Because SCW-8192 is not trying to be a shorter UUID.
It is trying to prevent causal contamination across a manifold-scale evidence system.

Or less politely:

You do realize what this project is and does, right?

---

Not a UUID in the strict RFC sense

SCW-8192 may be UUID-like in usage, but it is not an RFC 4122 UUID.

It should be treated as:

salted witness handle + causal namespace + receipt-binding envelope

not as:

a giant random identifier that proves something by itself

SCW-8192 is not proof. It is a routing and attestation handle that binds proofs, hashes, receipts, and lineage records together.

---

Canonical shape

SCW8192 := Salt256 || Header128 || Body7808

Where:

Region	Size	Purpose
Salt256	256 bits	leading domain salt / causal-universe gate
Header128	128 bits	version, schema, namespace, and mode flags
Body7808	7808 bits	witness envelope

Total:

256 + 128 + 7808 = 8192 bits

---

Leading salt law

The leading salt defines the causal universe in which the witness may be interpreted.

same artifact + different salt = different causal universe
same trace + different salt = forbidden merge
same legacy idea + new salt = sanitized re-entry

The salt is not padding. It is the first-class domain separator.

Two SCW-8192 identifiers may not be merged, compared as siblings, or treated as members of the same causal lineage unless their salt domains are compatible under the active schema.

---

Salt modes

Mode	Use	Meaning
random_salt	new event	prevents collision and replay coupling
domain_salt	project namespace	binds ID to OTOM / ENE / AMMR / NUVMAP context
quarantine_salt	legacy extraction	keeps old artifacts from contaminating active schemas

Legacy quarantine example

SCW8192_LEGACY_QUARANTINE =
    Salt256("legacy/quarantine/context-redacted")
 || Header128
 || Body7808

Active research example

SCW8192_ACTIVE =
    Salt256("active/otom/current-schema")
 || Header128
 || Body7808

---

Recommended body layout

The body layout is versioned. The following is the initial recommended layout for schema_version = 0.1.

Body7808
├── 128 bits   trace lineage root
├── 128 bits   span / operation seed
├── 256 bits   artifact content digest witness
├── 256 bits   parent AMMR digest witness
├── 256 bits   source / tool / connector digest witness
├── 256 bits   projection / adapter digest witness
├── 512 bits   residual / metric witness
├── 1024 bits  NUVMAP witness block
├── 1024 bits  AVMR vector-state witness block
├── 1024 bits  cryptographic agility reserve
├── 1024 bits  entropy reserve / nonce material
└── 1920 bits  extension / attestation region

The sum is:

128 + 128 + 256 + 256 + 256 + 256 + 512 + 1024 + 1024 + 1024 + 1024 + 1920 = 7808

---

Required companion fields

SCW-8192 must not be used alone. Every receipt that uses SCW-8192 must also carry:

Field	Purpose
artifact_digest	cryptographic content identity
trace_id	conventional 128-bit trace compatibility field, if needed
span_id	local operation identifier
parent_span_id	immediate causal parent, nullable
source	connector, runtime, repository, or tool origin
adapter_class	parser / projection / simulation adapter
receipt_id	stable evidence packet identifier
claim_state	BEAUTIFUL_PROVISIONAL, CALIBRATED_ENGINEERING_DELTA, or REVIEWED

---

Collision / contamination handling

A collision, parse ambiguity, salt mismatch, or incompatible schema interpretation is causal contamination.

When contamination is detected:

1. do not merge the trace,
2. do not promote affected receipts,
3. split the lineage,
4. re-attest artifacts by content hash,
5. assign fresh SCW-8192 identifiers under an explicit quarantine salt,
6. record the event in the AMMR history.

---

Encoding rules

Initial recommended textual encoding:

scw8192:<schema-tag>:<hex-2048>

Where:

Field	Meaning
scw8192	identifier family
schema-tag	versioned layout tag
hex-2048	8192 bits encoded as 2048 lowercase hex characters

Rules:

• Hex MUST be lowercase.
• Encoded body MUST be exactly 2048 hex characters.
• Parser MUST reject unknown schema tags unless explicitly configured for migration.
• Parser MUST validate salt mode and header before interpreting the body.
• No semantic claims may be inferred from random/reserve regions.

---

Security and claim discipline

SCW-8192 is designed to reduce accidental causal contamination, not to replace cryptographic proof systems.

Forbidden claims:

SCW-8192 proves artifact truth.
SCW-8192 replaces content hashing.
SCW-8192 replaces AMMR commits.
SCW-8192 makes collisions impossible.
SCW-8192 validates semantic meaning by itself.

Allowed claims:

SCW-8192 provides a large, salted causal witness namespace.
SCW-8192 binds a causal event to receipts, hashes, adapters, and lineage records.
SCW-8192 makes accidental false-lineage merge practically negligible under the active threat model.
SCW-8192 supports quarantine and domain separation for legacy artifact extraction.

---

Relationship to 128-bit trace IDs

128-bit trace IDs prevent accidental causal collision in ordinary distributed tracing.
SCW-8192 prevents accidental causal contamination in manifold-scale research workflows.

This is the distinction.

A trace ID answers:

Which request or execution path is this part of?

SCW-8192 answers:

Which salted causal universe, artifact lineage, adapter path, evidence receipt, and projection context may interpret this event?

---

Minimal implementation checklist

• Implement parser for scw8192:<schema-tag>:<hex-2048>.
• Enforce exact length.
• Decode leading Salt256.
• Validate Header128.
• Reject incompatible salt modes.
• Emit companion receipt fields.
• Add AMMR contamination handling path.
• Add tests for salt mismatch, malformed hex, wrong length, and schema mismatch.
• Add golden vectors.
• Add migration policy for future schema tags.

---

Formal summary

SCW-8192 = causal namespace insulation + witness envelope + anti-contamination gate.

It is intentionally long because the system it protects is intentionally broad.

It names not just a thing, but the permitted causal universe in which that thing may be interpreted.