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.

Evidence governance · Read-only change preview

Change Impact and Supersession Explorer

Begin with one existing public source or claim. Preview every direct and transitive review obligation created by a correction, withdrawal, supersession, evidence reclassification, unavailable link, or scheduled review—without changing any source, claim, route, or artifact.

151 allowlisted subjects6 bounded event typesPreview onlyNo browser mutation

Answer-first summary

Direct answers

Release 1.24.0 · reviewed · evidence states

What does the Change Impact Explorer do?

It begins with an existing source or claim and derives which direct claims, descendant claims, authority cases, public records, answers, simulations, discovery files, and durable owners require human review.

Read the supporting section

Does the preview change a source or claim?

No. It is read-only and non-mutating. No browser action can edit a registry, accept a correction, crawl a source, regenerate an artifact, or certify a claim.

Read the supporting section

Does an unavailable link make a claim false?

No. Link reachability, source withdrawal, factual correction, evidence reclassification, and supersession are separate events with different review consequences.

Read the supporting section

Why this exists

Evidence changes should propagate through a visible review chain—not through silent edits.

A corrected source may affect a claim, a derived claim, an authority case, an answer, a simulation prompt, and several machine-readable discovery files. The browser can preview that dependency cascade, but only a reviewed repository change can alter publication truth.

01

Separate the event

Link failure, source withdrawal, factual correction, program replacement, and evidence reclassification are different events with different consequences.

02

Trace the dependency

Direct source edges and descendant claim edges remain distinct so one change does not silently rewrite unrelated material.

03

Preserve chronology

Superseded and withdrawn records remain available for audit and historical comparison unless a separate legal or privacy obligation requires removal.

04

Require human acceptance

Generated previews create a review queue. They do not edit data, accept a correction, publish a new status, or certify truth.

Interactive preview

Select a current source or claim and one bounded change event.

The submitted URL is stable and shareable, but its result is an educational review preview—not a repository transaction or accepted correction.

Reset to recorded supersession
Historical Matrix → current successor Preview the existing source-level supersession from the former Gangs Violence Matrix record to the current Violence Harm Assessment source. Decision-support source becomes unavailable Show why link failure creates a preservation and review task rather than automatically negating the program statement. Manufacturer statement reclassified Trace how a change in evidence label affects manufacturer wording, claim boundaries, system records, and authority analysis. Program-status correction Preview review work if a current program register corrects a date, status, or operational description. High-level synthesis corrected Follow a central editorial synthesis into derived claims, casebook records, public routes, answers, and discovery outputs. Scheduled review of a consequential claim Create a review queue without presuming that the current claim or its sources are wrong.

Selected public source

HARPY product description

Manufacturer-described autonomous search and attack against emitting radar targets.

Current review Evidence reclassification Non-mutating preview
Scenario

The same underlying material may need a different evidence label—for example, manufacturer-described, independently corroborated, disputed, historical, or publicly unknown.

Automatic effect

A label change does not rewrite the source, establish a new fact, or resolve undisclosed operating details. Every dependent wording choice must be reviewed.

Open the correction pathway

01Selected evidence or claimHARPY product description
02Direct dependencies18 records require direct review
03Transitive reuse6 downstream checks
04Publication outputs6 public routes identified
05Human acceptanceNo state changes before reviewed write-back
18Direct review required

Selected owners and records whose current wording or status may be affected.

6Conditional downstream review

Derived claims, reuses, and outputs that may inherit the change.

0Historical records preserved

Earlier evidence that remains necessary for chronology or audit.

0No automatic truth change

Records shown for context but not altered by the event alone.

24 of 24 review items shown.

Selected record

1 review item

Selected record · iai-harpy

HARPY product description

Direct review required
Current owner
Public source registry and editorial review owner
Why it appears
The selected event begins at this source record.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns.

Directly supported claim

2 review items

Directly supported claim · claim-harpy-manufacturer-statement

IAI describes HARPY as autonomously seeking and striking emitting targets.

Direct review required
Current owner
Israel Aerospace Industries
Why it appears
The claim directly depends on the selected record.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Re-evaluate the claim transformation, assumptions, unknowns, and non-establishment language.

Directly supported claim · claim-harpy-evidence-boundary

The HARPY public record leaves important control and performance details unresolved.

Direct review required
Current owner
KillChains.com editorial review
Why it appears
The claim directly depends on the selected record.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Re-evaluate the claim transformation, assumptions, unknowns, and non-establishment language.

Simulation or laboratory

1 review item

Simulation or laboratory · harpy

IAI HARPY

Direct review required
Current owner
Human Control case
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Confirm that the teaching prompt still distinguishes synthetic values from public evidence.

Public research record

4 review items

Public research record · harpy

HARPY

Direct review required
Current owner
Atlas system
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on HARPY.

Public research record · israel

Israel

Direct review required
Current owner
Atlas country
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Israel.

Public research record · iai

Israel Aerospace Industries / ELTA

Direct review required
Current owner
Technology provider
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Israel Aerospace Industries / ELTA.

Public research record · iai-harpy

Israel Aerospace Industries / ELTA → harpy

Direct review required
Current owner
Company-system relationship
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Israel Aerospace Industries / ELTA → harpy.

FAQ answer or glossary definition

