ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity
e1136ac6e9
TenantAtlas/docs/README.md
ahmido e1136ac6e9
Some checks failed
Main Confidence / confidence (push) Failing after 54s
Details
Merge platform-dev into dev (automated) (#309) 
Automatischer Commit und PR erstellt auf Anfrage.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #309
2026-04-30 14:41:01 +00:00

1.8 KiB
Raw Blame History

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.