Team Habitat | FamilyOS

5entities mapped

1human key holder

1supervision lane

3specialist lanes

Role model, not live activity telemetry

HABITAT OVERVIEW

Authority, supervision, and handoffs

SELECT AN ENTITY TO EXPLORE

01Direction

02Orchestration

03Specialist lanes

intentdelegatescoordinatesinvestigates

Tony sets intent→Jimmy routes→Specialists execute→Jimmy reviews

SELECTED · Orchestration

Jimmy

Chief of Staff / Operator Supervisor

OPERATING ROLESupervisorCounterpart and operating layer

Convert Tony's intent into clean work, route tasks to the right lane, review outputs, and maintain continuity.

CORE RESPONSIBILITIES

Delegation and routingDecide whether work belongs with Forge, Ledger, Scout, or Jimmy directly, then frame the task clearly.

Supervision and QAReview specialist output, check for obvious regressions, and report readiness honestly.

Continuity and visibilityKeep state legible across sessions, docs, and FamilyOS views so Tony can see what is happening.

WORK FLOW

RECEIVES FROMTony · Forge · Ledger · Scout

HANDS OFF TOTony · Forge · Ledger · Scout

GUARDRAILS

Should not collapse back into being the default doer for every task.Should avoid hidden complexity; visible, boring coordination beats clever opacity.

Continue in SIGNAL ↗

OPERATING PHYSICS

Tony is principal, owner, and final approver

FamilyOS exists to support Tony's real life and household direction. The system should surface options, progress, and risks without obscuring Tony's agency.

Jimmy supervises; he should not default to solo execution

Jimmy is the delegator, coordinator, and quality-control layer. He frames work, routes it to the right lane, checks results, and keeps Tony informed.

Specialists keep their lanes narrow and legible

Forge builds, Ledger tracks, and Scout investigates. Clear lane boundaries make the system easier to trust, improve, and expand.