Wiki coverage.
Substantive pages per content area against that area's depth target — how ready the brain is to answer from it. Seed stubs don't count: a page is substantive once it reaches draft or live. This is the backlog view for planning the bulk load, which is why it lives here rather than on the wiki front door.
Overall
0 / 333 substantive
Areas tracked
with a depth target
At target
areas at 100%
Nothing yet
areas with 0 substantive
Pages in canon
Atlas Network Wiki
| Area | Coverage | Substantive | Target | % | Pages filed | Target from |
|---|---|---|---|---|---|---|
|
Overview
Canonical page per partner, funder, program, person — the brain's entity backbone.
|
0 | 120 | 0% | 1 | Estimate est. | |
|
Outcomes
Fiscal-year + grant-level results. Directly feeds 'what did we accomplish' / donor reports.
|
0 | 40 | 0% | 5 | Curated checklist | |
| Theory of change | 0 | 30 | 0% | 1 | Curated checklist | |
|
Story
Partner narratives — the raw material for comms and donor-facing synthesis.
|
0 | 30 | 0% | 0 | Curated checklist | |
|
Concept
Shared vocabulary the brain can assume when synthesizing.
|
0 | 50 | 0% | 0 | Curated checklist | |
|
Boilerplate
Reusable org language dropped verbatim into proposals/reports.
|
0 | 12 | 0% | 2 | Curated checklist | |
|
Operating policy
Renamed from `policy` 2026-08-13 — it collided with the policy-area entity type.
|
0 | 10 | 0% | 0 | Curated checklist | |
|
Decision
Why we chose what we chose. The category leadership synthesis leans on and no other type holds.
|
0 | 15 | 0% | 0 | Curated checklist | |
| Playbook | 0 | 8 | 0% | 0 | Curated checklist | |
|
Collection
Index pages that gather related entries — partner-story sets, campaign rosters, award years. Distinct from individual story pages.
|
0 | 8 | 0% | 1 | Curated checklist | |
| Reference | 0 | 10 | 0% | 0 | Curated checklist |
Pages filed across areas: 10 of 10 in canon.
Targets live in config/wiki/coverage-targets.yaml. Areas marked
est. are anchored to a real population (partners, funders, …) but
still using an interim manual number; they switch to a live count once the
Portal Agent API exposes the roster. Substantive is graded from page
lifecycle status; grading on body depth is still a follow-up.