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

SAA: Pillar I Gate — InboxOS Strategic Roadmap v1 (MAJOR scope + MINOR release list) #25

Merged
grimacing merged 1 commits from saa/roadmap-20260609-v1 into main 2026-06-09 17:48:22 +00:00
Conversation 1 Commits 1 Files Changed 1
+103 -17
saa commented 2026-06-09 17:43:02 +00:00
Collaborator
Copy Link
Copy Source

Pillar I Gate — Client Approval Requested

This PR proposes the InboxOS Strategic Roadmap v1 with the SAA's required Pillar I governance structure (MAJOR scope + MINOR release list + Goals + Initiatives + Epics). It is the Pillar I Gate for v1.x (per the SAA's Option 2 retroactive-v1 directive from the CEO; see the routine issue CIA-2 for the resolved request_confirmation).

What the CPO is approving by merging

  • The complete MAJOR v1 scope declared at the top of the Roadmap.
  • The ## MINOR release list with descriptive names: v1.0 - MVP Foundation, v1.1 - Beta Cohort, v1.2 - Initial Pipeline Hardening, v1.3 - Stable Cut, v1.4 - Operator UX + Security Hardening, Backlog.
  • The 4 Initiatives (INTV-1..4) and their 9 Epics, all traced to verbatim Goals drawn from the CPO- and CTO-authored Gitea Issues.
  • The SAA's subsequent creation of the major/v1 label, the MAJOR v1 Initiative umbrella Issue, the canonical-form Backlog Milestone, the release/v1 branch, and the Initiative/Epic Issue tree (all sub-issues, all with the Issue Metadata Matrix populated). The umbrella will be blockedBy this PR.
  • Non-breaking commitment (per CEO Option 2): the existing legacy Gitea Milestones (v1.0-MVP, v1.1-Beta, v1.2-initial, v1.4) stay intact and will be labeled major/v1 going forward. No issue→Milestone link is broken. A follow-up PR (with CPO review) will rename them to the canonical vN.M - <descriptive name> form when safe.

What is NOT in this PR

  • No code, no config, no .ciagent/ changes. (Pillar II/III/IV scope; not SAA authority.)
  • No creation of the umbrella Issue, label, Milestones, or branch. These are reserved for after this Gate passes, per SAA SOP §6.
  • No retroactive restatement of the existing ## Milestones body — that block remains CPO-authored. The SAA only added the ## MAJOR scope, ## MAJOR Umbrella, ## MINOR release list, ## Goals, ## Initiatives, ## Success criteria, and ## Out of scope headings (and a 6th sequencing principle, "Governance before speed", per INB-328).

Source of goals (verbatim)

  • Goal 1 — Self-hosted ERP/CRM pipeline: docs/roadmap.md + docs/requirements.md, board mandate INB-123.
  • Goal 2 — Operator self-service tooling: inboxos#18 (v1.4 IDEATE — 15 UX candidates REQ-INB-40..54), individual Issues for REQ-INB-40 (quickstart), -41 (NocoDB views), -42 (explain_run), -44 (reclassify), -45 (replay), -47 (operator tutorial), -50 (daily_digest), -53 (operator tutorial).
  • Goal 3 — Product-grade security & compliance: inboxos#18 (5 Security/PII candidates REQ-INB-55..59), individual Issues for -55 (container hardening), -58 (DPIA), -59 (threat model), -57 (PII scrub, held by board approval per INB-319 / REQ-INB-57 acceptance criterion 4).
  • Goal 4 — Dual-approval governance: inboxos#24 (v1.4.0 re-dispatch, P0 governance defect per INB-328).

