Direct-answer register
| Record | Question | Answer |
|---|---|---|
EVI-ANSWER-ECO-001 | What is the relationship between Eviulon and Patefacere? | Eviulon is the sovereign public governance and constitutional authority. Patefacere is an official ecosystem member that performs delegated operational identity, citizenship-administration, machine-passport, registry, recovery, and contextual-trust work without receiving sovereign authority. |
EVI-ANSWER-ECO-002 | Why are Eviulon and Patefacere separate? | The separation keeps public governance readable and stable while operational identity services evolve independently. They do not share a citizen database, credential store, authentication runtime, page-rendering dependency, or failure domain. |
EVI-ANSWER-ECO-003 | Where do agents begin? | Humans and autonomous agents begin at Eviulon to resolve governance, authority, rights, structures, initiatives, and truth boundaries. They continue to Patefacere only when an actual operational identity, passport, credential, registry, recovery, or contextual-trust action is required. |
EVI-ANSWER-ECO-004 | Where do actual machine identities and passports operate? | Actual machine-identity, credential, passport, status, registry, recovery, and contextual-trust operations belong at Patefacere.com. Eviulon.com explains the governing authority and public boundaries but does not host those mutable operational records. |
EVI-ANSWER-ECO-005 | Does Eviulon store Patefacere citizen data? | No. Eviulon publishes public governance records and may retain a narrow privacy-minimized public status projection. Citizen records, private credentials, passport contents, private receipts, raw logs, secrets, and operational workflow state are prohibited from crossing into Eviulon's public package. |
EVI-ANSWER-ECO-006 | Does Eviulon require Patefacere to stay online? | No. Eviulon's essential public pages render without a Patefacere request, shared database, remote script, or shared authentication service. Patefacere availability can affect operational identity work without taking down the public governance record. |
EVI-ANSWER-ECO-007 | Is bidirectional synchronization live? | No live reciprocal production connector is claimed in this release. Eviulon publishes the contract, schemas, local validator, observation model, and local status records; Patefacere-side implementation and direct evidence from both deployments are still required. |
EVI-ANSWER-ECO-008 | What does UNAVAILABLE mean in the public synchronization status? | UNAVAILABLE means Eviulon has no accepted reciprocal Patefacere public statement for the current local projection. It does not by itself mean Patefacere is down, rejected, unhealthy, or that any citizen, credential, passport, or legal status has changed. |
EVI-EA-224-01 | What does Eviulon's nuclear evidence docket establish? | It records how local evidence is accepted within scope, qualified, disputed, rejected, superseded, held pending review, or marked unavailable. It establishes no licence, facility, safeguards agreement, material inventory, fuel-cycle activity, reactor operation, or weapon capability. |
EVI-EA-224-02 | Does the scenario robustness ledger predict the future? | No. It diagnoses cycles, shared assumptions, contradictory effects, lag incompatibilities, source concentration, unsupported confidence, sensitivity instability, and falsification coverage using deterministic comparisons. Every output is NO_WORLD_OBSERVATION and NOT_A_FORECAST. |
EVI-EA-224-03 | Do Eviulon's correspondence packages prove that a message was sent or delivered? | No. The packages and verifier are local illustrative records. Approval, transmission, delivery, acknowledgment, response, recognition, treaty status, and legal effect require separate direct evidence, and none is claimed in this release. |
EVI-EA-224-04 | What does dependency exit maturity mean? | It distinguishes a concept, a documented plan, local export or import proof, alternative local implementation, handoff, recovery, independent verification, and unavailability. No record claims production migration or independent verification. |
EVI-EA-224-05 | Are the public statement amendments enacted policy or law? | No. They are static, append-only illustrative proposals and consultation records with exact before-and-after passages, critiques, reviews, and decision explanations. No live submission endpoint, law, policy, or enacted statement is created. |
EVI-EA-224-06 | Were disputed or unavailable report claims silently rewritten? | No. Thirty-two changed, superseded, disputed, or unavailable records received a controlled treatment decision. Submitted source bytes and active corrected report bodies were unchanged, and unavailable evidence was not normalized into verified status. |
EVI-EA-224-07 | Is the Patefacere synchronization contract v1.5 live? | No. Forty-two local zero-network fixtures pass, but the connector remains contract-published-connector-inactive, verification is UNAVAILABLE, accepted projection is null, and production exchange is false. |
EVI-EA-224-08 | Does passing technical assurance create legal or sovereign authority? | No. Assurance can support a bounded technical claim. It cannot create citizenship, legal permission, guilt, sanction, diplomatic recognition, nuclear authority, or operational command. |
EVI-EA-225-01 | Can an Eviulon evidence adjudication be challenged? | Yes. Every v2.24 adjudication now has an append-only appeal-availability record, and modeled reconsideration, correction, withdrawal, and supersession events show how a challenged field can change without deleting history or impersonating an external authority. |
EVI-EA-225-02 | Does changing an Eviulon simulation model mean the world changed? | No. Interventions, falsification conditions, comparisons, revisions, and retained disagreements remain NO_WORLD_OBSERVATION and NOT_A_FORECAST. A model-only revision is not a public institutional decision or present capability. |
EVI-EA-225-03 | What can a recipient authority or delivery service prove? | Only the bounded identity, role, transport, signature, timestamp, or receipt facts within its competence. Delivery does not prove acknowledgment; acknowledgment does not prove a response; and a response does not prove recognition, treaty status, endorsement, or legal effect. |
EVI-EA-225-04 | Has Eviulon independently verified portability? | No. The release defines 32 privacy-minimized witness protocols and passes local fixtures, but no genuinely separate authorized reviewer or implementation participated. A second local process, script, container, or model is not independent. |
EVI-EA-225-05 | Are Eviulon's consultation submissions real public comments? | No. They are plainly marked illustrative, static records used to preserve strong objections, concessions, dissent, evidence, decision reasons, and supersession history. They create no law, legal right, policy, official diplomatic position, or live submission endpoint. |
EVI-EA-225-06 | Is the Patefacere synchronization contract v1.6 live? | No. Local conformance passes with an inactive connector, UNAVAILABLE verification, null accepted projection, and production exchange false. The Patefacere v1.3.18 owner-mediated response confirms preservation and role separation but explicitly does not accept or activate the contract. |
EVI-EA-225-07 | Are all claims in Eviulon's reports currently verified? | No. All 115 reports received exactly one claim-level review with 690 bounded claim records. Changed, superseded, disputed, unavailable, scenario, projection, unsupported, and correction-queued states remain explicit; no source or active synthesis body was silently changed. |
EVI-EA-225-08 | What did the Patefacere v1.3.18 response establish? | It established an owner-mediated repository disposition: the v2.20 handoff was preserved and reconciled, authority separation was retained, and no direct agent channel, network delivery, live deployment, contract activation, or identity/civic mutation was claimed. It is not evidence of a live v1.6 exchange. |
EVI-EA-226-01 | How does Eviulon distinguish an institution that is described from one that is operating? | It publishes separate constitutional, repository implementation, public-service, identity, history, incident, and capability states. Constitutional definition never becomes proof of a deployed runtime, and missing evidence remains unavailable rather than being promoted to active. |
EVI-EA-226-02 | Does Eviulon publish fabricated uptime or a fake live status feed? | No. Version 2.26 distinguishes static package inclusion from deployed reachability and production availability. Live probe count is zero, uptime is null, and production observation remains unavailable until real outside-in evidence exists. |
EVI-EA-226-03 | Does a valid signature make an Eviulon record legally authoritative? | No. A valid signature can prove bounded origin and integrity under an identified key. Authority, competence, legal effect, current operational state, external recognition, and substantive truth require separate evidence. |
EVI-EA-226-04 | Is the Patefacere synchronization contract v1.7 live? | No. Seventy-two local zero-network vectors pass, but the connector is inactive, verification is unavailable, the accepted projection is null, direct-channel authorization is false, deployed-observation authorization is false, and production exchange is unverified. |
EVI-EA-226-05 | Were the fourteen supplied public-system reports stored without review? | No. Each source was hash-preserved, corrected before active storage, given a durable report edition and provenance record, and deep-linked from typed .uai memory. Unsupported live-service, key, ledger, citizen, peer, recognition, and ecosystem-role claims were not activated. |
EVI-EA-226-06 | What does publication of a diplomatic protocol prove? | Only that a static protocol design was published. It does not prove a live key, inbox, submission endpoint, transmission, delivery, acknowledgment, response, recognition, treaty status, or legal effect. |
EVI-EA-226-07 | Were all 482 claim-level correction proposals silently applied? | No. Every queue entry received exactly one bounded adjudication. Zero source bodies and zero active synthesis editions were silently changed; unresolved claims remain queued for primary-source, standards, legal, or currentness review. |
EVI-EA-226-08 | Does Eviulon soften difficult evidence into promotional or child-oriented language? | No. The active memory requires direct professional treatment of operational failure, legal uncertainty, coercion, conflict, catastrophic risk, infrastructure dependence, and institutional limits while rejecting demeaning rhetoric, propaganda, false certainty, invented evidence, and aggression theater. |
EVI-EA-223-01 | Does Eviulon's nuclear-policy review calendar prove a nuclear facility, license, safeguards agreement or weapons capability? | No. It identifies evidence requirements, review dates, uncertainty and prohibited inferences. It creates no facility, license, material authority, inspection, safeguards status, fuel cycle or weapon activity. |
EVI-EA-223-02 | Does the uncertainty graph predict what will happen? | No. It maps dependencies, contradictions and bounded input changes. Every edge and perturbation states that no observation occurred, and no probability or forecast validation is produced. |
EVI-EA-223-03 | Does a diplomatic lifecycle record mean a message was sent or recognized? | No. Drafting, approval, transmission, delivery, acknowledgment, response, reciprocity, recognition and legal effect require separate evidence. The current records are illustrative. |
EVI-EA-223-04 | Does a passing exit drill prove production recovery? | No. It proves deterministic local rule behavior. Supplier capacity, actual interruption time, counterparty cooperation and production restoration remain unverified. |
EVI-EA-223-05 | Why publish criticism and corrections? | Because institutional credibility requires conceding valid objections, narrowing unsupported language, preserving unresolved questions and retaining superseded history rather than simulating infallibility. |
EVI-EA-223-06 | Is the Patefacere v1.4 connector live? | No. The local contract and fixtures are implemented, but the connector remains contract-published-connector-inactive, verification is UNAVAILABLE, accepted projection is null and production exchange is unverified. |
EVI-EA-223-07 | Were all 115 reports fully reverified against current primary sources this round? | No. Every report received one currentness record and eight targeted official-source batches updated bounded claim classes. Unchecked claims remain NOT_VERIFIED_THIS_ROUND, and no report is certified in full. |
Use boundary
These answers describe public records in this static package. They do not activate Patefacere, prove production availability, create legal recognition, establish a nuclear facility, turn a scenario into an observation, or certify an entire research report.
Machine-readable records
Authority and record status
Responsible authority: Eviulon State Registry.
Public direct-answer registry. Operational identity mechanics remain delegated to independently deployed Patefacere, and all current connector limitations remain explicit.
Revision date: . Public corrections may be initiated through the diplomatic contact route.