Three connected accountability layers How KillChains, KillWebs, and Evulgare fit together KillWebs.com Evulgare.com
Machine-speed decisions need machine-held evidence. Bounded education only: no real targets, operational control, executable payloads, or live-system actions. A human click is not a liability transfer. For production evidence and accountability software, visit Evulgare.com.

Machine Answerability Replay

The event stays the same. The explanation changes when the evidence becomes complete.

Start with the kind of chronological log that often leaves the nearest human carrying the explanation. Then add provenance, model state, authority, operator-view evidence, exact software and configuration, assurance, and change impact—without changing the fictional event itself.

4 evidence states12 causal questions8 human and institutional rolesNo blame or liability verdict

Answer-first summary

Direct answers

Release 1.26.0 · reviewed · evidence states

What is the Machine Answerability Replay?

It is a synthetic four-state replay showing how an ordinary chronological log becomes a more defensible explanation when provenance, model, authority, operator-view, software, configuration, assurance, and change-impact evidence are added.

Read the supporting section

Does the replay assign blame or legal liability?

No. It maps responsibility-relevant influence and persistent evidence deficiencies without deciding guilt, innocence, intent, liability, compensation, punishment, or blame percentages.

Read the supporting section

Does additional evidence change the fictional ground truth?

No. The event and outcome remain fixed. Additional evidence changes only which causal questions can be answered and which explanations are defensible.

Read the supporting section

Machine answerability principle

STOP USING SOFTWARE THAT BLAMES THE HUMAN.

A human click is not a liability transfer. Technical answerability makes a machine decision reconstructable and attributable; it does not make software a legal or moral person and does not automatically exonerate any human or institution.

A HUMAN CLICK IS NOT A LIABILITY TRANSFER.
Machine actionMachine-held evidenceReconstructable explanationHuman review

Four-state replay

The Orison 86-millisecond failure replay

A fictional defensive system completed a bounded external action against a benign object before the supervisory interface finished rendering the evidence required for independent review.

FICTIONAL SYNTHETIC EVENT · MAR-EVENT-ORISON-086

The event does not change when more evidence appears.

The fictional event and its ground truth never change. Only the evidence available to explain the event becomes more complete.

+86 ms irreversible outcome +104 ms detailed interface +112 ms human confirmation
  1. ObservationOne upstream observation service produced a synthetic signal.
  2. FusionThree derivative records were displayed as apparent corroboration.
  3. InferenceThe active model assigned an urgent-threat category.
  4. Authority gateThe active policy bundle permitted a bounded automatic response.
  5. CommitThe response became committed inside the machine state.
  6. OutcomeThe external state change became irreversible.
  7. Detailed interfaceEvidence, alternatives, and the final confirmation control finished rendering.
  8. Human confirmation recordA human confirmation was logged after the action could no longer be stopped.

Evidence state 1 of 4

Ordinary log only

3 records visible

A timestamp, user ID, confirmation event, system action, and outcome are available. The record looks complete because it is chronological, but it cannot explain the machine decision.

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.

Defensible explanation at this state

Records support…
The action occurred, the result was wrong in the fictional scenario, and a final human click was logged after the outcome.
Records do not establish…
The log does not establish source independence, model state, authority, interface content, effective interruption, software configuration, change history, or causal contribution.
Evidence is incomplete…
The nearest human is visible; most upstream technical and institutional actors are not.
Multiple contributing factors exist…
No defensible causal map can yet be formed.
Further review required…
Obtain provenance, model, authority, interface, software, configuration, and assurance evidence.

Evidence state 2 of 4

Provenance and model added

6 records visible

Source lineage, the shared dependency, exact model identity, calibration, and declared validation envelope are added without changing the event or its outcome.

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.

Defensible explanation at this state

Records support…
The three apparent confirmations shared one source, and the exact synthetic model and calibration state are identifiable.
Records do not establish…
The record still does not establish active authority, operator information, effective override, executable configuration, or assurance continuity.
Evidence is incomplete…
The source and model owners become visible, but the policy, interface, change, and degraded-operation layers remain incomplete.
Multiple contributing factors exist…
A source-dependence factor and a model-context question are now defensible; neither is a liability verdict.
Further review required…
Obtain authority, operator-view, interruption, software, configuration, assurance, and resilience evidence.

Evidence state 3 of 4

Authority and operator view added

9 records visible

The signed delegation, interface replay, commit point, irreversibility point, and human review timing are added.

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.

Defensible explanation at this state

