Docs Index

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

• Humans looking for a doc (you, right now)
• The yc-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.

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
• Release notes — version-tagged release history
• Development timeline — chronological dev log (Feb → now)

Architecture

• Backend consolidation (Phase 4/5 cutover) — current backend architecture after Rocket retirement
• 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 — ring-based permissions via @plantagoai/auth
• Platform features
• Phase 1 GCP setup (2026-04-18)
• Plan: on-chain voting for Pillars 2 & 3

Security & PoH

• Security hardening sprint (2026-04) — App Check, CSP, governance schemas, identity_proofs lockdown
• Security fix plan (2026-04-20) — remediation backlog
• Phase 2b decisions (2026-04-20)
• Shared packages security review
• Foundation PoH architecture — core Proof-of-Humanity design
• PoH threat model — Sybil, spoofing, Semaphore desync, custody
• PoH Phase 0 audit — honest assessment of what the passport flow actually verifies
• PoH mDL status — mobile driving license / ISO 18013 type surface
• PoH API guide
• PoH OpenAPI spec
• ZK coverage for IL & PT — country-specific PoH gaps
• Self Protocol contribution issue (draft)

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
• Growth strategy (user onboarding)
• Action items

Pillars — public-facing docs

Pillar 1 — Your Voice (verified human governance)

• Whitepaper
• Executive summary
• Deck outline
• Demo plan

Pillar 2 — Your Share (UBI distribution)

• Whitepaper
• Executive summary
• Deck outline
• Demo plan

Pillar 3 — Your Market (cooperative commerce)

• Whitepaper
• Executive summary
• Deck outline
• Demo plan

YC application materials

• YC narrative overview — master narrative tying all three pillars together
• YC application draft
• YC demo video script
• YC founder video script
• YC submission notes (2026-04-08)
• YC funding sources (2026-04-08)
• YC review (2026-04-09)
• YC relevant submissions review (2026-04-09)

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.