Integrate founding explorations and bootstrap operational radar

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a09c77-b1a9-7eb3-b501-6cb24b458c97

ops/AUTOMATION-PROMPTS.md

@@ -0,0 +1,15 @@
+# Scheduling status and prompts
+
+Repository scheduling status: **not configured**. The source Grok archive contains
+external task/schedule UUIDs; ownership and execution were not verified. They are
+historical references only. No app notifications or email have been enabled here.
+
+Daily operator prompt: Review the watchlist for primary-source changes since the
+previous pass. Record evidence with provenance, publication/event and observation
+timestamps. Generate a draft for the event date, review each claim and mark gaps.
+
+Weekly operator prompt: Generate the ISO-week draft. Synthesize decision-relevant
+changes, unresolved contradictions, frontier evidence gaps, compendium edit proposals,
+and benchmark health. Link observation IDs. Do not pad an empty week with invented news.
+
+IR-WP-0003 tracks source adapters and an explicitly configured scheduler.

ops/CADENCE.md

@@ -0,0 +1,45 @@
+# Operating cadence
+
+Planned editorial targets; manually operated in v0.1. No scheduler is installed.
+
+## Daily — 21:30 Europe/Berlin
+
+Planned job name: `intelligence-radar-daily`
+
+Produce a brief (800–1,400 words) and store the pattern in `digests/daily/YYYY-MM-DD.md`.
+
+Must include:
+
+1. **Frontier & markets** — model releases, price or availability changes, benchmark rebases, capacity incidents.
+2. **Science of intelligence** — papers or results that change how intelligence is *modeled*, not just applied.
+3. **Engineering** — software, agents, chips, energy, inference stacks.
+4. **Political / legal / social** — statutes, suits, labor, safety designations.
+5. **Watchlist hits** — named thinkers or labs with a primary artifact.
+6. **Ledger actions** — what should be patched in `frontier/` or `task-router/` tomorrow.
+7. **Sources** — links to primaries only.
+
+Ignore rumor without a primary. Tag confidence per item: confirmed / reported / rumor.
+
+## Weekly — Sunday 20:00 Europe/Berlin
+
+Planned job name: `intelligence-radar-weekly`
+
+Produce `digests/weekly/YYYY-Www.md` (ISO week).
+
+Must include:
+
+- Top 10 events of the week, ranked by *decision relevance* (does it change who is Frontier, what things cost, what is legal, or what the theory of intelligence is).
+- Updated one-page frontier snapshot.
+- Compendium edit proposals (accept/reject next pass).
+- Open questions for the Task Router atlas (which evals saturated, which recipes broke).
+
+## On demand
+
+Any user task → Task Router ticket using `task-router/METHOD.md`.
+
+## Quality bar
+
+- No composite rank without naming the index version.
+- No “best model” without a task.
+- No copyrighted dumps; summarize.
+- Separate lab claim from independent eval.

ops/RUNBOOK.md

@@ -0,0 +1,42 @@
+# Operator runbook
+
+Run commands at the repository root with Python 3.11+. No installation is needed.
+
+1. Read INTENT, the source catalogs and the last reviewed digest. Choose a primary
+   artifact to inspect. Record event date separately from retrieval time.
+2. Capture the source hash (`sha256sum path/to/artifact`). Retain the artifact where
+   permitted; summarize rather than reproducing copyrighted text. A hash alone
+   cannot reconstruct an artifact or certify a claim.
+3. Prepare an observation JSON with the fields shown in
+   [the synthetic fixture](../examples/observation.json). Replace every synthetic
+   value with actual evidence. `observed_at` requires a timezone; `event_date` is
+   the event's date, not a future effective date. Record future plans in the claim.
+   Use source_kind primary/secondary/local; status reported/corroborated/disputed/retracted.
+   These are analyst assertions, not automatic verification results.
+4. Record and check:
+
+   ```bash
+   python3 -m intelligence_radar record /tmp/observation.json
+   python3 -m intelligence_radar validate
+   python3 -m intelligence_radar digest 2026-09-14
+   python3 -m intelligence_radar digest 2026-W38
+   ```
+
+   The CLI prints the immutable observation ID. Re-recording identical JSON is
+   idempotent. Changes create a new ID; for corrections add `supersedes` with the
+   old ID. The original remains available. Operators serialize writes; this local
+   prototype is not a concurrent database or a tamper-proof audit service.
+5. Review the generated draft and its linked evidence. Digests include all records
+   by event date, including disputes and corrections. A weekly draft is an evidence
+   listing, not an automatically synthesized newsletter. Add editorial synthesis,
+   distinguish source claims from independent evidence, and record evidence gaps.
+   Existing digests are never overwritten by the CLI; edit reviewed prose in Git.
+   Late evidence requires an explicit revision or follow-up, not a silent rewrite.
+6. For recommendations, complete task-router/TEMPLATE.md under the governing method.
+   Preserve unknowns. Real task outcomes later support calibration.
+7. Run `make check`, review changes, commit the evidence and artifacts. Update
+   workplan files and run `make sync` for Statehub projection.
+
+`make demo` uses a temporary directory; its synthetic observation never enters the
+repository ledger. No crawler, scheduled job, network fetch, or paid inference is
+triggered by these commands. The planned editorial cadence is in CADENCE.md.