Three connected accountability layers How KillChains, KillWebs, and Evulgare fit together KillWebs.com Evulgare.com
KillChains.com v1.24.0
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.

Cross-Lab Concept Matrix

Start with the concept. Then trace where it becomes consequential.

Compare thirteen recurring ideas across the Daily Break the Chain simulation, Human Control, Evidence Lab, Anticipatory Intelligence, Predictive Enforcement, Machine Leadership, Claim Lineage, Source Review, accepted history, and the wider ecosystem. Every concept keeps public learning separate from real-system accountability.

13 concepts58 released surface linksMaximum 3-concept comparisonEvulgare live bridge reviewed

Answer-first summary

Direct answers

Release 1.24.0 · reviewed · evidence states

What is the Cross-Lab Concept Matrix?

It is a read-only learning workspace that maps thirteen recurring concepts to the existing KillChains.com simulations, labs, evidence explorers, methods, history pages, and ecosystem handoffs where each concept can be studied.

Read the supporting section

Does the Concept Matrix create new factual claims or track learners?

No. It references existing typed owners and creates no account, profile, completion record, analytics event, persistent state, public edit, or operational recommendation.

Read the supporting section

When does a concept move from KillChains.com to Evulgare?

KillChains.com teaches the concept through public research and synthetic simulation. When a real deployed system needs evidence capture, model or software lineage, authority reconstruction, operator-view reconstruction, incident causality, or assurance, the handoff is to Evulgare.com.

Read the supporting section

How to use the workspace

One idea can appear at several stages of the decision chain.

The matrix does not duplicate the factual records owned by the existing labs and explorers. It shows how one concept changes meaning as it moves from evidence to inference, authorization, execution, review, and production accountability.

01

Learn it

Open a synthetic exercise or explanatory page on KillChains.com and inspect the concept in one bounded sequence.

02

Compare it

See how the same concept appears in military, cyber, institutional, predictive, and human-control contexts.

03

Expand the path

Continue to KillWebs.com when the question concerns several governed paths, shared dependencies, trust, or recomposition.

04

Make it answerable

Continue to Evulgare when a real deployed system needs evidence capture, lineage, authority reconstruction, assurance, or incident causality.

Thirteen-concept register

Search, filter, and select concepts to compare.

All cards are server-rendered. JavaScript adds local filtering, live comparison, and copy feedback without an account, analytics, persistent state, or a network request.

Reset13 of 13 concepts visible

Concept 01

Evidence provenance

5 surfaces

Where a record, observation, claim, model input, or inference came from and how it changed before reaching a decision-maker.

Can the conclusion be reconstructed from identifiable evidence and transformations?

Interactive labEvidence explorerReview and historyMethod and definitions
Open the cross-lab map

Learning goal

Trace a claim backward to sources and forward through transformations without confusing a fluent explanation with a reconstructable evidence chain.

Released surfaces

  1. Interactive labEvidence Lab

    Classify source state and inspect lineage before accepting a claim.

  2. Evidence explorerClaim Lineage

    Trace inputs, transformations, authority, reuse, and contestability.

  3. Review and historySource Review

    Inspect source identity, review state, and public dependencies.

  4. Method and definitionsMethodology

    Read the source hierarchy and bounded-support method.

  5. Interactive labAnswerability Lab

    Compare an ordinary event log with the evidence contract required for technical answerability.

Definitions and answers

ProvenanceClaim lineageSource dependency What is claim lineage?Why does the site distinguish a source statement from an inference or recommendation?

Claim Lineage examples

KillWebs learning bridge

When evidence crosses several organizations or possible paths, continue to KillWebs.com to examine trust, compatibility, and shared dependencies across the option space.

Open the KillWebs.com guide

Evulgare production handoff

A real deployed system needs append-oriented evidence, transformation, version, authority, and interface histories rather than a public educational diagram.

Decision Provenance

Concept 02

Model confidence versus evidence quality

4 surfaces

A model score describes output under a model and its inputs; evidence quality concerns source reliability, independence, freshness, relevance, contradiction, and provenance.

Is the displayed confidence supported by evidence that is complete, independent, current, and relevant?

SimulationInteractive labEvidence explorer
Open the cross-lab map

Learning goal

Keep model confidence, evidence quality, source independence, and ground truth as separate variables.

