fred
bc1149c15e
- docs/PRD.md: Part I product north star authored from ratified decisions D1-D14; Part II preserves all active workstream contracts verbatim (KBN-101, FCM #758, FCOM #766, TESS, #756, MOS-PORT, #1150, #1174, #1194, RI #1275, M1). Referenced anchors unchanged. - docs/archive/PRD-v0.1.md: v0.1.0 beta PRD body archived verbatim with supersession header. - docs/ROADMAP.md: all phases P0-P5 present from day one per D11 (P2-P5 as explicit placeholders). - docs/requirements/native-kanban-sot.md: Amendment A1 (D13) - hierarchy parentage + RBAC chain above workspaces; sections 1-7 untouched.
3.6 KiB
kind, status
| kind | status |
|---|---|
| spec | active |
Mosaic Stack Roadmap
Companion to docs/PRD.md. Governed by the D11 rule: every planned phase appears here from day one, even as a placeholder — nothing exists only in heads. A phase marked placeholder is a commitment to design it, not a design; scoping one requires its own PRD section or requirements doc plus review.
Phases are product phases. The in-flight platform workstreams (KBN-100/101 kanban SOT implementation, FCM #758, FCOM #766, TESS, RI #1275, and the other Part II contracts in the PRD) run as parallel tracks under their own issues and are prerequisites where noted.
| Phase | Scope | Status |
|---|---|---|
| P0 | Current state on next: read-only dashboard, chat, auth/SSO login, admin tabs |
shipped, evolving |
| P1 | v1 slice (PRD Part I §9) | next up |
| P2 | Connectors + comms | placeholder |
| P3 | Full onboarding profile + M365 | placeholder |
| P4 | Enterprise mode + one-way conversion | placeholder |
| P5 | Federation | placeholder (deliberately undesigned, D3) |
P0 — current state
What exists on next today: web dashboard (login/register/SSO, chat,
read-only projects/tasks, settings, admin user/system-health tabs), the
Gateway, the CLI-first framework tooling, and the fleet control plane. The
webUI audit (USC estate, webui-audit lane) measures the gap between this and
P1.
P1 — v1 slice (D11)
- Standalone onboarding wizard: system/company name, component choices, initial user, initial estate + project, seeded examples, re-runnable.
- Hierarchy core: company → estate → project → workspace → kanban, read-only task bubble-up (kanban SOT Amendment A1 is the schema contract).
- Basic RBAC on the hierarchy.
- Minimal agent enrollment: one harness, API key, name/persona.
Prerequisites: KBN-100/101 schema foundation; the D8 tool inventory and webUI→tool mapping (any missing tool is built first, D12).
P2 — connectors + comms (placeholder)
Email and drive connectors (Gmail/IMAP, Google Drive/OneDrive/Dropbox) with granular agentic-access consent; comms integrations (Matrix/Discord/Slack) including agent auto-enroll. Wizard gains the corresponding tabs (D4).
P3 — full onboarding profile + M365 (placeholder)
Complete user onboarding profile (communication-style capture, optional voice-matching interview) under the D14 custody rule; M365 integration for Enterprise-leaning deployments.
P4 — Enterprise mode + conversion (placeholder)
Enterprise install flow (org chart, RBAC focus, immediate OIDC, SSO prominent); per-user brains with architectural isolation (D14); Vault required; the one-way Standalone → Enterprise conversion (D3).
P5 — federation (placeholder)
Connecting deployments: system-level config, assigned users, rights and data-access control, trusts with boundaries, strict data access, exfiltration monitoring. Explicitly not designed yet (D3); nothing in earlier phases may foreclose it. Requires its own PRD + threat model before any scoping.