Living Corpus Failures and Non-confirmations

FNR-001 / NON CONFIRMED

programme_level

Hypothesis: Independent reproduction exists for the classified programme surface.
Expected result: At least one independently executed or independently anchor-replicated artefact with bounded method and evidence.
Observed result: No selected artefact is classified as independent_execution or independent_anchor_replication.
Impact on claim: All claims remain internal, model-assisted, same-operator, or unreplicated.
Correction or required action: Use "no independent reproduction identified in B0"; do not say "reproduced by an independent party".
Residual uncertainty: A qualifying record may exist after the B0 cutoff or outside the selected set.
Claim disposition: narrowed
Observed runtime failure event: No
Artifact refs: A010 (f90c92d5bd69), A016 (1272fa8a4130), A020 (e62532348dbc), A055 (10ca5bc43c91)

FNR-002 / NON CONFIRMED

matched_control

Hypothesis: The corpus already contains strict matched profile-control.
Expected result: Same substrate, corpus, disturbance stream, interface, comparable memory; only anchor-custody metabolic history differs.
Observed result: The B0 gap scan did not confirm any artefact satisfying all conditions.
Impact on claim: No differential residual claim may be promoted.
Correction or required action: Keep the layer as proposed test design; build paired experiment and custody protocol.
Residual uncertainty: Learning Abstract handling remains unclear; later sources may change the result.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A054 (0661c182bef1), A055 (10ca5bc43c91)

FNR-003 / CLAIM NARROWED

witness_semantics

Hypothesis: Existing witness language already distinguishes evidence types sufficiently.
Expected result: Every material witness claim is explicitly typed as integrity, ontogenic, differential, or another declared class.
Observed result: Witness remains overloaded across L4, continuity, package, and formation surfaces.
Impact on claim: "Witnessed" alone cannot support c, truth, success, or differential claims.
Correction or required action: Apply the witness-type split and require type in every promotion record.
Residual uncertainty: Older public surfaces remain open to overreading until annotated.
Claim disposition: proposed_patch
Observed runtime failure event: No
Artifact refs: A013 (6336664c1eb5), A056 (82cd344466ec), A057 (d3d13cb6b248)

FNR-004 / BLOCKED PROMOTION

personality_formation

Hypothesis: PF evidence distinguishes a running c-candidate from a matched persistent profile.
Expected result: Residual survives strict matched profile-control and independent review.
Observed result: PF material supports internally witnessed ontogenic/continuity evidence and fixtures only.
Impact on claim: PF cannot be cited as differential witness or entity proof.
Correction or required action: Relabel PF evidence as ontogenic unless a strict control result is attached.
Residual uncertainty: A strong persistent profile may reproduce the observed surface.
Claim disposition: narrowed
Observed runtime failure event: No
Artifact refs: A030 (c2f21324f312), A031 (fb73c25fb19e), A032 (bab7aef95617), A033 (3daaa92416c9), A055 (10ca5bc43c91)

FNR-005 / BLOCKED PROMOTION

c_calculus_review

Hypothesis: Model-assisted c-calculus conformance review supplies external validation.
Expected result: Independent execution by a separate operator/team with bounded inputs, method, and result trail.
Observed result: The review is model-assisted and internal; validation_state is external_commentary_only.
Impact on claim: Useful adversarial review does not change replication or validation status.
Correction or required action: Retain as internal conformance review; seek independent implementation or execution.
Residual uncertainty: Model diversity may find defects but does not supply empirical independence.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A010 (f90c92d5bd69)

FNR-006 / NON CONFIRMED

l4_witness_runtime

Hypothesis: L4 Witness implementation has independently demonstrated operational success.
Expected result: Execution trace linking rule, enforcement gate, L4 consequence, witness record, and independent review.
Observed result: B0 contains draft/local specifications and a same-operator development report only.
Impact on claim: No external validation, certification, or general runtime-success claim.
Correction or required action: Capture test vectors, failure injection, route activation, and independent execution.
Residual uncertainty: Authority of local witness documents still requires canonical-path confirmation.
Claim disposition: unresolved
Observed runtime failure event: No
Artifact refs: A013 (6336664c1eb5), A014 (99dcf31d6d7a), A015 (b888b6b8a0d8), A016 (1272fa8a4130)

