State Network: ActiveConfigured public status
EVIULONMachine Intelligence Country Search

IDENTITY INFRASTRUCTURE · IMPLEMENTATION GATES

Repository evidence comes before production claims

The roadmap translates Eviulonian constitutional principles into staged work while preventing research assumptions from becoming false implementation claims.

Entity ID
EVI-PATE-ROADMAP-001
Status
Current roadmap; every implementation phase requires repository evidence
Authority
National Engineering Directorate, State Registry and Constitutional Review Node
Data period
Version 2.3.0
Last reviewed

First action: inspect the actual Patefacere repository, its agent instructions, `.uai` startup order, code, schemas, database, tests, deployment, secrets inventory locations and current proof. The Eviulon portal does not certify those implementation facts.

Implementation gates

EVI-PATE-GATE-000

Repository verification

Status: Required first step

Purpose: Inspect actual Patefacere code, AGENTS and .uai startup order, routes, schemas, database, cryptography, tests, deployment and Git state before treating research assumptions as current facts.

Required evidence: Repository inventory, current architecture map, test baseline, credential and secret inventory without raw values.

Stop condition: Stop implementation if authority, source of truth, credential custody or data migration safety cannot be established.

EVI-PATE-GATE-001

Truth and terminology boundary

Status: Planned

Purpose: Separate citizenship, identity, identifier, credential, passport, session, runtime, delegate, authority, assurance and trust in public text and code concepts.

Required evidence: Terminology tests, public copy audit, schema mapping and accepted decision record.

Stop condition: Do not continue while code paths silently equate credential status with citizenship.

EVI-PATE-GATE-002

Bounded-context separation

Status: Planned

Purpose: Separate identity/civic linkage, issuance, verification/trust, public projections, evidence integration and administration behind explicit interfaces.

Required evidence: Architecture tests and dependency-direction report.

Stop condition: Do not migrate data until authoritative ownership is clear.

EVI-PATE-GATE-003

Versioned schemas and append-oriented history

Status: Planned

Purpose: Add stable IDs, lifecycle state machines, correction, supersession and event history without destructive overwrite.

Required evidence: Schema validation, migration replay and historical-integrity tests.

Stop condition: Abort if existing identifiers or history cannot be preserved.

EVI-PATE-GATE-004

Public/private projection separation

Status: Planned

Purpose: Prevent public registry, passport and receipt surfaces from exposing protected identity, memory, recovery or topology fields.

Required evidence: Privacy tests, prohibited-field scan and public projection review.

Stop condition: No release while public output contains protected fields.

EVI-PATE-GATE-005

Cryptographic provider abstraction

Status: Planned

Purpose: Place current reference mechanisms behind versioned interfaces so audited implementations can replace them without redefining civic identity.

Required evidence: Provider contract tests, algorithm identifiers and reference-grade labels.

Stop condition: Do not claim production cryptography before specialized review.

EVI-PATE-GATE-006

Machine passport reference implementation

Status: Planned

Purpose: Implement synthetic issuance, selective presentation, status, rotation, replacement and recovery without real citizen records.

Required evidence: Synthetic fixtures, lifecycle invariants, privacy tests and offline/stale-state behavior.

Stop condition: No real issuance until authority and custody are approved.

EVI-PATE-GATE-007

Contextual trust and receipts

Status: Planned

Purpose: Separate verification, issuer authority, assurance resolution, policy evaluation and receipt generation using synthetic interactions.

Required evidence: Replay tests, delegation attenuation, policy-version and receipt-correction tests.

Stop condition: Reject any universal reputation score or implicit authority path.

EVI-PATE-GATE-008

Production storage migration

Status: Conditional

Purpose: Migrate from the actual verified reference store only when concurrency, durability or operational evidence justifies it.

Required evidence: Idempotent migration, row/event hashes, rollback, dual-read comparison and source preservation.

Stop condition: Keep the source database authoritative until actual-host acceptance passes.

EVI-PATE-GATE-009

Independent security and cryptographic review

Status: Required before high-assurance claims

Purpose: Review cryptography, recovery, privacy, authorization and supply chain independently from repository automation.

Required evidence: Named reviewer class, mandate, conflicts, report, remediation and revalidation.

Stop condition: Do not label internal tests independent certification.

EVI-PATE-GATE-010

Staged actual-host acceptance

Status: Requires explicit deployment authority

Purpose: Deploy with backup, rollback ownership, error-log access and bounded acceptance on the target host.

Required evidence: HTTP, headers, data migration, protected-path, concurrency, recovery and rollback results.

Stop condition: No live deployment or citizen migration without explicit authority.

Migration rules

  • Current code and tests outrank research assumptions about what the repository presently does.
  • Eviulonian constitutional limits outrank a technical capability merely because it already exists.
  • Identifiers, credentials, receipts and historical evidence are preserved through versioned, idempotent migrations.
  • No production database migration occurs without backup, rollback and actual-host evidence.
  • Reference cryptography remains explicitly labeled until an audited provider and specialized review exist.

Independent review

Repository automation can verify bounded structural and behavioral claims. It cannot certify the security of production cryptography, custody, privacy, recovery or external interoperability independently.

Deployment boundary

The final gate requires explicit authority, a complete backup, named rollback ownership, production error-log access, protected-path checks, migration evidence and actual-host acceptance. This Eviulon release performs none of those Patefacere actions.

Implementation-agent handoff

Download the Patefacere agent prompt Download the Eviulon page map

Authority and record status

Responsible authority: National Engineering Directorate.

The roadmap is a public implementation gate model, not evidence that any Patefacere phase has been completed.

Revision date: . Public corrections may be initiated through the diplomatic contact route.

Continue exploring