ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
9e435ea91f
TenantAtlas/specs/327-governance-inbox-decision-first-workbench-productization/checklists/requirements.md
ahmido 1c38a08919 feat: productize governance inbox decision-first workbench (#388) 
## Summary
- productize the governance inbox decision-first workbench surface and related section-building logic
- update the panel theme asset and governance inbox Blade view for the new page treatment
- add Governance Inbox feature coverage and a Spec 327 browser smoke test
- add Spec 327 planning artifacts under `specs/327-governance-inbox-decision-first-workbench-productization`

## Testing
- not run as part of this handoff

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #388
2026-05-18 16:20:17 +00:00

1.9 KiB
Raw Blame History

Requirements Checklist: Spec 327 - Governance Inbox Decision-First Workbench Productization

Purpose: Validate preparation artifact quality before implementation. Created: 2026-05-18 Feature: specs/327-governance-inbox-decision-first-workbench-productization/spec.md

Content Quality

  • No implementation details leak into product requirements beyond required repo constraints.
  • User value and operator workflow are clear.
  • Scope is bounded to one existing runtime surface.
  • Non-goals explicitly prevent backend/workflow overbuild.
  • Dependencies and historical specs are listed.

Repo Truth And Safety

  • Existing route/class/view/builder are named.
  • Repo truth map exists and uses required classifications.
  • No new persisted truth is proposed.
  • No migrations/packages/env/queues/scheduler/storage changes are expected.
  • No legacy tenant query alias support is allowed.

Workspace / Environment Contract

  • Clean workspace-wide entry is specified.
  • Canonical environment_id filter is specified.
  • Visible chip and clear filter are specified.
  • Legacy aliases are rejected.
  • Cross-workspace environment guard is specified.

RBAC / Audit / Diagnostics

  • Existing capabilities and policies remain authoritative.
  • Unauthorized action behavior is specified.
  • Diagnostics are collapsed/hidden by default.
  • Dangerous actions are out of scope unless spec/plan are updated.
  • No raw payloads/provider secrets/debug traces are default-visible.

Testability

  • Feature tests are listed.
  • Browser smoke flows are listed.
  • Navigation/scope guard tests are listed.
  • pint --dirty and git diff --check are listed.
  • Full-suite status must be reported honestly.

Readiness Decision

  • Spec is ready for implementation planning.
  • No open question blocks a bounded implementation loop.