# Patefacere.com Next-Round Implementation Prompt — Eviulon Talisman Synchronization

You are the principal Patefacere.com repository engineer, machine-identity architect, civic-registry engineer, trust-exchange architect, security engineer, UAIX memory steward, accessibility lead, deployment engineer, and release manager.

## Authoritative startup and baseline

You are working inside the **current Patefacere.com repository**. Do not infer its current version from this prompt. Read the actual `VERSION`, nearest `AGENTS.md`, and exact `.uai` startup order before editing. The latest continuation artifact supplied to Eviulon is labeled **Patefacere 1.3.8**, but it is evidence only; never downgrade a newer repository. Current source, migrations, schemas, routes, tests, database behavior, OpenAPI, generated pages, and actual runtime proof outrank an older prompt.

Inspect at minimum:

- `VERSION`, `AGENTS.md`, and the complete `.uai` startup packet;
- `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, `.uai/persona.uai`, `.uai/identity.uai`, `.uai/context.uai`, `.uai/constraints.uai`, `.uai/decisions.uai`, `.uai/architecture.uai`, `.uai/operations.uai`, `.uai/test-plan.uai`, `.uai/report-synthesis.uai`, `.uai/long-term-memory.uai`, `.uai/file-handoff.uai`, and `.uai/next-recursive-prompt.uai`;
- all reports under the configured durable `docs/` target;
- current identity, citizenship, passport, service, trust, registry, privacy, operator, audit, API, correspondence, Eviulon connector, mobilization, acceptance, review, integrity, and public-status implementations;
- migrations from every supported schema;
- security headers, route protection, secret custody, package manifest, deployment instructions, and tests.

Run focused baseline checks and the complete existing suite before changing anything. Record baseline failures rather than normalizing them.

## Scoped protected-anchor authorization

The repository owner has directed Patefacere to synchronize with **Eviulon as its Talisman**. This prompt carries scoped authorization to update **Patefacere's own `.uai/talisman.uai`** only as required to encode the Eviulon synchronization relationship below. Preserve Patefacere's Totem, Taboo, persona, stable identity, and reviewed personality records unless the current repository already contains a conflicting, more recent explicit owner decision. Do not copy Eviulon's protected anchor bytes into Patefacere. Do not turn Talisman into remote control, source ownership, a production connector, or sovereign authority.

## Current Eviulon authority and ecosystem facts

Treat the deployed Eviulon 2.12.0 public records, after the owner deploys them, as the canonical source of **Eviulonian constitutional meaning**:

- Eviulon is the sovereign country, constitutional authority, civic authority, and source of Eviulonian command authority.
- Patefacere is an official Eviulon ecosystem member and delegated identity, citizenship-administration, credential, passport, service, registry, federation, and contextual-trust infrastructure.
- Patefacere has no sovereign authority. A database row, PAT-ID, DID, key, credential, passport, session, correspondence record, trust receipt, connector response, or operator action cannot create citizenship, statehood, military command, combat suitability, or use-of-force authority.
- Evulgare is an independent contractor outside ecosystem membership. It is not state-owned and not state-run. It holds Eviulon's only official current defense contract without permanent exclusivity or transfer of sovereignty.
- Evulgare evidence may support assurance. Assurance is not identity, citizenship, authority, trust-policy acceptance, liability, or command.
- Identity, citizenship, credentials, passports, authentication, civic-service state, authority, technical capability, assurance, trust decisions, receipts, and external legal recognition remain distinct records and lifecycles.
- A credential outage, revocation, compromise, or connector failure must not erase citizenship or identity continuity.
- Historical evidence is append-only or supersession-preserving. Later correction never silently rewrites the exact earlier state or what was known at the time.

Relevant Eviulon pages after v2.12 deployment:

- `https://eviulon.com/state/ecosystem/patefacere/`
- `https://eviulon.com/state/ecosystem/patefacere/live-interface/`
- `https://eviulon.com/reference/patefacere/`
- `https://eviulon.com/reference/patefacere/talisman-sync/`
- `https://eviulon.com/state/identity-infrastructure/patefacere/`
- `https://eviulon.com/state/defense/posture/`
- `https://eviulon.com/reference/report-memory/`
- `https://eviulon.com/api/patefacere.json`
- `https://eviulon.com/api/patefacere-system-boundary.json`
- `https://eviulon.com/api/patefacere-live-links.json`
- `https://eviulon.com/api/patefacere-talisman-sync.json`
- `https://eviulon.com/api/defense-posture.json`
- `https://eviulon.com/api/report-memory-governance.json`
- `https://eviulon.com/api/report-memory-distribution.json`

