jason.woltjeandClaude Opus 5.5
1f4882d2b4
Brand board revisions, the five dashboard mockups with their verify
script and evidence, the slice 1 S5 design note (SLICE1-VIEWS.md, rev 3
plus the S2c section 10 update), the Console mockup of inbox, tasks,
agents and trail (mockups/slice1/) and checks/slice1-verify.mjs (16
checks; check 16 pinned to bus at d27042fa). Also the CHAT-03 progress
log and the 2026-09-26 dirty-tree manifest. Design and evidence only;
no package code. Row 40 (#1522), committed on its own at Sage's
direction, 2026-10-09.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
14 KiB
14 KiB
WUI feature inventory (D01)
Author: Dewey. Date: 2026-09-12. Source baseline: working tree on refactor at 1993039c plus uncommitted docs.
Purpose: the source-linked list of capabilities the five dashboard mockups must show, with each item labelled by how real it is today. This inventory drives D02 routes and sample data. It is not a product commitment, a backend contract, or a claim that any item is user-tested.
Status labels
| Label | Meaning | Mockup treatment |
|---|---|---|
| implemented | Exists in the rebuild today as a script, extension, or suite-covered behavior. | Show as a working surface with realistic sample records. |
| planned | Owner-accepted plan, charter, or ruling with defined behavior, not yet built. | Show fully; mark "planned" in the mockup's feature legend. |
| proposed | Owner direction or concept note without an accepted plan. | Show where it shapes navigation; label "proposed" and keep it shallow. |
| mockup | Interface behavior invented for the prototype to make the flow complete. | Label "mockup" in the legend and in DESIGN.md open questions. |
No v1 UI was inspected. Nothing here was verified by running the runtime; labels come from reading the cited files.
1. Landing: control board (owner MVP decision)
| Capability | Status | Source |
|---|---|---|
| One page listing running agent sessions across projects with status. Deliberately smaller than the current registry line. | proposed, owner decision MOSAIC-STACK-D-001 (2026-09-12) | docs/plans/CURRENT.md lines 17-24 |
| A "waiting on you" section: items where the owner is the blocker (goal_report blocked, owner checkpoints, acceptance gates, quiet waits). | proposed, same decision | docs/plans/CURRENT.md lines 17-24; extensions/goal/README.md (blocked and quiet-wait states) |
| Per-session status vocabulary: running, waiting on owner, quiet wait, blocked, settled, stalled, stopped. | planned (goal states) and proposed (stall detection) | extensions/goal/README.md; docs/plans/2026-09-06_foundation-mechanical-workflow-topics.md |
| Cross-project view means agent, project, workspace shown together on each row. | planned (R5, R11) | docs/plans/2026-09-06_agent-project-workspace-foundation.md R5, R11 |
Design consequence: every mockup's home route is the control board. Everything else is one step away from it.
2. Agents, projects, workspaces
| Capability | Status | Source |
|---|---|---|
| Reusable agent definition: identity, type, harness, SOUL, configuration, permission ceiling. | planned (R1, record catalog agent-definition) |
foundation plan R1; phase2 contract section 3 |
| Project registers agents with RBAC; contains N workspaces; workspace has exactly one parent project. | planned (R2, R3) | foundation plan R2, R3 |
| Same agent in many projects and workspaces with separate sessions. | planned (R4) | foundation plan R4 |
| Launch names agent, project, workspace. Resume is default; Fresh is distinct; first use auto-creates and announces. | planned (R5, R7) and implemented today only as scripts/agent.sh <name> interactive TUI launch |
foundation plan R5, R7; docs/TOOLS.md agent.sh |
| Fresh work decision: Continue, Abandon, Select, None. | planned (R8; command flags --work) |
phase2 contract section 5 |
| Registration records with role, narrowing restrictions, active or revoked. | planned (R32; registration kind) |
phase2 contract sections 3, 4 |
| Workspace retire and reopen. | planned (R29) | phase2 contract section 5 |
| Legacy sessions adopted only by explicit reviewed assignment. | planned (R30) | foundation plan R30 |
| Managed worktrees: checkout ownership, protected work, recovery. | proposed concept | docs/concepts/managed-worktrees.md |
| Agent seats today: agents// with SOUL.md, CONTEXT.md, work folder. | implemented (repository convention) | agents/README.md; agents/dewey/* |
| Standard roles catalog: Reader, Contributor, Reviewer, Coordinator, plus separate explicit grants. | planned (phase2 section 4) | phase2 contract section 4; roles/*.json (implemented role files today) |
3. Sessions, attachment, control
| Capability | Status | Source |
|---|---|---|
Session directory per named session under <dataRoot>/sessions/; persistent sessions and forks for headless runs. |
implemented | AGENTS.md data map; docs/TOOLS.md run-task.sh |
| One controlling connection per running session; others observe; explicit transfer with generation. | planned (R24; execution connect, execution transfer) |
foundation plan R24; phase2 contract section 5 |
| Resume against an already-running session reports the conflict and offers connection, never auto-attaches. | planned (R21) | foundation plan R21 |
| Session attachment across TUI, desktop, and web with the same authority. | proposed concept | docs/concepts/session-attachment.md |
| Config-check: launch fingerprint versus current base configuration, non-blocking mismatch notice recommending Fresh. | planned (R16, R17; execution config-check) |
foundation plan R16, R17; phase2 contract section 8 |
| Steering and cancellation: queued versus started work, honest interruption semantics. | proposed concept | docs/concepts/queue-steering.md |
| Collaborative state awareness: changed decisions, reconciliation, notification boundaries. | proposed concept | docs/concepts/session-state.md |
| Managed terminal: Mosaic-controlled, Pi remains the engine, no native screen parity required. | planned (R34, owner Q28 A) | foundation plan R34 |
| tmux agent-send and agent-watch as the current transport. | implemented (scripts) | docs/TOOLS.md agent-send, agent-watch |
| Fresh during active work requests controlled replacement. | planned (R25) | foundation plan R25 |
4. Goals, missions, tasks, work coordination
| Capability | Status | Source |
|---|---|---|
| Goal extension: /goal set, stop, resume, clear; goal_report satisfied, blocked, in_progress; quiet waits; deadline wake; NG footer and Alt+G recall. | implemented (extension with test suite) | extensions/goal/README.md; docs/plans/2026-09-06_goal-quiet-waits.md; 2026-09-06_ng-goal-footer-dev.md |
| Missions and tasks as declarative JSON with strict schemas; missions govern tasks by least-privilege intersection. | implemented | AGENTS.md invariant 4, 7; missions/hello.json; tasks/workspace-demo.json |
| Missions at project and workspace level, single parent, one owner. | planned (R18) | foundation plan R18 |
| Assignments bind task to agent; coordinator decisions; delegated within-plan decomposition. | planned (R19; assignment, decision kinds) |
phase2 contract section 3; foundation plan R19 |
| Approved plan change pauses affected work for reconciliation. | planned (R31) | foundation plan R31 |
| Kanban triggering, stall detection, recovery ladder, minimal owner remediation. | proposed | docs/plans/2026-09-06_foundation-mechanical-workflow-topics.md |
| Standing intents: events, schedules, aspirations, real wake ownership. | proposed concept | docs/concepts/standing-intents.md |
| Conductor role: decompose, dispatch, review, verify, integrate; conductor-apply commits locally. | implemented (protocol and script) | docs/plans/CONDUCTOR.md; scripts/conductor-apply.sh |
| CURRENT.md single next action; SESSIONS.md registry; BUILD-LOG phases. | implemented (file conventions) | AGENTS.md session protocol |
5. Runs, evidence, releases
| Capability | Status | Source |
|---|---|---|
Headless task run: run-task.sh run <task.json>; write-once run record with result.json, snapshots, stderr.txt. |
implemented | docs/TOOLS.md; AGENTS.md invariant 5 |
mosaic-task.mjs validate, run, show, list, retry, prune, resolve-role; prune leaves a receipt. |
implemented | docs/TOOLS.md |
| Invocation-level command evidence: actor, scope, assignment, command, limits, start, end, outcome, evidence refs. | planned (R33, owner Q27 A) | foundation plan R33 |
| Audit recording failure blocks affected executions. | planned (R27) | foundation plan R27 |
| Release: package, activate, rollback, status; activation log append-only. | implemented | docs/TOOLS.md release.sh; AGENTS.md data map |
Release ensure and unified mosaic CLI. |
planned (ROADMAP M16, M20) | docs/plans/ROADMAP.md |
| Execution context inspector: selected agent, project, workspace, harness, model, each input's source, revision, hash, inclusion decision, size, token estimate. | planned (ACT-1) with partial prompt snapshot today | docs/concepts/context.md; docs/plans/2026-09-07_agent-context-templates-and-migration.md |
| Foundation synthetic inspector CLI: permission preview, always labelled SYNTHETIC PREVIEW. | planned charter, partly implemented as fixture-only increment (#1500) | docs/plans/2026-09-06_foundation-inspector-charter.md; docs/plans/CURRENT.md |
6. Auth, providers, harnesses, models
| Capability | Status | Source |
|---|---|---|
auth.sh status, accounts; runtime-only secrets, never in repo or image. |
implemented | docs/TOOLS.md; AGENTS.md invariant 3 |
Registry of providers, accounts (metadata split from credential file), settings profiles, seat selections, harness manifests; registry validate, list. |
planned charter (#1499 increment 1), fixture-only pieces done (#1500) | docs/plans/2026-09-10_m20-increment1-charter.md; 2026-09-10_m20-increment2-charter.md |
| Multi-account auth, per-seat default accounts, OAuth refresh (gate 7 resolved). | planned (ROADMAP M19; auth plan) | docs/plans/ROADMAP.md; docs/plans/2026-09-03_auth-provider-harness-registry.md |
| Agent runtimes: provider, model, harness distinctions; adapter evidence. | proposed concept | docs/concepts/agent-runtimes.md |
| Pi pinned exactly; release identity from RELEASE file. | implemented | AGENTS.md version pin |
7. Skills, extensions, packages
| Capability | Status | Source |
|---|---|---|
| Skills lifecycle: install, activate, deactivate, uninstall, role ceilings on skills. | planned (ROADMAP M17, M18) | docs/plans/ROADMAP.md |
| Extensions directory as canonical source; packages/* monorepo succession. | planned (M20, monorepo layout) | docs/plans/2026-09-06_monorepo-source-layout.md; technical map |
| unslop-check as a repository prose gate. | implemented | docs/TOOLS.md unslop-check |
| Skill launcher mismatch recovery. | implemented fix record | docs/plans/2026-09-08_skill-launcher-mismatch.md |
8. Messaging, people, federation
| Capability | Status | Source |
|---|---|---|
| Messages address a workspace; identity reuse must not mix conversations. | planned (R12) | foundation plan R12 |
mosaic comms boundary with site, instance, project, workspace, source, target; list and message. |
proposed (owner CLI example) | docs/plans/2026-09-06_foundation-federation-comms-topics.md |
| Master registry: site, instance, project, workspace, agent; federation across sites. | proposed | same file |
| Multi-user authority: attribution, observation, control, scoped permission. | proposed concept; owner also specified multi-user by default | docs/concepts/multi-user.md; install-onboarding topics |
| Transports behind Mosaic: tmux internal, Git durable comms, Matrix, Discord, Slack. | proposed, no backend selected | federation-comms topics |
9. Memory and context
| Capability | Status | Source |
|---|---|---|
| Memory architecture: knowledge categories, admission, scope, retrieval. | proposed concept | docs/concepts/memory-architecture.md |
| Memory provenance: lineage, correction, deletion coverage. | proposed concept | docs/concepts/memory-provenance.md |
| Only designated general preferences shared by default; personal and project context supplied where authorized. | planned (R28) | foundation plan R28 |
| One canonical SOUL per agent; template bootstrap; revision resolved at launch. | planned (R16; ACT-1) | docs/concepts/soul.md |
| Context sources with permitted scopes and sharing designation. | planned (context-source kind) |
phase2 contract section 3 |
10. Onboarding, installation, settings
| Capability | Status | Source |
|---|---|---|
| Install wizard: deployment type, system auth (SSO, OIDC, LDAP, internal), break-glass admin, initial user, site, instance, initial agent (name, gender, personality, communication style), default harness, harness account, first project and workspace, routing. Required versus optional steps with Skip. | proposed (owner requirements) | docs/plans/2026-09-06_foundation-install-onboarding-topics.md |
| Use-case presets: software factory, personal assistant, executive assistant, journal, health tracker, writing, social media, business operations, job applications. | proposed | same file |
| Advanced user profile and account linking, opt-in and access-controlled. | proposed | same file |
| Reconfiguration mode at any later time, resumable and validated. | proposed | same file |
| Ten palettes, Light, Dim, Dark, user-selectable, shared across site and apps. | mockup (brand board), owner-liked | DECISIONS.md; brand.js |
| System config is a single fail-closed file created by bootstrap only. | implemented | AGENTS.md invariant 2 |
11. Cross-cutting interface rules taken from the sources
- Show agent, project, workspace on every session and work surface (R5, R11). Never let the interface keep a competing task list.
- Distinguish accepted, planned, proposed, and unverified. Proposals are labelled as proposals (owner Q6). The interface must never present a mockup action as a live effect.
- Refusals are first-class: a fail-closed refusal is shown with its reason and what to do, never routed around (AGENTS.md invariant 6).
- Waiting on the owner is never expiry into approval (phase2 section 11). The control board shows what is waiting and for how long, with the next step.
- Observers cannot control. The interface shows the current controller, generation, and how to request transfer (R24).
- Configuration mismatch is a non-blocking notice with an on-demand check (R17).
- Secrets never appear. Accounts are shown by metadata only (AGENTS.md invariant 3; M20 charter).
- Append-only records are shown as history, never edited in place (AGENTS.md invariant 9).
12. Gaps the mockups will surface for the backend
These are not features. They are questions the UI raises that the docs do not yet answer.
- Where the "waiting on you" list comes from: goal reports, decision records, quiet waits, and acceptance gates are separate sources today.
- Stall detection thresholds and who may act on a stalled session from the web.
- Whether the web client can be a controller (R24) or only an observer at first.
- How notifications reach a user outside the app (no transport chosen).
- Whether project and workspace creation is a web action or a reviewed commit.
- How the control board scopes across sites and instances once federation exists.