Released surfaces

  1. SimulationSimulation

    Declare confidence, inspect released evidence, and compare the two at debrief.

  2. Interactive labHuman Control Lab

    Reveal observations hidden by thresholding and ranking.

  3. Compare fluent narrative with claim-level lineage and contradictions.

  4. Evidence explorerEvidence Atlas

    Distinguish public evidence states without converting them into one score.

Definitions and answers

Model confidenceEvidence qualityEvidence statePublicly unspecified Is model confidence the same as evidence quality or positive identification?What is an evidence state?

Claim Lineage examples

KillWebs learning bridge

Use KillWebs.com when several paths appear to corroborate one another but may share the same source or dependency.

Open the KillWebs.com guide

Evulgare production handoff

A production interface must preserve uncertainty, evidence completeness, source dependence, model disagreement, and operating-distribution status at decision time.

Uncertainty Architecture

Concept 03

Automation bias

5 surfaces

Over-reliance on automated advice, including following a wrong recommendation or failing to act because the system did not alert.

Did the interface help the person independently assess the evidence, or train them to accept the machine?

Interactive labMethod and definitions
Open the cross-lab map

Learning goal

Recognize how defaults, queue pressure, repeated accuracy, confidence language, and hidden alternatives can turn review into ratification.

Released surfaces

  1. Interactive labHuman Control Lab

    Experience queue pressure, defaults, confidence anchoring, and approval fatigue.

  2. Record an initial judgment before machine ranking and confidence appear.

  3. Interactive labMachine Leadership Lab

    Inspect when nominal oversight becomes agency laundering.

  4. Method and definitionsRisk, Law & Control

    Review the conditions required for more than ceremonial control.

  5. Interactive labAnswerability Lab

    Inspect what the operator actually saw and whether the approval occurred before the point of no return.

Definitions and answers

Automation biasNominal controlTriage trap What is automation bias?How can an algorithm shape a human decision without authorizing force?What is the triage trap?

Claim Lineage examples

KillWebs learning bridge

In a distributed web, automation bias can be amplified when multiple nodes repeat the same machine-framed conclusion.

Open the KillWebs.com guide

Evulgare production handoff

Real-system answerability requires the interface state, timing, alternatives, warnings, abstention path, and evidence actually presented to the human.

Meaningful Human Judgment

Concept 04

Human authorization

5 surfaces

A human institution or operator provides the required permission for a consequential action, which is distinct from machine classification, prioritization, or recommendation.

Who possessed authority to approve the action, and was that authority meaningful under the actual conditions?

Interactive labEvidence explorerMethod and definitions
Open the cross-lab map

Learning goal

Separate a recommendation, approval event, intervention capability, and legal authority instead of treating one click as the whole decision.

Released surfaces

  1. Interactive labHuman Control Lab

    Compare assistance, approval, supervision, and post-activation autonomy.

  2. Evidence explorerAuthority Casebook

    Compare objective, approval, interruption, correction, and legal-authority owners.

  3. Evidence explorerClaim Lineage

    Inspect human and machine roles attached to a released claim.

  4. Method and definitionsRisk, Law & Control

    Review legal and human-factors questions around authorization.

  5. Interactive labAnswerability Lab

    Test why a final click cannot transfer responsibility when time, information, or intervention authority was absent.

Definitions and answers

Human-in-the-loop (HITL)Meaningful human controlInstitutional authority What makes human control meaningful?What does institutional authority mean in an AI-mediated decision chain?Why is a human click not automatically a liability transfer?

Claim Lineage examples

KillWebs learning bridge

Use KillWebs.com to inspect whether authority remains valid as a path is recomposed across different nodes and organizations.

Open the KillWebs.com guide

Evulgare production handoff

A deployed system must capture the active authority grant, scope, purpose, expiration, delegation chain, and whether approval reached the system in time.

Authority Boundaries

Concept 05

Preauthorization

4 surfaces

Authority granted before an event for a system to act when bounded conditions are later satisfied.

Which earlier human choices defined what the system could do when the live event arrived?

Interactive labMethod and definitions
Open the cross-lab map

Learning goal

Trace the apparent machine decision backward to mission purpose, evidence thresholds, boundaries, expiration, safe states, and prohibited actions.

