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.

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

Selected Claim Lineage record

A U.S. watchlist record is not itself an arrest warrant or criminal finding.

The FBI’s public watchlisting overview distinguishes a threat-screening record from the downstream legal action another agency may take under its own authority.

KillChains.com synthesis Scheduled review Non-mutating preview
Scenario

The review date has arrived. Recheck the bounded statement, status, attribution, evidence class, and downstream use without presuming that anything is wrong.

Automatic effect

No factual state changes automatically. The event creates a human review queue only.

Open the correction pathway

01Selected evidence or claimA U.S. watchlist record is not itself an arrest warrant or criminal finding.
02Direct dependencies0 records require direct review
03Transitive reuse10 downstream checks
04Publication outputs3 public routes identified
05Human acceptanceNo state changes before reviewed write-back
0Direct review required

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

10Conditional downstream review

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

0Historical records preserved

Earlier evidence that remains necessary for chronology or audit.

6No automatic truth change

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

16 of 16 review items shown.

Supporting source or successor

2 review items

Supporting source or successor · pclob-watchlist-2025

Terrorist Watchlist Report and Recommendations

No automatic truth change
Current owner
Public source registry and editorial review owner
Why it appears
This source supports the selected claim and must remain visible while the claim event is reviewed.
Required review
Recheck the bounded statement, status, attribution, and continued public use.

Supporting source or successor · fbi-watchlisting-overview-2024

Terrorist Watchlisting Transparency Document

No automatic truth change
Current owner
Public source registry and editorial review owner
Why it appears
This source supports the selected claim and must remain visible while the claim event is reviewed.
Required review
Recheck the bounded statement, status, attribution, and continued public use.

Directly supported claim

1 review item

Directly supported claim · claim-watchlist-not-warrant

A U.S. watchlist record is not itself an arrest warrant or criminal finding.

Conditional downstream review
Current owner
KillChains.com editorial review
Why it appears
The claim directly depends on the selected record.
Required review
Recheck the bounded statement, status, attribution, and continued public use. Re-evaluate the claim transformation, assumptions, unknowns, and non-establishment language.

Institutional authority case

1 review item

Institutional authority case · terrorist-watchlisting-lifecycle

U.S. terrorism-watchlisting lifecycle

No automatic truth change
Current owner
Interagency watchlisting enterprise led by the FBI Threat Screening Center for acceptance and management functions
Why it appears
The case depends on an affected claim in its authority analysis.
Required review
Recheck the bounded statement, status, attribution, and continued public use. Recheck the authority map, machine functions, lifecycle status, and retained human powers.

Public page or declared reuse

3 review items

Public page or declared reuse · 6b1d21f7a73a

Authority Casebook

No automatic truth change
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Recheck the bounded statement, status, attribution, and continued public use. Review visible status, labels, links, and cross-references on Authority Casebook.

Public page or declared reuse · 39b10bb19026

FAQ

No automatic truth change
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Recheck the bounded statement, status, attribution, and continued public use. Review visible status, labels, links, and cross-references on FAQ.

Public page or declared reuse · e2860813f6ff

Predictive Enforcement

No automatic truth change
Current owner
Owning public registry and page template
Why it appears
The route contains or reuses an affected source or claim.
Required review
Recheck the bounded statement, status, attribution, and continued public use. Review visible status, labels, links, and cross-references on Predictive Enforcement.

Discovery artifact

5 review items

Discovery artifact · content-index

content-index.json

Conditional downstream review
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

Conditional downstream review
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

Conditional downstream review
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

Conditional downstream review
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

Conditional downstream review
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

4 review items

Durable owner and proof · claim-lineage-owner

Claim transformation and lineage register

Conditional downstream review
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 · authority-case-owner

Institutional authority case register

Conditional downstream review
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 Institutional authority case 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

Conditional downstream review
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

Conditional downstream review
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.

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.