Built on the Hannah Stulberg / Carl Vellotti TeamOS pattern (ours is PeachOS), diverged where PP's shape (one repo, multiple products coming, small team) called for it. Four structural decisions recommended by Aaron. No moves happen until Mario signs off.
Four structural choices. Read the tree first, then dive into details below if anything reads off.
The repo we're structuring is one of four surfaces the team operates across. Each has a different audience and purpose. The repo holds canonical artifacts; everything else syncs from or coordinates around it.
Every artifact has one canonical home. The other surface references or embeds it, never co-owns it. That is what kills dual-source drift.
GitHub is the brain, Notion is how humans read and comment on it, Drive is how finished things leave the building.
The flow is repo → distilled into Notion, never the reverse for product-dev artifacts.
Canonical product specs, principles, strategy, industry knowledge. The source of truth. Future home: peachpilot-ai/peachos. Code is not in here - the app lives in a separate sibling repo (Chris's structure, in peachpilot-ai). PeachOS holds docs and context only.
Ticket specs from the repo get loaded into Linear issues. The fleet reads, implements, runs through Ready for QA. Humans drive QA + Awaiting Release + Done + status tracking. Bug sub-issues (Bug + qa-bug labels) live here.
The company wiki + live coordination: the decisions log and action items (Notion is their home), OKRs, advisor calls (Alon Bochman), and the Market Intelligence System. Human-facing - canonical product-dev artifacts live in the repo and get distilled into Notion, not duplicated.
Daily product-development thread, vendor coordination, ad-hoc decisions. Captures the moment-by-moment. Important calls get promoted to Notion or the repo as canonical.
Click any folder to expand it. Hover any underlined item for a longer description.
Four decisions Aaron recommends. Push back on any if the framing reads wrong.
Decision: `product/` holds only products - `right-quote/`, future `peach-live/`, `chargebacks/`. Cross-product material moves up to top-level siblings: a `knowledge/` group (`personas/`, `industry-knowledge/`, `competitive-and-vendor-research/`), plus `strategy/`, `principles/`, `processes/`, `customers/`, and `meetings/`. Positioning / messaging / voice move into `brand/` as PP's identity home.
Admin clarification: Admin is a settings menu within Right Quote, not a separate product. The A1-A4 admin tab specs live under `product/right-quote/specs/` with the agent flow specs.
Keeps `product/` honest - if it isn't a product, it doesn't live inside it. Diverges from Hannah's function-first shape; PP has a multi-product roadmap.
Decision: Each product holds its own ticket specs in a `specs/` subfolder. One file per screen / surface.
Preserves the existing pattern. Linear ticket references need an audit before move - resolved in flag 1 below.
Decision: `research/` keeps its top-level slot for in-flight learning. Canonical references live in their settled top-level folders (`knowledge/`, `strategy/`, and the rest).
Promotion from research/ to product/ is an explicit editorial step - see lifecycle below.
Revisit at 3 months. If editorial gate isn't being maintained, fold research/ into product/.
Decision: `meetings/{standup, internal, vendor-discovery}/` at top level. Customer call summaries live under `customers/{name}/calls/`.
Internal team meetings (strategy sessions, advisor calls like Alon, touchpoints), standup, and vendor-discovery are PP-team artifacts worth sharing. 1:1s and personal notes file outside the team repo.
How a learning artifact moves from in-flight notes to canonical reference. The promotion step is an editorial moment - "is this actually canonical now?"