BIOME · Tenant 01Truth snapshot · 2026-08-16

Airic —
System Map

A human-interlocked rail system for an agentic chief of staff. What is powered, wounded, dark, drafted, planned, and gated—without polishing away the truth.

Snapshot · 2026-08-16
TV board · 16:9 ↗ Product evolution · W0–W6 ↗

Program signal · Human-reviewed work

Drafts awaiting approval

—pending
Safety rule: review before external action Queue: live feed required

You are here: the first connected-work slice is live

Release checkpoint · September 25, 2026: W3 reliability repair V2 was verified September 7. The W4, Focus, and command-center stack was published September 17 with authenticated owner save/readback and a 15-minute health check. A bounded local AI preparation route completed item 956 on September 24 with a verified result. The local Attention Board bridge mapped one selected card to canonical item 960 without creating a duplicate job. These are scoped production proofs; the August 16 component inventory below remains historical and must not be read as a fresh status census.

Direction update · September 27, 2026: The next BIOME proofs advance in parallel: daily attention parity across the existing desk, Workspace Today and World, and meeting-to-commitment onboarding through a verified connection and records room. Both use the same work identity, revision, permission, owner review and result receipt. Planning and a blank manual start support both. World and the shared-loop adapter remain local; selected Attention Board intake does not mean the board has migrated. This direction does not change the historical component inventory or authorize a new live action.

Build route

Reliability repair is activated

The W3 transaction receipt records activated_and_verified and a production change. Thirteen repository files and two runtime mirrors were verified. The later payroll workbook content was preserved. Do not replay the one-shot activation.

The daily Docket is operating

Today, first Work and relationship dossiers, Calendar, bounded read-only Chat, Kanban, and Focus are published. Owner Focus input persisted through canonical save and reload. The Mini can return one approved bounded local preparation result to the same card. This does not prove broad autonomous work or complete source coverage.

One command surface still needs source parity

Local Attention Board history is preserved while selected cards map into BIOME. Bulk migration, current artifact and ClickUp/BRD reconciliation, cross-app task monitoring, and cloud included-only controls are not verified. Eric's Team Pulse findings review and historical-context worksheet are not approved or complete. Packet sync is not packet-content approval.

  1. W0–2 Operating

    Docket + review loop

    Cards, meeting intake, owner review, MFA, Activity, and exact approvals are live.

  2. W3 Repair activated

    Evidence + reliability

    Natural Team Pulse recurrence, calibration, citations, retrieval, and runtime evidence remain active gates.

  3. W4 First slice live

    Connected work

    Canonical objects, the first Work and relationship dossiers, Today, read-only Chat and Calendar, Focus, and Kanban are live. One bounded local AI job and one selected-card bridge have receipts. Next, prove shared daily attention in Workspace and World while meeting onboarding establishes one verified source-to-commitment path. Broaden source coverage and artifact/task synchronization behind the existing gates.

  4. W5 Designed

    Money + growth

    Ledger, Profit First, cashflow, margin, sales, expansion, and content learning depend on W4 truth.

  5. W6 Designed

    Life stewardship

    Today, Work, Relationships, Money, Growth, Atlas, and Chat converge in the whole-life BIOME view.

Four release boundaries

System work and owner decisions run on separate rails. Finishing one never silently authorizes the next.

  1. 1Activated

    Preserve the W3 activation evidence

    The September 7 receipt proves the one-shot reliability repair, not approval of findings or historical context. Retain its private rollback bundle, unchanged payroll content, and natural recurrence evidence. The August proof counts below are historical, not a current observation.

  2. 2Live

    Use the published W4 Docket

    The September 17 release applied the approved schema and Edge changes and published Today, Work, Relationships, read-only Chat, Calendar, Focus, and Kanban. Owner save/readback and the health window passed. Keep deferred non-owner auth and live HTTP replay coverage visible rather than treating this as exhaustive certification.

  3. 3First proof live

    Connect local attention one card at a time

    The existing Focus runtime maps a selected card by stable source reference to one canonical BIOME item. Repeated intake for item 960 returned the same item and created no execution job. Preserve local notes and approvals as history, not new execution authority. Reconcile current source versions and ClickUp/BRD direction before expanding the bridge.

  4. 4Qualification open

    Expand AI and source coverage behind receipts

    Item 956 proves one bounded Mini preparation path, not general coding, design, browsing, or cloud execution. Verify included-only cloud controls, then qualify each route with held-out and real shadow work. Connect sources and current-work reconciliation with freshness, exact identities, conflict handling, and readback. Connector, Self-note, legacy retirement, and external actions retain separate gates.

