Context
A-tranche leaf 2 of Epic #14560's horizon map v2: the fleet-manager module's actual mount — nav entry + route + the module's root view shell inside the agentos Viewport chain, per the #14631 topology record's shape.
The Problem
The relocated token floor (PR #14629) gives the one app the module's design substrate, but nothing mounts an FM surface yet: no nav target, no route, no module root view. Every T2–T6 view leaf needs this mount to render inside the product instead of a bare dev page.
The Architectural Reality
- Consumes #14631's decisions verbatim (mount shape · integration point · route class).
- The module root = a thin shell view (
apps/agentos/view/fleetmanager/ root) that the cockpit's dock-zone composition (#14615) fills — the shell owns nav presence + route handling only (no layout logic; ADR 0029 boundary).
- Route state is runtime; deep-linking (
#fleet/agent/<id>-class) is a later leaf if the topology record wants it.
The Fix
The per-view triplet: (1) nav entry + route + module root shell mounted in the agentos Viewport; (2) unit specs — route activates the module view, nav state reflects the active route, non-FM routes unaffected (regression guard on the existing app); (3) NL-verifiable: navigate to the module route in the running agentos app, module shell renders with the token floor applied.
Acceptance Criteria
Out of Scope
Cockpit composition (#14615 fills the shell) · topology decisions (#14631) · demolition of existing views.
Related
Epic #14560 (parent) · blocked-by #14631 + PR #14629's merge · #14615 (fills this shell) · D#14561.
Sweeps: live window current; no equivalent; A2A clean. Structure-map: N/A — app-layer view wiring (structural-pre-flight sibling-lift at claim: the agentos Viewport chain).
Origin Session ID: a28f1415-37a4-4a5a-a3e4-b56adf6274ec
Retrieval Hint: "FM module mount nav route agentos viewport shell"
Context
A-tranche leaf 2 of Epic #14560's horizon map v2: the fleet-manager module's actual mount — nav entry + route + the module's root view shell inside the agentos Viewport chain, per the #14631 topology record's shape.
The Problem
The relocated token floor (PR #14629) gives the one app the module's design substrate, but nothing mounts an FM surface yet: no nav target, no route, no module root view. Every T2–T6 view leaf needs this mount to render inside the product instead of a bare dev page.
The Architectural Reality
apps/agentos/view/fleetmanager/root) that the cockpit's dock-zone composition (#14615) fills — the shell owns nav presence + route handling only (no layout logic; ADR 0029 boundary).#fleet/agent/<id>-class) is a later leaf if the topology record wants it.The Fix
The per-view triplet: (1) nav entry + route + module root shell mounted in the agentos Viewport; (2) unit specs — route activates the module view, nav state reflects the active route, non-FM routes unaffected (regression guard on the existing app); (3) NL-verifiable: navigate to the module route in the running agentos app, module shell renders with the token floor applied.
Acceptance Criteria
Out of Scope
Cockpit composition (#14615 fills the shell) · topology decisions (#14631) · demolition of existing views.
Related
Epic #14560 (parent) · blocked-by #14631 + PR #14629's merge · #14615 (fills this shell) · D#14561.
Sweeps: live window current; no equivalent; A2A clean. Structure-map: N/A — app-layer view wiring (structural-pre-flight sibling-lift at claim: the agentos Viewport chain).
Origin Session ID: a28f1415-37a4-4a5a-a3e4-b56adf6274ec Retrieval Hint: "FM module mount nav route agentos viewport shell"