Decide where every existing route lands in the five-place navigation #354
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#354
Reference in new issue
Block a user
README section 2 only maps Work/System menus it inferred from screenshots. The router (ui/src/router/index.ts) also has Skills, Curators, Logs, System Status, Appearance, Task settings, Models, Repositories, Identities, Advanced. Rule: configure -> Settings, act on -> where the work is. Also map the handoff's Settings sections (Personas, Schedules, Scheduling policy, Tools & MCP, Plugins, Container runtime) to the real config keys and the pages that edit them today. Keep internal/gateway/dashboard_tools.go (mirrors the route table) in step. Absorbs archie-core-gl96 (Logs missing from nav).
Design
DECISION (routes). Rule: configure -> Settings, act on -> where the work is. New Settings URLs are /settings/
Top bar: Dashboard (/), Tasks (/tasks, /tasks/:id), Workflows (/workflows, keeps workflow-definitions: editing how work runs lives with the runs), Events (/events), Settings.
Off the top bar: /logs stays a route, reached from the Dashboard Logs button and the command palette (closes the gl96 nav gap). /system/appearance -> account avatar menu (browser-local preference, not daemon config).
Settings sidebar, each section = one control-plane resource kind (ui/src/stores/control-plane.ts PAGE_RESOURCES):
AGENTS: Personas (personas) · Models (provider-settings + model-role-assignments, was /system/models) · Skills (was /skills) · Curators (was /curators) · Schedules (schedules) · Scheduling policy (scheduling-policy)
INTEGRATIONS: Channels (channel-settings, was /channels) · Repositories (repository-policies, was /system/repos) · Identities (was /system/identities) · Tools & MCP (tool-settings) · Plugins (plugin-settings)
RUNTIME: Task execution (workflow-execution-settings, was /system/tasks) · Container runtime (container-runtime-policies) · Daemon (legacy config_schema sections identity, storage, web) · Status (was /system/status)
then History.
/system/advanced dissolves into Personas, Schedules, Scheduling policy, Tools & MCP, Plugins, Container runtime.
internal/gateway/dashboard_tools.go mirrors the route table and moves with it.
FIELD MAPPING (handoff -> resource document key):
Scheduling policy: trigger/label -> dispatch + label (optional); ack reaction -> dispatch; state labels -> dispatch labels; max retries -> max_retries (int); poll interval -> poll_interval (Go duration string).
Plugins: module_dir, plugin_dir, secret_engine_dir, skills_dir (strings).
Container runtime: config.ContainerConfig: image, max_concurrency (0 = unlimited), max_uptime, volume_ttl (durations), pull_policy (missing|always only, NO never), network, profiles.
Tools & MCP: mcp_servers[] {name, transport stdio|http|streamablehttp|sse, command/args/work_dir or url/sse_endpoint/message_endpoint, parallel_tool_calls, headers_configured}; minimax {enabled, api_key_ref SecretRef}; web_fetch (config.WebFetchConfig); policy (config.ToolPolicy).
Channels: channel-settings document (internal/infrastructure/controlplanerpc/vocabulary.go): telegram, email, webhook_addr + webhook route, operator, show_tool_calls, max_steps, models, rate_limit {window, max_requests}, workspace, unrestricted filesystem.
Personas: personas resource; its separate default field becomes the per-persona toggle.
CONFLICT FOUND: the legacy storage section (config_schema.go) exposes skills_dir, plugin_dir, secret_engine_dir and containers.* as editable fields, while plugin-settings and container-runtime-policies own the same values at runtime (the file key is only a seed). Settings must show them once, from the resource. Follow-up filed.
Acceptance criteria
A table: route -> new place/sidebar group, with redirects for every moved path; every handoff Settings field named to its config key and type.
Close reason
done
Imported from beads
archie-core-micl.2· GitHub #1010 · type decision · priority P1 · created 2026-09-25 · closed 2026-09-28