docs(federation): PRD, milestones, mission manifest, and M1 task breakdown #467

jason.woltje · 2026-04-19T22:05:31Z

jason.woltje commented

2026-04-19 22:05:31 +00:00

Summary

Planning artifacts for the Federation v1 mission — PRD, milestones, mission manifest, and FED-M1 task breakdown. No code changes.

Federation builds asymmetric, gateway-to-gateway data federation between Mosaic Stack instances: a user's home gateway can query their work gateway in real time during a session, with scoped RBAC and no data persistence across the boundary. Uses X.509 mTLS via Step-CA for trust management.

What's in this PR

docs/federation/PRD.md — 16-section product requirements (locked)
docs/federation/MILESTONES.md — 7-milestone decomposition with per-milestone unit/integration/E2E acceptance test tables
docs/federation/MISSION-MANIFEST.md — mission scope, 13 success criteria, milestone table linked to issues
docs/federation/TASKS.md — FED-M1 fully decomposed into 12 tasks with agent assignments and budgets; M2–M7 deferred to per-milestone planning

Tracking issues

FED-M1 (#460) — Federated tier infrastructure
FED-M2 (#461) — Step-CA + grant schema + admin CLI
FED-M3 (#462) — mTLS handshake + list/get + scope enforcement
FED-M4 (#463) — search + audit + rate limit
FED-M5 (#464) — cache + offline + OTEL
FED-M6 (#465) — revocation + auto-renewal + CRL
FED-M7 (#466) — multi-user hardening + acceptance suite

All linked to milestone Federation v1.

Test plan

Docs-only PR — no code executes from this change.

PRD, MILESTONES, MISSION-MANIFEST, and TASKS.md render correctly on Gitea
All 7 tracking issues link back correctly in MISSION-MANIFEST table
Prettier check passes (already green locally)

Next step after merge

Begin FED-M1 implementation per docs/federation/TASKS.md. First task is FED-M1-01 (extend tier enum to include federated).

## Summary Planning artifacts for the Federation v1 mission — PRD, milestones, mission manifest, and FED-M1 task breakdown. No code changes. Federation builds asymmetric, gateway-to-gateway data federation between Mosaic Stack instances: a user's home gateway can query their work gateway in real time during a session, with scoped RBAC and no data persistence across the boundary. Uses X.509 mTLS via Step-CA for trust management. ## What's in this PR - `docs/federation/PRD.md` — 16-section product requirements (locked) - `docs/federation/MILESTONES.md` — 7-milestone decomposition with per-milestone unit/integration/E2E acceptance test tables - `docs/federation/MISSION-MANIFEST.md` — mission scope, 13 success criteria, milestone table linked to issues - `docs/federation/TASKS.md` — FED-M1 fully decomposed into 12 tasks with agent assignments and budgets; M2–M7 deferred to per-milestone planning ## Tracking issues - FED-M1 (#460) — Federated tier infrastructure - FED-M2 (#461) — Step-CA + grant schema + admin CLI - FED-M3 (#462) — mTLS handshake + list/get + scope enforcement - FED-M4 (#463) — search + audit + rate limit - FED-M5 (#464) — cache + offline + OTEL - FED-M6 (#465) — revocation + auto-renewal + CRL - FED-M7 (#466) — multi-user hardening + acceptance suite All linked to milestone **Federation v1**. ## Test plan Docs-only PR — no code executes from this change. - [ ] PRD, MILESTONES, MISSION-MANIFEST, and TASKS.md render correctly on Gitea - [ ] All 7 tracking issues link back correctly in MISSION-MANIFEST table - [ ] Prettier check passes (already green locally) ## Next step after merge Begin FED-M1 implementation per `docs/federation/TASKS.md`. First task is `FED-M1-01` (extend `tier` enum to include `federated`).

jason.woltje added 1 commit 2026-04-19 22:05:32 +00:00

docs(federation): PRD, milestones, mission manifest, and M1 task breakdown

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

47aac682f5

Plans the Federation v1 mission: cross-instance data federation between
Mosaic Stack gateways with asymmetric trust (home gateway sees blended
A+B at session time; work gateway sees only its own tenants), mTLS via
X.509 / Step-CA for auth, multi-tenant RBAC with no cross-user leakage,
and no data persistence across the boundary.

- docs/federation/PRD.md — 16-section product requirements (v1 locked)
- docs/federation/MILESTONES.md — 7-milestone decomposition with
  per-milestone acceptance test tables across unit/integration/E2E layers
- docs/federation/MISSION-MANIFEST.md — mission scope, success criteria,
  milestone table linked to issues #460-#466
- docs/federation/TASKS.md — FED-M1 decomposed into 12 tasks; M2-M7
  deferred to per-milestone planning to avoid speculative decomposition

Refs: #460 #461 #462 #463 #464 #465 #466

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

jason.woltje merged commit 46dd799548 into main

2026-04-19 22:09:21 +00:00

jason.woltje referenced this issue from a commit

2026-04-19 22:09:23 +00:00

docs(federation): PRD, milestones, mission manifest, and M1 task breakdown (#467)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#467