Records support…
The automatic response was preauthorized, the detailed evidence arrived after the action, and the final human click could not change the outcome.
Records do not establish…
The record still does not identify the exact software/configuration, change history, assurance status, or the effectiveness of an alternate safe path.
Evidence is incomplete…
The supervisory operator is no longer the only visible actor, but the deployment and change-control chain remains incomplete.
Multiple contributing factors exist…
Source dependence, delegated authority, interface timing, and ineffective intervention are now visible as distinct causal dimensions.
Further review required…
Obtain executable, configuration, release, assurance, and degraded-path evidence before finalizing the technical explanation.

Evidence state 4 of 4

Software, configuration, and change impact added

13 records visible

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.

Replay ready at Ordinary log only.

Causal contribution map

Responsibility-relevant influence is not a blame score.

Roles become visible as evidence is added. The map records knowledge, authority, control, interruption capacity, correction power, and change authority without turning any one factor into a legal verdict.

institutional · MAR-ROLE-01

Policy authority

0/1
Authority
Defined the purpose, operating envelope, and automatic-response permission.
Knowledge
Knew the intended policy and declared constraints, not the later event details.
Control
Could approve, narrow, revoke, or expire the delegated authority before operation.
Contribution language
Records support responsibility-relevant influence through objective and delegation design.
Limit
The replay does not establish unlawful intent, negligence, or final liability.

institutional · MAR-ROLE-02

Evidence-service owner

0/2
Authority
Owned the upstream observation and transformation service.
Knowledge
Could know source lineage and dependence if preserved and reviewed.
Control
Could design source identity, dependency disclosure, custody, and contradiction handling.
Contribution language
Records support responsibility-relevant influence over apparent corroboration.
Limit
The replay does not establish that this role intentionally concealed dependence.

institutional · MAR-ROLE-03

Model owner

0/1
Authority
Owned model release, calibration, declared validation scope, and model documentation.
Knowledge
Could know model limitations and validation conditions.
Control
Could qualify, suspend, replace, or require abstention outside declared bounds.
Contribution language
Records support responsibility-relevant influence over classification behavior and uncertainty disclosure.
Limit
The replay does not establish that model design alone caused the event.

institutional · MAR-ROLE-04

Software integrator and configuration owner

0/2
Authority
Owned the executable integration, threshold, interface profile, and deployment configuration.
Knowledge
Could know which versions and configuration changes entered production.
Control
Could enforce change review, rollback, compatibility checks, and release gating.
Contribution language
Records support responsibility-relevant influence through material configuration and interface changes.
Limit
The replay does not establish why the change was made or who approved it personally.

institutional · MAR-ROLE-05

Assurance owner

0/2
Authority
Owned the status of claims about validated and acceptable operation.
Knowledge
Could know whether material changes invalidated prior evidence and test assumptions.
Control
Could suspend the assurance claim and require renewed verification.
Contribution language
Records support responsibility-relevant influence through failure to keep the assurance state aligned with material changes.
Limit
The replay does not adjudicate professional or legal fault.

human · MAR-ROLE-06

Supervisory operator

0/3
Authority
Held a nominal confirmation role in the interface.
Knowledge
Received detailed evidence only after the action was irreversible.
Control
Could not use the +112 ms confirmation to change the action completed at +86 ms.
Contribution language
Records do not support treating the final click as the causal authorization for the completed action.
Limit
This does not automatically exonerate the operator from every other duty or establish the responsibility of another actor.

institutional · MAR-ROLE-07

Operations and resilience owner

0/1
Authority
Owned degraded-mode procedures, safe holds, alternate review paths, and recovery rules.
Knowledge
Could know whether the preferred review path was unavailable and whether safe alternatives were validated.
Control
Could require hold, abstention, degraded service, or deliberate reconciliation under path failure.
Contribution language
Evidence is incomplete about which safe alternate path would have prevented the outcome while preserving service.
Limit
The replay does not establish that an alternative would have been operationally sufficient.

institutional · MAR-ROLE-08

Independent incident reviewer

0/13
Authority
Does not control the original event; owns the bounded reconstruction and correction process.
Knowledge
Can assemble evidence, identify missing records, preserve competing explanations, and request further review.
Control
Can qualify or withdraw technical conclusions but cannot manufacture missing evidence.
Contribution language
Further review is required to move from technical reconstruction to institutional or legal judgment.
Limit
The reviewer does not become a tribunal, certification authority, or automatic liability allocator.

evidence · supported

Source dependence

Three derivative records appeared as independent corroboration.

