# Navigation Structure
Platform-wide UI Signal-to-Noise Browser Audit Navigation Evidence

Verification level: repo-verified
Audit date: 2026-06-08

Panel registration:
- Admin panel provider: apps/platform/app/Providers/Filament/AdminPanelProvider.php
- Admin panel path: /admin
- System panel provider: apps/platform/app/Providers/Filament/SystemPanelProvider.php
- System panel path: /system
- Provider registration location: apps/platform/bootstrap/providers.php is the expected Laravel 12 location per docs/filament-guidelines.md. This audit did not modify providers.
- Livewire runtime: Livewire 4.1.4 via Laravel Boost application_info; Filament 5.2.1.

Admin navigation groups declared in AdminPanelProvider:
- Inventory
- Monitoring
- Reporting
- Settings
- Governance
- Backups & Restore
- Directory
- Workspace-wide
- Workspace admin

Admin custom navigation items declared in AdminPanelProvider:
- Overview -> admin.home or admin.workspace.environments.show
- Inventory / Items -> InventoryCluster
- Inventory / Coverage -> InventoryCoverage
- Directory / Groups -> EntraGroupResource
- Workspace admin / Integrations -> ProviderConnectionResource
- Workspace admin / Settings -> WorkspaceSettings
- Workspace admin / Manage workspaces -> WorkspaceResource
- Workspace-wide Monitoring / Operations -> OperationRunLinks::index()
- Workspace-wide Monitoring / Alerts -> filament.admin.alerts
- Workspace-wide Monitoring / Evidence Overview -> admin.evidence.overview
- Workspace-wide Monitoring / Audit Log -> admin.monitoring.audit-log

Admin resources declared explicitly in AdminPanelProvider:
- PolicyResource
- ProviderConnectionResource
- InventoryItemResource
- AlertDestinationResource
- AlertRuleResource
- AlertDeliveryResource
- WorkspaceResource
- BaselineProfileResource
- BaselineSnapshotResource
- EnvironmentReviewResource

Admin discovery:
- discoverClusters: apps/platform/app/Filament/Clusters
- discoverResources: apps/platform/app/Filament/Resources
- explicit pages: BaselineCompareLanding, InventoryCoverage, EnvironmentRequiredPermissions, WorkspaceSettings, CrossEnvironmentComparePage, GovernanceInbox, DecisionRegister, FindingsHygieneReport, FindingsIntakeQueue, MyFindingsInbox, FindingExceptionsQueue, CustomerReviewWorkspace, ReviewRegister.

System panel discovery:
- discoverPages: apps/platform/app/Filament/System/Pages
- explicit page: Dashboard
- navigation groups observed in page classes: Directory, Ops, Security, Recovery.

Key custom admin routes from apps/platform/routes/web.php:
- /admin -> admin.home
- /admin/local/smoke-login -> local/test-only smoke login using existing users/workspace/environment
- /admin/workspaces/{workspace}/overview -> WorkspaceOverview
- /admin/workspaces/{workspace}/environments -> ManagedEnvironmentsLanding
- /admin/workspaces/{workspace}/environments/{environment} -> EnvironmentDashboard
- /admin/workspaces/{workspace}/environments/{environment}/diagnostics -> EnvironmentDiagnostics
- /admin/workspaces/{workspace}/environments/{environment}/access-scopes -> ManageEnvironmentAccessScopes
- /admin/workspaces/{workspace}/operations -> Operations
- /admin/workspaces/{workspace}/operations/{run} -> TenantlessOperationRunViewer
- /admin/evidence/overview -> EvidenceOverview
- /admin/audit-log -> AuditLog
- signed /admin/review-packs/{reviewPack}/download and /report

Route inventory source:
- specs/368-platform-ui-signal-to-noise-browser-audit/artifacts/raw/routes.txt

Browser fixture evidence:
- tenantpilot.backup_health.browser_smoke_fixture config exists for workspace spec-180-backup-health-smoke and user smoke-requester+180@tenantpilot.local.
- tenantpilot.review_output.browser_smoke_fixture config exists for workspace spec-351-review-output-smoke and user smoke-requester+351@tenantpilot.local.
- Local database read-only count before DB recovery interruption showed: users=35, workspaces=37, managed_environments=47, operation_runs=63, backup_sets=25, restore_runs=4, environment_reviews=21, evidence_snapshots=17, review_packs=15, stored_reports=31, platform_users=1.

Runtime limitation observed during audit:
- After initial data selection, Postgres logged PANIC "could not fdatasync file ... Input/output error" while updating sessions, then entered recovery mode.
- This blocked or delayed browser verification and is recorded in browser-notes.md / inaccessible-pages.md.