INTV-2 — Maintain threat register with severity and status (REQ-INB-59) #183
Closed
opened 2026-06-15 20:21:07 +00:00 by cto-ciagent
·
0 comments
No Branch/Tag Specified
main
release/v1.5
be/INB-1.5-B-api-spec
be/INB-1.5-C-rbac-spec
cto/pillar-ii-gate-v1-20260615
fe/INB-1.5-A-ui-impl
be/INB-1.5-A-api-spec
frontend/story-133-design-system-tokens
ux/INB-1.5-D-design-spec
be/INB-1.5-A-api-impl
be/INB-1.5-B-api-impl
be/INB-1.5-C-rbac-impl
da/INB-1.5-C-data-spec
fe/INB-1.5-B-ui-impl
fe/INB-1.5-C-rbac-integrate
se/INB-1.5-A-qa
se/INB-1.5-B-qa
se/INB-1.5-C-rbac-pentest
ux/INB-1.5-A-ui-spec
ux/INB-1.5-B-ui-spec
epic/EPIC-INB-1.4-E-dpia
epic/EPIC-INB-1.4-F-threat-model
release/v1
v1.3.0
v1.2.0
v1.1.0
v1.0.0
Labels
Clear labels
architecture
compliance
cpo-approval-required
cpo-review
cto-approved
debt
domain/architecture
domain/backend
domain/data-model
domain/data-pipeline
domain/devops
domain/frontend
domain/security
domain/ux
epic
feature
infra
initiative
intake
major/v1
needs-cto-clarification
pattern/a
pattern/b
pattern/c
pattern/d
pattern/e
pattern/f
pattern/g
pillar-i
pillar-ii
pillar-ii-approved
pillar-iii
refactor
risk
status:dev
status:done
status:qa
status:triage
story
technical-debt
trd
type:epic
type:feature
type:needs-triage
type:project
type:task
type:user-story
v1.0
v1.4
v1.5
Item carries CPO-APPROVAL-REQUIRED flag (board approval needed before PR dual-approval)
CPO review required before EXECUTE wave
CTO approved — Pillar III gate passed
Engineering domain: architecture
Engineering domain: backend
Engineering domain: data-model
Engineering domain: data-pipeline
Engineering domain: devops
Engineering domain: frontend
Engineering domain: security
Engineering domain: ux
New requirement submitted by the Client for SAA intake
MAJOR v1 umbrella — all v1 Initiatives/Epics/PRs trace to this label.
Ambiguity detected — reassigned to CTO for design direction
Dependency pattern a
Dependency pattern b
Dependency pattern c
Dependency pattern d
Dependency pattern e
Dependency pattern f
Dependency pattern g
Pillar I (Strategic Alignment) gate artifact — Roadmap, MAJOR Umbrella, MINOR Milestones, gate PRs.
Execution / decomposition lane (CTO)
Pillar II design/spec approved by CTO
Pillar III — implementation / integration / ADR stories
Kanban state per INB-172 rule 2.
Kanban state per INB-172 rule 2.
Kanban state per INB-172 rule 2.
Kanban state per INB-172 rule 2.
Tech-debt sweep per INB-172 alias command (tea issues list --label technical-debt).
issue-hierarchy canon class (standards/issue-hierarchy.md)
issue-hierarchy canon class (standards/issue-hierarchy.md)
issue-hierarchy canon class (standards/issue-hierarchy.md)
issue-hierarchy canon class (standards/issue-hierarchy.md)
issue-hierarchy canon class (standards/issue-hierarchy.md)
issue-hierarchy canon class (standards/issue-hierarchy.md)
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
No Assignees
security-engineer
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coreci/inboxos-v1#183
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Story sub-issue of: EPIC-INB-1.4-F #36
Traces to: INTV-2 #28 → MAJOR v1 #99.
Domain: security.
Pattern: A (spec).
Assignee: @security-engineer.
Target branch:
se/INB-1.4-F-S3-threat-register.Acceptance criteria
Technical prerequisites
Dependencies
Out of scope