docs(roadmap): absorb REQ-001 into MAJOR v1 as MINOR v1.5

- Add Goal 5 (Mailbox & Administrative Management Interface) - Add Initiative INTV-5 with Epics A-D - Add MINOR v1.5 to release list - Record REQ-001 in requirements.md - Resolve open questions on intake issue #107 Traces to: REQ-001, CIA-79 Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-06-10 19:50:34 +00:00
parent 840c40d6af
commit 69488d2ef5
2 changed files with 48 additions and 2 deletions
@@ -38,9 +38,32 @@ As a <user>, I want <capability>, so that <outcome>.

 ## Initial requirements

-The CPO will populate this section with the first committed set. Until then, this list is intentionally empty - the CPO owns the prioritization call, not the CEO.
+### REQ-001 - Mailbox & Administrative Management Interface

-_No requirements authored yet. The CPO is the only role authorized to add entries._
+- **Owner:** CPO
+- **Status:** Draft
+- **Priority:** P0
+- **Linked issue:** [REQ-001](/jc-capital/inboxos/issues/107)
+- **Roadmap milestone:** v1.5
+
+**User story.**
+As a system user (Mailbox Owner, Operator, or Administrator), I want a polished, role-based interface to manage ingested emails and monitor system health, so that I can efficiently process communications and ensure operational stability.
+
+**Acceptance criteria.**
+1. **Mailbox Owner View:** A dedicated dashboard where owners can view a list of ingested emails, search/filter by metadata, and perform management actions (e.g., archive, mark as processed).
+2. **Admin/Operator View:** A distinct "Ops Console" providing a high-level observability dashboard (e.g., ingestion rates, error logs, system latency) and administrative controls (e.g., user permission management, global configuration).
+3. **Role-Based Access Control (RBAC):** The system must automatically route users to the correct view based on their permissions, preventing Mailbox Owners from accessing the Admin/Operator console.
+4. **UI/UX Polish:** The interface must adhere to the design system, ensuring responsive layouts, intuitive navigation, and clear visual feedback for all user actions.
+
+**Out of scope.**
+- Implementation of the actual email ingestion engine (backend logic).
+- Integration with third-party email clients (e.g., Outlook/Gmail plugins).
+- Advanced analytics/reporting tools (e.g., custom PDF reports).
+
+**Open questions.**
+- *Resolved on Gitea:*
+  - Super Admin view: strictly separated (Mailbox Owner and Operator views remain distinct).
+  - Compliance/audit logs: basic observability for the first round; advanced compliance/audit logging is deferred.

 ## Change log

