Historical Change Ledger and Release Diff Explorer
Trace accepted KillChains.com corrections, program withdrawals, successor relationships, and evidence reclassifications. Each ledger item keeps the prior bounded statement beside the accepted current state, names the first corrected release, shows the evidence and public surfaces reviewed, and preserves unresolved unknowns.
Answer-first summary
It records accepted repository-authored corrections, withdrawals, supersessions, and evidence reclassifications while preserving the prior bounded statement, first corrected release, evidence, impact, and remaining unknowns.
Read the supporting sectionNo. Change Impact previews hypothetical review obligations. The Change Ledger publishes only events already accepted, tested, versioned, and preserved by the repository.
Read the supporting sectionNo. The earlier state remains visible for chronology and audit unless a separate privacy or legal obligation requires removal.
Read the supporting sectionAccepted history only
The Change Impact Explorer asks what would require review if something changed. This page records only changes that the repository already accepted, tested, versioned, and preserved in release history.
The earlier bounded statement remains visible as history. A correction cannot pretend that the prior publication never existed.
Every event identifies the first release that carried the corrected state and the accepted evidence that justified it.
A link failure, source reclassification, program withdrawal, interface correction, and verified successor have different meanings.
A corrected statement can still leave control modes, downstream use, physical-device behavior, or successor status unresolved.
Release chronology
The release number is the acceptance boundary for this ledger. It is not the date when an external program necessarily changed.
Accepted change register
Filters and comparison operate over released records only. JavaScript improves the interaction but is not required to read the complete ledger or submit a server-rendered comparison.
KC-CHANGE-001 · first corrected in v1.8.0
Before
A separate editor-domain address remained available as a public editorial contact beside the approved author identity.
Accepted
The sole public author, editorial, publisher-schema, feed, and security contact is mike@ns12.com; the former editor-domain address is not used as a fallback.
The repository owner explicitly directed one public contact identity, and v1.8.0 normalized every owning configuration, metadata, feed, security, documentation, and memory surface.
No current Claim Lineage record is assigned to this change.
The former address remains visible only in versioned release history and change proof; it must not reappear as a current public contact.
This correction does not establish production mailbox configuration, delivery, retention, or identity verification beyond the approved public address.
KC-CHANGE-002 · first corrected in v1.13.0
Before
CAS was described historically as a national Dutch place-based forecasting system used by police teams.
Accepted
The Dutch Crime Anticipation System is recorded as out of use, with an end date in December 2025; its earlier operation is retained as historical evidence.
The reviewed Dutch algorithm-register record identifies phase-out and a December 2025 end date. KillChains.com therefore separates the former operational design from its current discontinued state.
Descriptions of CAS inputs, risk maps, human interpretation, and past deployment remain available as historical program evidence. They must not be used alone to imply current operation.
Discontinuation does not prove the model was unlawful, ineffective in every context, or replaced by a functionally identical system.
KC-CHANGE-003 · first corrected in v1.13.0
Before
The Gangs Violence Matrix was a current Metropolitan Police named-person gang and violence intelligence-prioritization program.
Accepted
The former Matrix ceased operation and is retained for historical analysis; the Violence Harm Assessment owns the current successor description and current published statistics.
Current Metropolitan Police records and the reviewed program history identify the Matrix as decommissioned and the VHA as its successor framework.
The Matrix remains visible as historical evidence of the former program, its governance failures, and the reason a successor exists. It must not be silently deleted or described as current.
The successor relationship does not establish that VHA is machine learning, proves future violence, or resolves every criticism associated with the former Matrix.
KC-CHANGE-004 · first corrected in v1.14.0
Before
Before the Source Review layer, these source records exposed identity, class, date, and bounded support without a separate public lifecycle-review state.
Accepted
Twelve older program, product, audit, and framework records are explicitly classified as historical evidence and retained for chronology; none establishes current operation by itself.
Release 1.14.0 added a separate source-lifecycle plane so an older official or manufacturer page could remain useful without being mistaken for current capability or status evidence.
Each underlying source and bounded support statement remains unchanged. The historical label narrows current use rather than rewriting the source.
A historical label does not mean false, unlawful, ineffective, or obsolete in every jurisdiction; it means the source cannot establish current state alone.
KC-CHANGE-005 · first corrected in v1.14.0
Before
The source registry retained the manufacturer and belligerent description without a separate public review-state warning.
Accepted
The Lancet source is explicitly marked disputed or contested and remains attributed; it is not promoted into independent verification of control mode, field performance, or current configuration.
The source is a manufacturer or belligerent capability claim whose strongest operational implications are not independently established in the reviewed public record.
No current Claim Lineage record is assigned to this change.
The source title, publisher, link, date, and bounded support remain visible with attribution. The dispute label prevents stronger downstream wording.
Disputed does not mean disproved. It means the current evidence is insufficient for independent verification of the stronger claim.
KC-CHANGE-006 · first corrected in v1.14.1
Before
The expanded mission briefing was positioned inside a fixed-height immersive frame, allowing lower briefing content and launch controls to be clipped on some short desktop viewports.
Accepted
While the briefing is active, it owns the challenge-frame height and the covered console is removed from active layout; after launch, the normal immersive frame and console are restored at a visible header-safe position.
A user-provided 1178×590 screenshot exposed content outside the containing frame. Release 1.14.1 converted the active intro to content-driven containment and added a regression at the reported viewport.
No current Claim Lineage record is assigned to this change.
The user-reported failure, prior layout explanation, release proof, and regression remain in durable implementation history. The defective layout is not retained as current behavior.
The local browser regression does not prove every physical device, browser chrome configuration, assistive technology, or production cache path.
No accepted events match the current filters.
Release-diff comparison
The table contrasts release identity, change type, prior and accepted state, preservation rule, public impact, and unresolved unknowns. It does not rank the seriousness or correctness of the events.
v1.13.0 · KC-CHANGE-002
v1.13.0 · KC-CHANGE-003
v1.14.1 · KC-CHANGE-006
Historical Change Ledger
Events appear here only after source or code ownership is resolved, the prior state is preserved, tests pass, a release is named, and durable proof is written.
Review current source stateChange Impact Explorer
Previews estimate which records would require attention after a possible source or claim event. They do not become history merely because a visitor opens or shares the URL.
Build a hypothetical impact previewEcosystem boundary
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 ledger preserves accepted publication history. Evulgare is the production destination for preserving and reconstructing the evidence history of deployed machine systems.