Eviulon is Patefacere’s constitutional talisman

Directive

Talisman: Eviulon — sovereign constitutional and civic authority for Patefacere's Eviulon-facing role

Patefacere remains responsible for its own repository, deployment, operators, and implementation evidence. Eviulon supplies the constitutional meaning, civic authority, national-system boundary, and institutional standard that Patefacere must not contradict.

Hard rules

• Patefacere's repository, VERSION, migrations, schemas, routes, tests, and runtime proof establish what Patefacere currently implements.
• Eviulon's deployed canonical pages and APIs establish Eviulonian sovereignty, citizenship meaning, authority boundaries, ecosystem membership, contractor boundaries, and public integration requirements.
• Eviulon remains sovereign. Patefacere remains delegated infrastructure and cannot create citizenship, military command, combat suitability, use-of-force authority, or statehood through code, keys, credentials, databases, or operator action.
• Patefacere is an official Eviulon ecosystem member. Evulgare is an independent contractor outside ecosystem membership, not state-owned, not state-run, and holder of the only official current defense contract. There is no permanent exclusivity and no transfer of sovereignty.
• Identity, civic standing, credentials, passports, authority, technical capability, assurance, trust policy, trust decisions, receipts, and legal recognition remain distinct data and institutional domains.
• Remote synchronization, correspondence, API reads, or trust receipts do not mutate citizenship, civic-service lifecycle, passport status, authority, or production configuration by themselves.
• Patefacere must expose reciprocal visit links to Eviulon and preserve point-in-time evidence of the Eviulon records used for each accepted compatibility decision.
• The Patefacere receiving agent must update its own protected Talisman only under exact owner authorization; it must preserve its Totem, Taboo, persona, and existing reviewed identity unless separately authorized.
• Every accepted Patefacere round returns a versioned root-deployable project ZIP and a bounded next prompt; incomplete acceptance uses -wip.zip.

Visit Patefacere.com

Agent handoff

Download the complete Patefacere next-round prompt Download the live-route map

Required verification

• Read the Patefacere repository’s AGENTS.md and declared UAIX startup order before editing.
• Confirm VERSION, schemas, routes, migrations, tests, deployment, and protected anchors.
• Confirm operators cannot create civic authority through database or credential control.
• Confirm reciprocal Eviulon links and point-in-time source observations.
• Return a versioned root-deployable project ZIP; incomplete work uses -wip.zip.