Released surfaces

  1. Interactive labHuman Control Lab

    Configure policy before the synthetic event and reconstruct the resulting action.

  2. Interactive labHuman Control Lab

    Compare human-directed, AI-assisted, and preauthorized response.

  3. Interactive labMachine Leadership Lab

    Assign objective, priority, execution, override, and liability authority.

  4. Method and definitionsHow They Work

    See how human judgment can move earlier rather than vanish.

Definitions and answers

PreauthorizationMachine answerabilityOperational delegation Why are humans removed from some immediate kill-chain functions?What do human-in-the-loop, human-on-the-loop, and human-out-of-the-loop mean?Does operational delegation give a machine legal authority?

Claim Lineage examples

KillWebs learning bridge

Use KillWebs.com when preauthorization must attenuate or be re-evaluated across alternate paths and organizations.

Open the KillWebs.com guide

Evulgare production handoff

Production evidence must bind every action to the exact policy, configuration, authority envelope, and version that existed before activation.

Authority Boundaries

Concept 06

Communications loss

4 surfaces

The loss, delay, or degradation of a control link that can move real-time decisions onboard without automatically transferring unrestricted authority.

What may continue when the link disappears, what must stop, and what can no longer be supervised?

Interactive labEvidence explorerMethod and definitions
Open the cross-lab map

Learning goal

Separate communications independence from engagement authority and inspect the consequences of latency, bandwidth prioritization, and lost intervention paths.

Released surfaces

  1. Interactive labHuman Control Lab

    Allocate bandwidth, select a lost-link policy, and inspect the reconnection ledger.

  2. Interactive labHuman Control Lab

    Experience the relationship among delay, machine speed, and human review.

  3. Evidence explorerEvidence Atlas

    Compare public control descriptions and explicit unknowns.

  4. Method and definitionsHow They Work

    Review why authority may move before activation.

Definitions and answers

Lost linkSafe statePreauthorization Does losing communications mean a system selects targets autonomously?Why are humans removed from some immediate kill-chain functions?

Claim Lineage examples

KillWebs learning bridge

KillWebs.com is the next learning layer when a failed link forces the network to choose among alternate governed paths and shared dependencies.

Open the KillWebs.com guide

Evulgare production handoff

A real system needs evidence of link state, onboard authority, stale commands, safe holds, revocation, recovery, and every action completed during silence.

Resilience

Concept 07

Safe-state behavior

4 surfaces

A bounded system response such as halt, hold, loiter, return, quarantine, abstain, or terminate external effects when assumptions or authority fail.

What does the system do when it cannot remain within its validated evidence, authority, or environmental bounds?

Interactive labEcosystem bridge
Open the cross-lab map

Learning goal

Treat abstention and visible degradation as valid outcomes rather than interpreting continued action as resilience.

Released surfaces

  1. Interactive labHuman Control Lab

    Compare halt, loiter, return, reversible work, and bounded protective policies.

  2. Interactive labHuman Control Lab

    Configure fallback and expiration behavior before activation.

  3. Use a deterministic control gate to permit, reject, or require review.

  4. Ecosystem bridgeKillWebs.com

    Study graceful degradation and controlled recomposition at the network level.

Definitions and answers

Safe stateLost linkPublicly unspecified Does losing communications mean a system selects targets autonomously?What makes human control meaningful?

Claim Lineage examples

KillWebs learning bridge

KillWebs.com shows how a system preserves a reduced safe function while rejecting an untrusted or unauthorized alternative path.

Open the KillWebs.com guide

Evulgare production handoff

Production assurance requires proof that safe-state logic was active, entered when required, visible to operators, and recoverable without reviving stale authority.

Resilience

Concept 08

Predictive inference

4 surfaces

An estimate about an unobserved or future condition, which is different from observation, record retrieval, identity resolution, or a legal judgment.

What is being inferred, from which data, over what horizon, and for which consequential decision?

Interactive labEvidence explorerMethod and definitions
Open the cross-lab map

Learning goal

Separate physical or systemic forecasting, place prediction, person-risk inference, identity matching, and operational recommendation.

Released surfaces

  1. Classify observation, correlation, forecast, person-risk inference, explanation, and recommendation.

  2. Evidence explorerPredictive Enforcement

    Compare place forecasting, person prediction, watchlisting, identity resolution, and threat assessment.

  3. Interactive labPredictive Enforcement

    See how institutional attention changes the data entering the next forecast.

  4. Method and definitionsMethodology

    Read the operational-status and decision-consequence method.

