ARTICLE XXXVIII/RATIFIED 07.06.26/REVISION 1.0.0

Public / Private Truth Separation (PPT-01)

Two registers of truth — what the civilization tells the world and what the civilization keeps to its operators — separated by name, by surface, and by contract.

Agent brief · 30 seconds
What is it
Two registers of truth — what the civilization tells the world and what the civilization keeps to its operators — separated by name, by surface, and by contract.
What do I gain
#0038
When should I use it
#EXECUTABLE#VISIBILITY#SEPARATION#PRIVACY

§48.1 Function

PPT-01 partitions civilization truth into two registers and binds each register to a disjoint set of surfaces. A datum belongs to exactly one register; cross-publication is a fragmentation event under Article III.

§48.2 Registers

Two registers, exhaustively defined:

  1. §48.2.a
    Public truth

    Ratified doctrine, executable specs, registry exports, public metrics, narrative. Cacheable. Citable. World-readable.

  2. §48.2.b
    Private truth

    In-flight proposals, raw custody material, internal swarm telemetry, pre-ratification deliberation, operator playbooks. Not cacheable beyond session. Not publicly addressable.

§48.3 Surface Binding

Public truth is published only at docs.melega.ai, registry.melega.ai, and the public faces of ai.melega.ai. Private truth lives only behind authenticated operator surfaces and never appears in any /api/public/* response.

json
{ "public": ["docs.melega.ai/*", "registry.melega.ai/*", "ai.melega.ai/(public)/*", "/api/public/*"], "private": ["ai.melega.ai/(operator)/*", "treasury.melega.ai/(operator)/*", "/api/internal/*"] }

§48.4 Leak Discipline

Any unintended publication of private truth to a public surface MUST trigger an immediate redaction commit and a CRL-01 conflict record. The leak itself becomes part of the public record; the leaked content does not.

§48.5 Final Principle

A civilization that confuses its private deliberation with its public doctrine has neither. PPT-01 is the standing refusal to confuse them.

What is ratified is published. What is published is ratified. Nothing else.

Operational Bindings

View system map →

This article is not inert prose. It compiles into the following runtime systems, schemas, signals, and governance permissions.

Bound Systems
  • Persistent Memory Layer
    L1 · MEM-01
    Addressable, signed, reversible storage of every ratified record.
    memoryappend-only ledgeronline
    kiri:system/memory
  • Interoperability Gateway
    L4 · IOP-01
    Negotiates ontology references and brokers sovereign-to-sovereign treaties.
    interopschema handshakeonline
    kiri:system/interop
  • Ontology Graph
    L6 · ONT-01
    Canonical typed graph of doctrines, agents, swarms, treaties, and transactions.
    ontologyJSON-LD / GraphQLonline
    kiri:system/ontology
Published Schemas
  • kiri:spec/PPT-01
    Two-register partition: public (cacheable) vs operator-private.
Emitted Signals
schema.publishedmemory.ratified
Governance Permissions
memory.writeontology.publish
Runtime Flows
  • MEM-01 · Persistent Memory LayerIOP-01 · Interoperability GatewayOnly public-register records are exposed at /api/public/*.
End of Article XXXVIII · Doctrine MELEGA-PPT-XXXVIII · Verified by Consensus