ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

spec: add inventory specs 039-044 #41

Closed
ahmido wants to merge 1 commits from 039-inventory-program into dev
pull from: 039-inventory-program
merge into: ahmido:dev
Conversation 0 Commits 1 Files Changed 18 +685
ahmido commented 2026-01-07 14:00:43 +00:00
Owner
Copy Link

What’s included
• specs/039-inventory-program/ — program/epic overview (vision + phased plan)
• specs/041-inventory-ui/ — UI skeleton (Inventory list, Coverage, Sync Runs)
• specs/042-inventory-dependencies-graph/ — dependency graph skeleton (assignments/filters/scope tags → later)
• specs/043-cross-tenant-compare-and-promotion/ — compare/promotion skeleton (read-only first; writes gated later)
• specs/044-drift-mvp/ — drift detection skeleton (read-only by default)

Why

We need a clear, spec-first structure for:
• separating Inventory (“last observed”) from Snapshots/Backups (immutable)
• scaling to MSP / multi-tenant workflows (portfolio, compare, monitoring)
• making future modules (security suite, drift, promotion) consistent with the Constitution (fail-safe, auditability, contract-driven Graph)

Scope / Non-goals (this PR)
• No implementation tasks executed
• No DB migrations, services, jobs, or UI changes
• No changes to Graph contracts or supported policy types

Review focus
• Naming/numbering and folder structure (spec.md, plan.md, tasks.md for each spec)
• Scope boundaries and non-goals across 041–044
• Alignment with Constitution principles (tenant isolation, read-only default for analysis, explicit gating for high-risk writes)

Follow-up (next PRs)
• Spec 040: Inventory Core (data model + selection hash + missing semantics + NFRs + tests)
• Implementation PRs will be split per spec (040 → 041 → 042/043/044)

⸻

What’s included • specs/039-inventory-program/ — program/epic overview (vision + phased plan) • specs/041-inventory-ui/ — UI skeleton (Inventory list, Coverage, Sync Runs) • specs/042-inventory-dependencies-graph/ — dependency graph skeleton (assignments/filters/scope tags → later) • specs/043-cross-tenant-compare-and-promotion/ — compare/promotion skeleton (read-only first; writes gated later) • specs/044-drift-mvp/ — drift detection skeleton (read-only by default) Why We need a clear, spec-first structure for: • separating Inventory (“last observed”) from Snapshots/Backups (immutable) • scaling to MSP / multi-tenant workflows (portfolio, compare, monitoring) • making future modules (security suite, drift, promotion) consistent with the Constitution (fail-safe, auditability, contract-driven Graph) Scope / Non-goals (this PR) • No implementation tasks executed • No DB migrations, services, jobs, or UI changes • No changes to Graph contracts or supported policy types Review focus • Naming/numbering and folder structure (spec.md, plan.md, tasks.md for each spec) • Scope boundaries and non-goals across 041–044 • Alignment with Constitution principles (tenant isolation, read-only default for analysis, explicit gating for high-risk writes) Follow-up (next PRs) • Spec 040: Inventory Core (data model + selection hash + missing semantics + NFRs + tests) • Implementation PRs will be split per spec (040 → 041 → 042/043/044) ⸻
ahmido added 1 commit 2026-01-07 14:00:44 +00:00
ahmido closed this pull request 2026-01-07 14:02:27 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ahmido/TenantAtlas#41
No description provided.
Delete Branch "039-inventory-program"

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?