One BIOME · direction updated 2026-09-27

Daily clarity and connected stewardship

Two build tracks move together. Daily attention can improve now while one meeting connection proves the path from a real source to a reviewable commitment.

Explore the future experience

Targets are estimates, not release promises. A date never marks a milestone complete. Proof determines status, and dependent windows move if a gate slips.

01 · parallel track

Daily attention and follow-through

Today, saved state, review and safe AI routing over shared canonical work.

02 · parallel track

Meeting source to commitment

One visible setup, verified connection, records room and source-linked commitment.

Supporting work: Navigation, blank owner and access foundations: Shared shell/contracts and isolation work; no live invitation before enforcement. Controlled cutover and archive: Retire each duplicate only after proof, export and a normal-use observation window. Agent, source and permission boundaries: Local guidance plus enforced scoped actions, source provenance and capability-specific adversarial checks. Security Reviewer cannot grant itself permissions.

Live, scoped

Dated release evidence supports the first W4 operating slice. Publishing this roadmap does not deploy the local World, shared adapter or future capabilities. The September 17 release proved the first owner Today, Work, Relationships, Calendar, bounded Chat, Focus and Kanban slice.

Local, not connected

Today exact-item, saved direction, defer and recovery candidate at 9413dc9 passed bounded local QA; draft release remains behind owner/authenticated live gates. Meeting stored-pair reader is local, with trusted account/provider integration pending. Local World at 6804579 includes blank/manual start, Today attention, 360 camera and remembered entry view. Authenticated shared records and server entity Add/edit remain to integrate; no production-connected World claim.

Still open

Full daily operational parity, agent continuation and outside-owner readiness remain open.

Milestones M0–M5

Move when the proof passes

Each card shows its dependency, estimate and acceptance. W4, W5 and W6 keep their existing product meanings.

M0In progress

One current plan

Target window, estimate: September 27-28, 2026

Estimate confidence: near-term document checkpoint

Depends on: No earlier milestone

Role: Orchestrator and Workspace builder

Proof to move on: A reviewable roadmap, parity checklist and clear interim daily guide.

Acceptance checks
  • Publish the current Future and Map from one roadmap record.
  • Name each active track, its owner, dependencies and release proof.
  • Review the proposed navigation and keep current routes working.
M1In progress

Daily attention alpha

Target window, estimate: September 28 Workspace checkpoint target; combined daily alpha reforecast after World and shared-entity contract review

Estimate confidence: provisional; reforecast after M1

Depends on: M0

Role: Workspace builder with World frontend

Proof to move on: One real daily item and durable decision usable in both views, plus one shared client creation. Workspace-only proof is an interim checkpoint; advanced terrain/interior editing is later.

Acceptance checks
  • Reconcile selected current items; Board-only work links to its established writer without duplication.
  • Show request-level Needs me independent of assignee, a next focus with reasons, waiting work and source freshness.
  • Verify one authenticated Workspace item, exact saved direction and defer readback, preserving drafts through conflicts and retries.
  • In World, show the same authorized attention, context, true agent activity/results and shared decision/review/handoff panel. Add/edit one client through a shared service so both views reflect one identity.
  • Preserve scope, owner override, source links and access boundaries.
  • Run the applicable security checks before any source-driven AI action; local skill installation alone is not runtime enforcement.
M2In progress

Meeting connection first value

Target window, estimate: September 28-October 2, 2026

Estimate confidence: provisional; reforecast after M1

Depends on: M0

Role: Connector implementation with shared contract review

Proof to move on: One real permitted transcript is traceable from connection to storage to a reviewable commitment.

Acceptance checks
  • Configure or reuse one permitted Fathom connection through visible onboarding.
  • Verify a provider read and open one full transcript in its records room and Library.
  • Review a source-linked proposed commitment in the same attention queue.
  • Retry without duplicate ingestion or work.
M3Planned

Daily operating parity

Target window, estimate: October 2-9, 2026

Estimate confidence: provisional; reforecast after M1

Depends on: M1

Role: Workspace, World and operations routing owners

Proof to move on: Workspace becomes the primary writer only for journeys whose parity proof has passed.