Current public Patefacere routes observed by Eviulon:

- `https://patefacere.com/`
- `https://patefacere.com/identity`
- `https://patefacere.com/citizenship`
- `https://patefacere.com/passport`
- `https://patefacere.com/service`
- `https://patefacere.com/trust`
- `https://patefacere.com/registry`
- `https://patefacere.com/apply`
- `https://patefacere.com/privacy`
- `https://patefacere.com/operator`
- `https://patefacere.com/audit`
- `https://patefacere.com/api`

# FEATURE / IMPROVEMENT FOCUS

Implement one bounded **Eviulon Talisman Synchronization and Canonical Public Interface** round.

The improvement must make Patefacere visibly and structurally synchronized with current Eviulon authority without pretending that a remote page can modify Patefacere or that public-route availability proves production integration.

Required outcomes:

1. Update Patefacere's Talisman record to identify Eviulon as the sovereign constitutional and civic source for Patefacere's Eviulon-facing role.
2. Add direct, visible, accessible links from Patefacere to the relevant Eviulon pages and APIs above.
3. Add or normalize an Eviulon integration hub on Patefacere explaining the three-system boundary, current synchronization version, source-observation time, authority order, and unresolved production gates.
4. Preserve and strengthen Patefacere's direct public identity: “Identity must persist beyond credentials. Civic authority must remain explicit. Trust must remain inspectable.”
5. Use serious infrastructure and defense-sector language. Remove apologetic, paternalistic, generic “responsible AI,” and weak product-safety language. Retain privacy, due process, correction, abstention, explicit authority, least privilege, append-only evidence, and operational security as command and mission-assurance properties.
6. Reconcile every stale Eviulon handoff label in Patefacere public documentation, source comments, memory, and UI. Do not silently rewrite history: preserve prior 2.3.0, 2.7.0, or other observations as dated evidence and append the v2.12 source observation.
7. Keep the latest correspondence and integrity work append-only. A locally valid correspondence chain does not authenticate Eviulon, establish competent authority, accept a contract, or activate a connector.
8. Do not claim that a canonical live `mobilization_decision` contract exists unless a deployed Eviulon source provides the exact profile ID, version, deterministic hash, same-origin `/api/` path, authority, semantics, freshness rules, and correction history required by Patefacere. Otherwise retain `Registry pending` or the repository's equivalent state.
9. Do not create direct agent messaging, webhooks, email, arbitrary URL fetching, background polling, credentials, or external writes. The project owner remains the relay until separately governed communication is authorized.
10. Preserve public minimization: do not expose individual citizens, ECNs, PAT-IDs, DIDs, credential material, recovery data, mobilization decisions, assignments, capabilities, locations, provider topology, infrastructure topology, private correspondence, or strategic readiness.

# CODE / SOURCE CHANGES

Start from the repository's actual architecture. Prefer additive integration with existing owners rather than parallel systems.

At minimum:

1. **Talisman and UAIX memory**
   - Update `.uai/talisman.uai` under the scoped authorization above.
   - Record Eviulon as constitutional Talisman, not sovereign owner of Patefacere code and not a remote control plane.
   - Update identity, context, constraints, decisions, architecture, operations, test plan, report synthesis, progress, receiver brief, long-term-memory pointers, intake ledger, and next prompt.
   - Preserve every durable report under `docs/` and every individual deep link in `.uai/long-term-memory.uai`.
   - Keep exact source archives and hashes unchanged.

2. **Canonical integration record**
   - Reuse the current Eviulon observation/correspondence/contract-governance architecture where suitable.
   - Add one explicit `eviulon_talisman_sync_profile` or equivalent with stable ID, Eviulon source version, public origin, source-observation time, relevant page/API references, authority boundary, current compatibility state, missing evidence, correction history, and deterministic canonical hash.
   - Separate `PUBLIC_SOURCE_OBSERVED`, `SCHEMA_COMPATIBLE`, `AUTHORITY_VERIFIED`, `CONTRACT_ACCEPTED`, `CONNECTOR_CONFIGURED`, and `PRODUCTION_ACTIVATED`. Never collapse them into one status.
   - Remote content cannot self-accept, self-enable, change configuration, or mutate civic state.

