diff --git a/linear/docs/process/claw_v1_boundary_model_v1.md b/linear/docs/process/claw_v1_boundary_model_v1.md index 47d78eb..8a41822 100644 --- a/linear/docs/process/claw_v1_boundary_model_v1.md +++ b/linear/docs/process/claw_v1_boundary_model_v1.md @@ -1,8 +1,9 @@ # Claw v1 Boundary Model v1 -Status: Working baseline -Primary issue: [BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture) +Status: Active minimum-floor baseline +Primary issue: [BIT-215 — Taylor01: decide Claw v1 scope and boundary](https://linear.app/bitpod-app/issue/BIT-215/taylor01-decide-claw-v1-scope-and-boundary) Related issues: +- [BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture) - [BIT-114 — Define OpenClaw-native operator intake and dispatch surface](https://linear.app/bitpod-app/issue/BIT-114/define-openclaw-native-operator-intake-and-dispatch-surface) - [BIT-115 — Prove personal-computer -> OpenClaw HQ conversational/dispatch loop](https://linear.app/bitpod-app/issue/BIT-115/prove-personal-computer-openclaw-hq-conversationaldispatch-loop) - [BIT-205 — Define Taylor01 operator intake and supporting surface adapters](https://linear.app/bitpod-app/issue/BIT-205/define-taylor01-operator-intake-and-supporting-surface-adapters) @@ -86,6 +87,15 @@ So the current relationship is: - `bitpod-taylor-runtime` - owns the live runtime substrate and runtime proof lane +## Relationship to current OpenClaw doctrine in `bitpod-tools` + +- `bitpod-tools` remains the owning doctrine surface for the current + proving-ground operator contract +- [BIT-114 — Define OpenClaw-native operator intake and dispatch surface](https://linear.app/bitpod-app/issue/BIT-114/define-openclaw-native-operator-intake-and-dispatch-surface) + stays the practical OpenClaw-side contract owner for the current proof lane +- this boundary model constrains that doctrine from the Taylor01 side without + replacing it as the Bootstrap proving-ground operator contract + ## Required non-goals Do not use Claw v1 work to: diff --git a/linear/docs/process/openclaw_operator_intake_dispatch_contract_v1.md b/linear/docs/process/openclaw_operator_intake_dispatch_contract_v1.md index a91a81e..123353d 100644 --- a/linear/docs/process/openclaw_operator_intake_dispatch_contract_v1.md +++ b/linear/docs/process/openclaw_operator_intake_dispatch_contract_v1.md @@ -122,6 +122,31 @@ They must not do these things: - bypass Linear or repo truth for durable outcomes - force the system to depend on one transport-specific behavior +## Taylor01 supporting-surface boundary + +This proving-ground contract is also the current practical input to +[BIT-205 — Define Taylor01 operator intake and supporting surface adapters](https://linear.app/bitpod-app/issue/BIT-205/define-taylor01-operator-intake-and-supporting-surface-adapters). + +Taylor01-side retained artifact: + +- `linear/docs/process/taylor01_operator_intake_supporting_surface_adapters_v1.md` + +Use this split: + +- primary operator path: + personal computer control console -> HQ runtime -> durable repo or Linear + truth surfaces +- supporting adapters: + Discord or other transports that can relay intent, mirror progress, or return + links without becoming the primary truth surface +- non-goal: + do not treat a transport-specific command surface or local overlay as the + final Taylor01 adapter architecture + +This means the current OpenClaw contract informs the Taylor01 minimum floor, +but does not replace the Taylor01-side architecture owner under +[BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture). + ## Transitional versus target-state ### Transitional now diff --git a/linear/docs/process/phase4_return_sequence_post_taylor01_2026-03-12.md b/linear/docs/process/phase4_return_sequence_post_taylor01_2026-03-12.md index 4ddb41b..b44472c 100644 --- a/linear/docs/process/phase4_return_sequence_post_taylor01_2026-03-12.md +++ b/linear/docs/process/phase4_return_sequence_post_taylor01_2026-03-12.md @@ -1,116 +1,126 @@ -# Phase 4 Return Sequence Post-Taylor01 — 2026-03-12 +# Bootstrap Return Sequence Post-Taylor01 — Active Minimum-Floor-First Mirror -Status: Active -Primary issue: [BIT-95 — Define bootstrap closure gates for Taylor-real, minimum-team-ready, Discord acceptance, and startup-ready](https://linear.app/bitpod-app/issue/BIT-95/define-bootstrap-closure-gates-for-taylor-real-minimum-team-ready) +Status: Active Bootstrap-side sequence mirror +Primary issues: +- [BIT-104 — Execute Mac Mini execution-HQ bootstrap for NemoClaw runtime](https://linear.app/bitpod-app/issue/BIT-104/execute-mac-mini-execution-hq-bootstrap-for-nemoclaw-runtime) +- [BIT-113 — Phase 3 evidence pack and HQ go/no-go](https://linear.app/bitpod-app/issue/BIT-113/phase-3-evidence-pack-and-hq-gono-go) Related issues: +- [BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture) +- [BIT-214 — Taylor01: lock minimum real-Taylor runtime contract](https://linear.app/bitpod-app/issue/BIT-214/taylor01-lock-minimum-real-taylor-runtime-contract) +- [BIT-215 — Taylor01: decide Claw v1 scope and boundary](https://linear.app/bitpod-app/issue/BIT-215/taylor01-decide-claw-v1-scope-and-boundary) +- [BIT-205 — Define Taylor01 operator intake and supporting surface adapters](https://linear.app/bitpod-app/issue/BIT-205/define-taylor01-operator-intake-and-supporting-surface-adapters) +- [BIT-115 — Prove personal-computer -> OpenClaw HQ conversational/dispatch loop](https://linear.app/bitpod-app/issue/BIT-115/prove-personal-computer-openclaw-hq-conversationaldispatch-loop) - [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) -- [BIT-99 — Embody first specialist as a real AI agent/runtime beyond lane or skill proxy](https://linear.app/bitpod-app/issue/BIT-99/embody-first-specialist-as-a-real-ai-agentruntime-beyond-lane-or-skill) -- [BIT-98 — Prove real multi-agent team loop with Taylor plus embodied specialist agent(s)](https://linear.app/bitpod-app/issue/BIT-98/prove-real-multi-agent-team-loop-with-taylor-plus-embodied-specialist) -- [BIT-86 — Real Discord acceptance for team session contract and bridge command surface](https://linear.app/bitpod-app/issue/BIT-86/real-discord-acceptance-for-team-session-contract-and-bridge-command) -- [BIT-94 — Preserve Vera QA runtime behaviors from Zulip-era implementation for dedicated agent path](https://linear.app/bitpod-app/issue/BIT-94/preserve-vera-qa-runtime-behaviors-from-zulip-era-implementation-for) -- [BIT-96 — Stand up Taylor Discord conversational intake path for real agent acceptance](https://linear.app/bitpod-app/issue/BIT-96/stand-up-taylor-discord-conversational-intake-path-for-real-agent) -- [BIT-100 — Define AI-agent portability boundary and repo extraction strategy](https://linear.app/bitpod-app/issue/BIT-100/define-ai-agent-portability-boundary-and-repo-extraction-strategy) +- [BIT-216 — Taylor01: decide capability container direction beyond current `SKILL.md`](https://linear.app/bitpod-app/issue/BIT-216/taylor01-decide-capability-container-direction-beyond-current-skillmd) +- [BIT-217 — Taylor01: classify current artifacts by durability and overlay status](https://linear.app/bitpod-app/issue/BIT-217/taylor01-classify-current-artifacts-by-durability-and-overlay-status) +- [BIT-218 — Taylor01: define future dedicated repo extraction trigger for Claw](https://linear.app/bitpod-app/issue/BIT-218/taylor01-define-future-dedicated-repo-extraction-trigger-for-claw) +- [BIT-235 — Plan: Taylor01-HQ org-agnostic local environment and bootstrap boundary](https://linear.app/bitpod-app/issue/BIT-235/plan-taylor01-hq-org-agnostic-local-environment-and-bootstrap-boundary) ## Purpose -Return the active bootstrap focus to the pre-Taylor01 near-term Phase 4 execution gates while preserving the new Taylor01 portability rules as operating constraints rather than as the main workstream. +Mirror the active Taylor01 Claw minimum-floor-first plan into the Bootstrap +lane so Bootstrap proof work does not drift ahead of: -## Verified starting point +- truthful Phase 3 closeout +- the minimum Taylor01 architecture floor +- the locked ownership split between Bootstrap reality and Taylor01 architecture -- [PR #50 — [BIT-100] Implement Taylor01 co-equal product boundary BIT-100](https://github.com/BitPod-App/bitpod-tools/pull/50) is merged. -- [PR #49 — [BIT-96][BIT-97] Normalize Taylor-real vs Discord acceptance BIT-96 BIT-97](https://github.com/BitPod-App/bitpod-tools/pull/49) is merged. -- Taylor01 now exists as a separate project and policy boundary, but it is no longer the primary active execution lane. -- Phase 4 is still not complete. -- The stronger Phase 4 existence gates now on `main` are: - - Taylor embodied AI agent - - first specialist embodied AI agent - - real multi-agent team loop - - at least one accepted operator surface +This document is the Bootstrap-side execution mirror of the active Taylor01 +plan. It is not a second architecture owner. -## Return-to-execution sequence +## Locked ownership -### 1. Immediate active lane: Taylor-real +- Bootstrap proves reality and execution evidence. +- Taylor01 owns durable Claw architecture. +- [BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture) + is the single architecture owner. -Make [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) the immediate active gate. - -Rule: - -- do not wait for Discord if another surface can prove or fail Taylor-real faster -- prove or falsify Taylor-real first in the fastest honest live surface available +## Verified starting point -Why first: +- [BitPod-App/bitpod-tools PR #50 — [BIT-100] Implement Taylor01 co-equal product boundary BIT-100](https://github.com/BitPod-App/bitpod-tools/pull/50) + is merged. +- [BitPod-App/bitpod-tools PR #49 — [BIT-96][BIT-97] Normalize Taylor-real vs Discord acceptance BIT-96 BIT-97](https://github.com/BitPod-App/bitpod-tools/pull/49) + is merged. +- `bitpod-tools` remains the BitPod doctrine and proving-ground repo. +- `bitpod-taylor-runtime` remains the runtime and embodiment repo. +- `taylor01-skills` remains the portable substrate repo. +- Bootstrap Phase 3 is not yet truthfully closed. +- Bootstrap Phase 4 proof work remains open and must use the Taylor01 minimum + floor as a constraint rather than becoming a parallel architecture lane. -- Taylor-real is a direct missing truth gate -- current evidence still proves only Taylor operational orchestration, not embodied agent reality to CJ +## Active execution order -### 2. First specialist embodiment: Vera path +### 1. Close Bootstrap Phase 3 truthfully -Use Vera as the recommended first specialist embodiment path. +Use [BIT-104 — Execute Mac Mini execution-HQ bootstrap for NemoClaw runtime](https://linear.app/bitpod-app/issue/BIT-104/execute-mac-mini-execution-hq-bootstrap-for-nemoclaw-runtime) +plus [BIT-113 — Phase 3 evidence pack and HQ go/no-go](https://linear.app/bitpod-app/issue/BIT-113/phase-3-evidence-pack-and-hq-gono-go) +as the active Bootstrap closeout pair. -Primary lane: +Required focus: -- [BIT-99 — Embody first specialist as a real AI agent/runtime beyond lane or skill proxy](https://linear.app/bitpod-app/issue/BIT-99/embody-first-specialist-as-a-real-ai-agentruntime-beyond-lane-or-skill) +- reconcile current `taylor01` execution-account and Mini runtime truth +- assemble evidence from the existing Phase 3 spine +- disposition [BIT-49 — Lock down personal GitHub account to human-only access (remove AI/runtime paths)](https://linear.app/bitpod-app/issue/BIT-49/lock-down-personal-github-account-to-human-only-access-remove) + and [BIT-74 — Execute post-bootstrap local scope hardening window after migration closeout](https://linear.app/bitpod-app/issue/BIT-74/execute-post-bootstrap-local-scope-hardening-window-after-migration) + truthfully rather than by default escalation +- record the explicit go/no-go verdict before claiming Phase 3 is done -Support lane: +### 2. Lock the minimum Taylor01 architecture floor -- [BIT-94 — Preserve Vera QA runtime behaviors from Zulip-era implementation for dedicated agent path](https://linear.app/bitpod-app/issue/BIT-94/preserve-vera-qa-runtime-behaviors-from-zulip-era-implementation-for) +Do this under Taylor01 before treating Bootstrap proof tickets as the primary +active architecture lane: -Why Vera first: +- [BIT-214 — Taylor01: lock minimum real-Taylor runtime contract](https://linear.app/bitpod-app/issue/BIT-214/taylor01-lock-minimum-real-taylor-runtime-contract) +- [BIT-215 — Taylor01: decide Claw v1 scope and boundary](https://linear.app/bitpod-app/issue/BIT-215/taylor01-decide-claw-v1-scope-and-boundary) +- [BIT-205 — Define Taylor01 operator intake and supporting surface adapters](https://linear.app/bitpod-app/issue/BIT-205/define-taylor01-operator-intake-and-supporting-surface-adapters) -- current QA lane already exists and is real at a lane level -- Vera has preserved skill/runtime continuity that engineering specialist lanes do not yet have as strongly -- Zulip-era behavior inventory makes Vera the fastest plausible path to first specialist embodiment +Rule: -### 3. Real team proof +- Bootstrap proof work may inform these items, but it must not redefine them + silently. -After Taylor-real and first specialist embodiment, prove: +### 3. Run the first honest proof lane -- [BIT-98 — Prove real multi-agent team loop with Taylor plus embodied specialist agent(s)](https://linear.app/bitpod-app/issue/BIT-98/prove-real-multi-agent-team-loop-with-taylor-plus-embodied-specialist) +After the Phase 3 closeout pair and minimum floor are strong enough, run: -Recommended first proof shape: +- [BIT-115 — Prove personal-computer -> OpenClaw HQ conversational/dispatch loop](https://linear.app/bitpod-app/issue/BIT-115/prove-personal-computer-openclaw-hq-conversationaldispatch-loop) +- [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) -- Taylor delegates bounded QA-relevant work to embodied Vera -- Vera returns result artifact or verdict -- Taylor uses the returned output to synthesize or close the work +Escalation rule: -This is the first honest team-existence proof. +- activate [BIT-101 — Implement Taylor as a portable embodied AI agent/runtime beyond deterministic bot flows](https://linear.app/bitpod-app/issue/BIT-101/implement-taylor-as-a-portable-embodied-ai-agentruntime-beyond) + only if the current runtime cannot satisfy those proofs honestly -### 4. Discord acceptance after the above +### 4. Use proof results to refine later Taylor01 lanes -Keep [BIT-86 — Real Discord acceptance for team session contract and bridge command surface](https://linear.app/bitpod-app/issue/BIT-86/real-discord-acceptance-for-team-session-contract-and-bridge-command) active, but treat it as the session-surface gate after the stronger agent/team existence gates are materially underway. +Keep these as proof-informed refinement, not proof blockers: -Discord-specific intake/runtime path remains: +- [BIT-216 — Taylor01: decide capability container direction beyond current `SKILL.md`](https://linear.app/bitpod-app/issue/BIT-216/taylor01-decide-capability-container-direction-beyond-current-skillmd) +- [BIT-217 — Taylor01: classify current artifacts by durability and overlay status](https://linear.app/bitpod-app/issue/BIT-217/taylor01-classify-current-artifacts-by-durability-and-overlay-status) +- [BIT-218 — Taylor01: define future dedicated repo extraction trigger for Claw](https://linear.app/bitpod-app/issue/BIT-218/taylor01-define-future-dedicated-repo-extraction-trigger-for-claw) +- [BIT-235 — Plan: Taylor01-HQ org-agnostic local environment and bootstrap boundary](https://linear.app/bitpod-app/issue/BIT-235/plan-taylor01-hq-org-agnostic-local-environment-and-bootstrap-boundary) -- [BIT-96 — Stand up Taylor Discord conversational intake path for real agent acceptance](https://linear.app/bitpod-app/issue/BIT-96/stand-up-taylor-discord-conversational-intake-path-for-real-agent) +### 5. Keep later embodiment gates deferred -Rule: +Do not pull these forward before the proof lane is strong enough: -- do not let Discord block Taylor-real if another live surface can answer the question first -- use Discord to close the session-surface proof once the underlying agent reality is closer to true +- [BIT-173 — Final legacy secret removal and 1Password cutover gate before AI agent operability](https://linear.app/bitpod-app/issue/BIT-173/final-legacy-secret-removal-and-1password-cutover-gate-before-ai-agent) +- [BIT-98 — Prove real multi-agent team loop with Taylor plus embodied specialist agent(s)](https://linear.app/bitpod-app/issue/BIT-98/prove-real-multi-agent-team-loop-with-taylor-plus-embodied-specialist) +- [BIT-99 — Embody first specialist as a real AI agent/runtime beyond lane or skill proxy](https://linear.app/bitpod-app/issue/BIT-99/embody-first-specialist-as-a-real-ai-agentruntime-beyond-lane-or-skill) -## Taylor01 constraint while executing +## Bootstrap interpretation rules -Use the Taylor01 rules as constraints, not as the main workstream: +- do not let Bootstrap proof tickets become a second Claw architecture owner +- do not treat Discord or another supporting adapter as the architecture owner +- do not let later Taylor01 refinement tickets block the first honest proof pass +- do not treat current `SKILL.md` overlays as final Claw identity -- solve portability now by default when reasonable -- if not now, use explicit temporary bypass -- keep bypasses short-lived and reviewable -- do not turn temporary coupling into vague long-lived backlog +## Supporting Taylor01 constraints -Relevant artifacts: +Use these as active execution constraints while working Bootstrap: +- `linear/docs/process/taylor01_runtime_minimum_v1.md` +- `linear/docs/process/claw_v1_boundary_model_v1.md` +- `linear/docs/process/openclaw_operator_intake_dispatch_contract_v1.md` - `linear/docs/process/taylor01_portability_review_gate_v1.md` - `linear/docs/process/taylor01_active_bypass_register_v1.md` - -## Recommended issue states - -Historical note: - -- These recommendations were written before the current `Ready` rename. Read any older `Todo` references in this file as `Ready`. - -- [BIT-95 — Define bootstrap closure gates for Taylor-real, minimum-team-ready, Discord acceptance, and startup-ready](https://linear.app/bitpod-app/issue/BIT-95/define-bootstrap-closure-gates-for-taylor-real-minimum-team-ready) -> `Done` -- [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) -> `In Progress` -- [BIT-94 — Preserve Vera QA runtime behaviors from Zulip-era implementation for dedicated agent path](https://linear.app/bitpod-app/issue/BIT-94/preserve-vera-qa-runtime-behaviors-from-zulip-era-implementation-for) -> `Ready` -- [BIT-99 — Embody first specialist as a real AI agent/runtime beyond lane or skill proxy](https://linear.app/bitpod-app/issue/BIT-99/embody-first-specialist-as-a-real-ai-agentruntime-beyond-lane-or-skill) -> `Ready` -- [BIT-98 — Prove real multi-agent team loop with Taylor plus embodied specialist agent(s)](https://linear.app/bitpod-app/issue/BIT-98/prove-real-multi-agent-team-loop-with-taylor-plus-embodied-specialist) -> `Ready` -- [BIT-86 — Real Discord acceptance for team session contract and bridge command surface](https://linear.app/bitpod-app/issue/BIT-86/real-discord-acceptance-for-team-session-contract-and-bridge-command) -> remain `In Progress` diff --git a/linear/docs/process/taylor01_operator_intake_supporting_surface_adapters_v1.md b/linear/docs/process/taylor01_operator_intake_supporting_surface_adapters_v1.md new file mode 100644 index 0000000..fe98373 --- /dev/null +++ b/linear/docs/process/taylor01_operator_intake_supporting_surface_adapters_v1.md @@ -0,0 +1,134 @@ +# Taylor01 Operator Intake And Supporting Surface Adapters v1 + +Status: Active minimum-floor baseline +Primary issue: [BIT-205 — Define Taylor01 operator intake and supporting surface adapters](https://linear.app/bitpod-app/issue/BIT-205/define-taylor01-operator-intake-and-supporting-surface-adapters) +Related issues: +- [BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture) +- [BIT-214 — Taylor01: lock minimum real-Taylor runtime contract](https://linear.app/bitpod-app/issue/BIT-214/taylor01-lock-minimum-real-taylor-runtime-contract) +- [BIT-215 — Taylor01: decide Claw v1 scope and boundary](https://linear.app/bitpod-app/issue/BIT-215/taylor01-decide-claw-v1-scope-and-boundary) +- [BIT-114 — Define OpenClaw-native operator intake and dispatch surface](https://linear.app/bitpod-app/issue/BIT-114/define-openclaw-native-operator-intake-and-dispatch-surface) +- [BIT-115 — Prove personal-computer -> OpenClaw HQ conversational/dispatch loop](https://linear.app/bitpod-app/issue/BIT-115/prove-personal-computer-openclaw-hq-conversationaldispatch-loop) +- [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) +- [BIT-104 — Execute Mac Mini execution-HQ bootstrap for NemoClaw runtime](https://linear.app/bitpod-app/issue/BIT-104/execute-mac-mini-execution-hq-bootstrap-for-nemoclaw-runtime) +- [BIT-110 — Validate first AI HQ runtime path and complete first truthful smoke workflow](https://linear.app/bitpod-app/issue/BIT-110/validate-first-ai-hq-runtime-path-and-complete-first-truthful-smoke) + +## Objective + +Define the Taylor01-side operator intake surface and supporting adapter +boundary strongly enough to constrain the first honest proof lane without +pretending the current BitPod/OpenClaw proving-ground contract is already the +final Taylor01 adapter system. + +## Current truth + +- the personal computer remains the operator control console +- the current execution boundary remains the Mini runtime under the `taylor01` + execution account +- Linear and repo surfaces remain the durable truth anchors +- the current OpenClaw operator contract is practical proof-lane canon, not the + full Taylor01 architecture owner +- supporting chat transports remain useful, but they are not the primary truth + surface + +## Taylor01 operator entry model + +Taylor01 v1 should use this operator path: + +1. operator starts from the personal computer control console +2. operator anchors work in Linear +3. operator reaches the HQ runtime through the intended remote path +4. HQ executes inside the Taylor runtime boundary +5. durable outcomes return to Linear and repo-owned truth surfaces + +This means Taylor01 operator intake is defined first by: + +- control-console origin +- issue-anchored intent +- real remote execution boundary +- durable result materialization + +It is not defined first by: + +- a transport-specific bot surface +- local overlay behavior inside Codex chat alone +- a dashboard or package that does not yet exist + +## Supporting surface adapter model + +Supporting adapters may exist for: + +- Discord +- other chat transports +- future Taylor01-facing product surfaces + +In this phase they count as supporting only if they preserve all of: + +1. operator request entry with issue/context linkback +2. non-ambiguous handoff into the HQ runtime boundary +3. durable result return to Linear or repo truth +4. explicit non-primary status relative to the control-console to HQ path + +## Adapter requirements + +Every supporting adapter must carry: + +- target issue or explicit execution lane +- operator request +- constraints or guardrails +- returned durable link or artifact + +Every supporting adapter must not become: + +- the only place work scope lives +- the only continuity source when Linear or repo truth exists +- the only place decisions are recorded +- the claimed execution boundary + +## Relationship to OpenClaw doctrine + +[BIT-114 — Define OpenClaw-native operator intake and dispatch surface](https://linear.app/bitpod-app/issue/BIT-114/define-openclaw-native-operator-intake-and-dispatch-surface) +remains the practical proving-ground operator contract owner in `bitpod-tools`. + +This Taylor01-side artifact uses that proving-ground contract as input and +imposes these constraints: + +- preserve the personal-computer to HQ-runtime split +- preserve Linear and repo durable truth ownership +- keep supporting transports non-primary +- do not harden the current proving-ground transport details into the final + Taylor01 adapter architecture + +## What this constrains + +### For [BIT-115 — Prove personal-computer -> OpenClaw HQ conversational/dispatch loop](https://linear.app/bitpod-app/issue/BIT-115/prove-personal-computer-openclaw-hq-conversationaldispatch-loop) + +- the proof path must start on the personal computer +- the proof path must anchor in Linear +- the proof path must execute in the HQ runtime boundary +- the proof must end with durable repo or Linear evidence + +### For [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) + +- a supporting transport may host the proving interaction +- but the proving interaction must still be backed by the real runtime boundary +- local overlay behavior by itself does not satisfy the Taylor01 operator + contract + +## Explicit non-goals + +- no final capability-container decision +- no claim that Discord is the primary Taylor01 operator surface +- no requirement for a final dashboard before proving the first honest loop +- no forced extraction into a dedicated Taylor01/Claw repo yet +- no claim that current BitPod-local overlays are the durable Taylor01 adapter + library + +## Closeout read for BIT-205 + +BIT-205 can move toward closeout when this artifact and the current +OpenClaw-side contract agree on the following minimum floor: + +- one primary operator path exists +- supporting adapters are explicitly non-primary +- durable truth ownership is explicit +- the first proof lane can execute without waiting on final packaging decisions diff --git a/linear/docs/process/taylor01_runtime_minimum_v1.md b/linear/docs/process/taylor01_runtime_minimum_v1.md index 2e58bfa..74ef1a4 100644 --- a/linear/docs/process/taylor01_runtime_minimum_v1.md +++ b/linear/docs/process/taylor01_runtime_minimum_v1.md @@ -1,8 +1,9 @@ # Taylor01 Runtime Minimum v1 -Status: Working baseline -Primary issue: [BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture) +Status: Active minimum-floor baseline +Primary issue: [BIT-214 — Taylor01: lock minimum real-Taylor runtime contract](https://linear.app/bitpod-app/issue/BIT-214/taylor01-lock-minimum-real-taylor-runtime-contract) Related issues: +- [BIT-198 — Plan: Taylor01 runtime boundary and Claw-direction architecture](https://linear.app/bitpod-app/issue/BIT-198/plan-taylor01-runtime-boundary-and-claw-direction-architecture) - [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) - [BIT-115 — Prove personal-computer -> OpenClaw HQ conversational/dispatch loop](https://linear.app/bitpod-app/issue/BIT-115/prove-personal-computer-openclaw-hq-conversationaldispatch-loop) - [BIT-114 — Define OpenClaw-native operator intake and dispatch surface](https://linear.app/bitpod-app/issue/BIT-114/define-openclaw-native-operator-intake-and-dispatch-surface) @@ -56,6 +57,18 @@ To count as "real Taylor," all must be true: verb loop 5. durable outcomes can be written back to repo or issue truth surfaces +## Pass/fail gate + +Record the floor as: + +- `TAYLOR_RUNTIME_MINIMUM_V1=true` only when all five required runtime surfaces + above are true +- `TAYLOR_RUNTIME_MINIMUM_V1=false` if any required surface fails or cannot be + verified honestly + +If the verdict is false, Taylor-real or Claw-runtime claims must downgrade with +the failing condition named explicitly. + ## Required boundaries ### Execution boundary @@ -104,6 +117,21 @@ The runtime minimum is satisfied only when both are true: The runtime minimum is therefore necessary but not sufficient for full Claw v1 closure. +## Constraint on active proof tickets + +### For [BIT-97 — Prove Taylor as a real AI agent in any live operator surface](https://linear.app/bitpod-app/issue/BIT-97/prove-taylor-as-a-real-ai-agent-in-any-live-operator-surface) + +- BIT-97 must not pass from local `SKILL.md`, Codex chat, or command-only + overlay behavior by itself +- the proving surface must be backed by a runtime that satisfies this floor + +### For [BIT-115 — Prove personal-computer -> OpenClaw HQ conversational/dispatch loop](https://linear.app/bitpod-app/issue/BIT-115/prove-personal-computer-openclaw-hq-conversationaldispatch-loop) + +- BIT-115 must prove the control-console to HQ-runtime split rather than a + local MacBook shortcut +- the proof must materialize durable outcomes back to repo or issue truth + surfaces, not only a transport thread + ## Transitional allowances The following may remain transitional in v1: