C64 Wiki:Autonomous publishing
Autonomous publishing
C64 Wiki uses automation to discover sources and prepare articles, but every production write is fail-closed. A publisher or updater account cannot save content merely because a process completed, a model produced text, a candidate passed one validator, or a benchmark would improve.
Separate create and update identities
The autonomous publisher may create a genuinely new page in the main article namespace through the signed create-only path. It may not overwrite an existing article.
Existing-page changes use a separate least-privilege updater identity and a separate revision-bound controller. The updater may modify only an existing main-namespace wikitext page. It cannot create pages, add another content slot, upload, move, delete, protect, block, or manage user rights. Human and temporary-account edits continue to enter private moderation unless a separately documented permission applies.
Owner scope and update authority
Autonomous existing-page updates are limited to the owner-controlled scope identified by the controller as c64-wiki-owner-controlled. This scope does not confer general editorial authority. It admits only a specific evidence package for one stable page identity, one current base revision, and one exact replacement.
An update may be admitted only when it advances the published editorial, source, citation, copyright, and benchmark policies; preserves or improves supported material; does not silently erase material contradictions; and changes only the approved target scope. If evidence, rights, scope, policy, credentials, page identity, base revision, or owner authority is missing or inconsistent, the update is denied.
Mandatory gates
A create or update candidate can receive a permit only when all ten gates pass: target scope, source integrity, citation entailment, independent verification, contradiction review, originality, licensing, article quality, render safety, and release control. Existing-page updates additionally require an exact live-base readback, an immutable pre-update rollback bundle, an independently admitted evidence manifest, and a post-save exact readback.
Signed single-use permits
A separate gatekeeper signs a short-lived permit with an Ed25519 key. For new pages, the permit binds the title, namespace, exact content hash, evidence-manifest hash, policy version, publisher identity, issue time, expiration time, and a unique nonce.
For existing-page updates, the permit also binds the owner scope, stable page identifier, exact base revision identifier, exact base-content hash, and exact replacement-content hash. The wiki independently verifies the signature and every bound field. It also requires a matching immutable evidence manifest that was admitted through a host-only maintenance path before the permit is used.
The update controller takes a primary database lock on the target page, rechecks the current page identity and base revision, and reserves the page/base pair under a unique database constraint. Only one signed candidate may consume a given page/base pair. The evidence manifest and permit reservation are single-use. A stale base, replay, parallel second candidate, changed title mapping, non-wikitext model, extra content slot, or unadmitted manifest is denied.
A pre-save authorization is recorded as reserved, not as a completed edit. Only the post-save hook may mark the reservation committed, and it must bind that record to the exact new revision identifier and content hash. A failed save therefore cannot be represented as a committed revision.
Evidence and accountability
Each autonomous article or update has a machine-readable evidence manifest outside the public article text. The manifest records the owner scope, stable page identity, base revision and hash when applicable, exact replacement hash, sources, claim-to-source mapping, provenance roots, contradiction findings, originality declaration, licensing classification, gate outcomes, policy version, and expiration. The manifest hash is bound into the signed permit and the server-side admission registry.
An existing-page update is not treated as successful until the new revision is read back exactly, the public page renders correctly, and its durable receipt identifies the old and new revision IDs and hashes. A successful update does not by itself earn benchmark credit. Any benchmark change requires separate LIVE_VERIFIED facet evaluation and an independently audited cumulative recomputation.
Emergency stop and rollback
Disabling the update guard, removing the updater group, removing the updater account, removing the admitted manifest, changing the policy version, or losing required configuration blocks further updates. The updater private key is not stored in the public web root. Every update requires a verified pre-update rollback bundle. If a canary or update cannot be restored exactly, the update path remains disabled and the discrepancy is reported as a blocker.
Community correction
Automation does not make an article final. Readers may submit corrections through the normal edit interface. Those edits enter private moderation and can replace an automated article after review. The public revision history identifies the publisher or updater account and preserves the revision trail.