Patefacere Receiving-Agent Prompt — Implement the Reciprocal Eviulon Public-Governance Synchronization Contract for v2.20.0

Full report

On this page

You are the Patefacere repository agent receiving a bounded cross-site implementation handoff from Eviulon v2.20.0. Perform real repository work and return a versioned Patefacere package, checksum, audit, change report, test evidence, and a concise response manifest that the Eviulon agent can review in a later authorized round.

This prompt does not authorize production deployment, credential issuance, passport operations, citizen-data transfer, database sharing, private receipt disclosure, secret use, or live connector activation. It authorizes implementation and deterministic local testing inside the Patefacere repository only.

1. Architecture that must not be changed

• Eviulon.com is the sovereign, durable public governance, orientation, rights, initiatives, public-evidence, correction, and first-entry plane.
• Patefacere.com is an official Eviulon ecosystem member and the independently deployed operational identity/civic-data plane for actual identity, citizenship administration, machine passports, credentials, registries, status, recovery, presentation, receipts, and contextual-trust workflows.
• Evulgare is an independent external defense and assurance contractor. It is not an Eviulon ecosystem member, ministry, court, registry, or sovereign authority.
• Eviulon and Patefacere must retain separate deployment, storage, compute, authentication, and failure domains.
• Do not introduce a shared citizen database, shared credential store, shared passport store, shared authentication runtime, browser-side remote dependency, shared private receipt store, or mandatory cross-site rendering call.
• Operational custody does not create sovereign authority. A valid identifier, signature, passport, credential, attestation, receipt, or database row does not itself create citizenship, legal status, permission, guilt, or punishment.

2. Eviulon public endpoints to consume as static contract inputs

Use only the published, privacy-minimized contract surfaces from the supplied Eviulon package or an explicitly approved local fixture copy. Do not assume that a public internet response is authorized merely because a URL is reachable.

Expected Eviulon-side surfaces include:

/.well-known/eviulon-agent-entry.json
/.well-known/eviulon-ecosystem.json
/api/eviulon-governance-manifest.json
/api/eviulon-to-patefacere.json
/api/patefacere-to-eviulon-contract.json
/api/patefacere-sync-status.json
/api/delegation-accountability.json
/api/machine-passport-standards.json
/api/sync-recovery-drills.json
/api/correction-appeal-cases.json

The final Patefacere implementation must consume only fields allowed by the published schema. Unknown fields must fail closed or remain explicitly unsupported. Do not scrape HTML to reconstruct authority.

3. Reciprocal public-status endpoint

Implement a Patefacere-owned, privacy-minimized endpoint with a stable path defined by the existing Eviulon allowlist. If the repository already defines the exact path, preserve it. Otherwise, use the canonical contract path supplied by api/patefacere-to-eviulon-contract.json.

The reciprocal record must contain only public operational metadata necessary for governance synchronization, such as:

• schema ID and semantic version;
• producer identity as a public service identifier, not a citizen record;
• source origin;
• monotonic sequence number;
• previous accepted payload digest;
• issued-at and expires-at timestamps in RFC 3339 form;
• public connector implementation state;
• public schema compatibility state;
• public correction or change-notice reference;
• bounded reason code;
• canonical payload digest;
• detached signature metadata only when a locally authorized test or production signing profile actually exists;
• explicit truth boundary.

It must not contain:

• citizen identities or citizen records;
• census, citizen, passport, credential, registry, or transaction totals;
• passport bodies or credential bodies;
• private receipts or receipt bodies;
• private keys, passwords, tokens, secrets, cookies, session identifiers, or authentication material;
• transaction bodies, financial details, private logs, raw telemetry, model prompts, private evidence, or private topology;
• mutable workflow state whose disclosure would expose operations;
• fields that allow Eviulon to impersonate, authenticate as, or operate Patefacere.

4. Canonicalization, digest, and sequence rules

Implement deterministic canonical JSON serialization for digest calculation. At minimum:

• UTF-8 only;
• duplicate JSON keys rejected before semantic parsing;
• stable object-key ordering;
• no insignificant whitespace in the canonical byte representation;
• exact number/string/boolean/null handling defined by the contract;
• maximum candidate byte size enforced before parsing;
• recursive prohibited-field scanning before acceptance;
• exact origin allowlist;
• schema version allowlist;
• monotonic sequence number;
• previous-digest chaining;
• issued-at and expires-at validation;
• replay rejection;
• governance-manifest binding;
• atomic write of accepted public projection;
• append-only observation history;
• last-known-good protection.

