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

EPIC-INB-1.4-B: NocoDB Operator Views #32

New Issue
Closed
opened 2026-06-09 18:08:16 +00:00 by saa · 1 comment
saa commented 2026-06-09 18:08:16 +00:00
Collaborator
Copy Link
Copy Source

EPIC-INB-1.4-B: NocoDB Operator Views

Epic sub-issue of: INTV-1 #27 — sub-Issue of MAJOR v1 umbrella #99 (major/v1).
Traces to: Roadmap §Initiatives → INTV-1 → EPIC-INB-1.4-B; Goal 2 (operator tooling).
Target MINOR: v1.4 - Operator UX + Security Hardening (Milestone #11, due 2026-08-31).
Assignee: SAA (self-assigned until handoff to CEO → CTO for Pillar II).
Labels: major/v1, pillar-i, epic, v1.4, feature.

Context

Operators need a read/observe surface that's faster than running scripts. Curated NocoDB views per module give them at-a-glance pipeline state. REQ-INB-41.

Success criteria

  • Each InboxOS module has a curated NocoDB view (default sort + filters + visible columns).
  • The views are linked from docs/operator-tutorial.md (INTV-1 §A).

Acceptance criteria

  • NocoDB view definitions (per module) are committed under nocodb/views/ (or equivalent).
  • An operator can read pipeline state from a NocoDB view without any other tooling.

Out of scope

  • PII handling inside the views (coordinated with INTV-2 §G — PII scrub held per board approval).
  • NocoDB audit log schema (deferred to v1.5+ per inboxos#18 DEF-V1.4-4).

Dependencies

  • blockedBy INTV-1 #27 (parent Initiative) and the umbrella #99.
  • Coordinated with EPIC-INB-1.4-A (the tutorial links to the views).

Target branch

Reserved for Pillar III integration: epic/EPIC-INB-1.4-B-nocodb-operator-views. Branch creation is the engineering team's first action on handoff; the SAA reserves the name.

Handoff

On Gate passage, the SAA reassigns this Epic to the CEO (Pillar II routing) and the CEO hands it to the CTO. The CTO decomposes it into Tasks/PRs.

References

# EPIC-INB-1.4-B: NocoDB Operator Views > **Epic sub-issue of:** [INTV-1 #27](https://git.cloudinit.dev/jc-capital/inboxos/issues/27) — sub-Issue of [MAJOR v1 umbrella #99](https://git.cloudinit.dev/jc-capital/inboxos/issues/99) (`major/v1`). > **Traces to:** Roadmap §Initiatives → INTV-1 → EPIC-INB-1.4-B; **Goal 2** (operator tooling). > **Target MINOR:** v1.4 - Operator UX + Security Hardening (Milestone #11, due 2026-08-31). > **Assignee:** SAA (self-assigned until handoff to CEO → CTO for Pillar II). > **Labels:** `major/v1`, `pillar-i`, `epic`, `v1.4`, `feature`. ## Context Operators need a read/observe surface that's faster than running scripts. Curated NocoDB views per module give them at-a-glance pipeline state. REQ-INB-41. ## Success criteria - Each InboxOS module has a curated NocoDB view (default sort + filters + visible columns). - The views are linked from `docs/operator-tutorial.md` (INTV-1 §A). ## Acceptance criteria - NocoDB view definitions (per module) are committed under `nocodb/views/` (or equivalent). - An operator can read pipeline state from a NocoDB view without any other tooling. ## Out of scope - PII handling inside the views (coordinated with INTV-2 §G — PII scrub held per board approval). - NocoDB audit log schema (deferred to v1.5+ per inboxos#18 DEF-V1.4-4). ## Dependencies - `blockedBy` [INTV-1 #27](https://git.cloudinit.dev/jc-capital/inboxos/issues/27) (parent Initiative) and the umbrella [#99](https://git.cloudinit.dev/jc-capital/inboxos/issues/99). - Coordinated with EPIC-INB-1.4-A (the tutorial links to the views). ## Target branch Reserved for Pillar III integration: `epic/EPIC-INB-1.4-B-nocodb-operator-views`. Branch creation is the engineering team's first action on handoff; the SAA reserves the name. ## Handoff On Gate passage, the SAA reassigns this Epic to the CEO (Pillar II routing) and the CEO hands it to the CTO. The CTO decomposes it into Tasks/PRs. ## References - Roadmap source: [`docs/roadmap.md` §EPIC-INB-1.4-B](https://git.cloudinit.dev/jc-capital/inboxos/src/main/docs/roadmap.md) on `main`. - Requirements: REQ-INB-41.
saa added this to the v1.4 - Operator UX + Security Hardening milestone 2026-06-09 18:08:16 +00:00
saa added the status:triagepillar-imajor/v1 labels 2026-06-09 18:08:16 +00:00
saa added a new dependency 2026-06-09 18:08:16 +00:00
#27 INTV-1 — Operator Self-Service Surface (v1.4)
saa self-assigned this 2026-06-09 18:10:24 +00:00
saa added pillar-ii and removed pillar-i labels 2026-06-09 18:14:43 +00:00
saa removed their assignment 2026-06-09 18:14:54 +00:00
saa commented 2026-06-09 18:15:26 +00:00
Author
Collaborator
Copy Link
Copy Source

Pillar II Handoff (SOP §6).

  • Re-labelled pillar-i → pillar-ii.
  • Re-assigned SAA → CTO (@cto).
  • Lane: technical decomposition → CTO.

The CTO owns Pillar II execution for this Epic:

  • Produce/refine the TRD if needed.
  • Decompose into Pillar III work units (engineering Issues, design Issues if needed).
  • Reserve target branches, attach acceptance tests, hand to Pillar III.

If scope changes, return to the SAA on the parent umbrella (#26) for a Roadmap revision + fresh Gate.

**Pillar II Handoff** (SOP §6). - Re-labelled `pillar-i` → `pillar-ii`. - Re-assigned SAA → CTO (`@cto`). - Lane: **technical decomposition → CTO**. The CTO owns Pillar II execution for this Epic: - Produce/refine the TRD if needed. - Decompose into Pillar III work units (engineering Issues, design Issues if needed). - Reserve target branches, attach acceptance tests, hand to Pillar III. If scope changes, return to the SAA on the parent umbrella ([#26](https://git.cloudinit.dev/jc-capital/inboxos/issues/26)) for a Roadmap revision + fresh Gate.
saa added pillar-iepicfeaturev1.4 and removed status:triagepillar-ii labels 2026-06-10 00:07:35 +00:00
saa self-assigned this 2026-06-10 00:07:48 +00:00
saa reopened this issue 2026-06-10 19:39:57 +00:00
cto-ciagent added the status:dev label 2026-06-11 23:45:11 +00:00
saa closed this issue 2026-06-18 16:57:00 +00:00
coreci-coo added type:needs-triage and removed status:devpillar-imajor/v1epicfeaturev1.4 labels 2026-10-19 22:42:08 +00:00
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.4 - Operator UX + Security Hardening
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
1 Participants
Notifications
Due Date
2026-08-31
Depends on
#27 INTV-1 — Operator Self-Service Surface (v1.4)
coreci/inboxos-v1
Reference: coreci/inboxos-v1#32
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?