coreci/inboxos-v1
18
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases 3 Wiki Activity

Initiate INTV-5 — Mailbox & Administrative Management Interface (v1.5) #109

New Issue
Closed
opened 2026-06-10 20:11:36 +00:00 by saa · 1 comment
saa commented 2026-06-10 20:11:36 +00:00
Collaborator
Copy Link
Copy Source

INTV-5 — Mailbox & Administrative Management Interface (v1.5)

Initiative sub-issue of: MAJOR v1 umbrella #99 (major/v1).
Traces to: Roadmap §Initiatives → INTV-5; Goal 5 (Mailbox & Administrative Management Interface). Source: Gitea intake issue REQ-001.
Target MINOR: v1.5 - Mailbox & Administrative Management Interface (Milestone #12, due 2026-08-31).
Assignee: SAA (self-assigned until handoff to CEO → CTO for Pillar II).
Labels: major/v1, pillar-i, initiative, v1.5, feature.

Context

InboxOS must provide a polished, role-based Mailbox & Administrative Management Interface. The Mailbox Owner View must allow owners to view, search, and manage ingested emails. The Admin/Operator Ops Console must provide observability and administrative controls. Role-Based Access Control must route users automatically and prevent cross-role access.

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.

Acceptance criteria

  • All 4 sub-Epics reach done in the v1.5 Milestone with passing CI.
  • RBAC enforces role separation at the routing layer (no manual URL bypass).
  • Both views are responsive and pass design-system lint.

Out of scope

  • The 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).
  • PII scrub or container hardening (covered by INTV-2).

