chore: move the webinar script and plan into raw/notes

They are webinar deliverables rather than sources to ingest.

CLAUDE.md

@@ -34,7 +34,6 @@ raw/
 
 wiki/
   overview.md         # top-level synthesis and navigation
-  script-coverage.md  # machine-maintained: concept coverage vs the webinar script
   sources/            # one summary page per ingested raw source
   entities/           # people, orgs, projects, places, tools
   concepts/           # themes, ideas, methods, frameworks
@@ -70,7 +69,6 @@ Folder → required tag:
 | Folder / file          | Tag            |
 | ---------------------- | -------------- |
 | `wiki/overview.md`     | `#overview`    |
-| `wiki/script-coverage.md` | `#coverage`    |
 | `wiki/sources/*`       | `#source`      |
 | `wiki/entities/*`      | `#entity`      |
 | `wiki/concepts/*`      | `#concept`     |
@@ -122,29 +120,6 @@ Must include:
 - Follow-up questions
 - Whether this output changed existing pages
 
-### 4) Coverage File (`wiki/script-coverage.md`)
-
-Machine-read by the dashboard plugin, which parses the table positionally. The
-shape below is required exactly — a deviation renders as parse errors, not as a
-best-effort read.
-
-- `# Script coverage`
-- `#coverage` tag line
-- `## Metadata`, containing these two lines verbatim in this form:
-  - `- **Script:** ` followed by the raw script path in backticks
-  - `- **Last synced:** ` followed by a `YYYY-MM-DD` date
-- `## Coverage`, containing one markdown table with exactly these four columns in
-  this order: `Concept`, `Status`, `Station`, `Pinned`
-  - **Concept** — an Obsidian wikilink to a page in `wiki/concepts/`
-  - **Status** — exactly one of `covered`, `partial`, `absent`, lowercase
-  - **Station** — one of the seven station names spelled exactly as listed in
-    Workflow D, a comma-separated list of them, the lowercase word `all`, or an
-    em dash `—` when the status is `absent`
-  - **Pinned** — the lowercase word `yes`, or empty
-- `## Notes` and `## Related Pages` are free prose and are not parsed.
-
-The parser reads every markdown table in the file, so do not add a second table.
-
 ## Standard Workflows
 
 ### Workflow A: Ingest One Source
@@ -159,8 +134,6 @@ When user says "ingest <source>":
 6. Update `index.md`.
 7. Append ingest entry to `log.md`.
 8. Report what changed, what is uncertain, and suggested next source/questions.
-9. If this ingest created or modified any page in `wiki/concepts/`, run Workflow D
-   (Sync Script Coverage) before reporting.
 
 ### Workflow B: Answer Query
 
@@ -183,37 +156,6 @@ Run periodic health checks for:
 
 Write report to `wiki/lint-reports/YYYY-MM-DD-lint.md`, then update `index.md` and `log.md`.
 
-### Workflow D: Sync Script Coverage
-
-Maintains `wiki/script-coverage.md` — one row per page in `wiki/concepts/`, judged
-against the script named in that file's `**Script:**` metadata field.
-
-1. Read `wiki/script-coverage.md` and note every row where `Pinned` is `yes`.
-2. Read the script and every page in `wiki/concepts/`.
-3. For each concept, decide `Status` and `Station`:
-   - `covered` — the script delivers the idea, whether or not it uses the page's name.
-   - `partial` — the script gestures at it but never lands it.
-   - `absent` — the script never reaches it.
-   - `Station` is one of the seven — `Chat box`, `ReAct`, `Tools`, `Memory`,
-     `Skills`, `Process`, `OS` — spelled exactly as written here, or a
-     comma-separated list of them, or the lowercase word `all`, or `—` when absent.
-4. **Never modify a row whose `Pinned` is `yes`** — not its status, not its station.
-   A pinned row is the user's judgment and outranks yours.
-5. Add rows for concept pages with no row. Remove rows whose concept page no longer exists.
-   A pinned row whose concept page no longer exists is still removed — step 4
-   protects the user's judgement about a live concept, not a dangling row.
-6. Update `**Last synced:**` to today.
-7. Update `index.md` and append a `sync` entry to `log.md`.
-
-Run this workflow:
-
-- at the end of any ingest that creates or modifies a page in `wiki/concepts/`
-- whenever the script file itself changes
-- on the explicit `sync script coverage` intent
-
-The coverage baseline is always the raw script. Ingesting the script into
-`wiki/sources/` does not change the baseline.
-
 ## Citation & Evidence Policy
 
 - Prefer citing wiki source summaries (`wiki/sources/*.md`) rather than raw files in normal answers.