Acceptance checks
  • Verify notes, modes, grouping, ordering, timers, snooze, hierarchy and exact draft review.
  • Show source freshness and explain missing or stale information.
  • For each request choose a qualified workflow, existing agent task, teammate through the current team plan, manual work or a bounded new task proposal.
  • Preserve drafts across errors, retries and switching views; bind actual results to the originating item.
  • Pass representative existing attention journeys and account-denial checks.
  • Expand verified shared journeys in both views; advanced terrain and interior editing have separate gates and do not postpone basic Add/edit or daily World attention.
  • Capture outcome/decision evidence and review owner effort, avoidable escalations and quality using comparable workflow definitions; show missing measurements explicitly.
M4Planned

Retire duplicate daily surfaces

Target window, estimate: October 16, 2026 at earliest if M3 passes on October 9; later if a gate slips

Estimate confidence: provisional; reforecast after M1

Depends on: M3

Role: Orchestrator and Workspace migration owner

Proof to move on: Local Attention Board becomes read-only for migrated journeys, then a retrievable archive. Desktop AI apps remain available.

Acceptance checks
  • Observe five normal working days on the replacement with no unresolved critical parity gaps.
  • Reconcile selected item counts, notes, approvals, mappings and receipts.
  • Export a restorable archive; retain source identity and open references.
  • Disable duplicate writers and workers before retiring old entry points.
  • Keep a tested fallback and explicit cutover receipt.
M5Planned

Independent owner pilots

Target window, estimate: After M2 and M3; date set when isolation gates pass

Estimate confidence: not yet dateable

Depends on: M2, M3

Role: Platform owner and independent QA

Proof to move on: Both independent owners can use the core workflow with verified privacy and onboarding.

Acceptance checks
  • A blank owner completes the same useful workflow without inherited private data.
  • Prove tenant isolation, invitation visibility/action powers, revocation and filtered search/counts.
  • Complete setup and recovery without developer-only steps.
  • Pilot one pastor or church leader and one faith-driven business leader.

Interim daily guide

One writer for each action

  1. Use the local Attention Board as the daily desk for journeys not yet migrated.
  2. Use production Workspace/Docket for journeys with verified parity and the current authorized write path.
  3. Use the existing chief-of-staff task for coordination and the existing Codex or Claude task for scoped execution.
  4. Use World as a local preview until the same authenticated record and action are proven across views.

Reconcile an item before changing its writer. Avoid dual entry and duplicate jobs.

Retirement gates

Archive by evidence

One canonical writer per migrated action. Read-only reconciliation precedes archival. Preserve original records and a restorable export. Codex and Claude remain execution tools until an equivalent supported route is proven.

  • Observe five normal working days on the replacement with no unresolved critical parity gaps.
  • Reconcile selected item counts, notes, approvals, mappings and receipts.
  • Export a restorable archive; retain source identity and open references.
  • Disable duplicate writers and workers before retiring old entry points.
  • Keep a tested fallback and explicit cutover receipt.

Entry behavior accepted · menu labels proposed

Today first, World one click away

First use opens Today in Workspace. Later visits remember the last valid view. Explicit deep links win, and unavailable context falls back to Today. These are accepted build requirements, not a claim that navigation is already deployed.

View switch: Workspace / World. Proposed primary: Today · My Life · Library · Planning · Connections. Persistent: Chat · Homecoming · Search · Add.

Existing Work, Relationships, Money and Growth remain reachable; final grouping and aliases require owner review. Becoming, Incoming, Outcome, Overcome remain the method lenses.

Execution goals

Daily freedom, then a fuller life view

