State aggregation
Tasks, logs, events, and system status are shaped into one console model
Projects
An internal operations console for tasks, logs, events, and system status
An operations console for the personal website that brings tasks, logs, events, and system state into one maintainable view.
Verifiable entry points
No public demo
The console contains internal tasks, events, logs, and deployment state and requires administrator authentication, so it has no public demo.
Source evidence
Start with the API implementation, then inspect the companion dashboard-web client and tests in the same repository.
Tasks, logs, events, and system status are shaped into one console model
OSS and ETag conflicts remain explicit design constraints
The console can host content operations, deployment records, and Knock summaries
Asset status
Only repository-backed product mocks, public documentation, or an explicit no-public-image explanation appear here.
Asset type: Architecture diagram
Asset type: Documentation
The public plan records the monorepo shape, OSS data layout, API surface, ETag rules, and test requirements.
Content, deployments, logs, and tasks are scattered across tools, making it hard to understand current system state and the next priority.
Use dashboard-api to read and write tasks and events, while dashboard-web presents actionable state views with OSS and ETag conflict boundaries.
dashboard-api owns task and event reads and writes while dashboard-web renders operational status views. The storage layer currently uses OSS objects with ETag checks for conflict boundaries.
Step 01
The Next.js client handles administrator sign-in and reads current state and recent events.
Step 02
Administrator API calls use JWT, while automated event ingest uses a separate INGEST_TOKEN.
Step 03
Express routes define read and write boundaries for state, events, tasks, logs, and status.
Step 04
State, tasks, daily events, and daily logs use stable object-storage keys.
Step 05
Task and append-array writes use conditional requests and bounded retry, returning explicit conflicts when needed.
Decision 01
Decision 02
Decision 03