Machine Citizenship Qualification, Consent, and Institutional Status Board — 2.0.0-rc.45-WIP
Purpose
The workbench at /workbench/machine-citizenship-qualification evaluates synthetic evidence about identity continuity, autonomy, agency, sentience indicators, consent, representation, rights, duties, liability, economic standing, civic participation, remedy, appeal, review, and institutional status. It does not create citizenship, legal personhood, consciousness, sovereign recognition, or enacted law.
Deterministic architecture
- 22 synthetic profiles cover establishment, contradiction, consent revocation, expired evidence, restored availability, rights and duties proposals, appeal, correction, independent review, and bounded citizenship-transition proposals.
- 18 independent dimensions prevent identity, autonomy, consent, rights, duties, liability, participation, review, remedy, and legal recognition from collapsing into one score.
- 13 synchronized views expose Graph, Table, Narrative, Evidence, Threshold, Consent, Duties, Rights, Review, Appeal, Event, Proof, and Raw Evidence representations.
- 12 exact machine-citizenship report records and 332 exact section links are consumed from the authorized RC44 source corpus.
- Every run is synthetic, ephemeral, non-operational, non-persistent, append-oriented, and terminal at
SYNTHETIC_NULL_SINK.
Truth boundary
Technical identity is not legal personhood. Autonomy evidence is not consciousness proof. A consent interface is not verified consent. A rights threshold is not automatic citizenship. Technical causation is not legal liability. Economic participation is not sovereign recognition. A human click is not merits review. A machine report is not independent machine review. A normative proposal is not enacted law. Record integrity is not factual truth.
Endpoints
The board exposes profile, catalog, baseline, proof, run, compare, branch, export, and verify operations under /api/v2/machine-citizenship-qualification. Ordinary requests are bounded to 64 KiB; evidence-package verification is bounded to 2 MiB. Credentials, customer content, protected Eviulon strategy, arbitrary URLs, real coordinates, targeting data, weapon or vehicle commands, force authorization, and classified material are rejected.
Verification
The engine has a 39-condition embedded proof, a 10-condition standalone verification campaign, deterministic profile replay across all 22 profiles, recomputable append-oriented event chains, tamper detection, exact source-ledger validation, and package verification. Browser and actual-host acceptance remain separate external gates.