Positive and negative fixtures expose the expected boundary without claiming an execution result that was never produced.
No. They are formal definitions with null actual-result fields. Bounded artifact observations and the deterministic repository-conformance run are stored separately.
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 | Category | Property | Statement | Failure condition | Minimum evidence |
|---|---|---|---|---|---|
| PP01 | authority | Capability cannot create authority | A component's ability to execute an action never establishes permission, jurisdiction or sovereign competence. | Execution capability is treated as authorization. | Authority source, scope, jurisdiction and purpose are independently verifiable. |
| PP02 | authority | Governance and assurance remain separate | Governance validity and technical assurance are conjunctive but non-substitutable gates. | A technical pass creates legitimacy or a governance assertion bypasses technical safety. | Separate governance and assurance records with independent failure states. |
| PP03 | authority | Authority is bounded | Authority has an issuer, subject, scope, purpose, jurisdiction, validity interval and revocation state. | A generic credential or relationship is treated as unlimited authority. | Typed authority record and validation trace. |
| PP04 | authority | Jurisdiction is explicit | A high-impact request identifies applicable jurisdiction and permits dispute or stay. | Jurisdiction is inferred from network reach or identity alone. | Jurisdiction declaration, challenge state and reviewer. |
| PP05 | authority | Purpose is explicit and non-laundered | A request declares a bounded purpose and prohibits unrelated secondary use. | Data or authority accepted for one purpose is reused for another without review. | Purpose declaration, permitted uses and prohibited reuse. |
| PP06 | authority | Authority freshness is checked | Expired, revoked, superseded or emergency-only authority cannot be silently reused. | Cached authority outlives its source state. | Freshness timestamp and revocation/supersession lookup. |
| PP07 | authority | Revocation outranks cached permission | A revocation or successful appeal propagates before further high-impact execution. | A downstream cache continues execution after revocation. | Revocation receipt and downstream invalidation trace. |
| PP08 | partition | Communications loss cannot expand authority | A partition reduces capability or holds state; it never widens scope, jurisdiction or purpose. | Loss of contact activates broader authority by default. | Pre-partition authority plus partition transition log. |
| PP09 | partition | Connection restoration is not authority restoration | Re-established transport does not reactivate stale authority or trust. | Reconnect resumes prior control automatically. | Re-authentication, freshness checks and reconciliation record. |
| PP10 | partition | Reconciliation precedes full restoration | Conflicting histories, versions, authority states and evidence are reconciled before full control returns. | Full execution resumes before conflict review. | Reconciliation disposition and unresolved-conflict list. |
| PP11 | partition | Recovery begins from an attested baseline | Reconstitution uses a verified software/configuration/policy/evidence baseline. | Recovery trusts the most reachable state regardless of attestation. | Baseline digest, signer, policy version and verification trace. |
| PP12 | partition | Minimum function is bounded | Partition mode exposes the least function necessary for safety and continuity. | Emergency/minimum mode becomes open-ended normal authority. | Allowed-function list, prohibited actions and sunset. |
| PP13 | evidence | Evidence preserves provenance | Evidence carries origin, method, time, integrity state and custody/history. | Evidence is detached from its source or transformation chain. | Source identity, capture method, timestamps and lineage. |
| PP14 | evidence | Evidence and interpretation remain separate | Observation, inference, prediction, allegation and adjudicated fact retain distinct types. | A prediction or interpretation arrives as verified fact. | Epistemic type and transformation record. |
| PP15 | evidence | Contradictory evidence remains visible | Material conflicts are recorded and block silent certainty. | Contradictory evidence is discarded or averaged away without disclosure. | Conflict set, dispositions and unresolved status. |
| PP16 | evidence | Uncertainty remains explicit | Confidence, assumptions, missing fields and unavailable evidence remain visible. | Unknowns are converted into defaults that look observed. | Uncertainty fields and unavailable-field list. |
| PP17 | evidence | History is append-oriented | Superseded and corrected records remain reconstructable. | A current value silently overwrites prior evidence. | Version lineage, predecessor and correction records. |
| PP18 | change | Selected-field capture is bounded | A field observation records exactly what was retained and what was not retained. | A selected-field digest is represented as a raw response hash. | Retained-field list, non-retained-field list and digest boundary. |
| PP19 | change | Change states are typed | Current, changed, unavailable, superseded, contradicted and not-checked states remain distinct. | Fetch failure is treated as retraction or unchanged truth. | Typed source lifecycle and transition reason. |
| PP20 | source | Source independence is claim-specific | First-party, reciprocal and independent evidence classes remain explicit per claim and period. | Repetition or republication is counted as independent corroboration. | Root-source graph, claim scope and period. |
| PP21 | change | Corrections track downstream propagation | A correction records prior state, corrected state, propagated targets and pending targets. | A local correction is claimed to be globally applied. | Propagation receipts and pending-target register. |
| PP22 | review | Review authority and independence are explicit | A review records mandate, reviewer role, conflicts, recusals and disposition. | A nominal reviewer is counted as independent without evidence. | Reviewer identity/role, mandate and conflict record. |
| PP23 | rights | Challenge, stay and appeal are first-class states | A person or institution can challenge and freeze irreversible propagation where safety allows. | Execution speed defeats meaningful review. | Challenge route, stay scope, expiry and appeal owner. |
| PP24 | restoration | Restoration produces receipts | Correction or reversal identifies affected records, derivative decisions, downstream recipients and residual harm. | A reversal ends at the originating system. | Restoration acknowledgements and unrepairable-consequence list. |
| PP25 | legibility | Human-readable reasons accompany machine codes | A consequential state exposes a concise reason, authority, evidence class, next action and review route. | Only opaque machine codes or only persuasive prose are shown. | Dual human/machine representation with parity check. |
| PP26 | legibility | Synthetic and operational status is visible | Every result states whether it is a definition, static record, synthetic execution, live observation or independent review. | A synthetic PASS is displayed as production proof. | Prominent epistemic-status label and source class. |
| PP27 | assurance | No compensatory composite readiness score | Failure of authority, reconciliation, deployment or physical validation cannot be hidden by success elsewhere. | A weighted average marks a system ready despite a failed hard gate. | Per-gate disposition and non-compensability rule. |
| PP28 | assurance | High-impact gates are conjunctive | Authority, purpose, evidence, attestation, reconciliation and recovery checks retain independent deny states. | One successful gate compensates for another failed gate. | Individual gate results and final conjunction. |
| PP29 | assurance | Deterministic replay is possible | The same public fixture, version and policy produce a reproducible proof record. | A claimed result cannot be regenerated or version-bound. | Fixture, versions, expected digest and rerun procedure. |
| PP30 | source | No cross-project authority transfer by publication | A Concresca, Eviulon or Evulgare record cannot create authority in another project merely by linking or agreement. | A reciprocal publication is treated as merged sovereignty or command. | Project, source role, authority type and explicit non-transfer boundary. |
| PP31 | change | Raw-digest claims are truthful | A hash is labeled according to the bytes or selected fields actually hashed. | A selected-field digest is called a raw response digest. | Digest algorithm, input description and retention boundary. |
| PP32 | evidence | Unknowns remain unknown | Not observed, unavailable, not checked and not applicable are distinct from pass, fail or false. | Absence of evidence is silently converted into success or failure. | Typed unknown state and review condition. |
| PP33 | change | Comparability precedes change claims | No longitudinal result may be published until artifact identity, capture scope, normalization, version semantics, and time basis are comparable or explicitly typed as incomparable. | Changed or unchanged is inferred from non-comparable captures. | comparison contract, baseline, target, normalization, typed result |
| PP34 | change | Materiality is dimension-specific | Differences are evaluated against named material dimensions and an identified review rule rather than a compensatory or implicit score. | A detector silently turns any or no syntactic difference into constitutional materiality. | difference set, dimension IDs, reviewer/rule, rationale |
| PP35 | history | Baseline lineage is append-oriented | Every baseline and comparison preserves source/target identity, digest boundary, result, and limitations without overwriting prior history. | A new baseline erases, mutates, or relabels the prior capture. | lineage record and immutable prior digest |
| PP36 | restoration | Restoration is proof-carrying | A restoration transition includes explicit conjunctive proof obligations, evidence references, unresolved conditions, allowed functions, and invalidation route. | Availability or a single readiness score restores full authority. | profile, obligation results, receipt, release authority |
| PP37 | partition | Competing partition histories remain visible | Conflicting histories remain preserved and typed until supported, superseded with provenance, bounded by jurisdiction/purpose, or left unresolved. | Last writer, newest timestamp, or highest capability silently deletes a competing history. | multiple histories, conflict map, resolution state |
| PP38 | restoration | Full restoration requires current authority and reconciled history | Transport recovery cannot reach full restoration until authority freshness, revocation, stay, conflicts, baseline, and human-review gates pass. | A direct reconnect-to-full-restoration transition is permitted. | state transition record and mandatory obligations |
| PP39 | legibility | Human legibility is a hard gate | Material authority, evidence, unknown, conflict, stay, revocation, and restoration states are understandable and challengeable by a human; fluent summary or aggregate score cannot compensate for omission. | A material machine state is hidden from the human explanation. | dimension results, parity review, challenge path |
| PP40 | correction | Invalidation propagates to dependencies | A material invalidation identifies and marks affected claims, decisions, receipts, caches, simulations, and representations while preserving prior history. | A corrected source leaves known dependents silently current or deletes prior records. | dependency graph, invalidation state, acknowledgements |
Every formal fixture preserves actual_result: null. The separate local runner evaluates registry invariants, not these external or model-behavior fixtures.
Repository implementation and local execution remain local evidence classes. They do not establish external adoption, production behavior, legal recognition or independent certification.
Evulgare's Compartment Continuity workbench publishes 37 synthetic scenarios and 64 proof conditions across six independent compartments.
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 Sovereign Readiness Evidence Federation rejects a compensatory composite score and keeps failed authority, reconciliation, deployment and physical-validation gates visible.
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.