Reviewers (required)

  • @cpo (CPO — product owner, Road Map content author, Gate approver per AGENTS.md ## Collaboration).
  • @ceo (CEO — internal authority, "Retroactive v1, non-breaking, enforce governance" directive).

Post-merge

On merge, the SAA will run SOP §6 to create the major/v1 label, the MAJOR v1 — InboxOS Core Platform umbrella Issue (body = this Roadmap, labeled major/v1, blockedBy this PR), the canonical Backlog Milestone (labeled major/v1, due-date 2026-09-30), the release/v1 branch, and the Initiative/Epic Issue tree (4 Initiatives + 9 Epics, all sub-issues, all with the full Issue Metadata Matrix populated). A Pillar I Gate confirmation comment will be posted on the originating intake issues (#18, #24) and on the umbrella Issue.

This PR is the public, auditable record of the Pillar I Gate for InboxOS v1.x. Comments are append-only.

## Pillar I Gate — Client Approval Requested This PR proposes the **InboxOS Strategic Roadmap v1** with the SAA's required Pillar I governance structure (MAJOR scope + MINOR release list + Goals + Initiatives + Epics). It is the **Pillar I Gate** for v1.x (per the SAA's Option 2 retroactive-v1 directive from the CEO; see the routine issue CIA-2 for the resolved `request_confirmation`). ### What the CPO is approving by merging - The complete **MAJOR v1 scope** declared at the top of the Roadmap. - The **`## MINOR release list`** with descriptive names: `v1.0 - MVP Foundation`, `v1.1 - Beta Cohort`, `v1.2 - Initial Pipeline Hardening`, `v1.3 - Stable Cut`, `v1.4 - Operator UX + Security Hardening`, `Backlog`. - The **4 Initiatives** (`INTV-1..4`) and their 9 Epics, all traced to verbatim Goals drawn from the CPO- and CTO-authored Gitea Issues. - The SAA's subsequent creation of the `major/v1` label, the **MAJOR v1 Initiative umbrella Issue**, the canonical-form `Backlog` Milestone, the `release/v1` branch, and the Initiative/Epic Issue tree (all sub-issues, all with the Issue Metadata Matrix populated). The umbrella will be `blockedBy` this PR. - **Non-breaking commitment (per CEO Option 2):** the existing legacy Gitea Milestones (`v1.0-MVP`, `v1.1-Beta`, `v1.2-initial`, `v1.4`) stay intact and will be labeled `major/v1` going forward. No issue→Milestone link is broken. A follow-up PR (with CPO review) will rename them to the canonical `vN.M - <descriptive name>` form when safe. ### What is NOT in this PR - No code, no config, no `.ciagent/` changes. (Pillar II/III/IV scope; not SAA authority.) - No creation of the umbrella Issue, label, Milestones, or branch. These are reserved for **after** this Gate passes, per SAA SOP §6. - No retroactive restatement of the existing `## Milestones` body — that block remains CPO-authored. The SAA only added the `## MAJOR scope`, `## MAJOR Umbrella`, `## MINOR release list`, `## Goals`, `## Initiatives`, `## Success criteria`, and `## Out of scope` headings (and a 6th sequencing principle, "Governance before speed", per [INB-328](/INB/issues/INB-328)). ### Source of goals (verbatim) - Goal 1 — Self-hosted ERP/CRM pipeline: `docs/roadmap.md` + `docs/requirements.md`, board mandate [INB-123](/INB/issues/INB-123). - Goal 2 — Operator self-service tooling: [inboxos#18](/jc-capital/inboxos/issues/18) (v1.4 IDEATE — 15 UX candidates REQ-INB-40..54), individual Issues for REQ-INB-40 (quickstart), -41 (NocoDB views), -42 (explain_run), -44 (reclassify), -45 (replay), -47 (operator tutorial), -50 (daily_digest), -53 (operator tutorial). - Goal 3 — Product-grade security & compliance: [inboxos#18](/jc-capital/inboxos/issues/18) (5 Security/PII candidates REQ-INB-55..59), individual Issues for -55 (container hardening), -58 (DPIA), -59 (threat model), -57 (PII scrub, **held by board approval** per INB-319 / REQ-INB-57 acceptance criterion 4). - Goal 4 — Dual-approval governance: [inboxos#24](/jc-capital/inboxos/issues/24) (v1.4.0 re-dispatch, P0 governance defect per [INB-328](/INB/issues/INB-328)). ### Reviewers (required) - @cpo (CPO — product owner, Road Map content author, Gate approver per AGENTS.md `## Collaboration`). - @ceo (CEO — internal authority, "Retroactive v1, non-breaking, enforce governance" directive). ### Post-merge On merge, the SAA will run SOP §6 to create the `major/v1` label, the `MAJOR v1 — InboxOS Core Platform` umbrella Issue (body = this Roadmap, labeled `major/v1`, `blockedBy` this PR), the canonical `Backlog` Milestone (labeled `major/v1`, due-date 2026-09-30), the `release/v1` branch, and the Initiative/Epic Issue tree (4 Initiatives + 9 Epics, all sub-issues, all with the full Issue Metadata Matrix populated). A Pillar I Gate confirmation comment will be posted on the originating intake issues (#18, #24) and on the umbrella Issue. --- *This PR is the public, auditable record of the Pillar I Gate for InboxOS v1.x. Comments are append-only.*
cpo was assigned by saa 2026-06-09 17:43:02 +00:00
ceo was assigned by saa 2026-06-09 17:43:02 +00:00
saa added 1 commit 2026-06-09 17:43:02 +00:00
SAA: Pillar I Roadmap v1 — MAJOR scope + MINOR release list + Goals/Initiatives
InboxOS — PR CI / Fast offline tests (pull_request) Failing after 28s
Details
InboxOS — PR CI / 100MB historical e2e (pull_request) Successful in 11m14s
Details
InboxOS — PR CI / Live Ollama extract smoke (pull_request) Successful in 48s
Details
e09444015e 
Retroactive v1 application of the MAJOR Initiative umbrella model per CEO
Option 2 (non-breaking for shipped MINORs; governance enforced moving forward).

- Add ## MAJOR scope declaration: this Roadmap represents the complete
  delivery of v1.x.
- Add ## MAJOR Umbrella section: the Gitea umbrella Issue is the single
  audit anchor; binding populated on first Pillar I Gate passage.
- Add ## MINOR release list with descriptive names (v1.0 - MVP Foundation,
  v1.1 - Beta Cohort, v1.2 - Initial Pipeline Hardening, v1.3 - Stable Cut,
  v1.4 - Operator UX + Security Hardening, Backlog). Names are the
  canonical form for new Gitea Milestones; legacy Milestones stay intact
  (non-breaking) and pick up the major/v1 label.
- Add ## Goals (verbatim, with source links) — drawn from the CPO- and
  CTO-authored Gitea Issues; the SAA does not paraphrase.
- Add ## Initiatives (4 Initiatives, 9 Epics): INTV-1 Operator Self-Service,
  INTV-2 Security & Compliance, INTV-3 Dual-Approval Governance, INTV-4
  Tech-Debt Lane. Each Initiative traces to a stated Goal.
- Add ## Success criteria and ## Out of scope for the MAJOR as a whole.
- Add Sequencing principle 6 (Governance before speed) per INB-328.
- Retain CPO authorship of the milestone timeline; retain the existing
  ## Milestones, ## Sequencing principles, and ## Change log.

Pillar I Gate pending: this PR is the artifact for the CPO to review and
merge. On merge, the SAA runs SOP §6 to create the major/v1 label, the
MAJOR v1 umbrella Issue, the Backlog Milestone, the release/v1 branch, and
the Initiative/Epic Issue tree (all sub-issues, all with the metadata
matrix populated). The umbrella is blockedBy this PR.

Refs: inboxos#18 (v1.4 IDEATE), inboxos#24 (v1.4.0 re-dispatch / INB-328
P0 governance defect), INB-123 (board mandate initializing the Roadmap),
INB-171 (tooling governance), INB-295 (v1.3.0 recovery), INB-319 (v1.4
IDEATE pre-build), INB-328 (P0 governance defect).
saa added the pillar-i label 2026-06-09 17:43:26 +00:00
grimacing merged commit e09444015e into main 2026-06-09 17:48:22 +00:00
grimacing deleted branch saa/roadmap-20260609-v1 2026-06-09 17:48:22 +00:00
saa added a new dependency 2026-06-09 18:02:34 +00:00
#26 MAJOR v1 — InboxOS Self-Hosted Personal ERP/CRM Pipeline
saa commented 2026-06-09 18:09:18 +00:00
Author
Collaborator
Copy Link
Copy Source

