Project Sub-Indexes
This folder holds one curated entry point per active Cowork project. Each file tells Claude the 5–15 wiki pages that actually matter for that project, instead of scanning the 263-page master index every session.
Sub-indexes do not move or duplicate content — they link to pages in entities/, concepts/, sources/, analysis/, and decisions/ using [[wikilinks]].
Active Projects
- website — Pride Website (public-facing rebuild for patrons + investors)
- humphrey — Humphrey (live intelligence dashboard + operational command centre)
- finance — Pride Finance (bookkeeping, Xero, reconciliation, tax)
- ops — Pride Ops (venue operations, governance, strategy, capital raise)
- wiki-viewer — Pride Wiki Viewer (Quartz read-only site for Mat)
- pride-lvl-up — Cross-project meta-work, wiki infrastructure, workspace conventions, memory hygiene. Home of WIKI-, WORKSPACE-, and SYSTEMS-* meta-specs.
When to use a sub-index vs the master index
| Question | Start here |
|---|---|
| ”What’s the current spec for Humphrey’s event pages?” | projects/humphrey.md |
| ”What financial info is safe to publish on the investor section?” | projects/website.md |
| ”What clearing account needs fixing this week?” | projects/finance.md |
| ”When is Mat back from holiday?” | index.md (cross-project fact) |
| “Who is Mon?” | index.md (entity lookup) |
| “What’s our kitchen status?” | projects/ops.md |
If the question doesn’t obviously belong to one project, use the master index.md.
Maintenance
When a new active project starts:
- Create
projects/{slug}.mdusing the template in the WIKI-META-1 spec - Add to the list above
- Update the matching
_{slug}-project-setup/INSTRUCTIONS.mdto point at the new sub-index
When a project is retired:
- Move the sub-index to
projects/_archive/{slug}.md - Remove from the list above
Recent updates
- 2026-04-24 — Folder created, 5 initial sub-indexes filed (WIKI-META-1)