Every git repo that's part of FLME's own work on this machine, what it actually is, and its current status — built specifically so a new team member doesn't waste a day exploring a repo that turns out to be abandoned, a sandbox, or someone else's reference copy.
This page defers to flme-agents/README.md's who's-who table for agent ownership — that file stays canonical for "which agent owns what scope"; this page is a wider inventory covering repos with no named agent too, and links back to README.md/each repo's own docs rather than restating their authority.
| Repo | What it is | Status | Authoritative for |
|---|---|---|---|
ReqDoc |
The requirements-authoring vault — an Obsidian/Markdown corpus of FLME's formal specs, plus Python governance tooling (extract/validate/analyze). No application code. | Active | Pipeline_Manual.md (the authoritative pipeline description); Requirements/Core/0. Introduction/ (naming, layering, and authoring standards); Requirements/AGENTS.md (vault-editing rulebook). Has its own auto-generated navigational Requirements/Wiki/ — link to it, never copy its content (it's regenerated by tools/build_vault_wiki.py and explicitly "owns no content"). |
backend-template |
The schema-driven NestJS/Temporal backend framework — one JSON Schema per entity, everything else (validators, types, docs) derived from it. | Active | Backend architecture (README.md, docs/extending-the-codebase.md); its docs/design/ + docs/compliance/ suite is FLME's most mature documented subsystem — privacy/PII tiering, encryption, SOC2/ISO27001 control mapping. |
ux-template |
FLME's UI-codegen infrastructure — parser, codegen, IR schema, and per-client UI generation (steps 7–9 of the release pipeline). Owned by agent Wren. | Active | docs/ — the IR/codegen design rationale, the step-9 pre-flight/reconciliation gate mechanics, and requirements-markup presentation conventions. |
flme-release-coordination |
Release process coordination (Snapshot → Resolve → Review → Revise → Freeze) across every client. Owned by agent Sam. | Active | gate-registry.md, clients/README.md (repo root, not docs/ — that folder is just dated engineering logs). |
ux-tools |
Small, spun-out repo for UX tooling — currently one tool, a Figma plugin (flme-field-binder-plugin) binding UI fields to real API fields as structured Figma node data. Grew out of ux-template as a spike, split out 2026-08-26/08-31 to evolve independently. |
Active | Its own README.md/STATE.md. |
flme-deployments |
FLME's own internal deployments registry — demos, reference clients, test clients (currently: pawstop). |
Active | Its own README.md. |
flme-engine-core |
An early, small prototype of a field-level privacy-classification mixin pattern. | Superseded | Nothing — formalized and superseded by backend-template/docs/design/tiered-privacy-design.md and privacy-field-treatment-model.md. No README/CLAUDE.md of its own. |
| Repo | What it is | Status | Notes |
|---|---|---|---|
backend |
Not a client — this is backend-template's own generic reference copy, the architecture anchor that real clients are derived from. |
Active | Treat its docs as duplicates of backend-template's, not independent content. |
browser |
The current flagship client — an e-commerce/pet-retail deployment ("Browser"), derived from backend-template. |
Current | Most recently active repo of all surveyed. Its README is mostly template boilerplate shared with petstore/backend — the client-specific facts are in its commit history and .reqdoc-client metadata, not its docs. |
petstore |
An earlier pet-retail client, same lineage as browser but an older backend-template version. |
Superseded | Superseded by browser. Not a separate architecture reference — same template boilerplate as above. |
dktest |
Not a client. Two unrelated parts: a dormant, abandoned "DrB.care" scaffold (ignore), and an active sandbox of Claude Code skills for practicing ReqDoc-shaped spec authoring. | Active (sandbox) | The active half is explicitly not authoritative and barred from touching the real ReqDoc vault. Don't mistake it for a real client repo. |
drb-web-ui |
An early, minimal Next.js UI prototype for "DrB.care" (a healthcare/telehealth concept). | Abandoned | Largely unmodified scaffold, stale for over a month relative to other repos. No real product documentation. |
drb-web-ui-Test |
An AI-coding-workflow experiment (built via Aider) converting static DrB.care mockups to React. | Abandoned | Interesting only as a workflow case study — not a real deployment. |
| Repo | What it is | Status | Authoritative for |
|---|---|---|---|
flme-agents this repo |
Home for FLME's cross-repo coordination agents (Nora, Sage, Marlowe, Hearth) and shared conventions. | Active | README.md (who's-who table — canonical), SYNC.md (cross-cutting conventions), Agents & How We Work. |
FLME-Site |
FLME's public corporate website (flme.ai), presenting the product as "Specstrum." Owned by agent Herald. | Active | Its own STATE.md/CONVENTIONS.md. Deployment specifics are intentionally not reproduced on this wiki — see Open Questions for why. |
johns-skills |
A separate repo, maintained by John Trustman — FLME's Codex-native (not Claude Code) requirements-authoring skill system (intake, generation, promotion, review, orchestration). | Active | Its own README and skill folders. Maintained independently of flme-agents — see that repo directly for detail; not otherwise characterized on this wiki. |