September 27-28: Workspace decision checkpoint and parallel World integration; combined alpha date follows World/entity proof. No full parity or retirement claim. Shared Today decision contract first; meeting source verification alongside; useful World daily attention/actions and basic shared entity Add/edit qualify the combined alpha. Advanced terrain/interior editing follows later. Security checks accompany every source/action boundary.

  1. G0: Reliable daily desk. verified local. Depends on no prior goal. Owner: Sol repair + Astra.
  2. G1: Independent review and execution plan. complete planning. Depends on no prior goal. Owner: Claude Opus 5.5 consultant + Astra.
  3. G2: Trustworthy Today. draft pr local qa passed live gates pending. Depends on G1. Owner: Workspace Sol builder.
  4. G3: Durable owner decision. draft pr local qa passed live gates pending. Depends on G2. Owner: Workspace Sol builder.
  5. G4: Verified meeting source. local reader verified integration pending. Depends on G1. Owner: Meeting Sol worker.
  6. G5: Daily World and basic shared growth. local navigation verified live integration pending. Depends on G2, G3. Owner: Visible World Sol builder; Claude art review; Workspace service owner.
  7. G6: Daily alpha qualification. pending. Depends on G2, G3, G5. Owner: Independent QA + Astra + Eric.
  8. G7: Journey parity and retirement. planned. Depends on G6. Owner: Workspace/World builders + independent QA.
  9. G8: Reusable ownership. design only. Depends on G2. Owner: Platform builder + security QA.
  10. G9: Useful life domains. planned. Depends on G3, G4, G8. Owner: Bounded domain builders.
  11. G10: Sustainable whole-life operation. planned. Depends on G7, G8, G9. Owner: Astra + bounded owners + QA.
  12. G11: Security and prompt-injection defense. local guidance installed runtime planned. Depends on G1. Owner: Scoped Security Reviewer + shared-service owner + independent QA.
  13. G12: Time returned, useful throughput and owner attention. direction captured measurement unbuilt. Depends on G1. Owner: Astra metric definitions + existing shared-service builder + independent QA.

Owner review points: Today and view-switch UX; First real transcript meaning; Morning and between-task follow-through; Sharing and privacy before outside-owner pilots.

Later goals include relationships, client delivery and capacity, read-only money and COGS with source coverage, family, faith and rest. No spiritual worth score. Each new source is onboarded deliberately.

Time, throughput and attention

More useful outcomes, less routine owner effort

More accepted useful outcomes with less routine owner effort and fewer avoidable escalations, while retaining quality and required judgment.

  • Owner and total human time returned, with measured versus estimated effort
  • Accepted outcomes by workflow type, cycle time, aging work, arrivals and work in progress
  • Owner touches, waiting-owner time and avoidable versus required attention
  • Quality, rework and missed-escalation checks
  • Evidence-linked business outcomes and owner-chosen noncommercial commitments

Proposed comparable complete pre/post workflow periods using scoped ClickUp/work receipts. Missing historical effort remains unknown; no baseline calculated yet.

No productivity-to-revenue guarantee, no life-worth score, no autonomous approval to improve metrics, no hidden-record leakage. No new telemetry enabled by this roadmap.

State: direction accepted; implementation and metric details proposed.

Roadmap record one-biome-2026-09-27, revision 5c8901ef72e3. This section is generated from the versioned record and shares its milestone status.

The human interlocking

Every outbound rail converges here. Agents can prepare the route; only a person can clear the signal to the outside world.

01 · Dispatch trunk
Inputs

Source sidings

  • Fathom meetings
  • Gmail
  • Calendar
  • ClickUp
  • Hubstaff
Rails

Connectors / pipeline

Raw events + routed records

Registry

Agent yard

Agents read records in their lane

Outputs

Output sidings

DRAFTDRAFT

Drafts → approval queue

Attention ↘ morning brief
Visual heart

Approval interlock

—pending

Human queue · live count when feed is available

Required

Human clears signal

Approve → dispatch

Hard floor

Never-Auto wall

  • Client email sends
  • Payments
  • Payroll
  • Hiring / firing
  • Roadmap changes
After approval

Outside world

Nothing external without approval

Health return rail

  1. Pulse heartbeats + error ledger
  2. Orchestrator scan
  3. Attention items
  4. Today / EOD read surface

Trust-stage lever · 0–3

  1. 0 · Shadow
  2. 1 · Draft-only
  3. 2 · Supervised auto
  4. 3 · Autonomous in lane

Promotion is earned through approval counts. Any incident triggers demotion.

Action policy · T0–T4

T0T1T2T3T4

Separate from trust stages; the Never-Auto floor remains.

The complete build yard

Every verified system component is mounted below on its lane and wave. The build intentionally leapfrogged several generic Wave 1–2 agents to establish the Docket, Meeting Intelligence, and Team Pulse operating loop first; those earlier rails remain visible rather than being quietly marked done.

02 · Inventory

Signal key · status is shape + texture + label

    Wave sequence W0–W7 · all visible at once
      Loading verified components… Click any relay plate for source detail · / focuses search
        No component matches those filters. Reset the board to restore the full verified inventory.

        Truth rule: live telemetry adds an observation ring only. It never rewrites the embedded lifecycle status.

        Verified inventory · 11 lanes · waves 0–7
        Relay inspection

        What it is
        Lane
        Status
        Status reason / source note
        Wave
        Dependencies

        Live observation · canonical status unchanged