BIOME

Owner product architecture · living destination

A life that gives life.

See how today’s Docket grows—without losing its clarity—into a Life Stewardship OS for work, relationships, money, growth, and the person you are becoming.

BecomingIncomingOutcomeOvercome
The centerHomecomingPresence with God

Release checkpoint · September 25, 2026

The first W4 operating slice is live.

The September 17 protected release put Today, the Work and relationship dossiers, Calendar, read-only Chat, Kanban, and Focus into production. An owner session verified canonical Focus save and readback. The September 24 local route then completed one bounded Mini AI preparation job, item 956, with a verified result and no human send. These receipts establish specific working slices, not completion of every W4 promise.

The local Attention Board can hand one selected card to the same canonical BIOME item; item 960 proved repeat intake did not create a duplicate job. Bulk migration, live cross-app task monitoring, automatic ClickUp/BRD reconciliation, broad AI work, and cloud included-only spending controls remain open. Team Pulse findings review and its historical-context worksheet also remain Eric decisions. The product sketches below are future direction unless a capability is specifically marked live.

Direction update · September 27, 2026: Workspace and World are two views of one BIOME, sharing the same commitment, revision, permission, and verified result. Two urgent tracks advance in parallel: daily attention parity across the existing desk, Workspace and World, and one meeting connection carried through storage, a source-linked commitment, preparation and owner review. Daily attention does not wait for a full connector rollout. Planning and a useful manual start develop alongside both. The World prototype and shared-loop adapter are local work, not a published or connected feature.

See what is live and what comes next

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.

See the system map

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.

Product evolution · W0–W6

From captured work to whole-life stewardship.

You are here · W4 first slice live

One connected model

Not eight products. Eight views of one life.

Every view resolves to the same people, organizations, engagements, commitments, evidence, money, and outcomes. The focused views help Eric work at the right altitude; BIOME zooms back out to show how all of it affects a life that gives life.

OrientationBecoming · Incoming · Outcome · Overcome decide what deserves attention and why.
Operating viewsToday · Work · Relationships · Money · Growth show the leader what is true and what needs movement.
IntelligenceAtlas, Pulse, and the evidence graph reconcile meetings, files, ClickUp, Hubstaff, communications, and financial facts.
AgencyBIOME Chat can ask, plan, draft, delegate, monitor, and—with exact approval—act.
IntegrationBIOME shows how every domain affects the others, the four moves, Homecoming, and the ecology of the whole life.

Future destination · clickable prototype

One navigation. Every altitude.

Choose a destination below to see a deliberately nonworking product sketch. These pages share one evidence graph and one visual language; they differ only in the altitude and decisions they are designed to support.

BBIOME