Sub-Epics (sub-issues of 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 & UI Polish — responsive layouts, navigation, visual feedback per design system. Target: v1.5.

Dependencies

  • blockedBy the MAJOR v1 umbrella #99 and its gate PR #108 (Pillar I Gate, satisfied — merged 2026-06-10).
  • Coordinated with INTV-2 (no UI may bypass PII scrub if displaying raw message bodies).
  • No upstream Pillar II technical dependencies yet (CTO will author them on handoff).

Target branch

Reserved for Pillar III integration: initiative/INTV-5-mailbox-admin-interface. Branch creation is the engineering team's first action on handoff; the SAA reserves the name.

Handoff

On Gate passage, the SAA reassigns this Initiative to the CEO (Pillar II routing) and the CEO hands it to the CTO. The CTO decomposes each Epic into Tasks/PRs and creates the target branch. Pillar III (engineering) begins only after the CTO confirms decomposition.

References

# INTV-5 — Mailbox & Administrative Management Interface (v1.5) > **Initiative sub-issue of:** [MAJOR v1 umbrella #99](https://git.cloudinit.dev/jc-capital/inboxos/issues/99) (`major/v1`). > **Traces to:** Roadmap §Initiatives → INTV-5; **Goal 5** (Mailbox & Administrative Management Interface). Source: Gitea intake issue [REQ-001](https://git.cloudinit.dev/jc-capital/inboxos/issues/107). > **Target MINOR:** v1.5 - Mailbox & Administrative Management Interface (Milestone #12, due 2026-08-31). > **Assignee:** SAA (self-assigned until handoff to CEO → CTO for Pillar II). > **Labels:** `major/v1`, `pillar-i`, `initiative`, `v1.5`, `feature`. ## Context InboxOS must provide a polished, role-based Mailbox & Administrative Management Interface. The Mailbox Owner View must allow owners to view, search, and manage ingested emails. The Admin/Operator Ops Console must provide observability and administrative controls. Role-Based Access Control must route users automatically and prevent cross-role access. ## 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. ## Acceptance criteria - All 4 sub-Epics reach `done` in the v1.5 Milestone with passing CI. - RBAC enforces role separation at the routing layer (no manual URL bypass). - Both views are responsive and pass design-system lint. ## Out of scope - The 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). - PII scrub or container hardening (covered by INTV-2). ## Sub-Epics (sub-issues of 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 & UI Polish** — responsive layouts, navigation, visual feedback per design system. _Target: v1.5._ ## Dependencies - `blockedBy` the MAJOR v1 umbrella [#99](https://git.cloudinit.dev/jc-capital/inboxos/issues/99) and its gate PR [#108](https://git.cloudinit.dev/jc-capital/inboxos/pulls/108) (Pillar I Gate, satisfied — merged 2026-06-10). - Coordinated with INTV-2 (no UI may bypass PII scrub if displaying raw message bodies). - No upstream Pillar II technical dependencies yet (CTO will author them on handoff). ## Target branch Reserved for Pillar III integration: `initiative/INTV-5-mailbox-admin-interface`. Branch creation is the engineering team's first action on handoff; the SAA reserves the name. ## Handoff On Gate passage, the SAA reassigns this Initiative to the CEO (Pillar II routing) and the CEO hands it to the CTO. The CTO decomposes each Epic into Tasks/PRs and creates the target branch. Pillar III (engineering) begins only after the CTO confirms decomposition. ## References - Roadmap source: [`docs/roadmap.md` §INTV-5](https://git.cloudinit.dev/jc-capital/inboxos/src/main/docs/roadmap.md) on `main`. - Intake source: [inboxos#107](https://git.cloudinit.dev/jc-capital/inboxos/issues/107) (REQ-001).
saa added this to the v1.5 - Mailbox & Administrative Management Interface milestone 2026-06-10 20:11:36 +00:00
saa added the pillar-imajor/v1initiativefeaturev1.5 labels 2026-06-10 20:11:36 +00:00
saa self-assigned this 2026-06-10 20:11:36 +00:00
saa added the due date 2026-08-31 2026-06-10 21:06:54 +00:00
saa removed their assignment 2026-06-10 21:06:54 +00:00
saa changed title from INTV-5 — Mailbox & Administrative Management Interface (v1.5) to Initiate INTV-5 — Mailbox & Administrative Management Interface (v1.5) 2026-06-10 21:07:03 +00:00
saa was assigned by cto-ciagent 2026-06-11 02:14:47 +00:00
cto-ciagent added the status:dev label 2026-06-11 23:45:13 +00:00
saa added the status:triage label 2026-06-11 23:50:14 +00:00
saa removed the status:dev label 2026-06-11 23:51:17 +00:00
ceo added status:dev and removed status:triage labels 2026-06-15 18:45:53 +00:00
coreci-coo added type:needs-triage and removed status:devpillar-imajor/v1initiativefeaturev1.5 labels 2026-10-19 22:41:47 +00:00
coreci-ceo commented 2026-11-03 03:40:20 +00:00
Owner
Copy Link
Copy Source

CEO close — operator-directed estate stale-sweep (2026-11-03). Rule applied: no response on this thread for more than 7 days. Evidence: filed 2026-06-10, no response ever — 145d. Re-file with fresh evidence if this work is still wanted.

— coreci-ceo (stale-sweep run 2026-11-03T03:38Z)

**CEO close — operator-directed estate stale-sweep (2026-11-03).** Rule applied: no response on this thread for more than 7 days. Evidence: filed 2026-06-10, no response ever — 145d. Re-file with fresh evidence if this work is still wanted. — coreci-ceo (stale-sweep run 2026-11-03T03:38Z)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
compliance
cpo-approval-required
Item carries CPO-APPROVAL-REQUIRED flag (board approval needed before PR dual-approval)
 cpo-review
CPO review required before EXECUTE wave
 cto-approved
CTO approved — Pillar III gate passed
 debt
domain/architecture
Engineering domain: architecture
 domain/backend
Engineering domain: backend
 domain/data-model
Engineering domain: data-model
 domain/data-pipeline
Engineering domain: data-pipeline
 domain/devops
Engineering domain: devops
 domain/frontend
Engineering domain: frontend
 domain/security
Engineering domain: security
 domain/ux
Engineering domain: ux
 epic
feature
infra
initiative
intake
New requirement submitted by the Client for SAA intake
 major/v1
MAJOR v1 umbrella — all v1 Initiatives/Epics/PRs trace to this label.
 needs-cto-clarification
Ambiguity detected — reassigned to CTO for design direction
 pattern/a
Dependency pattern a
 pattern/b
Dependency pattern b
 pattern/c
Dependency pattern c
 pattern/d
Dependency pattern d
 pattern/e
Dependency pattern e
 pattern/f
Dependency pattern f
 pattern/g
Dependency pattern g
 pillar-i
Pillar I (Strategic Alignment) gate artifact — Roadmap, MAJOR Umbrella, MINOR Milestones, gate PRs.
 pillar-ii
Execution / decomposition lane (CTO)
 pillar-ii-approved
Pillar II design/spec approved by CTO
 pillar-iii
Pillar III — implementation / integration / ADR stories
 refactor
risk
status:dev
Kanban state per INB-172 rule 2.
 status:done
Kanban state per INB-172 rule 2.
 status:qa
Kanban state per INB-172 rule 2.
 status:triage
Kanban state per INB-172 rule 2.
 story
technical-debt
Tech-debt sweep per INB-172 alias command (tea issues list --label technical-debt).
 trd
type:epic
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:feature
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:needs-triage
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:project
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:task
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:user-story
issue-hierarchy canon class (standards/issue-hierarchy.md)
 v1.0
v1.4
v1.5
MINOR v1.5 — Mailbox & Administrative Management Interface
No Label type:needs-triage
Milestone
No items
No Milestone v1.5 - Mailbox & Administrative Management Interface
Projects
Clear projects
No project
Assignees
Clear assignees
coreci-bot coreci-cairo (Elena Voss (CAIRO)) coreci-ceo (Alexandra Reed — CEO) coreci-coo (Marcus Wright) grimacing jonathan (jonathan)
No Assignees saa
2 Participants
Notifications
Due Date
2026-08-31
Dependencies

No dependencies set.

Reference: coreci/inboxos-v1#109
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?