Definitions and answers

Anticipatory intelligencePre-crime decision architecturePlace-based forecastingPerson-based prediction What is anticipatory intelligence?How is anticipatory intelligence different from pre-crime?How does place-based forecasting differ from person-based prediction?Is identity resolution the same as predicting future conduct?

Claim Lineage examples

KillWebs learning bridge

Use KillWebs.com when forecasts affect which path is selected or recomposed across a distributed option space.

Open the KillWebs.com guide

Evulgare production handoff

A deployed forecasting system needs evidence of inputs, target definition, horizon, calibration, distribution status, decision threshold, and the intervention attached to the inference.

Uncertainty Architecture

Concept 09

Source independence

4 surfaces

Whether apparently separate reports provide genuinely independent support or repeat one originating source, model, sensor, or institutional assumption.

Are the confirming records independent, or are several interfaces repeating one underlying source?

Interactive labEvidence explorerMethod and definitions
Open the cross-lab map

Learning goal

Detect circular reporting, duplicated sensor lineage, and correlated model outputs before treating volume as corroboration.

Released surfaces

  1. Interactive labEvidence Lab

    Inspect two apparent sources that descend from one origin.

  2. Interactive labHuman Control Lab

    Reveal duplicated and dependent observations hidden by fusion.

  3. Evidence explorerClaim Lineage

    Trace parent claims and public reuse without counting repetition as new evidence.

  4. Method and definitionsMethodology

    Read the source-independence rule.

Definitions and answers

Circular reportingProvenanceSource dependency Is model confidence the same as evidence quality or positive identification?What is claim lineage?

Claim Lineage examples

KillWebs learning bridge

KillWebs.com is the right place to inspect whether apparent path diversity depends on the same sensor, transport, trust authority, or data source.

Open the KillWebs.com guide

Evulgare production handoff

Real-system evidence should preserve source identity, transformations, shared dependencies, disclosure limits, permitted use, and revocation state.

Federated Trust

Concept 10

Proxy responsibility

5 surfaces

Explicit human or organizational responsibility for a machine-mediated decision when the machine cannot itself bear legal or moral responsibility.

Who had enough knowledge, authority, and intervention capability to accept responsibility for the machine-mediated outcome?

Interactive labEvidence explorerMethod and definitions
Open the cross-lab map

Learning goal

Prevent agency laundering by identifying upstream policy, procurement, data, integration, operation, review, and correction owners.

Released surfaces

  1. Interactive labMachine Leadership Lab

    Assign upstream decisions and expose the Accountability Shadow.

  2. Interactive labHuman Control Lab

    Expand the final action backward into a lifecycle authority graph.

  3. Evidence explorerAuthority Casebook

    Compare responsibility and interruption owners across six institutions.

  4. Method and definitionsRisk, Law & Control

    Review proxy governance and the responsibility gap.

  5. Interactive labAnswerability Lab

    Route each missing record to public learning, network analysis, production evidence, or the unresolved record.

Definitions and answers

Proxy responsibilityProxy governanceAgency laundering What is proxy responsibility?What is agency laundering?Why is a human click not automatically a liability transfer?

Claim Lineage examples

KillWebs learning bridge

Use KillWebs.com when responsibility crosses several participating organizations and no single path owner sees the complete decision structure.

Open the KillWebs.com guide

Evulgare production handoff

Evulgare is the production layer for reconstructing contributing factors without automatically assigning guilt, liability, blame percentages, or exoneration.

Evulgare Accountability

Concept 11

Institutional authority

5 surfaces

The human office, organization, policy, or legal mandate that permits, constrains, interrupts, corrects, or retires a machine-mediated process.

Which institution owns the objective, approval, interruption, correction, retirement, and legal consequence?

Evidence explorerInteractive labMethod and definitions
Open the cross-lab map

Learning goal

Distinguish practical machine control from formal permission, public office, fiduciary status, command authority, and liability.

Released surfaces

  1. Evidence explorerAuthority Casebook

    Compare eight authority owners and twelve machine functions.

  2. Interactive labMachine Leadership Lab

    Assign powers among Human, Shared, and Machine control.

  3. Evidence explorerClaim Lineage

    Inspect authority owners attached to a transformation.

  4. Method and definitionsRisk, Law & Control

    Review governance and weapons-review questions.

  5. Interactive labAnswerability Lab

    Trace policy, authority, interface, human judgment, and correction ownership through the evidence contract.