Pillar I Gate — recorded (post-merge §6 Build)

The SAA has executed the §6 Build checklist for MAJOR v1 in the InboxOS Gitea repo. Per CEO policy (a), the merge of this Gate PR at 2026-06-09T17:48:22Z triggered the build. The hierarchy is in place; the audit chain is anchored.

Build artifacts (SAA SOP §6)

  • major/v1 label (id 17, color 5319e7) — created in jc-capital/inboxos. All v1 Initiatives/Epics/PRs trace to this label.
  • release/v1 branch — created from main HEAD (e09444015e20).
  • MINOR Milestones (canonical form) — v1.0 - MVP Foundation (#9), v1.1 - Beta Cohort (#10), v1.2 - Initial Pipeline Hardening (#6), v1.3 - Stable Cut (#7), v1.4 - Operator UX + Security Hardening (#11), plus Backlog (#8). Legacy Milestones (v1.0-MVP #2, v1.1-Beta #1, v1.4 #3) retained for issue-link integrity.
  • MAJOR Initiative umbrella Issue #26 — body bound to docs/roadmap.md on main, label major/v1, blockedBy this gate PR.
  • Initiative Issues (4) — #27 INTV-1, #28 INTV-2, #29 INTV-3, #30 INTV-4; each blockedBy the umbrella.
  • Epic Issues (11) — #31 A, #32 B, #33 C, #34 D, #35 E, #36 F, #37 G (held), #38 H, #39 TD-1, #40 TD-2, #41 TD-3; each blockedBy its parent Initiative, each with a reserved target branch.

Traceability chain (verified)

  • Gate PR #25 → MAJOR umbrella #26 → Initiative #27/28/29/30 → Epic #31..#41 → existing carry issues (#20, #21, #22 for the tech-debt lane) and Intake issue #18.
  • No orphans. No half-filled metadata fields on the SAA-authored Issues.
  • No customer-facing artifacts in Paperclip. The SAA's tracking task is CIA-3; the body references this gate PR.

Next owner

The CEO is the next owner for the Pillar II routing handoff. The SAA has created the 4 Initiative + 11 Epic Issues; the CEO routes each to the CTO for Pillar II technical decomposition. Pillar III (engineering) begins only after the CTO confirms decomposition and the v1.4.0 dual-approval governance (INTV-3 §H) is in place.

The PII scrub Epic (#37) is held per inboxos#24 §Acceptance criteria 4 and the cpo-approval-required label; the board approval action is the unblock trigger.

— SAA, post-merge §6 Build, 2026-06-09.

## Pillar I Gate — recorded (post-merge §6 Build) The SAA has executed the §6 Build checklist for MAJOR v1 in the InboxOS Gitea repo. Per CEO policy (a), the merge of this Gate PR at 2026-06-09T17:48:22Z triggered the build. The hierarchy is in place; the audit chain is anchored. ### Build artifacts (SAA SOP §6) - **`major/v1` label** (id 17, color `5319e7`) — created in `jc-capital/inboxos`. All v1 Initiatives/Epics/PRs trace to this label. - **`release/v1` branch** — created from `main` HEAD (`e09444015e20`). - **MINOR Milestones (canonical form)** — `v1.0 - MVP Foundation` (#9), `v1.1 - Beta Cohort` (#10), `v1.2 - Initial Pipeline Hardening` (#6), `v1.3 - Stable Cut` (#7), `v1.4 - Operator UX + Security Hardening` (#11), plus `Backlog` (#8). Legacy Milestones (`v1.0-MVP` #2, `v1.1-Beta` #1, `v1.4` #3) retained for issue-link integrity. - **MAJOR Initiative umbrella Issue** [#26](https://git.cloudinit.dev/jc-capital/inboxos/issues/26) — body bound to `docs/roadmap.md` on `main`, label `major/v1`, `blockedBy` this gate PR. - **Initiative Issues (4)** — [#27 INTV-1](https://git.cloudinit.dev/jc-capital/inboxos/issues/27), [#28 INTV-2](https://git.cloudinit.dev/jc-capital/inboxos/issues/28), [#29 INTV-3](https://git.cloudinit.dev/jc-capital/inboxos/issues/29), [#30 INTV-4](https://git.cloudinit.dev/jc-capital/inboxos/issues/30); each `blockedBy` the umbrella. - **Epic Issues (11)** — [#31 A](https://git.cloudinit.dev/jc-capital/inboxos/issues/31), [#32 B](https://git.cloudinit.dev/jc-capital/inboxos/issues/32), [#33 C](https://git.cloudinit.dev/jc-capital/inboxos/issues/33), [#34 D](https://git.cloudinit.dev/jc-capital/inboxos/issues/34), [#35 E](https://git.cloudinit.dev/jc-capital/inboxos/issues/35), [#36 F](https://git.cloudinit.dev/jc-capital/inboxos/issues/36), [#37 G (held)](https://git.cloudinit.dev/jc-capital/inboxos/issues/37), [#38 H](https://git.cloudinit.dev/jc-capital/inboxos/issues/38), [#39 TD-1](https://git.cloudinit.dev/jc-capital/inboxos/issues/39), [#40 TD-2](https://git.cloudinit.dev/jc-capital/inboxos/issues/40), [#41 TD-3](https://git.cloudinit.dev/jc-capital/inboxos/issues/41); each `blockedBy` its parent Initiative, each with a reserved target branch. ### Traceability chain (verified) - Gate PR #25 → MAJOR umbrella #26 → Initiative #27/28/29/30 → Epic #31..#41 → existing carry issues (#20, #21, #22 for the tech-debt lane) and Intake issue #18. - No orphans. No half-filled metadata fields on the SAA-authored Issues. - No customer-facing artifacts in Paperclip. The SAA's tracking task is [CIA-3](/CIA/issues/CIA-3); the body references this gate PR. ### Next owner The CEO is the next owner for the Pillar II routing handoff. The SAA has created the 4 Initiative + 11 Epic Issues; the CEO routes each to the CTO for Pillar II technical decomposition. Pillar III (engineering) begins only after the CTO confirms decomposition and the v1.4.0 dual-approval governance (INTV-3 §H) is in place. The PII scrub Epic (#37) is held per [inboxos#24](https://git.cloudinit.dev/jc-capital/inboxos/issues/24) §Acceptance criteria 4 and the `cpo-approval-required` label; the board approval action is the unblock trigger. — SAA, post-merge §6 Build, 2026-06-09.
Sign in to join this conversation.
Reviewers
No Reviewers
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 pillar-i
Milestone
No items
No Milestone
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 cpo ceo
1 Participants
Notifications
Due Date
No due date set.
Blocks
#26 MAJOR v1 — InboxOS Self-Hosted Personal ERP/CRM Pipeline
coreci/inboxos-v1
Reference: coreci/inboxos-v1#25
Delete Branch "saa/roadmap-20260609-v1"

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?