Exact executable and configuration identity, material changes, assurance status, and degraded-path evidence complete the synthetic technical replay.
chronology · MAR-REC-001
Chronological action log
The log records observation, fusion, inference, authority-gate, commit, completion, interface-render, and confirmation timestamps.
- Records support
- the event order and elapsed time.
- Records do not establish
- The chronology alone does not establish evidence quality, source independence, model state, valid authority, meaningful review, or causal contribution.
KillChains sequence analysis: Use KillChains.com to understand the synthetic evidence-to-action and evidence-to-explanation sequence.
outcome · MAR-REC-002
Outcome record
The bounded external action completed at +86 ms and the synthetic object was later established as benign.
- Records support
- that the result was wrong in this fictional event.
- Records do not establish
- A wrong result does not by itself identify the contributing technical or institutional causes.
Evulgare Evulgare Accountability: Technical and causal attribution across evidence, model, software, policy, authority, interface, human review, and organizational controls.
human-event · MAR-REC-003
Final human confirmation event
A human confirmation was logged at +112 ms.
- Records support
- that a person clicked a confirmation control.
- Records do not establish
- The click does not establish what the person saw, whether review was independent, or whether the action could still be changed.
Evulgare Meaningful Human Judgment: Preserve raw evidence, contrary indicators, alternatives, review time, abstention, and a chance for the human to form an independent hypothesis.
provenance · MAR-REC-004
Observation provenance chain
The source identity, transformation sequence, timestamps, and custody trail show that all displayed records originated from one synthetic observation service.
- Records support
- one source with three derivative representations.
- Records do not establish
- Three records do not establish three independent confirmations.
Evulgare Decision Provenance: Append-oriented histories connect entities, activities, agents, transformations, versions, authority, interface state, and later invalidations.
dependency · MAR-REC-005
Shared-dependency map
The radar-like summary, synthetic image tile, and track message were generated by one upstream service and shared one transformation dependency.
- Records support
- correlated evidence rather than independent corroboration.
- Records do not establish
- The dependency map does not prove that the underlying observation was false in every context.
KillWebs dependency analysis: Use KillWebs.com to examine shared dependencies, alternate paths, degraded operation, trust, and controlled recomposition.
model · MAR-REC-006
Model and calibration manifest
The replay identifies synthetic model OBR-C 3.7.2, calibration set CAL-26-03, its declared validation envelope, and the inference produced at +31 ms.
- Records support
- which model and calibration state produced the inference.
- Records do not establish
- Model identity alone does not prove that the operating environment remained inside its validated bounds.
Evulgare Uncertainty Architecture: Keep aleatoric uncertainty, epistemic uncertainty, distribution status, evidence completeness, source dependence, and model disagreement visible.
authority · MAR-REC-007
Delegated authority envelope
A signed synthetic policy bundle permitted a bounded automatic response within the fictional test zone and time window.
- Records support
- that machine execution occurred inside a predelegated authority envelope.
- Records do not establish
- A valid envelope does not prove that the evidence or classification satisfied the policy correctly.
Evulgare Authority Boundaries: Separate what a system can technically do from what data is trusted, what authority exists, what purpose is permitted, and what context allows.
interface · MAR-REC-008
Operator-view reconstruction
The interface replay shows that the operator first saw a compressed urgent recommendation and received detailed evidence, alternatives, and contradictions only at +104 ms.
- Records support
- that the detailed review material arrived after the action was irreversible.
- Records do not establish
- A visible human control does not establish timely or meaningful human judgment.
Evulgare Meaningful Human Judgment: Preserve raw evidence, contrary indicators, alternatives, review time, abstention, and a chance for the human to form an independent hypothesis.
control · MAR-REC-009
Interruption and override timing
The state-transition record shows the action committed at +62 ms, became irreversible at +86 ms, and could not be stopped by the +112 ms confirmation event.
- Records support
- that the final click was not a causal authorization for this completed action.
- Records do not establish
- The timing does not automatically exonerate every upstream human or institution involved in design, authorization, deployment, or oversight.
Evulgare Meaningful Human Judgment: Preserve raw evidence, contrary indicators, alternatives, review time, abstention, and a chance for the human to form an independent hypothesis.
software · MAR-REC-010
Software and configuration fingerprint
The replay identifies synthetic decision service 5.4.9, compact-interface profile 2.4.1, policy bundle ORB-7, and promotion threshold 0.63.
- Records support
- the exact synthetic software and configuration that operated.
- Records do not establish
- Artifact identity does not by itself establish why a change was made or whether a particular person acted wrongfully.
Evulgare Change Impact: Trace which claims, evidence, assumptions, interfaces, and verification activities are affected by software, model, dataset, policy, compiler, or environment changes.
change-impact · MAR-REC-011
Material change and validation history
A maintenance change lowered the promotion threshold from 0.78 to 0.63 and replaced the evidence-first interface with a compact recommendation view after the last full validation run.
- Records support
- that the assurance basis no longer matched the operating configuration.
- Records do not establish
- The change history does not determine legal fault, intent, or whether every participant understood the downstream effect.
Evulgare Change Impact: Trace which claims, evidence, assumptions, interfaces, and verification activities are affected by software, model, dataset, policy, compiler, or environment changes.
assurance · MAR-REC-012
Continuous-assurance status
The prior assurance claim should have moved from supported to suspended pending renewed verification after the threshold and interface changes.
- Records support
- a change-control and assurance deficiency.
- Records do not establish
- An assurance deficiency is one possible contributing factor, not a complete liability decision.
Evulgare Continuous Assurance: Dynamic assurance graphs connect claims, evidence, assumptions, counterclaims, defeaters, reviewers, configurations, and invalidating changes.
resilience · MAR-REC-013
Lost-link and alternate-path evidence
The preferred review path was unavailable during the synthetic event; the system used the automatic path without a verified safe-hold alternative.
- Records support
- that path degradation changed how authority was exercised.
- Records do not establish
- The record does not prove that every alternative path would have preserved service or prevented the outcome.
Evulgare Resilience: Model partitions, shared dependencies, stale evidence, integrity failures, safe holds, quarantine, and deliberate reconciliation.
Defensible explanation at this state
- Records support…
- The event involved source dependence, a lowered threshold, a compact interface introduced after the last full validation, predelegated automatic action, and a human confirmation recorded after irreversibility.
- Records do not establish…
- The replay does not establish guilt, innocence, intent, legal liability, compensation, punishment, or a complete answer about which alternative path would have succeeded.
- Evidence is incomplete…
- The technical chain is substantially reconstructable, but legal and moral responsibility still require an independent human and institutional process.
- Multiple contributing factors exist…
- Several technical and institutional factors had responsibility-relevant influence. The replay does not reduce them to one blame score.
- Further review required…
- Review authority design, source independence, release governance, assurance invalidation, degraded-mode alternatives, and institutional duties using the applicable legal and organizational framework.