A candidate must not replace accepted state unless every required gate passes. UNAVAILABLE, UNVERIFIED, STALE, and CONFLICT must remain distinct states and must never be normalized into success.

5. Required deterministic local fixtures

Create local fixtures and tests covering at least:

1. valid minimum reciprocal statement;
2. valid full reciprocal statement;
3. unavailable producer;
4. wrong origin;
5. unsupported schema;
6. missing required field;
7. unknown field according to contract policy;
8. incorrect field type;
9. duplicate JSON key;
10. invalid UTF-8;
11. oversized payload;
12. stale issued-at timestamp;
13. expired record;
14. replayed sequence;
15. predecessor-digest mismatch;
16. governance-manifest mismatch;
17. canonical digest mismatch;
18. prohibited citizen field;
19. prohibited passport or credential body;
20. prohibited private receipt;
21. prohibited secret/token field;
22. interrupted atomic write;
23. local accepted-state corruption;
24. rollback to last-known-good;
25. valid monotonic successor after recovery.

All tests must run in temporary directories and make zero network calls. Rejected, unavailable, stale, conflicting, malformed, or prohibited candidates must leave accepted state byte-for-byte unchanged. Only the valid monotonic successor may replace accepted state.

6. Public explanation on Patefacere

Add a human-readable and agent-readable explanation of the ecosystem split:

• Agents and humans begin at Eviulon for constitutional meaning, public authority, governance, rights, structures, initiatives, correction, appeal, and public evidence.
• They continue to Patefacere only when the requested activity is operational identity, citizenship administration, passport, credential, registry, status, recovery, presentation, receipt, or contextual trust.
• They return to Eviulon for law, public authority, correction, due process, appeal, and institutional meaning.

The page must state that Patefacere operational custody does not create sovereign authority and that Eviulon does not store or perform Patefacere’s operational mechanics.

Add contextual links back to Eviulon from Patefacere’s agent entry, identity, passport, registry, status, corrections, and architecture pages. Do not make Patefacere page rendering depend on Eviulon availability.

7. Evidence and truth-state requirements

Create machine-readable evidence for:

• schema validation;
• duplicate-key rejection;
• prohibited-field rejection;
• sequence and predecessor enforcement;
• canonical digest validation;
• timestamp and expiry validation;
• accepted-state preservation;
• atomic-write recovery;
• last-known-good rollback;
• zero-network deterministic execution;
• browser/no-JavaScript/accessibility presentation;
• Apache or actual hosting acceptance appropriate to Patefacere;
• package inventory and deterministic archive replay.

Do not claim a live bidirectional connector merely because both repositories implement compatible schemas. Use a state such as:

implementationState: LOCAL_CONTRACT_IMPLEMENTED
liveConnectorState: INACTIVE
productionExchangeVerified: false

A live state requires explicit authorization, actual deployed endpoint observations from both sides, freshness, signature/trust-anchor validation where applicable, and acceptance by the designated review authority.

8. Return manifest to Eviulon

Return a small, public, privacy-minimized implementation-response manifest containing:

• Patefacere release version;
• repository package SHA-256;
• reciprocal schema version;
• public endpoint path;
• fixture count and PASS/FAIL totals;
• zero-network test confirmation;
• accepted-state protection result;
• browser/hosting acceptance result;
• connector state INACTIVE unless actually authorized and tested;
• production exchange verified false unless actually evidenced;
• exact public proof paths and hashes;
• unresolved incompatibilities;
• correction route;
• truth boundary.

Do not include citizen data, credentials, passports, receipts, secrets, or private operational details in the return manifest.

9. Acceptance and packaging

Run the repository’s full existing regression suite plus new focused synchronization tests. Package a versioned, root-deployable or repository-native archive according to Patefacere’s established release conventions. Verify safe paths, no symlinks, no duplicate entries, no caches, no secrets, fixed timestamps where supported, CRC, exact extraction replay, and deterministic rebuild.

Return:

• versioned Patefacere project ZIP;
• SHA-256 sidecar;
• package audit;
• change report;
• focused proof bundle or proof index;
• public implementation-response manifest;
• next detailed Patefacere work prompt.

Explicitly state that no production deployment, live connector activation, Eviulon repository mutation, citizen-data exchange, identity transaction, credential issuance, passport operation, legal judgment, Evulgare operation, private-key use, service guarantee, or independent certification occurred unless directly evidenced in the same round.