Source inventory
Every place BoRo knowledge lives, what each document is for, whether it moves here — and, now, whether it has.
Knowledge is in three places and only one of them is readable by the whole team. This wiki holds the conversation lifecycle and its documentation. boro-ops holds the design system, brand and standards — and is CJ's personal repository. Google Drive holds around sixty documents, mostly rendered output.
The middle one is the problem. boro-ops is a staging area and it did its job: it existed so the standards and the specification could be got into shape without waiting on anyone. That is why almost everything below reads Move rather than Retire. These are promotions, not corrections.
The first one has happened. The Master FSD was promoted on 2026-08-24 and its staged copy is now a stub — every canon claim on this site can be checked against the document itself by the people who own it. The rule that move followed is written down at How a document gets promoted.
How to read the table
Action is the recommendation. State is what actually happened. They are two columns on purpose — a row reading Move / not started is the honest shape of most of this table, and collapsing them into one would hide exactly the thing this page exists to show.
Action — what should happen
- Move
- Belongs here. The team needs it and cannot currently reach it.
- Point
- Stays where it is, but this wiki should link to it.
- Stay
- Correctly where it is. Not knowledge this wiki is for.
- Retire
- Superseded. Keep the file, stop treating it as current.
- Ask
- Cannot be judged from outside. Somebody has to look.
State — what has
- Promoted
- Moved here, and its origin is stubbed.
- Next
- Released and next in line.
- Not started
- Recommended, not begun.
- Retired
- Marked superseded where it sits.
- —
- Nothing to do — it stays where it is.
What could and could not be assessed: the Markdown and HTML were read. PDFs were identified by name and context but not opened, and .gdoc files are pointers to documents whose contents are not on disk at all — those are marked Ask. Bulk asset folders are grouped rather than listed one by one.
Canon
The documents everything else defers to
Every “the FSD governs” statement on this site resolves against these. They are the reason this inventory exists.
| Document | What it is | Action | State |
|---|---|---|---|
BoRo_MasterFSD.mdboro-opsproduct/BoRo_MasterFSD.md | v9.0, “Controlling — confirmed current 2026-08-20.” The governing functional specification. Sixteen of its sections are cited across this wiki. Corrected against Jay's export on 2026-08-24 — the first conversion had dropped three table cells. | Move | PromotedACCESS-1 |
BoRo USA Terms of Service v2 5.docxDriveLanding Page/LP Images/Products/ | The controlling Terms — v2.5, “Complete and Restated”, effective 2026-08-06, thirty sections. §8.4 is Category H, H-1 through H-9 — the eligibility schedule every listing is screened against, cited twenty-two times here. In no repository, and filed among the landing-page product images.Promoted 2026-08-24 — ACCESS-3. Converted by tools/promotion/convert-docx.py so it can be re-converted rather than hand-edited. No stub is left behind: the origin is an executed .docx in Drive, not a staging repository — it is the source of record and stays where it is, the same arrangement the FSD has. A separate §8A Private Sales insertion is PROPOSED and is not part of this document — CANON-3. | Move | PromotedACCESS-3 |
BoRo Master FSD V8.1.pdfDriveDevelopment/ | The FSD as a PDF — v8.1, two versions behind the controlling v9.0. The copy the team can currently open is the one that is out of date. | Retire | Not started |
Design system and brand
boro-ops/brand/
The simulator embeds a copy of boro-tokens.css from here, and token-drift.py already treats that copy as a known drift risk. The next promotions after canon.
| Document | What it is | Action | State |
|---|---|---|---|
BoRo_DesignSystem.mdboro-opsbrand/BoRo_DesignSystem.md | The DS itself — tokens, components, the accessibility envelope. Ten unapplied amendments are outstanding (R-5).The wiki is the design handoff; the DS should not be one repository away from it. | Move | Not started |
BoRo_BrandGuidelines_Team.mdboro-opsbrand/BoRo_BrandGuidelines_Team.md | The team-facing subset. Known to drift from the DS — which is an argument for promoting both together, not one. | Move | Not started |
BoRo_BrandFoundation.md, BoRo_BrandPrecedence.mdboro-opsbrand/ | Brand rules, and which document wins when two disagree. | Move | Not started |
BoRo_DesignSystem_Bindings.md, _ExecutionHandoff.md, _Step1_TokenHandoff.mdboro-opsbrand/ | How the DS binds to code and how it is handed over. This is exactly what Brad reads. | Move | Not started |
brand/artifacts/, brand/experience/, brand/generator/boro-opsbrand/ | Artifact registry, the experience page, and the token generator.The generator may be tooling rather than knowledge — tooling moves differently. | Ask | Not started |
BoRo_ShieldFraming.md, BoRo_PitchDeckReview.mdboro-opsbrand/ | Shield positioning; a pitch-deck critique. | Point | — |
Branding & Design/Brand Foundation/*.html (4 files + zzz_Archive/)DriveBranding & Design/ | Rendered versions of the above, plus superseded ones.The markdown in boro-ops is the source; these are its outputs. | Retire | Not started |
Standards
boro-ops/standards/
| Document | What it is | Action | State |
|---|---|---|---|
BoRo_ProjectSOP.mdboro-opsstandards/BoRo_ProjectSOP.md | v1.11, “Alive.” How work is run on BoRo. | Move | Not started |
BoRo_ArtifactStandard.mdboro-opsstandards/BoRo_ArtifactStandard.md | The artifact lifecycle — four states, slug naming, DS-bump sweeps. This wiki is now the artifact host, so this standard governs it. | Move | Not started |
BoRo_ProjectInstructions.md, BoRo_PartnerAccount*.md (3), BoRo_MemoryEntries_Internal.mdboro-opsstandards/ | Assistant and partner-account configuration.Operating configuration, not team knowledge. | Stay | — |
Product
Drive Product/ and boro-ops/product/
| Document | What it is | Action | State |
|---|---|---|---|
BoRo_Edge_Case_Reference_V1.pdfDriveProduct/ | Edge cases. Directly adjacent to the lifecycle — likely overlaps the twelve exception screens.Read before anything is archived. Could hold live material. | Ask | Not started |
BoRo Rental Cycle Milestones.gdocDriveProduct/ | A Google Doc on rental milestones. The name suggests an earlier statement of the thing this wiki now specifies.If it is, retire it — two lifecycle sources is the exact duplication to avoid. | Ask | Not started |
boro-ops/product/landing/boro-opsproduct/landing/ | Landing compliance — the prohibited-items screen. Ties to FSD §14.5 and Terms §8.4, which the lifecycle screens against.The next design track (N-6) needs it. | Move | Not started |
BoRo_Founding10K_FeeStructureInput.mdboro-opsproduct/BoRo_Founding10K_FeeStructureInput.md | Fee-structure input. | Point | — |
Product/Founding 10k Program/ (3 docs + CJ feedback)DriveProduct/ | The Founding 10K programme. | Point | — |
Product/Growth Programs & GTM/ (v1.5, v1.6 + feedback)DriveProduct/ | GTM specification. Two versions side by side.Point at v1.6 and retire v1.5. | Point | Not started |
BoRo Fee Proposal V-2.pdfDriveProduct/Platform Fee Structure/ | Fee proposal. The 7%/3% split it presumably carries is deliberately absent from every screen (N-3). | Point | — |
BoRo PLG v3.docxDriveProduct/ | Product-led growth. | Ask | Not started |
Development
Drive Development/boro_pdfs_20260409/
Twenty-eight PDFs from April 2026 — a numbered FSD set (fsd-00 through fsd-14), a rental lifecycle document, two chat-system documents, business rules, and a decisions file. They predate FSD v9.0 by four months and predate this specification entirely.
| Document | What it is | Action | State |
|---|---|---|---|
boro_pdfs_20260409/ — 27 of 28DriveDevelopment/ | Anyone opening 01-rental-lifecycle.pdf or 03-chat-system-borrower.pdf today reads a superseded account of what this wiki now specifies.Retire as a set, with one exception — the row below. | Retire | Not started |
REMAINING-DECISIONS.pdfDriveDevelopment/boro_pdfs_20260409/ | The exception. If it lists decisions that were never made, some may still be open — and open decisions belong in the register, not in a PDF from April.Worth one read before the set is retired. | Ask | Not started |
Landing page
Drive Landing Page/
| Document | What it is | Action | State |
|---|---|---|---|
BoRo_LandingMerge_Handoff_v2_1.md, _v2_2.mdDriveLanding Page/ | Two versions of the merge handoff. The boro-ops/archive/ copy suggests this is already considered done.Retire v2_1. | Retire | Not started |
BoRo_LandingBundle_KnownIssues_v1_0.mdDriveLanding Page/ | Known issues from the landing bundle.If any issue is still live it belongs in a tracker, not a file. | Ask | Not started |
LP Mockups/, Old Original LP/, Design Rationale/, Content Strategy/, Jay Feedback/DriveLanding Page/ | The landing page shipped; these are its working history. | Stay | — |
Everything else
Grouped rather than listed document by document
| Document | What it is | Action | State |
|---|---|---|---|
Photos — 114 PNG, 22 JPG, plus categories, headshots, lifestyle, team, stockDrive | Asset library. The simulator embeds four of these as data URIs. | Stay | — |
Legal & partner — trademark filing, STS agreement, an old development contractDrive | Executed and in-force documents. | Stay | — |
Marketing — pitch decks, EKO scripts, Crunch Fitness ad, marketing plan, competitive analysisDrive | Mostly working material. The competitive analysis and the marketing plan are knowledge. | Point | — |
Intake & Discovery — credit co-brand spec, unified brand spec, research, team updatesDrive | Mostly April-era; likely historical. | Ask | Not started |
Admin Dashboard — three HTML prototypesDrive | If any is a live specification it belongs here as an artifact, the same way the lifecycle is. | Ask | Not started |
BoRo_AutomationDiscovery (HTML in Drive, markdown in boro-ops)boro-opsops/BoRo_AutomationDiscovery.md | Automation discovery. | Point | — |
Jay 1-on-1s — collaboration plan, meeting foldersDrive | Personnel. | Stay | — |
Promotion log
What has actually left staging, and what proves it
| Document | From | To | Body hash at promotion | Date |
|---|---|---|---|---|
| BoRo_MasterFSD.md | boro-ops/product/BoRo_MasterFSD.md | src/canon/BoRo_MasterFSD.md | 86687827981cfd69 | 2026-08-24 |
| BoRo USA Terms of Service v2 5.docx | Drive · BoRo USA/Landing Page/LP Images/Products/BoRo USA Terms of Service v2 5.docx | src/canon/BoRo_TermsOfService_v2_5.md | c6e04cc76440ae50 | 2026-08-24 |
The hash is the check, not a decoration.tools/promotion/verify-promoted.py recomputes it on every verification run and fails if a promoted document has been hand-edited here, or if the copy it came from is still a whole document rather than a stub. It reads this table's data rather than keeping a list of its own.
What I would do next, in order
- Promote Terms of Service v2.5 —
ACCESS-3. §8.4 is screening authority for every listing on the platform, it is cited twenty-two times here, and it is in no repository at all. And the FSD names v2.4, which is a canon question for Jay before anyone builds against either. - Read three documents before archiving anything —
REMAINING-DECISIONS.pdf,BoRo_Edge_Case_Reference_V1.pdf, andBoRo Rental Cycle Milestones.gdoc. Each could hold live material, and each would be lost silently if its folder were archived first. - Promote the design system and standards. The wiki is the design handoff; the DS being one personal repository away is the same problem as the FSD, one step smaller.
- Retire the stale FSD PDF in Drive. One file, and it is actively misleading — the copy the team can currently open is two versions behind.
- Then archive the superseded sets — the April PDFs, the brand HTML renders, the landing merge v2_1.
The principle worth keeping: a document is not duplicated when a copy exists — it is duplicated when two copies can both be edited. The Drive artifacts are rendered outputs of
boro-opsmarkdown, which is fine.boro-opsmarkdown that only one person can read is not.