Docs Index

A categorized map of everything in docs/. Used by:

• Humans looking for a doc (you, right now)
• The partners site /development browser (renders this index as navigation)
• The docs-site static builder (generates a nav page from these categories)

Categories are declarative — the order below is the order shown in the browser.

Status markers. Entries tagged [historical] carry a "Historical record — do not update" banner: they describe the system as of their own date and are deliberately not corrected. Entries tagged [superseded] describe a subject that no longer exists at all.

An untagged entry is not automatically current. The 2026-09-03 triage classified only the 50 files that mention the retired identity stack (Self Protocol, Semaphore, the device-attestation humanity seal); every other doc listed here was simply out of its scope, tagged neither way. Several of those are plainly dated snapshots too — a date in the filename still signals one, per the naming convention at the bottom of this page. Read untagged as "not covered by that triage", not as "verified current". The full per-file classification, and the sweep's exact scope, are in Doc status triage (2026-09-03).

Overview

• README (root) — project overview, stack, deployment
• Packages overview — the 12 @plantagoai/* shared packages, their APIs and integration points
• Firestore schema — every collection, field, and rule
• Foundation API guide — client-facing callables (sign-in, identity, voting, Market)
• Cloud Functions reference — exhaustive CF catalog
• Your Market API guide — Pool/Source commerce-agent callables; host Join / Place order
• Release notes — version-tagged release history
• Doc status triage (2026-09-03) — which docs are live references, which are dated records, and why
• Docs / Partners / Kit site status (2026-09-05) — what Plan 6 refreshed in the three secondary sites, what was fixed same-day, and what's still pending
• Next-domain setup guide — step-by-step Firebase console + DNS instructions for partners.next / docs.next / kit.next.foundation-global.com
• Development timeline — [historical] chronological dev log; a dated record by construction, appended to rather than corrected

Architecture

• Identity architecture — current — the current-state reference for enrollment, PoH roots, anonymous voting and attestations (Rarimo/RariMe); supersedes the identity sections of every doc marked historical below
• Your Market architecture — current — commerce-agent bulk-buy harness (Pool + Source, skills not subagents); sits beside the older vote-on-bids marketplace, does not replace it
• Architecture flows — mermaid sequences for auth, PoH, attestations, and Market bulk-buy
• Backend consolidation (Phase 4/5 cutover) — [historical] the Rocket → Cloud Functions cutover as designed on 2026-04-18; its identity sections predate the Rarimo consolidation
• Components design (2026-04-15)
• Components update (2026-04-16)
• Next-wave packages (2026-04-16) — db, i18n, legal, flows, seeders roadmap
• Wave 3 architecture (2026-04-16)
• Multi-tenant architecture — tenant isolation across Firestore, Solana, auth, rules
• Auth architecture design — [historical] the 2026-04-14/16 design record for ring-based permissions via @plantagoai/auth
• Platform features
• Phase 1 GCP setup (2026-04-18) — [historical] one-off console checklist for the Rocket → Functions migration
• Plan: on-chain voting for Pillars 2 & 3

Security & PoH

• Security hardening sprint (2026-04) — [historical] April 2026 sprint record: App Check, CSP, governance schemas, identity_proofs lockdown
• Single Account Per Person hardening (2026-05-15) — [historical] empirical Sybil bypass via Self SDK devMode; ToS v3 mitigation + 3 open technical follow-ups
• Security fix plan (2026-04-20) — [historical] remediation backlog as scoped on 2026-04-20
• Phase 2b decisions (2026-04-20) — [historical]
• Shared packages security review — [historical] 2026-04-20 review of the 12 @plantagoai/* packages
• Foundation PoH architecture — [historical] the 2026-04-11 stack evaluation that selected Self Protocol; retained as a record, not as the current design (see Identity architecture — current above)
• PoH threat model — Sybil, spoofing, de-anonymization, coercion, custody. Revised 2026-09-03 for the Rarimo cutover; states the new anonymity set and carries five open questions.
• PoH Phase 0 audit — [historical] 2026-04-11 assessment of what the pre-cutover passport flow actually verified
• PoH mDL status — mobile driving license / ISO 18013 type surface
• PoH API guide — the live Soulbound Attestations (GaaS) endpoint; its second half documents a retired REST API and is marked as such
• PoH OpenAPI spec
• ZK coverage for IL & PT — [historical] 2026-04-14 CSCA-certificate research against Self Protocol's circuits
• Self Protocol contribution issue (draft) — [superseded] Foundation no longer uses Self Protocol (retired 2026-08-31); see Identity architecture — current
• PoH UX parity plan (2026-04-23) — [superseded] matching Persona's UX while keeping Self Protocol's privacy posture; the whole comparison is moot post-retirement

Shared packages

• pkg-ai — Claude / Gemini with prompt caching
• pkg-auth — ring permissions, invite flows, account deletion
• pkg-db — schema validation, tenant scoping, export, cleanup
• pkg-firebase-core — Firebase init, Firestore CRUD
• pkg-flows — XState + Firestore-backed flows
• pkg-i18n — translations
• pkg-legal — privacy policy, ToS, consent
• pkg-messaging — email, push, in-app notifications
• pkg-payments — Braintree
• pkg-seeders — data seeding

Ops & tooling

• Admin tools guide
• Staging seeder — functions/seed-foundation-staging.mjs + EnvBadges
• M365 email forwarding — foundation-global.com tenant config + outbound anti-spam scoped policy
• M5 migration session (2026-05-07) — pre-M5 audit, decisions, repo inventory, manual transfer checklist
• Growth strategy (user onboarding)
• Action items

Pillars — public-facing docs

Pillar 1 — Your Voice (verified human governance)

• Whitepaper — [historical] "Foundation White Paper | April 2026"; the standing partner whitepaper is foundation-whitepaper.md
• Executive summary — [historical] "Foundation | May 2026" snapshot
• Deck outline — [historical] YC S26 pitch-deck snapshot
• Demo plan

Pillar 2 — Your Share (UBI distribution)

• Whitepaper
• Executive summary — [historical] "Foundation | May 2026" snapshot
• Deck outline
• Demo plan

Pillar 3 — Your Market (cooperative commerce)

• Your Market architecture — current — engineer reference for the commerce-agent slice
• Your Market API guide
• Whitepaper — partner-facing reverse-marketplace narrative (not the agent harness)
• Executive summary
• Deck outline
• Demo plan

Narrative

• Narrative overview — master narrative tying all three pillars together

Grants

• Grants directory — ESP (Ethereum Foundation), Gitcoin Public Goods, NLnet/NGI Zero, outreach

Conventions for adding new docs

• File names: kebab-case with optional date suffix for dated snapshots (architecture_backend-consolidation-2026-04-18.md, security-fix-plan-2026-04-20.md). Filename dates are the source of truth for the timeline view's chronological sort.
• Use the existing category closest to the content; create a new category only if you have 3+ docs that don't fit anywhere.
• Keep the root README → INDEX → doc-file hop chain short — don't orphan a doc.
• Archive, don't delete. If a doc is fully superseded, move it to archive/rocket-retirement-2026-04-19/docs/ (or create a new dated archive directory) and remove its entry from this file.
• A dated record is never corrected. If a doc carries the "Historical record — do not update" banner, fix the current doc it points at instead and leave the record alone; editing it would falsify what it captured. Add the banner (and the [historical] tag here) rather than rewriting a snapshot to match today's system.

Last status pass: 2026-09-04 — Task 9 of superpowers/plans/2026-09-03-docs-and-partner-material-refresh.md. No entry was removed: the 21 files deleted by that plan's Task 8 were kit-site/ translations, none of which were ever indexed here.