ahmido
b0a724acef
## Summary - harden the canonical operation run viewer so mismatched, missing, archived, onboarding, and selector-excluded tenant context no longer invalidates authorized canonical run viewing - extend canonical route, header-context, deep-link, and presentation coverage for Spec 144 and add the full spec artifact set under `specs/144-canonical-operation-viewer-context-decoupling/` - harden onboarding draft provider-connection resume logic so stale persisted provider connections fall back to the connect-provider step instead of resuming invalid state - add architecture-audit follow-up candidate material and prompt assets for the next governance hardening wave ## Testing - `vendor/bin/sail bin pint --dirty --format agent` - `vendor/bin/sail artisan test --compact tests/Feature/144/CanonicalOperationViewerContextMismatchTest.php tests/Feature/144/CanonicalOperationViewerDeepLinkTrustTest.php tests/Feature/Operations/TenantlessOperationRunViewerTest.php tests/Feature/OpsUx/OperateHubShellTest.php tests/Feature/Monitoring/OperationsTenantScopeTest.php tests/Feature/RunAuthorizationTenantIsolationTest.php tests/Feature/Filament/OperationRunEnterpriseDetailPageTest.php tests/Feature/Monitoring/HeaderContextBarTest.php tests/Feature/Monitoring/OperationRunResolvedReferencePresentationTest.php tests/Feature/Monitoring/OperationsCanonicalUrlsTest.php` - `vendor/bin/sail artisan test --compact tests/Feature/ManagedTenantOnboardingWizardTest.php tests/Unit/Onboarding/OnboardingDraftStageResolverTest.php tests/Unit/Onboarding/OnboardingLifecycleServiceTest.php` ## Notes - branch: `144-canonical-operation-viewer-context-decoupling` - base: `dev` Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #173
138 lines
5.3 KiB
Markdown
138 lines
5.3 KiB
Markdown
# Product Roadmap
|
||
|
||
> Strategic thematic blocks and release trajectory.
|
||
> This is the "big picture" — not individual specs.
|
||
|
||
**Last updated**: 2026-03-15
|
||
|
||
---
|
||
|
||
## Release History
|
||
|
||
| Release | Theme | Status |
|
||
|---------|-------|--------|
|
||
| **R1 "Golden Master Governance"** | Baseline drift as production feature, operations polish | **Done** |
|
||
| **R1 cont.** | Ops canonicalization, action surface contract, ops-ux enforcement | **Done** |
|
||
| **R2 "Tenant Reviews & Evidence"** | Evidence packs, stored reports, permission posture, alerts | **Partial** |
|
||
| **R2 cont.** | Alert escalation + notification routing | **Done** |
|
||
|
||
---
|
||
|
||
## Active / Near-term
|
||
|
||
### Governance & Architecture Hardening
|
||
Canonical run-view trust semantics, execution-time authorization continuity, tenant-owned query canon, findings workflow enforcement, Livewire trust-boundary reduction.
|
||
Goal: Turn the new audit constitution into enforceable backend and workflow guardrails before further governance surface area lands.
|
||
|
||
**Active specs**: 144
|
||
**Next wave candidates**: queued execution reauthorization and scope continuity, tenant-owned query canon and wrong-tenant guards, findings workflow enforcement and audit backstop, Livewire context locking and trusted-state reduction
|
||
**Source**: architecture audit 2026-03-15, audit constitution, product spec-candidates
|
||
|
||
### UI & Product Maturity Polish
|
||
Empty state consistency, list-expand parity, workspace chooser refinement, navigation semantics.
|
||
Goal: Every surface feels intentional and guided for first-run evaluation.
|
||
|
||
**Active specs**: 122, 121, 112
|
||
|
||
### Secret & Security Hardening
|
||
Secret redaction integrity, provider access hardening, required permissions sidebar.
|
||
Goal: Enterprise trust — no credential leaks, no permission gaps.
|
||
|
||
**Active specs**: 120, 108, 106
|
||
|
||
### Baseline Drift Engine (Cutover)
|
||
Full content capture, cutover to unified engine, resume capability.
|
||
Goal: Ship drift detection as the complete production governance feature.
|
||
|
||
**Active specs**: 119 (cutover)
|
||
|
||
---
|
||
|
||
## Planned (Next Quarter)
|
||
|
||
### R2 Completion — Evidence & Exception Workflows
|
||
- Review pack export (Spec 109 — done)
|
||
- Exception/risk-acceptance workflow for Findings → **Not yet specced**
|
||
- Formal "evidence pack" entity → **Not yet specced**
|
||
- Workspace-level PII override for review packs → deferred from 109
|
||
|
||
### Policy Lifecycle / Ghost Policies
|
||
Soft delete detection, automatic restore, "Deleted" badge, restore from backup.
|
||
Draft exists (Spec 900). Needs spec refresh and prioritization.
|
||
**Risk**: Ghost policies create confusion for backup item references.
|
||
|
||
### Platform Operations Maturity
|
||
- CSV export for filtered run metadata (deferred from Spec 114)
|
||
- Raw error/context drilldowns for system console (deferred from Spec 114)
|
||
- Multi-workspace operator selection in `/system` (deferred from Spec 113)
|
||
|
||
---
|
||
|
||
## Mid-term (2–3 Quarters)
|
||
|
||
### MSP Portfolio & Operations (Multi-Tenant)
|
||
Multi-tenant health dashboard, SLA/compliance reports (PDF), cross-tenant troubleshooting center.
|
||
**Source**: 0800-future-features brainstorming, identified as highest priority pillar.
|
||
**Prerequisite**: Cross-tenant compare (Spec 043 — draft only).
|
||
|
||
### Drift & Change Governance ("Revenue Lever #1")
|
||
Change approval workflows (DEV→PROD with audit pack), guardrails/policy freeze windows, tamper detection.
|
||
**Source**: 0800-future-features brainstorming.
|
||
**Prerequisite**: Drift engine fully shipped, findings workflow mature.
|
||
|
||
### Standardization & Policy Quality ("Intune Linting")
|
||
Policy linter (naming, scope tag requirements, no All-Users on high-risk), company standards as templates, policy hygiene (duplicate finder, unassigned, orphaned, stale).
|
||
**Source**: 0800-future-features brainstorming.
|
||
|
||
---
|
||
|
||
## Long-term
|
||
|
||
### Tenant-to-Tenant / Staging→Prod Promotion
|
||
Compare/diff between tenants, mapping UI (groups, scope tags, filters, named locations, app refs), promotion plan (preview → dry-run → cutover → verify).
|
||
**Source**: 0800-future-features, Spec 043 draft.
|
||
|
||
### Recovery Confidence ("Killer Feature")
|
||
Automated restore tests in test tenants, recovery readiness report, preflight score.
|
||
**Source**: 0800-future-features brainstorming.
|
||
|
||
### Security Suite Layer
|
||
Security posture score, blast radius display, opt-in high-risk enablement.
|
||
**Source**: 0800-future-features brainstorming.
|
||
|
||
### Script & Secrets Governance
|
||
Script diff + approval + rollback, secret scanning, allowlist/signing workflow.
|
||
**Source**: 0800-future-features brainstorming.
|
||
|
||
---
|
||
|
||
## Infrastructure & Platform Debt
|
||
|
||
| Item | Risk | Status |
|
||
|------|------|--------|
|
||
| No `.env.example` in repo | Onboarding friction | Open |
|
||
| No CI pipeline config | No automated quality gate | Open |
|
||
| No PHPStan/Larastan | No static analysis | Open |
|
||
| SQLite for tests vs PostgreSQL in prod | Schema drift risk | Open |
|
||
| No formal release process | Manual deploys | Open |
|
||
| Dokploy config external to repo | Env drift | Open |
|
||
|
||
---
|
||
|
||
## Priority Ranking (from Product Brainstorming)
|
||
|
||
1. MSP Portfolio + Alerting
|
||
2. Drift + Approval Workflows
|
||
3. Standardization / Linting
|
||
4. Promotion DEV→PROD
|
||
5. Recovery Confidence
|
||
|
||
---
|
||
|
||
## How to use this file
|
||
|
||
- **Big themes** live here.
|
||
- **Concrete spec candidates** → see [spec-candidates.md](spec-candidates.md)
|
||
- **Small discoveries from implementation** → see [discoveries.md](discoveries.md)
|
||
- **Product principles** → see [principles.md](principles.md)
|