ahmido
ba0b6ec07e
## Summary - add the Spec 306 docs-only reconciliation package under `specs/306-decision-register-reconciliation/` - reconcile existing Spec 265, runtime pages/builders/tests, and product docs so Decision Register is treated as repo-verified rather than a missing greenfield feature - minimally sync `docs/product/implementation-ledger.md`, `docs/product/roadmap.md`, and `docs/product/spec-candidates.md` to reflect current repo truth - classify Decision Register as `partial productization`, not `not implemented` - recommend one narrow next step instead of a broad restart: `307-decision-register-evidence-operationrun-link-polish` ## Scope - docs-only reconciliation and product-doc truth sync - no application runtime changes - no migrations - no routes, policies, providers, or UI asset changes - no test edits ## Key Conclusions Recorded - a broad new `Decision Register v1` or `Decision Register & Approval Workflow v1` spec should not be created - Spec 265 runtime is repo-verified and usable on `/admin/governance/decisions` - the remaining gap is narrow productization around direct evidence/report links, OperationRun links, and adjacent customer-safe consumption polish - product docs previously understated repo truth and were corrected minimally in this branch ## Filament / Runtime Notes - remains compliant with Filament v5 on Livewire v4 - no provider registration changes; provider registration location remains `apps/platform/bootstrap/providers.php` - no globally searchable resources were added or changed in this docs-only PR - no destructive actions were added or changed - no asset registration changes; existing deploy posture for `cd apps/platform && php artisan filament:assets` is unchanged ## Validation Notes - the reconciliation artifact records the focused existing test evidence used to support the product-truth claims - no new runtime validation was executed in this turn beyond committing and pushing the docs-only package Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #361 |
||
|---|---|---|
| .. | ||
| architecture | ||
| audits | ||
| product | ||
| research | ||
| security | ||
| strategy | ||
| ui | ||
| architecture.svg | ||
| HANDOVER.md | ||
| PERMISSIONS.md | ||
| PROJECT_SUMMARY.md | ||
| README.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.