## Summary - rebuild the public Tenantial homepage around an evidence-first Microsoft tenant governance narrative - replace the old hero visual with a new static dashboard preview and add dedicated Trust Bar and Feature Pillars sections - update the shared public shell, navigation, footer, dark design tokens, assets, and homepage content to match the new brand direction - align website smoke coverage and Spec 400 artifacts with the rebuilt homepage ## Testing - not run in this pass - updated website smoke specs under apps/website/tests/smoke ## Note - `website-dev` was pushed to `origin` so the requested PR base exists remotely - the remote `website-dev` branch is an ancestor of `origin/dev`, so this PR may also show upstream `dev` history relative to that base Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #387
60 lines
1.8 KiB
Markdown
60 lines
1.8 KiB
Markdown
# 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. |