Current bounded status
| Field | Value | Canonical record |
|---|---|---|
| Latest attempted observation | EVI-SYNC-OBS-008 | Open record |
| Latest verified fixture observation | EVI-SYNC-OBS-002 | Open record |
| Current public connector state | contract-published-connector-inactive | Open record |
| Live reciprocal implementation tested | No | — |
The fixture chain demonstrates local validation behavior. No live Patefacere statement was observed, accepted, or transmitted.
Fixture-derived observation history
VERIFIED
EVI-SYNC-OBS-001
Local fixture demonstrates a valid sequence-one chain root accepted as a last-known-good public projection.
NO_REJECTION_REASON
VERIFIED
EVI-SYNC-OBS-002
Local fixture demonstrates a valid sequence-two successor with a matching previous digest.
NO_REJECTION_REASON
CONFLICT
EVI-SYNC-OBS-003
Local fixture demonstrates that a replayed or non-monotonic sequence is recorded but never accepted.
NON_MONOTONIC_SEQUENCE, PREVIOUS_DIGEST_CONFLICT
CONFLICT
EVI-SYNC-OBS-004
Local fixture demonstrates rejection when a candidate claims a different Eviulon governance digest.
GOVERNANCE_DIGEST_CONFLICT
STALE
EVI-SYNC-OBS-005
Local fixture demonstrates that an expired statement remains visible as stale evidence and cannot replace last-known-good.
PROJECTION_EXPIRED
UNVERIFIED
EVI-SYNC-OBS-006
Local fixture demonstrates exact-origin and exact-path enforcement.
SOURCE_ROUTE_MISMATCH
UNVERIFIED
EVI-SYNC-OBS-007
Local fixture demonstrates recursive rejection of secrets, private citizen data, credentials, passport bodies, or operational workflow state.
PROHIBITED_FIELD
UNVERIFIED
EVI-SYNC-OBS-008
Local fixture demonstrates duplicate-key rejection before semantic validation.
DUPLICATE_JSON_KEY
Observation versus acceptance
A rejected, stale, conflicting, or malformed candidate may produce a bounded observation receipt. It cannot replace accepted last-known-good bytes, cannot silently become operational truth, and cannot alter an identity, credential, passport, or civic status. Acceptance requires a valid chain, current governance binding, exact origin, current freshness, canonical digest, known schema, and a clean privacy scan.
Privacy boundary
Observation receipts preserve only digests, byte counts, high-level reason codes, routes, times, and truth boundaries. Candidate bodies containing citizen records, credentials, passports, private receipts, raw logs, secrets, tokens, workflow state, private topology, counts, or statistics are not republished.
Machine-readable records
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
Repository-local fixture evidence only; no production observation, remote health statement, identity action, or independent certification.
Revision date: . Public corrections may be initiated through the diplomatic contact route.