Provenance and decisions
A dated record of the work
The history preserves what was recorded, what changed and what remains unverified. A date or hash does not establish scientific validity.
Read dates as source history
This chronology derives from the retained roadmap, governance register, source notes and owner decisions, the September case, and dated website changelogs and Git handoff records. It is not a complete project biography or a current activity assessment. Recorded dates keep their original scope; this draft adds no independent timestamp verification.
Chronology
11 July 2026 · work-area ledger
Eight retained entries, L0001–L0008, record worked maneuver records; core ontology and semantics; conformance and verification tooling; adversarial review and remediation; the public site and documentation; landscape and positioning analysis; knowledge-base ingestion and reconciliation; and provenance tooling.
The ledger retains hashes, declared counts and snapshot timestamps. All eight referenced timestamp proof files are absent from the preview. The recorded anchoring dates have not been independently verified here.
23–24 August 2026 · interim registers
The governance page identifies 23 August as the prior stewardship register. The roadmap identifies 24 August as the historical work-area register. These are source-register dates, not proof of a new institutional charter or continuing activity in every area.
5 September 2026 · archived case
The ShieldBreak / RoguePlanet case records a source-derived analysis, machine export 0.4.0 and later reporting revisions through 0.4.2. It retains provisional ontology bindings and zero perturbation runs. The new site presents that archive; it does not turn the archive's reporting checks into empirical evidence.
5 October 2026 · architecture and review iterations
The first preview added architecture and current-state orientation. The v3 review withdrew the Results pages for flawed methodology, clarified capability and version status, restored the landscape area and marked historical activity as unassessed and timestamp proofs as missing.
The v4 review aligned the reading path and corrected remaining claim, terminology and metadata inconsistencies. It removed the disputed implementation-variant to Software correspondence pending discussion. The planned project contact channel became an email alias, with the actual address still unavailable.
5 October 2026 · development source snapshot
Source notes distinguish intended architecture, bounded implementation, independent version identities, known failures and selected evaluation templates. The retained failures concern temporal/context handling in ontology consumers, native identity joins and measured-evidence carriage in ontology constraints. The six master evaluation templates record no completed runs.
6 October 2026 · development status
The previous Results pages were withdrawn because their methodology did not support their conclusions. Development content remains subject to revision, and the proposed Software mapping remains unresolved.
6 October 2026 · local successor draft
This review draft reorganizes the experience into Threat Lab, Research, How It Works, Build and About, and prepares a presentation of the archived case. It adds no new empirical experiment, public formal release, publication or deployment.
7 October 2026 · local correctness revision
Draft 0.2.1 corrects generated prose and distinguishes authored requirements from derived model conclusions. A fuller sanitized formal model accompanies the reading slice, with a source hash and explicit change record. The original archival bytes remain unchanged. This revision adds no new incident research, empirical validation or normative release.
8 October 2026 · website draft 0.3.0
The changelog dates the local homepage change from the prepared replay to the World State Explorer to 8 October. It retained the supporting pages and archival records without a new normative release. The inspected Git handoff for 0.3.0 is dated 9 October (a486ee4); the preceding 8 October commit described drafts only through 0.2.1.
9 October 2026 · Explorer 0.5.1 and independent review package
The local Explorer gained coordinated views, Environment and Execution, stacked what-if changes, claim challenges, source withdrawal and undo/reset while the website remained draft 0.3.0. Its propagation illustrates a prepared model rather than a measured security result.
Git records the component update as 957ad85 and the independent review package as 54b2c60. That package stated that its task had not pushed the branch or published, merged or deployed it. This is the package's creation-time scope, separate from the later handoff.
9 October 2026 · recorded prose and draft snapshot
The changelog, prose application record and handoff date website 0.3.1, approved prose 0.2.0 and local Explorer 0.5.2 to 9 October. The supplied reference Explorer remained 0.5.1; case/archive versions remained separate. These dated documents entered the inspected Git history on 19 October, so the document date is not presented as a 9 October commit or deployment.
19 October 2026 · draft-branch GitHub handoff
The retained handoff records preparation for GitHub on the historical branch codex/site-draft-0.3.0-handoff, carrying website 0.3.1 and local Explorer 0.5.2. Commit 5d66f2e is dated 19 October. This was draft-branch handoff publication, not production site deployment or a public normative MC release.
The commit did not change production-root web/site output. Its saved verification report carried the checks and limits of that handoff, including browser checks not repeated and clean installation unverified at that point. This chronology adds no deployment-platform audit or independently verified push timestamp. The website repository was verified private on 19 October.
Historical state and present availability differ
Recorded means a historical ledger entry exists. It does not mean the area is active today. Published was retained metadata for an existing artifact in that historical register. It does not indicate this draft has been published or that the artifact's substance was validated.
Retained work areas
| Area | Focus | Ledger entry |
|---|---|---|
| A01 | Core ontology and semantics | L0002 |
| A02 | Conformance and verification tooling | L0003 |
| A03 | Worked maneuver records | L0001 |
| A04 | Adversarial review and remediation | L0004; earlier evaluation withdrawn |
| A05 | Public site, documentation and brand | L0005 |
| A06 | Landscape and positioning analysis | L0006 |
| A07 | Knowledge-base ingestion and reconciliation | L0007 |
| A08 | Provenance and roadmap tooling | L0008 |
Current activity in these areas has not been independently assessed. This is historical orientation rather than a release schedule.
What provenance can establish
A hash helps identify bytes when the relevant artifact and manifest are available. A valid timestamp proof can establish that particular bytes were committed no later than a verified time. Neither establishes authorship, correctness, capability, conformance or practical value. The ledger's missing proof files prevent independent verification of its anchoring claims in this preview.
Carry unresolved questions forward
The withdrawn Results remain outside the served site. The implementation-variant to Software relation has no accepted replacement. A stronger coherent-witness support policy remains an open semantic choice. The case's specification/ontology pin mismatch remains explicit. This rebuild settles none of those questions through presentation.
History reviewed: 19 October 2026. Earlier entries retain their original dates and scopes. Sources include the retained roadmap, governance/source notes and owner decisions; archived case records; website changelog, prose application record and handoffs; and the identified Git commits. Repository history and byte identity do not establish scientific validity or an independently verified research timestamp.