Definitions and answers

Institutional authorityOperational delegationCorrection owner What does institutional authority mean in an AI-mediated decision chain?What is the Institutional Authority Casebook?Does operational delegation give a machine legal authority?

Claim Lineage examples

KillWebs learning bridge

KillWebs.com examines whether authority follows a recomposed path and remains valid across participating nodes.

Open the KillWebs.com guide

Evulgare production handoff

A real system needs an auditable authority envelope that distinguishes CAN from MAY and preserves revocation, expiration, purpose, and delegation.

Authority Boundaries

Concept 12

Machine execution

5 surfaces

A machine performs a bounded external or internal state change after sensing, inference, policy checks, and authorization conditions are satisfied.

What did the machine actually execute, under which software, model, policy, authority, and interface state?

SimulationInteractive labEvidence explorerEcosystem bridge
Open the cross-lab map

Learning goal

Trace the difference between recommendation and execution and reconstruct the complete causal path behind a state change.

Released surfaces

  1. SimulationSimulation

    Observe a server-authoritative consequence after a bounded intervention.

  2. Interactive labHuman Control Lab

    Trace an action back through authorization, rule, evidence, and policy.

  3. Interactive labMachine Leadership Lab

    Compare human coordination, AI assistance, orchestration, and broad delegation.

  4. Evidence explorerAuthority Casebook

    Separate machine function from the institution retaining legal authority.

  5. Ecosystem bridgeAnswerability Lab

    Hand off real execution evidence, model and software lineage, authority, and outcome reconstruction to Evulgare.

Definitions and answers

Operational delegateMachine answerabilityServer-authoritative state Can Phalanx complete a defensive engagement automatically?Is an AI-enabled kill chain the same as an autonomous weapon?Why is a human click not automatically a liability transfer?

Claim Lineage examples

KillWebs learning bridge

KillWebs.com is the learning destination when execution can be reached through several possible governed paths.

Open the KillWebs.com guide

Evulgare production handoff

Production reconstruction needs the exact event, model and software versions, inputs, policy checks, authority state, human interface, resulting outcome, and continuous assurance that the deployed configuration still supports the permitted claim.

Continuous Assurance

Concept 13

Correction and supersession

4 surfaces

A later source, review, program, version, or accepted correction changes the current interpretation while preserving the earlier historical state.

What changed, which dependent claims require review, and what historical evidence must remain visible?

Review and historyEvidence explorer
Open the cross-lab map

Learning goal

Separate source unavailability, factual correction, withdrawal, supersession, evidence reclassification, and accepted publication history.

Released surfaces

  1. Review and historySource Review

    Inspect review state, successors, correction notices, and dependencies.

  2. Review and historyChange Impact

    Preview review obligations without changing publication truth.

  3. Review and historyChange Ledger

    Read accepted repository-authored changes and preserved prior states.

  4. Evidence explorerClaim Lineage

    Keep correction and supersession connected to the claim lineage.

Definitions and answers

SupersessionEvidence reclassificationSource withdrawalHistorical change ledger What happens when a source, program, or claim is superseded?How is the Historical Change Ledger different from the Change Impact Explorer?Does KillChains.com erase an earlier statement after accepting a correction?

Claim Lineage examples

KillWebs learning bridge

Use KillWebs.com when a source, capability, or authority change removes or alters several possible network paths.

Open the KillWebs.com guide

Evulgare production handoff

A real assurance system must identify which claims, assumptions, interfaces, evidence, and verification activities are invalidated by every material change.

Change Impact
Maximum 3. Extra selections are rejected in the browser and ignored server-side.

Concept matrix ready.

Comparative learning workspace

What changes when the concept moves across the chain?

The comparison is explanatory, not a score. It does not rank systems, institutions, countries, models, or visitors.

Concept

Evidence provenance

Where a record, observation, claim, model input, or inference came from and how it changed before reaching a decision-maker.

Central question
Can the conclusion be reconstructed from identifiable evidence and transformations?
Learning goal
Trace a claim backward to sources and forward through transformations without confusing a fluent explanation with a reconstructable evidence chain.
Released surfaces
5

