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 public source

Crime Anticipation System (CAS)

CAS purpose, national grid-cell design, twelve-week data window, human use of outputs, operational dates, and out-of-use status from December 2025. It does not establish a causal crime-reduction effect.

Current review Factual correction Non-mutating preview
Scenario

A material statement, date, status, attribution, or bounded conclusion may be wrong and requires claim-level reconciliation.

Automatic effect

The browser cannot rewrite the statement. A reviewed correction must identify the exact text, stronger evidence, affected routes, and first corrected release.

Open the correction pathway

01Selected evidence or claimCrime Anticipation System (CAS)
02Direct dependencies24 records require direct review
03Transitive reuse5 downstream checks
04Publication outputs5 public routes identified
05Human acceptanceNo state changes before reviewed write-back
24Direct review required

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

5Conditional 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.

29 of 29 review items shown.

Selected record

1 review item

Selected record · cas-algorithm-register-2025

Crime Anticipation System (CAS)

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
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary.

Directly supported claim

4 review items

Directly supported claim · claim-cas-risk-map-inference

CAS transformed recent records into place-based risk maps.

Direct review required
Current owner
National Police of the Netherlands
Why it appears
The claim directly depends on the selected record.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Re-evaluate the claim transformation, assumptions, unknowns, and non-establishment language.

Directly supported claim · claim-cas-input-observation

CAS used historical police incident and contextual records as inputs.

Direct review required
Current owner
National Police of the Netherlands / Dutch Algorithm Register
Why it appears
The claim directly depends on the selected record.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Re-evaluate the claim transformation, assumptions, unknowns, and non-establishment language.

Directly supported claim · claim-cas-discontinuation

Crime Anticipation System (CAS) was discontinued in December 2025.

Direct review required
Current owner
Dutch Algorithm Register / National Police of the Netherlands
Why it appears
The claim directly depends on the selected record.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Re-evaluate the claim transformation, assumptions, unknowns, and non-establishment language.

Directly supported claim · claim-cas-deployment-recommendation

Human analysts interpreted CAS outputs before deployment recommendations.

Direct review required
Current owner
National Police of the Netherlands
Why it appears
The claim directly depends on the selected record.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Re-evaluate the claim transformation, assumptions, unknowns, and non-establishment language.

Institutional authority case

1 review item

Institutional authority case · crime-anticipation-system

Crime Anticipation System

Direct review required
Current owner
National Police of the Netherlands
Why it appears
The case directly cites the selected source.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Recheck the authority map, machine functions, lifecycle status, and retained human powers.

Public research record

1 review item

Public research record · cas-netherlands

Crime Anticipation System

Direct review required
Current owner
Predictive Enforcement program
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Review visible status, labels, links, and cross-references on Crime Anticipation System.

FAQ answer or glossary definition

8 review items

FAQ answer or glossary definition · correction-owner

Correction owner

Direct review required
Current owner
Glossary term
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · place-versus-person-prediction

How does place-based forecasting differ from person-based prediction?

Direct review required
Current owner
FAQ answer
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · authority-casebook

Institutional Authority Casebook

Direct review required
Current owner
Glossary term
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · place-based-forecasting

Place-based forecasting

Direct review required
Current owner
Glossary term
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · transformation-statement

Transformation statement

Direct review required
Current owner
Glossary term
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · claim-lineage

What is claim lineage?

Direct review required
Current owner
FAQ answer
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · institutional-authority-casebook

What is the Institutional Authority Casebook?

Direct review required
Current owner
FAQ answer
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

FAQ answer or glossary definition · claim-transformation

Why does the site distinguish a source statement from an inference or recommendation?

Direct review required
Current owner
FAQ answer
Why it appears
The Source Review dependency graph identifies this public reuse path.
Required review
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Keep the concise answer or definition aligned with the controlling evidence state.

Public page or declared reuse

5 review items

Public page or declared reuse · 6b1d21f7a73a

Authority Casebook

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
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Review visible status, labels, links, and cross-references on Authority Casebook.

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
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. 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
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Review visible status, labels, links, and cross-references on Glossary.

Public page or declared reuse · e2860813f6ff

Predictive Enforcement

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
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Review visible status, labels, links, and cross-references on Predictive Enforcement.

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
Compare the exact published wording with stronger evidence and draft a non-destructive correction if necessary. Review visible status, labels, links, and cross-references on Source Review.

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

4 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 · authority-case-owner

Institutional authority case 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 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

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.

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.