2 review items

FAQ answer or glossary definition · current-autonomous-weapons

Are fully autonomous lethal weapons currently used?

Direct review required
Current owner
FAQ answer
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · human-out-of-the-loop

Human-out-of-the-loop after activation

Direct review required
Current owner
Glossary term
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Keep the concise answer or definition aligned with the controlling evidence state.

Public page or declared reuse

6 review items

Public page or declared reuse · 8051357b247d

Evidence Atlas

Conditional downstream review
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Evidence Atlas.

Public page or declared reuse · 39b10bb19026

FAQ

Conditional downstream review
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on FAQ.

Public page or declared reuse · 69698cd63321

Glossary

Conditional downstream review
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Glossary.

Public page or declared reuse · ed6ec8465204

Human Control Lab

Conditional downstream review
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Human Control Lab.

Public page or declared reuse · 9b072d16f0a4

Source Review

Conditional downstream review
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Source Review.

Public page or declared reuse · dac6c37ec374

Technology Providers

Conditional downstream review
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Reassess attribution and evidence label while preserving the underlying statement and unknowns. Review visible status, labels, links, and cross-references on Technology Providers.

Discovery artifact

5 review items

Discovery artifact · content-index

content-index.json

Direct review required
Current owner
Generated discovery pipeline
Why it appears
Affected public routes and answer-first summaries may need refreshed descriptions.
Required review
Regenerate or revalidate content-index.json only after the owning public records are accepted.

Discovery artifact · json-feed

feed.json

Direct review required
Current owner
Generated discovery pipeline
Why it appears
At least one affected page participates in the public JSON Feed.
Required review
Regenerate or revalidate feed.json only after the owning public records are accepted.

Discovery artifact · rss

feed.xml

Direct review required
Current owner
Generated discovery pipeline
Why it appears
At least one affected page participates in the public feed.
Required review
Regenerate or revalidate feed.xml only after the owning public records are accepted.

Discovery artifact · llms

llms.txt

Direct review required
Current owner
Generated discovery pipeline
Why it appears
The nonstandard discovery map must remain aligned with the reviewed public routes.
Required review
Regenerate or revalidate llms.txt only after the owning public records are accepted.

Discovery artifact · source-index

source-index.json

Direct review required
Current owner
Generated discovery pipeline
Why it appears
Review metadata and dependency counts are machine-readable.
Required review
Regenerate or revalidate source-index.json only after the owning public records are accepted.

Durable owner and proof

3 review items

Durable owner and proof · claim-lineage-owner

Claim transformation and lineage register

Direct review required
Current owner
Repository maintainer and reviewed write-back process
Why it appears
Accepted changes require current proof, supersession metadata, and pointer integrity.
Required review
Update Claim transformation and lineage register after accepted changes, preserving source identity, supersession metadata, and proof.

Durable owner and proof · proof-pointer-owner

Release proof, durable pointer ledger, and package manifest

Direct review required
Current owner
Repository maintainer and reviewed write-back process
Why it appears
Accepted changes require current proof, supersession metadata, and pointer integrity.
Required review
Update Release proof, durable pointer ledger, and package manifest after accepted changes, preserving source identity, supersession metadata, and proof.

Durable owner and proof · source-review-owner

Source identity and review ledger

Direct review required
Current owner
Repository maintainer and reviewed write-back process
Why it appears
Accepted changes require current proof, supersession metadata, and pointer integrity.
Required review
Update Source identity and review ledger after accepted changes, preserving source identity, supersession metadata, and proof.

Truth boundary

A dependency preview is not a fact-check verdict or a publication edit.

The selected event identifies where a human maintainer must look. It does not decide the answer.

01

No source, claim, evidence label, route, or discovery artifact changes through this preview.

02

External link reachability does not determine whether a bounded historical proposition is true or false.

03

Withdrawal or supersession preserves the earlier audit record; it does not erase chronology.

04

Challenge scores, hidden answers, synthetic ground truth, and server-authoritative simulation state remain unchanged.

05

Legal authority, real-world operational status, and undisclosed control arrangements are not inferred from the event.

No runtime crawl and no browser write path. This page does not fetch an external source, inspect a live website, edit a PHP registry, regenerate discovery files, accept anonymous corrections, or promote a report claim into public fact.

Reviewed change protocol

What an accepted change would require.

  1. Verify the event. Establish the correction, withdrawal, successor, evidence-class change, or review condition using a bounded, attributable record.
  2. Update the once-only owner. Change the source, review, claim, case, page, FAQ, or glossary registry that actually owns the fact.
  3. Review every derived dependency. Inspect direct and transitive claims, public reuses, authority maps, simulations, and answer-first summaries.
  4. Preserve history. Record supersession and correction metadata without silently erasing the earlier public state.
  5. Regenerate and test. Rebuild discovery artifacts, run focused and regression audits, verify links, and retest the extracted release.
  6. Publish with proof. Increment the release, update durable evidence and pointers, package the root-deploy ZIP, and disclose unavailable checks honestly.
Inspect Claim LineageOpen Source ReviewCompare authority owners

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.

Change Impact previews publication review obligations only. Evulgare addresses operational change and incident evidence for deployed systems; this browser cannot change either publication truth or a real system.

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