🔄 Registry-reported update — August 19, 2026. The exact runnable-file count is derived from the registry and recorded inside manifest.json. This wrapper does not independently attest that a daily propagation job ran or that the ZIP matches a published hash; treat the date as directory metadata until an artifact digest and verification receipt are exposed.
Importance bars, factory chain, and single-engine routing
Every task now carries a 1-5 importance score (max of frequency, ads/revenue, and gating) so a pixel install can outrank a long SOP. The dashboard shows the Content Factory line — Produce, Process in Descript, Post, Promote — with Digital Plumbing as Gate. Model routing is first-class for Claude-only and Grok-only operators; multi-engine is optional throughput on the same line. 123 incomplete skills inventoried; highest-value ads and access stations fleshed. How we closed the factory gap.
Monthly capability refresh — and the first entry this panel has been able to record since it was built
Reviewed the July 2026 releases across Anthropic, Google and OpenAI and rewrote the operating layer against them. Opus 5’s per-turn reasoning-effort dial (July 24) became a routing rung of its own — raise effort before raising model — and every scheduled job now names a fallback tier, after Fable’s two-and-a-half-week suspension in June proved a single-engine routing table is a single point of failure. Sonnet 5 replaces the smaller models as the default for any step that chains tool calls. The same run found three of three download buttons advertising hand-typed counts frozen months earlier: /dealcon offered 10 skills for a 19-skill pack, and both Task Library surfaces said 239 for a 247-file download. Counts are now derived from each pack’s own VERSION.txt on every daily run. What broke and what we changed.
Gap in the record. One monthly cycle is missing from this record. The panel used to live inside the dashboard app itself, which moved to a host we hold no write credential for — so from June 10 to August 1 there was no way to append to it, while the daily “updated” badge above it kept stamping the correct date. The gap is left visible on purpose. A proof-of-recursion panel that hides the months it could not record is not proof of anything.
Task Library dashboard published
239 documented tasks across 13 categories, each a runnable skill.md, with the searchable dashboard and the downloadable pack. How the library was built.
Every monthly refresh appends an entry here, and this panel lives in this page’s own content — not inside the dashboard app — so the job that is supposed to write to it always can. The changelog is the proof of recursion; a panel nothing can append to proves nothing.
Monthly capability refresh — and the first entry this panel has been able to record since it was built
Reviewed the July 2026 releases across Anthropic, Google and OpenAI and rewrote the operating layer against them. Opus 5’s per-turn reasoning-effort dial (July 24) became a routing rung of its own — raise effort before raising model — and every scheduled job now names a fallback tier, after Fable’s two-and-a-half-week suspension in June proved a single-engine routing table is a single point of failure. Sonnet 5 replaces the smaller models as the default for any step that chains tool calls. The same run found three of three download buttons advertising hand-typed counts frozen months earlier: /dealcon offered 10 skills for a 19-skill pack, and the Task Library surfaces mixed a 239-file hub count with larger versioned downloads. This page now labels the live registry, runnable ZIP, and archived bundle separately; upstream PR #1 makes the Task Library counts build-derived after merge. What broke and what we changed.
Gap in the record. One monthly cycle is missing from this record. The panel used to live inside the dashboard app itself, which moved to a host we hold no write credential for — so from June 10 to August 1 there was no way to append to it, while the daily “updated” badge above it kept stamping the correct date. The gap is left visible on purpose. A proof-of-recursion panel that hides the months it could not record is not proof of anything.
Task Library dashboard published
Legacy migration imported 239 local task-skill files across 13 categories. That count did not prove definitive-article coverage, ownership, or production reliability; current status and evidence fields expose those gaps. How the library was built.
Every monthly refresh appends an entry here, and this panel lives in this page’s own content — not inside the dashboard app — so the job that is supposed to write to it always can. The changelog is the proof of recursion; a panel nothing can append to proves nothing.
Where this sits in the system
Context is what the worker knows. A skill is the method it follows. A pack is a folder of methods. None of them does any work alone. Work happens when a job runs the right skill against the right context on a schedule, checks its output, and leaves a receipt the next worker can inspect.
- Context — the verified facts, goals, evidence, decisions, and working state kept in user-owned Markdown, Obsidian, Drive, or Git so any authorized model can pick up the same work.
- SkillYOU ARE HERE — one task, written down to a standard, so an agent can run it without you in the room. There are 243 of them.
- Pack — those skills bundled into a download you install in one paste.
- Agent — a named role with a job description — not a chat window you retype every morning.
- Job — a schedule, a QA cycle, and somewhere to keep working files. Miss any of the three and nothing runs twice.
- Proof — every finished run written up in public, and the lesson pushed back into the skill.
The map: The System · every asset: Asset Tracker · next door: How we build agents.