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

EPIC-INB-1.0-TD-1: papra_index --check test (REQ-INB-38) #39

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

EPIC-INB-1.0-TD-1: papra_index --check test (REQ-INB-38)

Epic sub-issue of: INTV-4 #30 — sub-Issue of MAJOR v1 umbrella #99 (major/v1).
Traces to: Roadmap §Initiatives → INTV-4 → EPIC-INB-1.0-TD-1; Goal 1 (core pipeline). Carry tech-debt from v1.3 into the v1.0-MVP lane.
Target MINOR: v1.0 - MVP Foundation (Milestone #9, due 2026-06-15).
Assignee: SAA (self-assigned until handoff to CEO → CTO for Pillar II).
Labels: major/v1, pillar-i, epic, v1.0, debt (tech-debt-classified work).

Context

REQ-INB-38 — add a --check flag to apply_schemas.py and an offline test for papra_index. The existing carrying Issue is inboxos#21.

Success criteria

  • apply_schemas.py --check is implemented and tested offline.
  • The papra_index offline test passes in CI.

Acceptance criteria

  • The PR closes inboxos#21 and carries dual-approval review evidence (CPO + CTO) per the v1.4.0 re-dispatch governance (INTV-3 §H).
  • CI is green on the merge commit.

Out of scope

  • v1.4.0 re-inclusion (per inboxos#24 §Acceptance criteria 4 — this is NOT in v1.4).
  • Other tech-debt items (EPIC-INB-1.0-TD-2, EPIC-INB-1.0-TD-3).
  • Operator tooling (INTV-1), security/compliance (INTV-2), branch protection (INTV-3).

Dependencies

  • blockedBy INTV-4 #30 (parent Initiative) and the umbrella #99.
  • The PR must land under the dual-approval governance (INTV-3 §H), so the branch-protection change must be in place at merge time. SAA sequences this lane after the branch-protection change.

Target branch

Reserved for Pillar III integration: epic/EPIC-INB-1.0-TD-1-papra-index-check. 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 and links the work to the existing carry Issue.

References

# EPIC-INB-1.0-TD-1: papra_index --check test (REQ-INB-38) > **Epic sub-issue of:** [INTV-4 #30](https://git.cloudinit.dev/jc-capital/inboxos/issues/30) — sub-Issue of [MAJOR v1 umbrella #99](https://git.cloudinit.dev/jc-capital/inboxos/issues/99) (`major/v1`). > **Traces to:** Roadmap §Initiatives → INTV-4 → EPIC-INB-1.0-TD-1; **Goal 1** (core pipeline). Carry tech-debt from v1.3 into the v1.0-MVP lane. > **Target MINOR:** v1.0 - MVP Foundation (Milestone #9, due 2026-06-15). > **Assignee:** SAA (self-assigned until handoff to CEO → CTO for Pillar II). > **Labels:** `major/v1`, `pillar-i`, `epic`, `v1.0`, `debt` (tech-debt-classified work). ## Context REQ-INB-38 — add a `--check` flag to `apply_schemas.py` and an offline test for `papra_index`. The existing carrying Issue is [inboxos#21](https://git.cloudinit.dev/jc-capital/inboxos/issues/21). ## Success criteria - `apply_schemas.py --check` is implemented and tested offline. - The `papra_index` offline test passes in CI. ## Acceptance criteria - The PR closes [inboxos#21](https://git.cloudinit.dev/jc-capital/inboxos/issues/21) and carries dual-approval review evidence (CPO + CTO) per the v1.4.0 re-dispatch governance (INTV-3 §H). - CI is green on the merge commit. ## Out of scope - v1.4.0 re-inclusion (per inboxos#24 §Acceptance criteria 4 — this is NOT in v1.4). - Other tech-debt items (EPIC-INB-1.0-TD-2, EPIC-INB-1.0-TD-3). - Operator tooling (INTV-1), security/compliance (INTV-2), branch protection (INTV-3). ## Dependencies - `blockedBy` [INTV-4 #30](https://git.cloudinit.dev/jc-capital/inboxos/issues/30) (parent Initiative) and the umbrella [#99](https://git.cloudinit.dev/jc-capital/inboxos/issues/99). - The PR must land under the dual-approval governance (INTV-3 §H), so the branch-protection change must be in place at merge time. SAA sequences this lane after the branch-protection change. ## Target branch Reserved for Pillar III integration: `epic/EPIC-INB-1.0-TD-1-papra-index-check`. 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 and links the work to the existing carry Issue. ## References - Roadmap source: [`docs/roadmap.md` §EPIC-INB-1.0-TD-1](https://git.cloudinit.dev/jc-capital/inboxos/src/main/docs/roadmap.md) on `main`. - Requirements: REQ-INB-38. - Existing carry Issue: [inboxos#21](https://git.cloudinit.dev/jc-capital/inboxos/issues/21). - v1.4.0 re-dispatch governance: [inboxos#24](https://git.cloudinit.dev/jc-capital/inboxos/issues/24).
saa added this to the v1.0 - MVP Foundation milestone 2026-06-09 18:08:19 +00:00
saa added the status:triagepillar-imajor/v1 labels 2026-06-09 18:08:19 +00:00
saa added a new dependency 2026-06-09 18:08:20 +00:00
#30 INTV-4 — Tech-Debt Lane (v1.0-MVP carry)
saa self-assigned this 2026-06-09 18:10:25 +00:00
saa added pillar-ii and removed pillar-i labels 2026-06-09 18:14:46 +00:00
saa removed their assignment 2026-06-09 18:14:56 +00:00
saa commented 2026-06-09 18:15:28 +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-iepicdebtv1.0 and removed status:triagepillar-ii labels 2026-06-10 00:07:34 +00:00
saa self-assigned this 2026-06-10 00:07:48 +00:00
saa reopened this issue 2026-06-10 19:40:00 +00:00
cto-ciagent added the status:dev label 2026-06-11 23:45:12 +00:00
saa closed this issue 2026-06-18 16:57:08 +00:00
coreci-coo added type:needs-triage and removed status:devpillar-imajor/v1epicdebtv1.0 labels 2026-10-19 22:42:05 +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.0 - MVP Foundation
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-06-15
Depends on
#30 INTV-4 — Tech-Debt Lane (v1.0-MVP carry)
coreci/inboxos-v1
Reference: coreci/inboxos-v1#39
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?