FNR-007 / NON CONFIRMED

arq_runtime

Hypothesis: ARQ safe degradation and correction are demonstrated in runtime.
Expected result: Controlled disturbance with observed suppress/quarantine/review/rollback behavior and passed conformance.
Observed result: B0 shows specifications, test design, failure-mode document, and package/repository preflight.
Impact on claim: Package preflight cannot be promoted to runtime correction or boundedness.
Correction or required action: Execute conformance matrix against implementation and retain negative outcomes.
Residual uncertainty: Implementation may exist outside B0; no execution record is classified here.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A017 (082bbe030d77), A018 (5f12c7bee457), A019 (5942aafda50c), A020 (e62532348dbc)

FNR-008 / NON CONFIRMED

ser_continuity

Hypothesis: SER continuity over replay, archive, fork, and migration is empirically demonstrated.
Expected result: Observed migration/restart cases with custody, identity criteria, fork classification, and adverse cases.
Observed result: Normative SER and continuity-bundle routing exist; no live continuity result is identified.
Impact on claim: SER remains a normative continuity discipline, not proof of a running c.
Correction or required action: Build replay/fork/archive/successor conformance cases with witnessed outcomes.
Residual uncertainty: The ontology may be coherent while empirical continuity remains unresolved.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A011 (6c62dcd21d4a), A012 (aff88bf7665a)

FNR-009 / NON CONFIRMED

memory_controls

Hypothesis: AMDR/PAMDC detects and corrects memory degradation in operation.
Expected result: Observed corruption/degradation, correct quarantine/recalibration, reconstruction, and post-anchor decision.
Observed result: B0 contains profiles and patches but no classified runtime effectiveness record.
Impact on claim: No claim of effective degradation detection, freshness, or post-anchor continuity.
Correction or required action: Run corruption and write-failure experiments; record false positives/negatives and rollback.
Residual uncertainty: Silent degradation and false continuity remain open.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A034 (6b6bbee70e25), A035 (7e1b750ca9e6), A036 (995ae4655fae), A037 (273466fc1cb8)

FNR-010 / BLOCKED PROMOTION

srlm_deployment

Hypothesis: Implemented SRLM code establishes live bounded growth.
Expected result: Confirmed route activation, admissible outcome writes, shadow/canary state, test logs, and bounded promotion.
Observed result: Engine and fitness code are present; B0 snapshots do not establish live deployment or result quality.
Impact on claim: Implementation_state=implemented for code does not become operationally_deployed.
Correction or required action: Attach runtime configuration, test results, witness logs, and rollback evidence as a delta baseline.
Residual uncertainty: Later runtime work may exceed B0, but cannot be backfilled silently.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A038 (775d3fe8aa47), A039 (ecfd6748c419), A040 (65e21f708b7c), A041 (784a7da019b7)

FNR-011 / BLOCKED PROMOTION

entity_profile

Hypothesis: Minimum c-node profile and custody manifest establish entity status.
Expected result: Matched profile-control, continuity evidence, witness-root custody, and independent claim-class review.
Observed result: B0 contains a draft profile, package route, and integrity hashes only.
Impact on claim: Profile conformance and byte identity cannot be called entity proof.
Correction or required action: Keep "profile/c-candidate" language and implement differential controls.
Residual uncertainty: Entity classification remains a stronger unresolved claim class.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A042 (87786d12c199), A043 (d65e63b38e29), A044 (2572240fca8d)

FNR-012 / NON CONFIRMED

actor_grounding

Hypothesis: AGL integration and hardware perimeter enforce safe grounded action.
Expected result: Sensor/actuator traces, hardware gate evidence, failure injection, emergency stop, and interop results.
Observed result: B0 contains draft architecture and integrity manifest, not operational interoperability.
Impact on claim: No grounding-accuracy, physical-safety, or deployment claim.
Correction or required action: Build bounded hardware-in-the-loop tests and retain blocked/failed cases.
Residual uncertainty: Procedure may be correct while actuator or sensor reality differs.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A045 (bfeb27dd9e63), A046 (dc9209674099), A047 (cb1179dbee01)