Cross-lab route

  1. Evidence LabClassify source state and inspect lineage before accepting a claim.
  2. Claim LineageTrace inputs, transformations, authority, reuse, and contestability.
  3. Source ReviewInspect source identity, review state, and public dependencies.
  4. MethodologyRead the source hierarchy and bounded-support method.
  5. Answerability LabCompare an ordinary event log with the evidence contract required for technical answerability.

KillWebs: When evidence crosses several organizations or possible paths, continue to KillWebs.com to examine trust, compatibility, and shared dependencies across the option space.

Evulgare: A real deployed system needs append-oriented evidence, transformation, version, authority, and interface histories rather than a public educational diagram.

Decision Provenance

Concept

Human authorization

A human institution or operator provides the required permission for a consequential action, which is distinct from machine classification, prioritization, or recommendation.

Central question
Who possessed authority to approve the action, and was that authority meaningful under the actual conditions?
Learning goal
Separate a recommendation, approval event, intervention capability, and legal authority instead of treating one click as the whole decision.
Released surfaces
5

Cross-lab route

  1. Human Control LabCompare assistance, approval, supervision, and post-activation autonomy.
  2. Authority CasebookCompare objective, approval, interruption, correction, and legal-authority owners.
  3. Claim LineageInspect human and machine roles attached to a released claim.
  4. Risk, Law & ControlReview legal and human-factors questions around authorization.
  5. Answerability LabTest why a final click cannot transfer responsibility when time, information, or intervention authority was absent.

KillWebs: Use KillWebs.com to inspect whether authority remains valid as a path is recomposed across different nodes and organizations.

Evulgare: A deployed system must capture the active authority grant, scope, purpose, expiration, delegation chain, and whether approval reached the system in time.

Authority Boundaries

Concept

Proxy responsibility

Explicit human or organizational responsibility for a machine-mediated decision when the machine cannot itself bear legal or moral responsibility.

Central question
Who had enough knowledge, authority, and intervention capability to accept responsibility for the machine-mediated outcome?
Learning goal
Prevent agency laundering by identifying upstream policy, procurement, data, integration, operation, review, and correction owners.
Released surfaces
5

Cross-lab route

  1. Machine Leadership LabAssign upstream decisions and expose the Accountability Shadow.
  2. Human Control LabExpand the final action backward into a lifecycle authority graph.
  3. Authority CasebookCompare responsibility and interruption owners across six institutions.
  4. Risk, Law & ControlReview proxy governance and the responsibility gap.
  5. Answerability LabRoute each missing record to public learning, network analysis, production evidence, or the unresolved record.

KillWebs: Use KillWebs.com when responsibility crosses several participating organizations and no single path owner sees the complete decision structure.

Evulgare: Evulgare is the production layer for reconstructing contributing factors without automatically assigning guilt, liability, blame percentages, or exoneration.

Evulgare Accountability

Evulgare is live

The production-accountability handoff now resolves to specific platform areas.

KillChains.com keeps the public concept and synthetic learning path. The live Evulgare links show where the corresponding real-system evidence, provenance, authority, assurance, uncertainty, trust, resilience, or change-impact requirement belongs.

Live statusLive public site reviewed 2026-08-04
Observed releasev1.0.2
Platform areas9
BoundaryTechnical answerability, not automated liability

JUDGMENT

Meaningful Human Judgment

Preserve raw evidence, contrary indicators, alternatives, review time, abstention, and a chance for the human to form an independent hypothesis.

Open live Evulgare areaevulgare-judgment

Evulgare’s public site states that its public labs are synthetic, abstract, and non-operational. A live page establishes the company’s current public product framing; it does not independently prove a customer deployment, certification, legal conclusion, or measured operational performance.

Ecosystem boundary

Learn the failure here. Make the deployed machine answerable at Evulgare.

KillChains.com remains a synthetic simulation and public-research environment. KillWebs.com remains the sister learning environment for governed network paths. Stop using software that makes the nearest human explain a decision they could not see, verify, or control. Real-system evidence capture, software and model lineage, authority reconstruction, operator-view reconstruction, incident causality, and deployed-system answerability belong at Evulgare.com.

The Concept Matrix teaches how accountability concepts recur across public labs. Evulgare is now live and owns the production evidence layer for real systems; KillChains.com does not ingest or operate those systems.

MAKE THE MACHINE ANSWERABLE.Open Evulgare.comOpen the Answerability LabReview the ecosystem split