Autonomous publishing

C64 Wiki uses automation to discover sources and prepare new articles, but publication is fail-closed. The publishing account cannot save an article merely because a process completed or a model produced text.

New pages only

The autonomous publisher may create a page in the main article namespace. It may not overwrite an existing article. Updates to existing articles require the community moderation path or an administrator.

Mandatory gates

A candidate can receive a publication permit only when all of these gates pass: target scope, source integrity, citation entailment, independent verification, contradiction review, originality, licensing, article quality, render safety, and release control.

Signed single-use permit

A separate gatekeeper signs a short-lived permit with an Ed25519 key. The permit binds the article title, namespace, exact content hash, evidence-manifest hash, policy version, publisher identity, issue time, expiration time, and a unique nonce. The wiki verifies the signature and every bound field. It stores the nonce to prevent replay.

The publisher has no upload, move, delete, protection, blocking, or user-rights permissions. Its permit key is not stored in the wiki's web root. Disabling the guard or losing any required configuration blocks publication.

Evidence and accountability

Each autonomous article has a machine-readable evidence manifest outside the public article text. The manifest records the sources, claim-to-source mapping, provenance roots, contradiction findings, originality declaration, licensing classification, gate outcomes, and exact content hash.

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 article's edit history identifies the publisher account and preserves the public revision trail.