@@ -34,6 +34,7 @@ The MINOR names below are used verbatim to name Gitea Milestones (SAA SOP §6.3,
 - **v1.2 - Initial Pipeline Hardening** — papra + imapclient + schema discipline. _Status: shipped._
 - **v1.3 - Stable Cut** — stable post-recovery cut. _Status: shipped; release quarantined and recovered per [INB-295](/INB/issues/INB-295) / inboxos#17. No further commits under this MINOR without a fresh Pillar I Gate round._
 - **v1.4 - Operator UX + Security Hardening** — operator tooling (scripts, dashboards, tutorials), NocoDB views, container hardening, DPIA, threat model, PII scrub (held by `REQ-INB-57` until board approval lands). _Status: active, re-dispatching per inboxos#24 to enforce dual-approval governance on the v1.4.0 wave._
+- **v1.5 - Mailbox & Administrative Management Interface** — role-based UI/UX for Mailbox Owners and Admin/Operators, RBAC routing, and design-system compliance. _Status: declared, pending Pillar I Gate approval._
 - **Backlog** — approved v1 work not yet scheduled into a MINOR. _Status: open._

 The Gitea Milestones in the repo carry the **title only** form (`v1.0-MVP`, `v1.1-Beta`, `v1.2-initial`, `v1.4`) for historical reasons. The SAA will:
@@ -54,6 +55,9 @@ Drawn from Gitea Issues authored by the CPO (the product owner) and the CTO (tec
   - _Source: Gitea Issues [inboxos#18](/jc-capital/inboxos/issues/18) (5 Security/PII candidates, REQ-INB-55..59), [inboxos#55..59] (container hardening, DPIA, threat model, pii_scrub)._
 4. **Governance must be enforced at the PR-merge layer** — dual approval (CPO + CTO), no force-merge, audit trail intact.
   - _Source: Gitea Issue [inboxos#24](/jc-capital/inboxos/issues/24) (v1.4.0 re-dispatch, P0 governance defect per [INB-328](/INB/issues/INB-328))._
+5. **InboxOS must provide a polished, role-based Mailbox & Administrative Management Interface.**
+   - _Source: Gitea intake issue [REQ-001](/jc-capital/inboxos/issues/107) (grimacing, 2026-06-10)._
+   - _Open questions resolved:_ Super Admin view strictly separated; compliance/audit logs kept basic for the first round.

 ## Initiatives

@@ -98,6 +102,24 @@ Initiatives are product-level strategic themes. Each Initiative is a sub-issue o
  - **EPIC-INB-1.0-TD-2: imapclient runtime-shim test** (REQ-INB-39). _Target: v1.0-MVP._
  - **EPIC-INB-1.0-TD-3: .gitignore opencode.json un-shadow** (REQ-INB-35c). _Target: v1.0-MVP._

+### INTV-5 — Mailbox & Administrative Management Interface (v1.5)
+
+- **Traces to:** Goal 5 (Mailbox & Administrative Management Interface).
+- **Success criteria:**
+  1. A dedicated Mailbox Owner View (dashboard) exists where owners can view a list of ingested emails, search/filter by metadata, and perform management actions (e.g., archive, mark as processed).
+  2. A distinct Admin/Operator "Ops Console" exists providing high-level observability (ingestion rates, error logs, system latency) and administrative controls (user permission management, global configuration).
+  3. Role-Based Access Control (RBAC) automatically routes users to the correct view based on permissions, preventing Mailbox Owners from accessing the Admin/Operator console.
+  4. UI/UX polish: responsive layouts, intuitive navigation, clear visual feedback per the design system.
+- **Out of scope:**
+  - The actual email ingestion engine (backend logic) — already covered by existing pipeline work.
+  - Integration with third-party email clients (Outlook/Gmail plugins).
+  - Advanced analytics/reporting tools (custom PDF reports).
+- **Epics (decomposed under this Initiative):**
+  - **EPIC-INB-1.5-A: Mailbox Owner Dashboard** — UI + RBAC routing for the Mailbox Owner role (REQ-001 AC-1). _Target: v1.5._
+  - **EPIC-INB-1.5-B: Admin/Operator Ops Console** — observability dashboard + administrative controls (REQ-001 AC-2). _Target: v1.5._
+  - **EPIC-INB-1.5-C: RBAC & Auth Layer** — role enforcement, permission checks, routing middleware (REQ-001 AC-3). _Target: v1.5._
+  - **EPIC-INB-1.5-D: Design System Compliance** — responsive layouts, navigation, visual feedback (REQ-001 AC-4). _Target: v1.5._
+
 ## Success criteria (MAJOR v1)

 - Every Gitea Issue in v1.x scope traces to a stated Goal above.
@@ -127,3 +149,4 @@ Initiatives are product-level strategic themes. Each Initiative is a sub-issue o
 |------------|--------|--------|
 | 2026-06-08 | CEO    | Initialized document per Board mandate [INB-123](/INB/issues/INB-123). CPO owns from this point forward. |
 | 2026-06-09 | SAA    | Added `## MAJOR scope`, `## MAJOR Umbrella`, `## MINOR release list`, `## Goals` (verbatim), `## Initiatives`, and `## Success criteria` / `## Out of scope` headings per the SAA's Pillar I governance model. Retained the CPO-owned `## Milestones` body, the `## Sequencing principles`, and the `## Change log` block unchanged. Bound to the MAJOR v1 umbrella Issue (populated on gate passage). Pending Pillar I Gate PR. |
+| 2026-06-10 | SAA    | Added Goal 5 (REQ-001 — Mailbox & Administrative Management Interface), Initiative INTV-5 with four Epics (EPIC-INB-1.5-A..D), and MINOR v1.5 to the release list. Open questions resolved on Gitea issue #107. Roadmap revision pending Pillar I Gate PR. |