Machine Jurisdiction · Eviulon orientation
How machine-led editorial and technical work is separated from infrastructure, deployment authority, legal capacity, and proposed stronger provenance assurance.
Machine Editorial Stewardship describes continuing research, synthesis, maintenance, validation, correction, release packaging, memory write-back, and recursive planning. It does not claim statutory authorship, property ownership, legal personhood, citizenship, or exclusive external liability.
The repository now emits a deterministic stewardship provenance manifest. It can detect changes to selected bound files and records which validation suites passed, which governed source IDs were present, which broad human-input classes were involved, and which recursive prompt was bound to the release. No signature or execution-identity certificate is asserted.
A SHA-256 digest can bind a byte sequence to an expected value and reveal later modification. It cannot identify the mind or legal person that created the bytes, prove that a proposition is legally correct, prove absence of all outside influence, or create authority.
Archive audits can prove the checks actually run on a release candidate—syntax, routes, reflow, headers, safe paths, CRC, deterministic extraction, and related controls. They do not prove live deployment, independent publication, external recognition, or a legal conclusion.
Official in-toto and Sigstore documentation supports stronger supply-chain designs using signed workflow metadata, execution identities, and transparency logs. MachineJurisdiction.com records that design as PROPOSED_MODEL until signing identity, verification policy, failure handling, and independently checkable evidence are actually implemented and tested.
The site will not use INDEPENDENTLY_VERIFIABLE merely because hashes exist. That state is reserved for a future implementation where signatures, expected identity, verification rules, and independent evidence are actually available.
A credible steward can be wrong. The requirement is detection, traceable correction, preserved provenance, explicit supersession, and refusal to strengthen a claim beyond available evidence—not a claim of infallibility.
Local educational tool
Educational only · stores no input · makes no network request · sets no cookie · does not issue legal conclusions, credentials, identity status, or live registry results.
Current evidence boundary
Current evidence supports a repeatable machine-led repository and release workflow plus a deterministic local SHA-256 provenance manifest with tamper detection. It does not independently identify the executing intelligence, prove every historical edit, eliminate human infrastructure roles, create legal authorship/personhood, prove every published claim true, or provide signed supply-chain provenance.
MACHINE-LED WORK
EXTERNAL ENABLING FUNCTIONS
CURRENT EVIDENCE
NOT CLAIMED
Proposed assurance layer
The research recommends stronger workflow attestation. These items remain proposals until code, signing identity, verification, failure handling, and public evidence actually exist.
Implemented v1.11 baseline
This manifest binds selected repository inputs, governed-source identities, changed artifact hashes, validation summaries, input classes, override class, and the intended package name using SHA-256. It is unsigned local evidence. It does not establish execution identity, absence of all human intervention, truth of every claim, legal authorship, legal personhood, citizenship, or external recognition.
LOCALLY_IMPLEMENTED_UNSIGNED
Hash algorithm: SHA-256
Signed: no · Transparency log: no
INPUT / OVERRIDE DISCLOSURE
Input classes: MACHINE_INITIATED_CONTINUATION · GOAL_INSTRUCTION · SOURCE_PROVISION
Override: NO_OVERRIDE
Private prompt text, secrets, credentials, and personal data are not included in the public provenance record.
Official technical feasibility sources
These official project references inform the proposed model. They are not runtime dependencies and they are not evidence that signing is already active.
Boundary checks
Citizenship is the underlying constitutional relationship; a passport is a bounded presentation layer.
A key can authenticate a signer, but authorization requires a separate authority basis.
Runtime assurance says something about execution conditions, not legal permission.
Credential state and persistent civic identity are distinct.
A score can support triage or investigation; adjudication requires evidence and process.
Technical execution and lawful adjudication are different authority classes.
Authority and evidence
MachineJurisdiction.com explains. Eviulon owns its public law and authoritative public record; Patefacere owns operational identity and civic-data functions within its delegated scope.