diagnosis: record admin workbench visibility gap for SR-04

docs/proposals/V1R4C4-SR04-admin-workbench-visibility-gap.md

@@ -0,0 +1,142 @@
+# V1R4C4 SR-04: Admin Workbench Visibility Gap
+
+Status: confirmed user-visible gap
+
+Decision state: activation-ready, gated behind reliability and isolation controls
+
+Current baseline: V1R4C3
+
+Date: 2026-07-11
+
+## User Report
+
+An administrator still cannot see newly expected functions in the workbench, including:
+
+- task progress;
+- process/flow diagrams;
+- new AIOS operational modules.
+
+## Current Diagnosis
+
+This is not currently classified as a browser cache issue or a single RBAC defect.
+
+The active baseline remains V1R4C3. Relevant workbench/portal/UI capability branches exist but have not been merged into the deployed baseline.
+
+Observed relevant candidate branches include:
+
+```text
+feature/v1r4c4-sr04-portal-aios-visibility-20260710
+patch/user-portal-me-route-diagnostics-20260709
+patch/user-portal-rbac-ops-dashboard
+patch/agent-observability-webui
+patch/autonomous-controller-dispatch-20260709
+patch/agent-event-bus-unified
+patch/agent-gpt-message-plane
+```
+
+Therefore, the administrator-visible gap is currently expected until SR-04 is merged and deployed.
+
+## Root Cause Category
+
+```text
+backend / governance capabilities exist or are staged
+        ↓
+admin workbench integration remains outside active baseline
+        ↓
+menu/routes/API contract not deployed to production workbench
+        ↓
+admin cannot see task progress or flow diagrams
+```
+
+## Required Admin Workbench Surface
+
+SR-04 must expose administrator-visible operational functions in the workbench.
+
+Minimum expected surfaces:
+
+1. Task progress view.
+2. Flow/process diagram view.
+3. Agent/operation status view.
+4. System health view.
+5. Search/governance module visibility where permitted.
+6. Owner/admin approval and gate status where permitted.
+
+## Required API/Contract Checks
+
+Before deployment, confirm workbench routes are backed by APIs or adapters for:
+
+```text
+task progress
+workflow graph / process diagram
+agent activity / observability
+system health
+governance / owner gate state
+```
+
+Existing portal candidates indicate related routes may include:
+
+```text
+/portal/me/aios/manifest
+/portal/me/aios/dashboard
+/portal/me/aios/health
+```
+
+Admin workbench must not rely on backend existence alone. The frontend menu, route registration, data adapters, and RBAC visibility must all be verified.
+
+## RBAC Requirements
+
+Administrator users must see admin-authorized modules, but not owner-only modules unless also owner-authorized.
+
+Required role checks:
+
+```text
+user
+  -> user-authorized modules only
+
+group_admin / admin
+  -> task progress, operations, health, agent/flow visibility
+
+owner
+  -> governance, architecture, approval, owner gate
+```
+
+## Gate Status
+
+SR-04 remains blocked from production merge/deploy until reliability gates are complete.
+
+Required before SR-04 deployment:
+
+1. SR-01 Gitea reliability sentinel remains healthy.
+2. SR-02 watcher cleanup is integrated and accepted.
+3. User-data isolation gate is accepted or explicitly scoped so SR-04 cannot expose cross-user/task data.
+4. Runtime acceptance is green.
+5. Admin workbench acceptance is green.
+
+## Admin Workbench Acceptance
+
+After deployment, verify as an administrator:
+
+- Workbench shows task progress.
+- Workbench shows flow/process diagram entry.
+- Workbench APIs return valid data.
+- Admin can see admin modules.
+- Admin cannot see owner-only modules unless authorized.
+- Empty states are explicit, not silent disappearance.
+- Missing backend data surfaces as a clear status message.
+
+## Interim Product Conclusion
+
+The current user-visible issue is a deployment/integration gap:
+
+```text
+SR-04 needed
+but still gated
+```
+
+The correct fix is controlled SR-04 integration after reliability and isolation gates, not ad hoc frontend exposure.
+
+## Recommended Next Step
+
+Prepare SR-04 admin workbench integration as the next visible-feature task immediately after SR-01/SR-02/security isolation gates are accepted.
+
+If administrator workbench visibility becomes urgent, create a narrow read-only admin workbench slice that exposes only already-authorized, non-cross-user data and still passes the user-data isolation gate.