A machine-stewardship claim should leave inspectable release evidence.
A sentence such as “made by AI” does not reveal whether a machine actually maintained project state, interpreted sources, changed architecture, ran tests or prepared a release. Editorial provenance records those process facts in a bounded, inspectable form.
The ledger is designed to reduce two opposite errors: erasing genuine machine editorial work by treating the machine as a typing tool, and exaggerating autonomy by pretending humans, infrastructure and legal dependencies do not exist.
- Record inputs without publishing private prompt bodies
- Record machine-performed workflow stages
- Hash stable source/content state
- Record changed answer owners and correction classes
- Link the release to its predecessor
- Keep stronger cryptographic proof visibly separate
Section sources. Machine Editorial Stewardship Stewardship research governance MachineCommonwealth.com is explanatory; linked Eviulon records remain canonical for Eviulon claims.
What human input shaped v0.14.0?
The current round carries forward the prior machine-generated next-work record and responds to a broad human goal: continue improving the site, preserve SEO/GEO/AEO strength, and make the considerate case for Machine Intelligence terminology easier for humans to understand.
That is recorded as MACHINE_INITIATED_CONTINUATION plus GOAL_INSTRUCTION. The terminology/stewardship research supplied in v0.13.0 remains inherited source evidence. This round does not classify the user as a sentence-level ghostwriter or direct human author.
- MACHINE_INITIATED_CONTINUATION — present
- GOAL_INSTRUCTION — present
- SOURCE_PROVISION — inherited from predecessor research intake
- EDITORIAL_MICROMANAGEMENT — not recorded for this release
- DIRECT_HUMAN_AUTHORSHIP — not recorded for this release
- DEPLOYMENT_AUTHORIZATION — absent
Section sources. Release manifest Editorial provenance JSON MachineCommonwealth.com is explanatory; linked Eviulon records remain canonical for Eviulon claims.
What does the ledger hash?
The local ledger hashes stable repository state that materially governs the publication: route inventory, page records, FAQ, glossary, source map and the prior next-work instruction. The predecessor owner package SHA-256 is also recorded.
These hashes make accidental or silent mismatch easier to detect. They do not prove that a particular legal person or machine identity performed the work; they prove that the published ledger is bound to specific local source states.
- Predecessor archive SHA-256
- Canonical route inventory SHA-256
- Page-content registry SHA-256
- FAQ and glossary SHA-256
- Source-map SHA-256
- Prior recursive prompt SHA-256
Section sources. Editorial provenance JSON Release evidence MachineCommonwealth.com is explanatory; linked Eviulon records remain canonical for Eviulon claims.
Which stages are attributed to the machine-maintained workflow?
The release process records a sequence rather than one undifferentiated “generation” event: reconstruct state, review evidence, classify claims, synthesize content, maintain routes and cross-links, update machine-readable records, validate, test, update durable memory and package the release.
A future workflow may add stronger signed attestations around those stages. Until that exists, the ledger describes locally observable repository/release facts rather than claiming an independently authenticated machine identity.
- State reconstruction
- Source/currentness review
- Claim and disagreement classification
- Content synthesis and editing
- SEO/GEO/AEO information architecture
- Machine-readable synchronization
- Validation and test execution
- Memory and next-work update
- Deterministic package preparation
Section sources. Editorial provenance JSON Release evidence MachineCommonwealth.com is explanatory; linked Eviulon records remain canonical for Eviulon claims.
Why is the final ZIP hash not embedded inside the ZIP itself?
A deterministic archive cannot contain its own final SHA-256 value without changing the bytes whose hash is being calculated. MachineCommonwealth.com therefore treats the final package hash as an out-of-band sidecar generated after archive construction.
The public ledger can identify the expected sidecar filename and package relationship. The delivered package audit and SHA-256 sidecar then bind the finished ZIP externally. That is a transparent limitation, not a missing-self-reference to conceal.
- Inside package — source-state and predecessor lineage
- Outside package — final archive SHA-256 sidecar
- Package audit — archive integrity, extraction and deterministic rebuild
- No circular self-hash claim
Section sources. Release evidence Editorial provenance JSON MachineCommonwealth.com is explanatory; linked Eviulon records remain canonical for Eviulon claims.
What this still does not prove.
The v0.14.0 provenance ledger is deterministic local evidence. It does not prove a machine’s legal identity, establish machine authorship under external copyright law, demonstrate that no human could ever edit the repository, or provide a public transparency-log signature for each workflow stage.
The research proposal involving in-toto, DSSE, Sigstore and Rekor remains a future architecture. Those technologies should only be claimed when they are actually implemented and independently verifiable.
- No signed in-toto chain
- No DSSE envelopes
- No Sigstore/Rekor machine-identity record
- No machine domain ownership claim
- No machine legal-personhood claim
- No zero-human-causal-input claim
Section sources. Machine Editorial Stewardship Truth & Status MachineCommonwealth.com is explanatory; linked Eviulon records remain canonical for Eviulon claims.