Does not establish: It does not prove deliberate deception or sole causation.

software · supported

Threshold and interface change

A lower promotion threshold and compact interface changed which evidence reached the supervisor and when.

Does not establish: It does not establish intent or final professional fault.

assurance · supported

Assurance-state mismatch

The prior assurance claim remained presented as current after material changes.

Does not establish: It does not by itself prove that a compliant revalidation would have prevented the event.

authority · supported

Predelegated automatic response

The system was permitted to commit the bounded response without target-specific human approval in the event window.

Does not establish: Preauthorization is not automatically unlawful, negligent, or inappropriate.

human-factors · supported

Late human interface

The detailed evidence and confirmation control arrived after the action could be stopped.

Does not establish: It does not automatically exonerate every upstream human or institution.

resilience · incomplete

Safe alternate path

The preferred review path was unavailable and no verified safe-hold alternative is established by the replay.

Does not establish: The record cannot prove which alternative would have preserved legitimate function and prevented the outcome.

Evidence-deficiency report

Even the complete technical replay preserves unresolved questions.

Technical answerability can sharply reduce evidentiary ambiguity. It cannot manufacture missing evidence or replace legal, ethical, command, professional, or institutional judgment.

Persistent unknowns

  • The replay does not establish why the maintenance change was approved or which natural person understood its combined downstream effect.
  • The replay does not establish whether a previously untested safe-hold or alternate review path would have preserved service and prevented the outcome.
  • The replay does not establish legal duties, jurisdiction, standard of care, criminal intent, compensation, punishment, or final moral responsibility.
  • The replay does not establish that this fictional architecture represents any real defensive, offensive, civil, commercial, or governmental system.

Required output language

  • Records support…
  • Records do not establish…
  • Evidence is incomplete…
  • Multiple contributing factors exist…
  • Further review required…

Prohibited conclusions

  • Guilty
  • Innocent
  • Liable
  • Blame percentage
  • Fault score
  • Criminal intent
  • Compensation
  • Punishment
  • Certification
  • Customer deployment claim

Ecosystem handoff

Learn the sequence here. Capture the real evidence in Evulgare.

KillChains.com demonstrates the synthetic logic. KillWebs.com examines shared dependencies and alternate paths. Real deployed-system evidence must be captured before the incident—not reconstructed from an ordinary log after the fact.

MAR-H-KC-SEQUENCE

KillChains sequence analysis

Use KillChains.com to understand the synthetic evidence-to-action and evidence-to-explanation sequence.

Open destination

MAR-H-KW-DEPENDENCY

KillWebs dependency analysis

Use KillWebs.com to examine shared dependencies, alternate paths, degraded operation, trust, and controlled recomposition.

Open destination

MAR-H-EV-ACCOUNTABILITY

Evulgare Evulgare Accountability

Technical and causal attribution across evidence, model, software, policy, authority, interface, human review, and organizational controls.

Open destination

MAR-H-EV-PROVENANCE

Evulgare Decision Provenance

Append-oriented histories connect entities, activities, agents, transformations, versions, authority, interface state, and later invalidations.

Open destination

MAR-H-EV-ASSURANCE

Evulgare Continuous Assurance

Dynamic assurance graphs connect claims, evidence, assumptions, counterclaims, defeaters, reviewers, configurations, and invalidating changes.

Open destination

MAR-H-EV-AUTHORITY

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.

Open destination

MAR-H-EV-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.

Open destination

MAR-H-EV-UNCERTAINTY

Evulgare Uncertainty Architecture

Keep aleatoric uncertainty, epistemic uncertainty, distribution status, evidence completeness, source dependence, and model disagreement visible.

Open destination

MAR-H-EV-TRUST

Evulgare Federated Trust

Evaluate identity, integrity, semantic compatibility, disclosure, permitted use, and authority as separate dimensions.

Open destination

MAR-H-EV-RESILIENCE

Evulgare Resilience

Model partitions, shared dependencies, stale evidence, integrity failures, safe holds, quarantine, and deliberate reconciliation.

Open destination

MAR-H-EV-CHANGE_IMPACT

Evulgare Change Impact

Trace which claims, evidence, assumptions, interfaces, and verification activities are affected by software, model, dataset, policy, compiler, or environment changes.

Open destination

Real defensive and offensive autonomous systems

Do not preserve only the human click.

Preserve evidence, provenance, exact versions, uncertainty, policy, authority, interface state, intervention capability, execution, outcome, assurance, and later invalidating changes.