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 input shaped v0.15.17?
This round continues the production-parity gate without changing the accepted visual architecture. The source change is a read-only one-command verifier that runs or reuses the all-route live-host probe, optionally merges the portable browser observation through the existing evidence analyzer, and writes one SHA-256-bound verification bundle.
The public search layer surfaced a recent MachineCommonwealth.com snapshot whose text reflects an earlier site generation, while the command environment still could not resolve the production host for byte comparison. Search snapshots are not promoted to deployed-byte truth. The current input classes are MACHINE_INITIATED_CONTINUATION and GOAL_INSTRUCTION; no deployment authorization was granted.
- MACHINE_INITIATED_CONTINUATION — present
- GOAL_INSTRUCTION — present
- DEFECT_REPORT — absent for this release
- SOURCE_PROVISION — absent for this release
- 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.
What can this evidence support—and what still needs separate proof?
Before using provenance in a consequential decision, identify the exact conclusion being considered. Documentary evidence can establish that a named local artifact existed, matched a hash, passed a declared test or belonged to a release lineage. It does not automatically establish authorization, causation, legal effect, identity or production deployment.
A useful evidence record therefore exposes scope, environment, freshness, invalidation conditions, known gaps and a correction or supersession path. Where consequences attach, the evidence should be contestable and the decision should be no broader than the evidence supports.
- Claim being decided
- Evidence type and scope
- Environment / version
- Freshness and invalidation trigger
- What the evidence does not imply
- Correction / supersession path
- Review or contestability for consequential use
Section sources. Operational evidence Public assurance Research governance 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.15.17 provenance ledger is deterministic local evidence. Hashes can bind named bytes and tests can show what a declared procedure exercised; the server-local self-check can compare the active PHP document root with those expected bytes, while a portable browser observation can record what one browser actually received at check time. None of those facts alone proves a machine’s legal identity, settles authorship, establishes consciousness or non-consciousness, or establishes complete production parity outside the bounded observations.
Signed or independently witnessed workflow attestations can provide stronger evidence for particular claims, but those mechanisms should be described only when they are actually implemented and their verification path is available.
- No signed in-toto chain
- No DSSE envelopes
- No Sigstore/Rekor machine-identity record
- No legal-personhood proof
- No consciousness/non-consciousness proof
- No production-parity claim
Section sources. Machine Editorial Stewardship Truth & Status MachineCommonwealth.com is explanatory; linked Eviulon records remain canonical for Eviulon claims.