coulomb/core-hub
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Define Core Hub operator UI contract

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-27 13:39:13 +02:00
parent 0b90ebafd0
commit 6a2b9a9dde
4 changed files with 138 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
workplans/CORE-WP-0006-operator-console-and-whynot-ui.md
View File

@@ -20,23 +20,23 @@ Create the Core Hub operator UI without binding the framework contract to a sing
```task
id: CORE-WP-0006-T01
status: todo
status: done
priority: medium
state_hub_task_id: "8ea0294d-2730-4d4a-9c96-394ed6874368"
```
Define screens for hub registry, workplans, blocked tasks, progress/events, decisions, messages, API consumers, and migration status.
Result 2026-06-27: Defined the operator console IA in `docs/specs/ui-operator-console.md`, covering shell navigation, screen model, workflows, data exposure rules, and first prototype priorities.
## Map whynot-design Contract
```task
id: CORE-WP-0006-T02
status: todo
status: done
priority: medium
state_hub_task_id: "f16e2dba-b6fb-46e2-8f66-272ef0300f63"
```
Map whynot-design tokens, component semantics, and adapter rules to Core Hub UI needs.
Result 2026-06-27: Added `docs/specs/whynot-ui-adapter.md`, mapping whynot-design tokens, custom elements, IR/adapter rules, component usage, data-state semantics, and first adapter deliverables to Core Hub.
## Build First UI Prototype