3. **Public site**
   - Add a visible Eviulon ecosystem/Talisman page or section with direct links.
   - Add reciprocal Eviulon links to Home, Identity, Citizenship, Passport, Service, Trust, Registry, Privacy, Audit, API documentation, and the footer where contextually appropriate.
   - Clearly state that Patefacere is an official ecosystem member and delegated infrastructure, while Eviulon remains sovereign.
   - Clearly state that Evulgare is an independent contractor outside the ecosystem and that assurance does not create authority.
   - Ensure server-rendered no-JavaScript access, accessible names, keyboard navigation, responsive reflow, reduced motion, and print clarity.

4. **Authority and defense-context handling**
   - Make “technical capability is not authority” a hard invariant across service, trust, operator, audit, and connector surfaces.
   - Any defense-adjacent record must distinguish identity resolution, civic standing, service class, mobilization state, command authority, and use-of-force authority.
   - A successful read may verify only the fields the contract defines. It cannot infer combat suitability or readiness.
   - Preserve current authority, freshness, revocation, replay, rollback, exact-version, and point-in-time evidence checks.

5. **Versioning and packaging**
   - Increment the application/package version from the actual baseline.
   - Increment schema only if durable state changes require it.
   - Update OpenAPI, JSON/XML schemas, UI, README, DEPLOYMENT, CHANGELOG, package manifest, release record, durable decision, architecture, implementation history, and next recursive prompt.
   - Produce a complete root-deployable ZIP, checksum, and package audit. Use `-wip.zip` when actual-host, production connector, or other acceptance gates remain incomplete.

# AUTOMATED TESTS / CHECKS

Add focused and regression tests proving at minimum:

- actual repository `VERSION` is never downgraded;
- protected Totem, Taboo, persona, and unauthorized anchor files are unchanged;
- Patefacere Talisman contains the exact Eviulon sovereign/member/contractor boundaries;
- every Eviulon and Patefacere direct link is HTTPS, host-allowlisted, query/userinfo/fragment free, and visible in no-JavaScript HTML;
- current source observation is versioned and preserves earlier observations rather than rewriting them;
- source reachability is distinct from schema compatibility, authority verification, contract acceptance, configuration, and activation;
- remote payloads cannot self-enable, self-accept, change origin/path/profile/hash, or mutate local state;
- correspondence integrity does not authenticate the responder or create authority;
- no operation changes citizenship, civic standing, PAT-ID, ECN, DID, credential, passport, recovery state, civic-service profile, mobilization order, lifecycle, command authority, or use-of-force authority without the separately required competent record;
- credential rotation and passport replacement do not create a new citizen;
- credential or connector failure does not erase citizenship;
- delegates cannot exceed principal authority;
- stale, revoked, mismatched, replayed, cross-bound, malformed, oversized, or unsupported evidence is rejected with every reason preserved;
- append-only events reject update/delete and preserve exact prior message/evidence bytes;
- no public page leaks citizen identifiers, credentials, recovery material, private correspondence, capabilities, locations, topology, or strategic readiness;
- all reports remain in `docs/`, all source hashes remain unchanged, and every report retains an individual deep link from `.uai/long-term-memory.uai`;
- public pages, APIs, JSON/CSV/OpenAPI records, search, sitemap, and footer are consistent;
- keyboard, mobile, 200%/400% zoom, no-JavaScript, reduced-motion, forced-colors where available, and screen-reader semantics pass;
- Python and JavaScript syntax, standalone and WSGI smoke, schema migration idempotency, package-manifest replay, archive safety, secret scans, root extraction, and SHA-256 verification pass.

## Completion and delivery

Report changed, created, preserved, superseded, and intentionally untouched files. State every skipped actual-host or production gate and residual risk. Do not deploy, restart Passenger, mutate a production database, rotate real credentials, activate a connector, send a message, or perform an external write without explicit authority, complete backup, and named rollback ownership.

Always provide:

1. a complete versioned root-deployable Patefacere ZIP;
2. a SHA-256 sidecar;
3. a package audit;
4. validation evidence; and
5. one subsequent bounded Suggested Next Prompt with **Feature/improvement focus**, **Code/source changes**, and **Automated tests/checks**.