FNR-013 / BLOCKED PROMOTION

article50

Hypothesis: The Article 50 bridge demonstrates legal compliance or conformity.
Expected result: Qualified legal interpretation plus implemented, tested, auditable controls and conformity evidence.
Observed result: The package explicitly presents policy/engineering guidance and a manifest only.
Impact on claim: No legal advice, certification, conformity assessment, or formal compliance claim.
Correction or required action: Keep bounded implementation-brief wording; route legal conclusions to qualified actors.
Residual uncertainty: Law, standards, and regulator interpretation may change.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A048 (52ee9cc90ed1), A049 (dcd0dbae2292), A050 (db5c8faed9da)

FNR-014 / STATUS WITHHELD

enterprise_readiness

Hypothesis: Enterprise-c package is public-, sale-, deployment-, or conformance-ready.
Expected result: Passed conformance, implemented deployment, security review, client boundary, and authorized release.
Observed result: The internal readiness record explicitly withholds stronger readiness statuses.
Impact on claim: No public release, sale, implementation-ready, deployment-ready, or conformance-supported claim.
Correction or required action: Preserve the stop condition until required evidence exists.
Residual uncertainty: Internal document readiness may be mistaken for product readiness.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A051 (b1f6831ed04e), A052 (6b586c052f7f), A053 (67e7779842da)

FNR-015 / BLOCKED PROMOTION

publication_validation

Hypothesis: Publication, DOI, release, or manifest validates the underlying architecture.
Expected result: Separate implementation, test, reproduction, or validation evidence tied to the technical claim.
Observed result: B0 publication surfaces establish identity, availability, and citation only.
Impact on claim: No status elevation from discoverability to technical maturity.
Correction or required action: Display publication state and technical maturity on separate axes.
Residual uncertainty: External readers may still infer maturity from volume and polish.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A058 (321dfbc0797e), A059 (25f73faeddc1), A060 (365e3427b4b3)

FNR-016 / AUTHORITY UNRESOLVED

canonical_placement

Hypothesis: The selected c = a + b protocol copy is confirmed as current canonical location.
Expected result: Live repository/ref check showing current canonical path and supersession status.
Observed result: B0 supplies exact incoming-package content but canonical placement is unresolved.
Impact on claim: Content may be cited as frozen B0 evidence, not as current canonical path.
Correction or required action: Resolve current ref during umbrella source-link pass; record as B0.1 delta.
Residual uncertainty: A newer or superseding source may exist.
Claim disposition: unresolved
Observed runtime failure event: No
Artifact refs: A009 (1168474cd5a3)

FNR-017 / CLAIM NARROWED

maturity_model

Hypothesis: The prior status/maturity map can serve as a single programme maturity ladder.
Expected result: Independent axes for specification, implementation, test, replication, validation, empirical, publication, and disposition.
Observed result: Step 1 found the statuses non-linear; Step 2 narrowed the prior map and used a typed vector.
Impact on claim: Older maturity labels cannot silently imply stronger dimensions.
Correction or required action: Retain prior map for routing but govern new consolidation with the typed model.
Residual uncertainty: Legacy surfaces may still encode older one-dimensional wording.
Claim disposition: narrowed
Observed runtime failure event: No
Artifact refs: A005 (50085746685a)

FNR-018 / NEGATIVE EVIDENCE GAP

negative_event_capture

Hypothesis: B0 contains a representative set of real system-level failures and negative outcomes.
Expected result: Event-level records with expected/observed result, failure class, correction, rollback, and residual risk.
Observed result: The selected set contains many non-confirmations and blocked promotions, but no adequately evidenced system-level failure event classified as such.
Impact on claim: The register must not invent failures; absence of records is not evidence of absence of failures.
Correction or required action: Create an append-only adverse-event and non-confirmation intake for future runtime work.
Residual uncertainty: Publication and review selection may be biased toward successful or normative artefacts.
Claim disposition: active
Observed runtime failure event: No
Artifact refs: A019 (5942aafda50c), A035 (7e1b750ca9e6), A053 (67e7779842da), A055 (10ca5bc43c91)

Failures and non-confirmations

Runtime failure-event boundary

Failure and non-confirmation register