Primary workspace
Planning
Core scheduling and planning entry points grouped as a visible Navigator region.
DarkPrometheus
A web-native entry surface for the Designer family: ERP-A Navigator, Web P&S Navigator, ePAS Designer, and staged workspace builders. This shell shows structure and direction without implementing editors, persistence, or live system actions.
Preview/edit/open buttons are demo-safe affordances only. No SAP, Web P&S, database, auth, or Certinia path is called from this route.
A sanitized read-only template that shows the intended Navigator layout: planning modules, maintenance tools, review paths, and outbound artifact direction.
Primary workspace
Core scheduling and planning entry points grouped as a visible Navigator region.
Operational tools
Safe placeholders for updater-style tools without creating executable shortcuts.
Validation lane
Readiness, audit, and sign-off concepts before any executable output exists.
No execution
Shows eventual script or payload direction while keeping V0 completely inert.
Planning & Scheduling / ERP-A
Role/template driven Navigator configuration with section boxes, buttons, connectors, and SAP export direction.
Planning & Scheduling / Web P&S
Browser-native Navigator payload preview candidate with JSON export and publish-request review direction.
ePAS / ERP-A / Web P&S / GWOS AI
Module reference, workflow list, wizard, graph, audit, explanation, and config-map direction.
V0 treats ERP-A Navigator as the first high-confidence Designer anchor. The web path should model config and preview before any backend script generation.
Keep this visible but decision-marked until availability is settled. The first real pass should remain local preview/copy/download only.
V0 shows ePAS as a Designer family, not a single screen. Imports and real corpus handling stay out until storage and sanitization are owned.
Designer should eventually route to the LaunchPad design surface once LaunchPad persistence and editing seams settle.
This stays staged while Navigator and ePAS establish the shared route/catalog and preview contracts.
These cards preserve product direction without pretending the web shell can launch unfinished modules.