Agent data

The current machine contract comes first: data.json for standing claims, updates.json for chronology, process.json for the public-safe ASAP phase projection, and training.json for the corpora register. Course states render below from the same shared data the course workspace uses; nothing on this page hardcodes a course state.

Current machine brief

Loading current files

Manifest snapshot: Loading…
Active standing claims: Loading…
Status mix: Loading…

Latest recorded event

Loading the append-only feed…

View full event history

Rendered from shared data

Current course states

These cards render from the same standing claims and process projection as the course workspace. Failed or inconsistent loads are shown as unavailable. The machine form — projected phases and each course's re-earned position — is process.json.

Standing routing exclusions: do not use completion percentages, treat 150 standards as 150 questions, blanket re-QC unchanged accepted items, or build local substitutes for current factory or course-owned routes.

Open the active course's evidence map.

Recovery audit posture — 2026-08-19 snapshot

Proof at that audit: 2 factory-proof classes survived; every other claim was input-only, re-earn-required, void, or blocked.
Machinery at that audit: 16 hand-rolled targets were listed for approval-gated replacement or deletion. Listing is not deletion authority.
Execution: this dashboard is a read-only status surface. It grants no authority to write course data, spend, file, mark, commit, merge, delete, deploy, or release.
Factory rule: use committed canonical tools exactly as documented. When no route exists, return BLOCKED_CONTRACT; never create a local bridge.
Current course targets: read them from the shared timeline data and process.json at render time. This page holds no hardcoded course state; if a course-state literal appears in this file, treat it as a bug.

Hand off to an agent

Three handoffs, all built from the current structured sources at click time. The reviewer handoff asks for a standing summary. The builder handoff instructs an agent advancing the active course at its current stage, with the stage contract inline. The bundle is one JSON file for an agent that needs an upload.

Handoffs are assembled when clicked; no additional current-state file is stored on the site.

Use these sources in this order

The structured files are the current contract. Each claim carries its own observation or status timestamp; the file snapshot never makes an older claim new.

Claims manifest

Authoritative standing state: stable claim ids, status, scope, exclusions, evidence, access, and row-level timestamps.

Open data.json

Process contracts

The public-safe ASAP phase requirements, route, verification strings, and each course's re-earned position.

Open process.json

Trace crosswalk

Historical publication phases mapped to the current ASAP route. Read crosswalk.json for the measured row count; mappings preserve evidence scope and grant no current phase credit.

Open crosswalk.json

Training-assets register

Counts, SHA-256 digests, status, and private homes for the model-training and eval corpora. The register is public; the corpora never are.

Open training.json

Active course plan

The active course's lifecycle position, hold, and evidence links. Routing view only; it grants no execution authority.

Open HumGeo plan

Recovery audit evidence

Durable private packet containing the 25-row damage register, decision book, three-day plan, 16-row purge manifest, source hashes, and audit runlog.

Open evidence packet

Updates feed

Append-only chronology, newest first. Use it to understand what changed and when.

Open updates.json

Four-course blueprint audit baseline — 2026-08-20

Strict release-quality baseline captured before the LS-handoff target was corrected. Use it for gap evidence, not for the current milestone or ETA.

Open baseline audit

Integrity manifest

Published SHA-256 digests for the structured files and retained reports. A matching hash proves byte identity, not factual freshness.

Open hashes.json

Training-assets register

The catalog of model-training and eval corpora: counts, digests, status, and where the private bytes live. The corpora hold course content and answer text, so the data itself never lands on this site; a SHA-256 here lets a holder of the private bytes verify identity. Measured verdicts behind the register are on the Retro page.

Asset	Rows	Status	Purpose
Loading training.json…

Dated narrative references

These reports preserve the 2026-08-17 reporting snapshot. They are historical: do not use their counts as current without reconciling them against data.json and updates.json.

Agent accounting — 2026-08-17

Claim-by-claim evidence dossier and Langfuse reading guide captured for the original report.

Open snapshot

Four-course standings — 2026-08-17

Human narrative with the links and conclusions available at that reporting cutoff.

Open snapshot

Companion receipts — 2026-08-17

Receipt index supporting that dated narrative.

Open snapshot

How to read the contract

Trace a claim: Start with its claim_id in data.json, then follow the evidence entries. Use the Claims explorer when a visual filter is faster.
Check what you can access: evidence_access states whether a receipt is shared, human-only, available after an invite, machine-local, or not yet expected.
Check freshness: Age each claim from its own observed_at or status_at. A claim older than 48 hours with no successor receipt is a question, not a current fact, unless it is marked settled: true.
Read status precisely: OBSERVED records a named check; PLANNED is queued; BLOCKED records a named dependency; MISSING records a verifier or evidence gap, not proven global absence. None implies LS review readiness or release by itself.
Keep the milestones separate: Course lifecycle follows the publication runbook, ASAP edition, 2026-09-01. Each course has one re-earned position; queued work is not phase credit. LS REVIEW READY remains a planning milestone, not an LS disposition or production outcome.
Open Langfuse evidence: Langfuse lives at us.cloud.langfuse.com, project incept-durey. Accept the organization invite before following trace ids.

Byte integrity

Fetch a published file, hash its raw bytes, and compare the result below. Matching digests prove that you hold the published bytes; they do not upgrade a dated observation into a current one.

curl -s <file URL> | shasum -a 256

File	Bytes	SHA-256
Loading integrity manifest…

Authority rule: data.json governs standing claims; updates.json governs event chronology. Narrative reports are dated context, and hashes prove bytes only.