Operations Dashboard · DJ TakeRun OS

PMO.
running in public.

Every active project, Claude Code session, and decision — tracked in one place. Read top to bottom: current state → active work → who owns what → how time is spent → what's next.

Live Data Operator: DJ TakeRun
Current Status

Project counts and key metrics from pmo.json. Rings animate to current values on load.

This Week's Focus  w/o 2026-05-04
  1. Complete all 7 hub page redesigns — make every page readable without prior context
  2. 01 Update pmo.json with session data from the hub redesign work
  3. 02 Push pmo.json to GCS and verify live dashboard renders correctly
  4. 03 Review and commit open BigQuery schema changes for usage logging

UPDATE WEEKLY · manually maintained · last updated 2026-05-06

Active Projects

All projects by stream — status, progress, and lead agent. Filter to see only what's in flight.

IDProjectStreamStatusProgressOwnerTarget
Milestones

Key delivery checkpoints across all projects. Done = shipped. Active = in progress. Pending = not yet started.

Agent Assignment Board
What are "agents"?

TakeRun OS uses 18 role-based agents — not autonomous software, but defined decision-making perspectives. Each agent (CEO, CFO, COO, DJ, Health, etc.) represents a domain of focus and owns a slice of the portfolio. When a Claude Code session runs, it logs under the agent whose domain it serves. The board below shows which agents are carrying work right now, and how loaded they are.

AgentWIP LoadAssigned ProjectsStatus
Session Log

Recent Claude Code sessions — what was built, how long it ran, and how much of the context window was used.

Resource Usage

Cumulative token and time spend across all sessions. Sessions nearing 100% context hit hard cutoffs — split long work across multiple focused sessions when possible.

SessionDateModelTokens (est.)Ctx %DurationFilesTasks
Value Stream — Where Work Flows and Stalls

Toyota-style flow map from idea to deployment. Green = value-add time. Red = wait time. Current-state bottleneck: the 2-day queue after Idea Capture — ideas sit until a Claude Code session starts. Toggle to see the future-state target.

Next 7 Days

3–5 concrete actions for this week. Update each Sunday.

May 4–5
Finish all 7 hub page redesigns (/pmo /travel /run /health /library /gym /viz)
Agent: COO · Project: D-02
done
May 6–7
Update pmo.json with session data from the hub redesign work
Agent: PMO · Project: E-01
active
May 8–10
Push pmo.json to GCS and verify live dashboard renders correctly
Agent: PMO · Project: E-01
pending

MANUALLY MAINTAINED · update each Sunday

How to Keep This Page Current

Manual Update Protocol

After each Claude Code session, update pmo.json in GCS and the static blocks below:

1. Session Log — Add entry to sessions[]: date, model, tokens, duration, tasks, outcome.

2. Tokens — Read from Claude Code context indicator (e.g. "857k / 200.0k"). Record as tokensApprox.

3. Projects — Update status and pct when a project phase changes.

4. Milestones — Change status:"pending""done" when reached.

5. Next 7 Days (§⑧) — Update the static block in pmo.html each Sunday: replace dates, actions, and agent references.

6. This Week's Focus (§①) — Update the 3 focus items when priorities shift.

Future: Cloud Function auto-export from BigQuery → dashboard auto-updates from CDN JSON.

Supplementary Detail
Timeline — Apr → Jun 2026
System Architecture — 18 Agent Network

Interactive force graph of all 18 agent roles and their dependencies. Click a node to see mission, KPIs, and connections. Drag to rearrange.

Agent Detail

Click a node to select. Role, KPIs, and connections will expand here.

Build Strata — From Zero to Live

The trajectory from empty repo to live djtakerun.jp, read like geology — oldest layers at the bottom, each band's height proportional to the lines of code in that phase. Click a band to expand. Source: takerun.pmo_phases in BigQuery.

— loading from pmo.json