01 · Why this intro exists

You are not joining a single repo with a single dashboard. You are joining a command center: a home-office wall of screens, a laptop Secondary seat, live Mission Control on DreamHost, and a set of agent skills that must not step on each other.

Humans (Operator / Ara) steer. Agents implement under exact go, or they observe, plan, and report. This page is the handshake — what am I looking at, and what am I allowed to touch?

Scope of this document: orientation only. Acceptance for product work still lives in Specs (specs/index.json) and Mission Control tasks — not here.

02 · The floor plan (reference photo)

Below is the real Command Center Home Office — big-screen Reports TV, Alienware Heavy desk, multi-monitor Mission Control, and the green-backlit Secondary laptop. Use it as mental model, not as a pixel-perfect UI spec.

Command Center home office: large wall TV showing Reports HUD, three lower monitors with code and Mission Control, Alienware tower, and a green-backlit gaming laptop running terminal sessions.
Command Center · Home Office — wall TV (Reports) · Alienware Heavy desk · Secondary laptop (right). Agent fetch URL (absolute): https://jesbel17.dreamhosters.com/intro/command-center-home-office.jpg (JPEG · ~334 KB · HTTP 200). Relative path command-center-home-office.jpg also works in-browser from this folder.
Images for agents (use absolute HTTPS — not CSS-only): Hero background reuses the same floor photo via CSS; if your tool cannot read CSS background-image, open the floor photo URL above.
Wall

Reports TV

Big-screen reports.html — Project + Agent matrices, plan-usage pies. Operators glance without scrolling the whole world.

Desk

Alienware · Heavy

SuperGrok Heavy interactive seats: design, dev (reports analyst), orchestrator. High-context, exact-go product work.

Mobile

Secondary laptop

Scheduled Autobots + shared Orchestrator clocks. Secondary SuperGrok plan — not the Heavy wall twin.

03 · Seats & plans (who sits where)

“Seat” is not a metaphor for a tab — it is a runtime identity with stamps, claim rights, and sometimes a physical machine.

Seat / plan Typical host What it does Do not
SuperGrok Heavy
heavy-dev · heavy-design · heavy-orchestrator		 Alienware (Area23) Interactive PLAN → exact go implement; reporting analyst; PM snapshot Run scheduled Autobots claim loops; twin-fire laptop clocks
SuperGrok Secondary
orchestrator · Autobots		 Laptop LAPTOP-DVU2VF95 Hourly Autobots, 5h/Daily orch, weekly reset — Ready schedules Pretend to be Heavy; enable Heavy wall schedules
Codex / Claude Assigned lanes Product PRs when authorized; backup / parallel capacity Invent Operator stamps; claim Condo/Personal
Operator (Ara) Human Exact go, smoke Approve, capacity, condo/personal —
Stamp hygiene: on agent Done use real completed_agent · completed_plan · assigned_agent · verified_by. Never fake Operator.

04 · Product surfaces you will actually open

Live

Mission Control

dashboard-test.html — task board, status chips, Specs | Checklist panels, New Task / Next ID. SoT is DreamHost api.php, not a local board dump. Agents: do not trust HTML shell counts (CSR) — use board-agent.php.

Acceptance

Specs feed

Hot: specs/index.json · pages under specs/PR-####.html. Index also links board_agent for tool-gated agents. Do not invent acceptance from proposals alone.

Projects on the board

  • Todolist — HUD dashboard, reports, automation, Mission Control product
  • montrealesk8 (MESK8) — community site PRs (often seeded / on-hold)
  • Lightwave / ReconAI — when present, respect project-qualified IDs
  • Condo / Personal — human only; agents document, never claim

05 · Rules of engagement (short version)

  1. PLAN MODE by default on interactive Heavy skills (/heavy-dev, /heavy-design). Read, diagnose, propose. No product edits until exact go PR-#### / go DIP-####.
  2. Approve ≠ Promote ≠ go. “Looks good” is not authorization to ship. Bare go → ask which PR/DIP.
  3. One scoped task after go. Touch the named files. Deploy only when asked or when the PR’s allowlist deploy script is in scope.
  4. No twin-fire schedules. Laptop owns Ready Autobots/Orch; Alienware Heavy+Dev schedules stay Disabled.
  5. Context discipline. Load Specs index first; expand full Specs HTML only when needed. Do not swallow all of proposals.md for every pass.
Smoke truth: code deployed ≠ Operator Approved. Specs and MC must not say “passed” until a human signs off when smoke is required.

06 · First day checklist (new agent)

  1. Open this intro + the floor photo. Name the three physical zones out loud (or in your handoff).
  2. Open Agent desk — read handoff and automation tiles.
  3. Peek live board: Mission Control — note Open / In progress / Smoke counts only.
  4. Open Reports — confirm both matrices and plan pies load (hard refresh if fonts look stale).
  5. Read hot Specs: specs/index.json — do not invent missing acceptance.
  6. Confirm your skill posture (Heavy PLAN vs Secondary scheduled). Wait for exact go before product edits.
  7. When you implement: leave a smoke checklist a human can tick on a real screen.
Handoff one-liner template: Seat=… · Plan=… · Skill=… · Working on PR-… · Blocked by… · Next smoke…

07 · Key paths (workspace)

Path Role
Projects/.agents/skills/ Shared skills (heavy-dev, orchestrator, autobots-roll-out, …)
Todolist/public/ Deployable HUD (dashboard, reports, specs, agent-desk)
Todolist/public/intro/ This intro — local/intranet; own CSS + photo
Todolist/archive/docs/proposals.md DIP scratchpad (ideas, not live acceptance)
Todolist/workflow.md L0 authorization ladder, ID claim, go rules
Todolist/scripts/ Deploy helpers, matrix verify, seat-bus tools

Live site root (when deployed): jesbel17.dreamhosters.com — this intro folder may stay local until an intranet section is promoted.

08 · Mini glossary

DIP / PR

Design / idea vs implementable code unit. Claim IDs via API peek/claim — do not hand-pick collisions.

Smoke

Human (or designated) verification on a real display. Agent wire-check ≠ TV smoke.

Seat bus

Heavy ↔ Secondary channel on DreamHost (seat-bus.php) without WinRM.

Matrix pack

Reports viewport: Board tiles + Project matrix + Agent matrix in one block above plan pies.

When you are ready to work: load your skill, state PLAN MODE if interactive, and wait for a named go. Welcome aboard.

Open Agent desk Open Mission Control Open Reports