overview
Overview
The narrative entry point to this wiki — a map of content (MOC). Where Index is an exhaustive catalog, this page is the curated tour: the main threads, the big open questions, and the pages worth starting from.
The maintainer agent keeps this updated as themes emerge.
Its twin: Method Reflection tracks how this wiki knows things, and where its sources say the method is wrong. Start there to improve the wiki rather than read it.
What this wiki is about
A personal knowledge base that began (June 2026) around how AI changes work, branched into the engineering craft of building data products, and by November 2026 had grown eight threads, including the wiki's own method (agents & memory, cybernetics) and the design of its front door. The through-line: when execution gets cheap and abundant, value and correctness migrate to the scarce, well-placed human judgment — what to build, where to put it, what counts as good, and what you can still verify. The threads below are a tour; the front door's Location lens shows which of them the links themselves support.
Main threads
- AI and work (the founding domain) — The Bottleneck Shift (deciding what to do is the new scarce input), AI Commoditizes Expertise → Slop → demand for difference, The Human Sandwich and the two modes of working with agents, Personal vs Team Agents. Synthesis: What's Scarce When Execution Is Cheap.
- Engineering craft (opened 2026-06-26 via Working Heuristics — Data, Matching, Product, Org, Tooling) — hands-on rules for building data products. Hubs: Data Contract, One Fact Per Grain, Pipeline Legibility, Shrink the Candidate Space, System of Record, Human-in-the-Loop by Exception, Data Gravity, Build With, Not Against. Recurring sub-themes: Do It Once, at the Right Place, directionality/naming is load-bearing, compose don't conquer. Several hubs are grounded in canonical sources (Kimball on grain, McCrory on data gravity, Databricks on the medallion, Sanderson on data contracts).
- Software security (opened 2026-06-20) — Control-Flow Integrity and its default-deny stance, which Allowlist over Blocklist now rhymes with. Extended 2026-11-08 by Provable Inference (auto-ingested Anthropic — Progress on Provable Inference for Large Language Models): cryptographic proof of which model produced a response. Its principle, "trust the verifier, not the prover," is the engineered answer to Verification Requires Domain Knowledge.
- Thinking & learning (opened 2026-11-08 via Willingham — Critical Thinking, Why Is It So Hard to Teach) — Critical Thinking Is Domain-Bound, Surface vs Deep Structure, Metacognitive Strategies. It explains why judgment is the scarce human input (it's knowledge-bound) and questions the wiki's own maxim-distilling method.
- Agents & memory (opened 2026-11-08 via the auto-ingested Anthropic — The Components of Agent Memory) — Agent Memory, Dreaming (Offline Memory Consolidation), Agent-Maintained Wiki. This domain turns back on the wiki itself: it is external evidence about the pattern this wiki runs on (see T5 in Method Reflection). Extended 2026-11-08 by Blumenfeld — Scaling Karpathy's LLM Wiki (Neo4j) (human-requested): the pattern's cost is in reading and navigating, not writing; Navigation vs Search names the two retrieval modes, and the front door's graph now also serves the agent. The pattern's primary source, Karpathy — LLM Wiki Gist, was read the same day; its scale estimate (~100 sources) and dropped page quota are recorded against T5.
- AI & science (opened 2026-11-08 via the auto-ingested Anthropic — How Scientists Use Claude) — AI Use Tracks AI Capability, AI-Accelerated Science. It is the first large-scale usage evidence in the wiki, and it tests the AI-and-work thesis: ideation is underused, as The Bottleneck Shift predicts, but may not stay human-only. Extended 2026-11-08 by Anthropic — Investigating Vault Particles with Claude, the wiki's first worked case of the thing the scenarios model — including its errors, which produced Verification Requires Domain Knowledge. Extended again by Anthropic — Teaching AI to Build Scientific Models: AI speeds up fitting more than understanding, so it should report Distributions over Best Fits and what failed.
- Cybernetics (opened 2026-11-09 via Ashby — An Introduction to Cybernetics, fetched during the first daily pass) — Communication and Control Are Intertwined, promoted from the wiki's oldest seed: a regulator can control no more than its channel carries, which also gives Verification Requires Domain Knowledge and T3 a measure. Norbert Wiener primary still unread.
- Process / methodology — Match Process Weight to Stage and Stakes, promoted 2026-11-08 (partially grounded by Rao on legibility; the stage × stakes dial is still open).
- Front door / information architecture (opened 2026-11-08) — Legibility in the Lens, Not the Land is the foundation: Tree vs Semilattice, LATCH, Legibility, Living Structure, Pattern Language (Alexander, Wurman, Rao). The design basis for a Svelte front door, written as a six-pattern sequence in Front Door Pattern Language.
Cross-cutting syntheses
- What's Scarce When Execution Is Cheap — value migrates to scarce human judgment.
- Placement and Judgment Over Raw Execution — its companion: the two domains share three recurring moves (do it once at the right place; reserve judgment for the exception; put the thing where the mass is), all responses to cheap execution.
Open questions
Questions worth investigating
- Do the AI-and-work and engineering-craft domains share a deeper spine? Partly answered by Placement and Judgment Over Raw Execution — but is "placement" really separable from "judgment," or is choosing the right place itself the highest-leverage judgment? (If so it collapses into What's Scarce When Execution Is Cheap.)
- Which of the new craft heuristics generalize beyond data work, and which are domain-bound? (e.g. Falsification Is Asymmetric is general epistemics; One Fact Per Grain is dimensional-modeling-specific.)
New (2026-11-08, from the Willingham ingest)
- If judgment is knowledge-bound (Critical Thinking Is Domain-Bound), does handing knowledge work to AI erode the very judgment the AI-and-work thesis calls the human premium? (Also T3 in Method Reflection.)
- If AI absorbs the junior work that used to build expertise, where does the next generation of "difference"-supplying experts come from? (See AI Commoditizes Expertise.)
- Should T1 in Method Reflection become practice, giving every craft heuristic at least two worked examples, and is the human's own heuristic list the right first test?
New (2026-11-08, from the agent-memory auto-ingest)
- Agent wikis help most on cross-source synthesis and least on single-document lookup. Which pages here are lookup-shaped, so that
raw/search would serve as well? (See Agent-Maintained Wiki.)- "Salience over hoarding": should INGEST touch fewer pages, keeping only what is worked out, not what's re-readable? (T5 in Method Reflection.)
New (2026-11-08, from the science-usage auto-ingest)
- Is ideation's low AI use a matter of preference or of capability? The answer decides whether The Bottleneck Shift is durable or temporary.
- If AI is strongest where success is easy to verify (AI Use Tracks AI Capability), does the human premium end up in work that is inherently hard to verify, or only in work nobody has made verifiable yet?
New (2026-11-08, from the vault-particle auto-ingest)
- If you can only catch AI's errors where you already have expertise (Verification Requires Domain Knowledge), what is the right amount of competence to retain in work you've delegated — and how would you know you'd fallen below it?
- How much "irreducible" physical lab time is actually a protocol nobody has reconsidered? One method substitution cut a 3-day step to 90 minutes with no automation (contradiction on AI-Accelerated Science).
- Claude both argued against the method that worked and proposed the unconventional trick that made it fast. What distinguishes a model objection worth overriding from one worth heeding?
New (2026-11-09, from crossing the Category and Location lenses)
- Software security is the one Overview domain whose pages do not cluster by their links: three sit with AI & science, two with engineering craft (Front Door Pattern Language). Is it a thread without a cluster yet, a cross-cutting theme that belongs in a synthesis, or two topics filed under one name? (The human: "I do not know the answer off the top of my head.")
New (2026-11-08, from the Neo4j scaling ingest)
- At what wiki size does the agent's grep-based "search before you write" start producing duplicate pages and missed links, and would we notice before the Borges check does? Karpathy's own estimate for index-first is "~100 sources, ~hundreds of pages." (See Navigation vs Search.)
- Blumenfeld says the file-based wiki "can't be scaled"; Anthropic scaled one to a 420M-token corpus. Are they measuring the same thing? (Contradiction on Agent-Maintained Wiki.)
New (2026-11-08, from the provable-inference auto-ingest)
- Which AI outputs can be reshaped into a small, mechanically checkable claim, and which can't? If only formalizable work escapes Verification Requires Domain Knowledge, the human premium concentrates in the unformalizable. (See Provable Inference.)
- Should this wiki shape its own claims for cheap review (verbatim quote per key claim)? (T3 in Method Reflection.)
New (2026-11-08, from the scientific-models auto-ingest)
- If insight comes from building the model, does a reported list of failed alternatives restore it for someone who didn't build it, or only make it checkable? (See Distributions over Best Fits; T4 in Method Reflection.)
- "Run the experiment that rules out the most models" turns part of choosing what to do into a calculation. How much of The Bottleneck Shift survives once a model distribution exists?
How to use this
- Add a source: drop it in
raw/, then tell the agentingest raw/<file>. - Ask a question: just ask; good answers get filed into
syntheses/. - Keep it healthy: periodically ask the agent to
lint the wiki.