Concept System Map
Concepts are reusable mental models: they explain a primitive that transfers across projects, tools, workflows, skills, architectures, or decisions.
Use this page to choose which concept article to read or update. Use wiki/concepts/README.md for the local directory router and Concepts Filing for the filing rule. A concept page should make future action clearer; if it only names a topic, it belongs as a section, table row, generated view, or redirect.
Concept Families
Merge Decisions
No existing concept pages were merged in the 2026-07-01 pass. The current near-duplicates are mostly layered concepts, not duplicate pages.
| Cluster | Decision | Reason |
|---|---|---|
| Loop pages | Keep distinct | Agent Looping is the product/UX shift, Browser Testing Skills is an implementation workflow, The Eval Loop (Slop Is an Output Problem) is a quality loop, and The Brain-Agent Loop is the wiki memory loop. |
| Harness pages | Keep distinct, link through this map and Agent Harness | Agent Harness, Harness Engineering, Agent Harness Capsules, and Agent Harness, Runtime, Memory, and Evals answer concept, discipline, capsule, and layer-synthesis questions. |
| Browser pages | Keep distinct | Browser QA, computer use, complementary testing, local verification, rendering pipeline, and browser-testing skills route different task shapes. |
| Skill-family pages | Keep generated | The *-skills concept pages are generated synthesis, not hand-written duplicates of executable skill source. |
| Finance pages | Keep as hub plus catalogs | Finance Hacks and Tax Hacks Catalog are routers; individual/company/equity/investment pages are specialized reference ledgers. |
| Architecture-like concepts | Keep in concepts only when reusable | Pages such as Persistent Sandbox Thesis and Agent + Machine as the Primitive are conceptual primitives; concrete system boundaries stay in architecture/. |
Concept Page Contract
A concept article should answer five questions:
- What reusable primitive does this page own?
- What failure mode does the primitive prevent?
- Which projects, tools, workflows, skills, or architectures operationalize it?
- What adjacent pages should not be confused with it?
- What proof, source, or timeline evidence keeps the concept grounded?
If a page cannot answer those questions, fold it into a stronger concept, a directory router, a generated skill-family page, or a project/tool/architecture page.
Update Rule
When updating any concept page:
- update its
updated:date - keep a one-line lead
- link it to the relevant concept family
- preserve or add timeline evidence
- connect the idea to operational pages, not only adjacent ideas
- regenerate
_index.md, backlinks, qmd, and generated packs when routing changes - log structural category work in
wiki/log.md
Timeline
- 2026-07-01 | Created as the category-level concept graph for the Concepts rewrite. Added concept families, no-merge decisions, and the page contract used to update all concept articles. Source: User request, 2026-07-01