TenantAtlas/docs
ahmido a9c54205bf feat: finding exceptions accepted risk resolution guidance v1 (spec 354) (#425)
Implemented the accepted risk resolution guidance, including the AcceptedRiskResolutionAdapter, guidance cards, and updated related Filament views. Added unit, feature, and browser tests.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #425
2026-06-05 02:20:46 +00:00
..
architecture feat: customer-facing localization adoption (275) (#327) 2026-05-04 23:14:20 +00:00
audits chore: commit all changes (automated) 2026-04-30 16:25:12 +02:00
brand Spec 323: add tenantial enterprise UI audit foundation (#383) 2026-05-17 17:49:54 +00:00
product feat: clean up legacy tenant environment context (#372) 2026-05-16 18:25:36 +00:00
research refactor: consolidate internal tenant model naming (#355) 2026-05-14 11:13:28 +00:00
security chore: commit all changes (automated) 2026-04-30 16:25:12 +02:00
strategy chore: commit all changes (automated) 2026-04-30 16:25:12 +02:00
ui Automated: commit from 278-cross-domain-indicator-audit (#334) 2026-05-06 09:21:06 +00:00
ui-ux-enterprise-audit feat: finding exceptions accepted risk resolution guidance v1 (spec 354) (#425) 2026-06-05 02:20:46 +00:00
AGENTS-draft.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
ai-coding-rules.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
architecture-guidelines.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
architecture.svg feat: customer-facing localization adoption (275) (#327) 2026-05-04 23:14:20 +00:00
deployment-checklist.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
filament-guidelines.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
HANDOVER.md feat: clean up legacy tenant environment context (#372) 2026-05-16 18:25:36 +00:00
package-governance.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
performance-guidelines.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
PERMISSIONS.md chore: commit all changes (automated) 2026-04-30 16:25:12 +02:00
PROJECT_SUMMARY.md chore: commit all changes (automated) 2026-04-30 16:25:12 +02:00
README.md chore: commit all changes (automated) 2026-04-30 16:25:12 +02:00
security-guidelines.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
stack-overview.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00
testing-guidelines.md fix: enforce workspace surface scope for customer review workspace (#366) 2026-05-15 20:52:37 +00:00

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 context
  • docs/product/spec-candidates.md - active spec candidate queue
  • docs/product/principles.md - product and architecture principles
  • docs/strategy/product-vision.md - long-term product vision
  • docs/strategy/domain-coverage.md - domain and coverage strategy

Product Operations

  • docs/product/discoveries.md
  • docs/product/implementation-ledger.md
  • docs/product/prompts/
  • docs/product/standards/

Technical Research

  • docs/research/

UI Standards

  • docs/ui/

Audits

  • docs/audits/

Security And Access References

  • docs/PERMISSIONS.md
  • docs/security/

Historical Or Superseded Material

  • docs/audits/archive/
  • audit-derived candidate documents that are marked Historical, Superseded, or Needs 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.