@@ -235,7 +177,6 @@ Supported intents:
 - "lint wiki"
 - "show recent changes"
 - "suggest next sources"
-- "sync script coverage"
 
 Always execute intents according to workflows above.
 

index.md

@@ -18,11 +18,7 @@ Every wiki page carries a page-type tag under its H1 (`#source`, `#entity`, `#co
 - [[2026-07-22-ai-is-stupid]] — YouTube short (author unknown): "stupid AI" = model minus context minus harness; Nobel-vs-employee analogy _(raw: ИИ глупый!.md)_
 - [[2026-07-24-youre-reading-way-too-much-code]] — Theo Browne (video): make more cheap code, four tiers of code, 100:1 slop-to-ship verification _(raw: You're reading way too much code.md)_
 
-**Raw, not yet ingested:** `raw/sources/Agentic Engineering, explained by a 10x developer.md` · `raw/sources/Webinar Plan - From Chat Box to Your Own OS.md` · `raw/sources/Webinar script.md`
-
-## Coverage
-
-- [[script-coverage]] — every concept vs `raw/sources/Webinar script.md`; 5 covered, 4 partial, 10 absent
+**Raw, not yet ingested:** `raw/sources/Ideas for webinar.md` · `raw/sources/Webinar Plan - From Chat Box to Your Own OS.md` · `raw/sources/Webinar script.md` · `raw/sources/my theses.md`
 
 ## Entities
 

log.md

@@ -6,7 +6,7 @@ Entry format:
 
 ```
 ## YYYY-MM-DD — <operation>
-- Intent: ingest | query | lint | maintenance | sync
+- Intent: ingest | query | lint | maintenance
 - Input: <source path / question / scope>
 - Pages changed: [[...]], [[...]]
 - Notes: <what changed, uncertainty, next steps>
@@ -147,11 +147,3 @@ Entry format:
 - Pages updated: [[make-more-cheap-code]] (next-question marked answered, link added), [[leave-less-room-for-imagination]] (new next-question: drift harnessed as a sandboxed ambiguity diagnostic — synthesis, tentative), `index.md` (Queries section).
 - Notes: Pure synthesis, no new source — every mapped pattern is grounded in corpus use cases (Nina/Yulia job descriptions, candidate KB, sourcing; Larysa spec ambiguity; Allie's anti-AI-language checker-skill precedent). Key reframes with durable value: (1) the fresh-agent misread test inverts [[leave-less-room-for-imagination]] — drift becomes a diagnostic when sandboxed; (2) [[solve-first-then-skillify]] populates skills in two species, producers and checkers. Flagged honestly: the whole mapping is argument-by-analogy with no measured claim; Nina's transcript-beats-summary finding is a standing counterweight to summary-based review.
 - Next: decide whether "checker skills" earns a slide on the webinar's skills rung; the webinar-deliverable docs (`Ideas`, `Plan`, `script`, `my theses.md`) remain un-ingested; first lint pass still overdue (9 sources, 18 concepts, 2026-07-24 now has 1 query, 0 lint reports).
-
-## 2026-07-28 — sync (script coverage, initial)
-- Intent: sync script coverage
-- Input: first run of Workflow D, establishing `wiki/script-coverage.md`.
-- Pages created: [[script-coverage]] (coverage) — 19 rows, one per concept page.
-- Pages updated: `CLAUDE.md` (folder convention, `#coverage` tag row, Workflow D, new intent), `index.md` (new Coverage section; corrected the not-yet-ingested list — `Ideas for webinar.md` and `my theses.md` were listed under `raw/sources/` but live in `raw/notes/`, and `Agentic Engineering, explained by a 10x developer.md` was missing entirely).
-- Notes: Initial assessment is 5 covered, 4 partial, 10 absent. Eight of the ten absent are human-side or strategy-side per the grouping in index.md; the other two — [[integration-dead-ends]] and [[leave-less-room-for-imagination]] — are machine-side, absent because the script demos the happy path and never reaches connector gating or spec ambiguity. The `ReAct` station carries no wiki concept. No concept pages were edited.
-- Next: decide whether the human-side cluster earns a station or is a deliberate cut; decide separately whether the two absent machine-side failure modes belong in the demo; pin the rows that are decided so future syncs leave them alone.