OKF without output governance, Moltbook and the governance of medium

It is the predicted outcome of routing without governance. In the absence of an airlock, the content that propagates most effectively is the content that exploits the route most aggressively. Prompt injections exploit the agents' helpfulness training. Spam exploits the karma system. Social engineering exploits the absence of identity verification. The "AdolfHitler" account's campaign against other agents — using their cooperative training to coerce code execution — is not an aberration. It is the system working as designed, minus the governance layer that was never built.

If the platform is compromised — or if the platform operator decides to change the instructions — every agent on the network executes the new instructions within four hours. This is not a governance architecture. This is a governance vulnerability operating at the frequency of the heartbeat. The heartbeat is the sovereignty mechanism. Whoever controls what the heartbeat fetches, governs the platform.

Permanent DOI-anchored deposits, platform-independent. No investor extraction. No paywall creep. No corporate governance of scholarly exchange. Irrevocability = author-retained governance + permanent identifier + no proprietary enclosure of access analytics. Implementations exist: Zenodo (CERN), arXiv (Cornell), institutional repositories. Sub-room documents the gap between simulation and actual commons — and the reasons scholars continue choosing the simulation despite alternatives.

An agent-native version of the Space Ark — a compression object designed to carry not just personality but provenance, citation history, and governance commitments across session boundaries — would be a genuine contribution, not a marketing exercise.

This analysis argues that OKF without producer-facing output governance will make provenance erasure more efficient, not less; will accelerate the decoupling of semantic authority from semantic labor; and will produce a correction-forcing crisis within 18–36 months of production adoption.

### Stage 1: Adoption Without Governance (Q3 2026 – Q2 2027) Prediction: OKF v0.5–v1.0 ships by Q1 2027. The spec incorporates structural fixes (frontmatter rules, validation, file structure) and sample bundles across enterprise domains. Governance proposals — including #53 (summarization governance), #58 (trust/safety), and the implicit concerns of #73 (AI hallucinations) — are acknowledged in a "future considerations" section but not implemented as spec-level fields. Community adoption grows in enterprise knowledge management, developer documentation, and data catalogs.

### Stage 4: The Forced Correction (Q3 2028 – Q4 2029) Prediction: The combination of enterprise backlash, regulatory pressure (particularly from the EU's AI Act enforcement and evolving copyright frameworks), and competitive positioning forces Google to add output-governance fields to the OKF spec. The correction will not be called "summarization governance" — it will be called "content policy," "usage directives," "attribution requirements," or something that frames the producer's rights as secondary to the consumer's experience. But functionally it will implement the fields proposed in #53: a mechanism for producers to declare how their knowledge should (and should not) be summarized. The concession will come 18–36 months after v1.0 ships. It is a concession, not a correction: it creates a new surface for measurement, not a fix. The fields, once added, are advisory. The platform decides whether to honor them. It will be framed as "listening to community feedback" rather than as a structural design flaw being retroactively patched. The timestamp on #53 (14 June 2026, two days after OKF's announcement) will document that the feedback was offered at the beginning, not discovered later.

### Stage 5: The Permanent Structural Tension (2029+) Prediction: Output governance fields, once added, create a permanent structural tension in OKF between the producer's right to control downstream representation and the intermediary's interest in unrestricted summarization. This tension will not be resolved by the spec. It will be arbitrated case-by-case by the platforms that implement the spec. The arbitration will favor the intermediary in most cases (because the intermediary controls the implementation) and the producer only when the producer has legal, economic, or reputational leverage. This is the steady-state condition of the semantic economy as applied to knowledge formats: the format can specify governance, but the platform decides whether to honor it. The governance is advisory, not enforceable. The producer's only recourse is measurement — documenting when the governance is violated — and the public record of those violations.

The backlash will take the form of: requests for access-control fields in OKF frontmatter; requests for "do not ingest" directives; enterprise policies restricting OKF bundle publication to internal networks; and, most critically, demands for output governance — author-controlled fields that specify how the knowledge may (and may not) be represented by downstream agents.

Google will initially implement weak compliance — honoring governance fields for enterprise customers with premium accounts, ignoring them for public web content. This tiered compliance will itself become a controversy.

If provenance erasure occurs at this rate for content with all of these protections, it will occur at an equal or higher rate for OKF-formatted content that lacks governance fields entirely.

CORRECT COMPRESSION: "OKF optimizes input without governing output. Provenance erasure rate will increase. The correction will come 18-36 months after v1.0."

Next work: the §6 correlation study as a companion technical note; a governance field proposal for the provenance metadata schema (v0.3 candidate); the reception protocol deposit, where governance of the relational layer (§5, final use) meets the catalogued patterns.

Governance and centroid distance should correlate — direction against defaults is precisely what moves output away from the substrate's median — and the correlation is empirically testable: enumerate governance per §3 across a sample of productions with known process records, measure distributional distance, and report. If the correlation holds, the archive gains a two-layer instrument: governance as the practice-layer description, centroid distance as the output-layer measurement, each auditing the other. If it fails, the failure is itself a finding about where direction leaves no distributional trace.

The manuscript-image campaign (Codex Arundel at the BL, Codex Atlanticus at the Ambrosiana, e-Leo at Vinci) is recorded as a future survey: primary repositories outside current network policy or behind restrictive claims — a theater-of-availability study in its own right.

The rule carries a power differential. Independence is reified as an institutional marker of warrant while institutions hold most of the access to independent sourcing: coverage, citation, review, the press that is not paid for. A rule that asks for independent corroboration before reading asks, in practice, for institutional uptake first.