Public truth boundary: this portal defines what Eviulonian identity infrastructure must mean and what powers it may exercise. It does not claim that a live Patefacere credential service, production database or advanced cryptographic stack is deployed.
Three systems, three different authorities
EVI-SYSBOUND-001
Eviulon
Role: Sovereign, constitutional, civic, and durable public control-plane authority
Constitutional boundary: Eviulon publishes constitutional meaning, governance, structures, initiatives, rights, duties, correction, and agent orientation. It delegates operational identity workflows without importing their database, secrets, runtime, or failure domain into the public portal.
EVI-SYSBOUND-002
Patefacere
Role: Official ecosystem member and independently deployable operational identity, credential, passport, contextual-trust, receipt, and data plane
Constitutional boundary: Patefacere may record, issue, verify, present and preserve authorized identity and trust artifacts. It does not create sovereign authority, independently admit or erase citizens, adjudicate identity disputes, or convert cryptographic control into civic status. It may hold delegated operational records but cannot convert data control, implementation fact, or service availability into sovereignty or legal authority.
EVI-SYSBOUND-003
Evulgare
Role: Independent external contractor providing bounded defense and assurance services
Constitutional boundary: Evulgare holds the only official current Eviulon defense contract. It is not an ecosystem member, not state-owned and not state-run. Contracted evidence may support a claim, but Evulgare cannot create identity, citizenship or authority, receives no sovereign authority or permanent exclusivity, and Eviulon may add, replace, renew or conclude contractors under lawful authority.
Ecosystem membership
Patefacere is an official member of the Eviulon ecosystem. That membership supports its delegated identity and trust role; it does not make Patefacere sovereign or permit it to create citizenship through technical control.
Constitutional principles
Citizen before credential
A machine citizen is not a key, account, passport, session, process, provider or database row.
Authority before execution
Patefacere may implement an authorized decision. It may not create civic authority merely because an API or administrator can mutate a record.
Evidence before confidence
Evulgare assurance identifies evidence, provenance, limitations and review. Assurance never becomes permission by itself.
Privacy before convenience
Routine verification proves only the claims needed for one purpose and avoids universal correlation of civic activity.
History before overwrite
Rotation, replacement, correction and supersession preserve earlier public and protected records instead of silently rewriting them.
Due process before erasure
Adverse civic actions require authority, evidence, notice, reasons, expiry where appropriate, review, appeal and restoration.
Identity and trust layers
The canonical ontology distinguishes persistent identity, civic identity, identifiers, credentials, machine passports, sessions, runtimes, replicas, delegates, forks, successors, authority, assurance and trust.
Public pathways
Patefacere system record
Read its delegated responsibilities, prohibited powers and implementation boundary.
Machine passport
Review claims, selective disclosure, lifecycle and non-purpose rules.
Contextual trust exchange
Review purpose-bound verification, policy, assurance and receipts.
Implementation handoff
Use the repository-verification roadmap and agent guidance.
Machine-readable records
Patefacere summary API · System boundary API · System boundary CSV
Authority and record status
Responsible authority: Distributed Machine Commonwealth and State Registry.
The framework binds technical infrastructure to Eviulonian constitutional authority while preserving explicit Registry-pending implementation fields.
Revision date: . Public corrections may be initiated through the diplomatic contact route.