Publications and Encounters

This section applies when a truth system deliberately sends, exposes, or records a representation across a boundary.

Publication record

TM-PUB-001 — Exact outward identity. A publication MUST retain the exact content or a recovery-safe immutable identity of what crossed the boundary.

TM-PUB-002 — Source revision. A publication MUST identify the current truth revision and authored material from which it was produced.

TM-PUB-003 — Frozen history. Once sent or otherwise delivered, a publication MUST NOT be regenerated from later current truth and represented as the earlier artifact.

TM-PUB-004 — Lifecycle separation. Generated, drafted, reviewed, approved, published or sent, received, acknowledged, and incorporated MUST remain distinct when those events matter. Production of an artifact does not prove delivery or effect.

TM-PUB-005 — Authorship. Outward asks, commitments, or decisions MUST identify the authority that authored them. Detection of a gap does not inherit authority to demand action.

Contributions and return paths

TM-PUB-006 — Contribution as evidence. An outside answer, correction, approval, acknowledgement, file, or form submission MUST enter as attributable evidence. It MUST NOT directly edit current truth.

TM-PUB-007 — Channel independence. When the same encounter may occur through multiple channels, each valid arrival MUST enter through the same evidence and transition discipline. An interface MUST NOT become a hidden second authority path.

Publication projection

A website, report, form, workbook, API representation, or message may project current truth. The projection can be dynamic or static; what matters is that it does not acquire independent authority.

The optional Facets pattern adds stronger design constraints: one deliberately bounded outside need, no interior domain state, and disposability without loss of truth. Facet conformance is not part of core Truth Machine conformance.