Implemented the final operator workflow for the Governance Inbox. This includes refactoring the inbox page, updating finding resources, adding UI enforcement policies, updating related blade views, and adding comprehensive tests for operator workflow and scope contracts. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #418 |
||
|---|---|---|
| .. | ||
| architecture | ||
| audits | ||
| brand | ||
| product | ||
| research | ||
| security | ||
| strategy | ||
| ui | ||
| ui-ux-enterprise-audit | ||
| AGENTS-draft.md | ||
| ai-coding-rules.md | ||
| architecture-guidelines.md | ||
| architecture.svg | ||
| deployment-checklist.md | ||
| filament-guidelines.md | ||
| HANDOVER.md | ||
| package-governance.md | ||
| performance-guidelines.md | ||
| PERMISSIONS.md | ||
| PROJECT_SUMMARY.md | ||
| README.md | ||
| security-guidelines.md | ||
| stack-overview.md | ||
| testing-guidelines.md | ||
TenantPilot Documentation Index
Status: Active
Last reviewed: 2026-04-30
Use for: Navigating current documentation sources and understanding how to maintain them with low overhead
Do not use for: Assuming any document is implementation truth without repo verification
Current Source of Truth
docs/product/roadmap.md- current product roadmap and prioritization contextdocs/product/spec-candidates.md- active spec candidate queuedocs/product/principles.md- product and architecture principlesdocs/strategy/product-vision.md- long-term product visiondocs/strategy/domain-coverage.md- domain and coverage strategy
Product Operations
docs/product/discoveries.mddocs/product/implementation-ledger.mddocs/product/prompts/docs/product/standards/
Technical Research
docs/research/
UI Standards
docs/ui/
Audits
docs/audits/
Security And Access References
docs/PERMISSIONS.mddocs/security/
Historical Or Superseded Material
docs/audits/archive/- audit-derived candidate documents that are marked
Historical,Superseded, orNeeds Review
Lightweight Maintenance Model
- Keep only the current source-of-truth documents actively maintained.
- Update a document when the underlying roadmap, policy, or decision actually changes.
- Mark older material with status headers instead of rewriting it to feel current.
- Prefer archive or superseded markers over deletion.
- Verify implementation claims against repo code, specs, and tests.
Rules For Agents
- Treat docs as guidance, not implementation truth.
- Verify implementation claims against repo code.
- Specs are not automatically implemented.
- Tests are not automatically executed.
- Historical audits may be outdated.
- Prefer current roadmap and spec-candidates for prioritization.