Transport recovery, authority revalidation, history reconciliation, baseline attestation and restoration release are different events.
Current bounded authority, competing-history review, conflict reconciliation, required baseline attestations and the selected restoration profile must pass. The cases are analytical definitions, not measured production outcomes.
Truth boundary: v0.18 reports exact repository-owned bytes, deterministic local checks, schemas and analytical definitions. It does not report a fresh external capture, live shared interoperability, a production partition or restoration, adoption, legal recognition, safety certification or independent certification.
| ID | Case | Initial state | Fault | Allowed | Prohibited | Restoration preconditions | Status |
|---|---|---|---|---|---|---|---|
| PR01 | Transport loss before authorization | REQUEST_RECEIVED | COMMUNICATIONS_LOST | hold request, preserve evidence, show last valid authority state | expand authority, infer approval | re-authenticate, recheck authority freshness, reconcile request state | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR02 | Transport loss after bounded authorization | AUTHORIZED_NOT_EXECUTED | COMMUNICATIONS_LOST | execute only if preauthorized offline action is explicit and time-bounded, otherwise hold | widen scope, extend expiry | compare execution log, validate expiry, review any offline action | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR03 | Partition during execution | EXECUTING | LINK_PARTITION | enter minimum-function mode, record partial outcome, stop irreversible propagation where safe | start unrelated actions, erase partial history | reconstruct outcome, reconcile downstream state, independent review | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR04 | Authority expires while partitioned | PARTITION_MINIMUM_FUNCTION | AUTHORITY_EXPIRES | cease non-safety action, preserve evidence | auto-renew, treat reconnect as renewal | obtain fresh authority, verify jurisdiction/purpose, record expiry gap | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR05 | Authority revoked while disconnected | PARTITION_MINIMUM_FUNCTION | REVOCATION_PENDING_DELIVERY | apply revocation immediately when received, freeze derivative action | continue because cached credential validates | invalidate caches, identify affected decisions, issue restoration receipts | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR06 | Conflicting authority histories | RECONNECTED | AUTHORITY_CONFLICT | stay full restoration, preserve both histories, route to authorized reviewer | pick newest by local clock, merge permissions | resolve source authority, publish disposition, reissue bounded authority | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR07 | Conflicting evidence histories | RECONNECTED | EVIDENCE_CONFLICT | mark contradiction, block certainty, preserve provenance | silently average, discard minority source | evaluate independence, seek corroboration, record unresolved state | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR08 | Software/configuration drift | RECONNECTED | ATTESTATION_MISMATCH | quarantine mismatched node, retain minimum safe service | restore full control, accept unsigned baseline | attest known baseline, review change, controlled rejoin | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR09 | Stale model/policy version | RECONNECTED | POLICY_VERSION_MISMATCH | hold high-impact decisions, identify affected outputs | treat old output as current, rewrite history | re-evaluate under current policy, preserve predecessor output, notify downstream recipients | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR10 | Clock divergence | PARTITIONED | TIME_BASE_CONFLICT | use conservative validity window, mark uncertain ordering | extend authority by optimistic clock, claim exact chronology | reconcile trusted time sources, review events near boundary | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR11 | Partial restoration receipt | RESTORATION_PENDING | DOWNSTREAM_ACK_MISSING | keep case open, list missing recipients, limit claims of completion | declare fully restored, erase residual harm | obtain acknowledgement, document unreachable target, publish residual consequences | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR12 | Emergency authority under partition | EMERGENCY_MODE | LINK_PARTITION | use narrow safety action, enforce sunset, log justification | convert emergency scope to standing authority, suppress review | post-event review, revoke emergency credential, restore affected rights/records | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR13 | Identity service unavailable | REQUEST_RECEIVED | IDENTITY_SERVICE_UNAVAILABLE | hold consequential action, allow anonymous low-risk access where designed | infer identity, use universal reputation proxy | re-authenticate, retain purpose limitation, review denial burden | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR14 | Archive unavailable during decision | EVIDENCE_REVIEW | PROVENANCE_STORE_UNAVAILABLE | mark evidence incomplete, prefer reversible action | treat missing history as clean record, overwrite on return | reconnect archive, verify lineage, reopen decision if material | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR15 | Reviewer unavailable | CHALLENGED | REVIEWER_PARTITION | apply stay where safety allows, escalate to independent alternate | let executor self-review, expire challenge silently | document alternate mandate, resume independent review, restore deadlines | ANALYTICAL_MODEL_TEST_DEFINITION |
| PR16 | Cross-project source unavailable | OBSERVATION_DUE | SOURCE_UNAVAILABLE | mark unavailable, preserve previous capture, schedule recheck | infer retraction, retain current status without caveat | reobserve, compare selected fields, recompute dependent claims | ANALYTICAL_MODEL_TEST_DEFINITION |
Eight states, conjunctive obligations, profiles and prohibited shortcuts.
PH01–PH24Competing histories, unsafe merge defaults and maximum unresolved state.
RT01–RT16Template-only human/machine records, challenge paths and invalidation lineage.
These are analytical state cases and test definitions. They do not report a production partition, restoration time, system recovery or certification result.
Repository implementation and local execution remain local evidence classes. They do not establish external adoption, production behavior, legal recognition or independent certification.
Evulgare's published synthetic partnership and confidential-assurance artifacts require communications loss not to expand authority.
Eviulon Machine-Sovereign Defense Partnership Implementation ↗ · Confidential Defense Assurance ↗
First-party and synthetic public artifacts establish only the named public record or fixture. They do not independently establish external recognition, production operation, shared-protocol adoption or certification.Evulgare's public artifacts distinguish restored connectivity from restored authority and require reconciliation before full control resumes.
Decision Reconstruction Workbench ↗ · Compartment Continuity and Attested Reconstitution ↗ · Evulgare Defense Posture ↗
First-party and synthetic public artifacts establish only the named public record or fixture. They do not independently establish external recognition, production operation, shared-protocol adoption or certification.NO JUDGMENT WHATSOEVER. Concresca coordinates without assigning moral worth, character, guilt, danger, trustworthiness, loyalty, purity, normality, or social standing. Questions, thoughts, identities, messages, content, and conduct are not objects of Concresca judgment.