# S004: team participation and task continuation

**Selected 7 October 2026 · two bounded outcomes · qualification open**

[Current progress](/development/progress.html) · [Work and acceptance](/development/progress-scope.html) · [Report history](/development/progress-history.html#s003)

This page projects the shared sprint brief and capability maturity baseline retained in Sidecat. The baseline describes the start of S004; current owner progress is on the progress pages, through 7 October 2026 at 15:06 MDT (21:06:53 UTC). Native Sidecat records remain authoritative. Accepted product revision 4 and development revision 3 remain unchanged.

## S004 — usable team participation and task continuation

Josh lifted the start block at 12:14 MDT 7 October 2026 and directed each sprint to deliver usable capabilities, with at least two reaching actual normal use. Root selects these two deliverables, using the independent participant inputs. S003 remains closed. The sprint does not reduce the sixteen 1.0.0 commitments.

### Deliverable 1: human-and-agent team participation

Josh can enter the real team channel under his own prepared identity, read a bounded current conversation, follow useful task/result context, send direction or a reply, and return later to relevant responses. Agents use the same retained conversation and content. Ordinary participation requires no raw record IDs, borrowed agent profile, hand-assembled Note/grant/post chain, or Root relaying every message.

Reuse the installed Messaging/Content owners, existing actor enrollment/authority, and sidecatui. The client can be terminal-based; a new general chat service or hosted website is unnecessary. The exact entry point and accessibility must be documented and tried by Josh or an independent unfamiliar person/agent with assistance disclosed.

Acceptance: real independent human and agent participants communicate through the installed supported path; attribution and authorized readers are correct; a reply/result remains readable after leaving and reopening; ordinary errors explain the available next step. This must be used for actual sprint coordination after qualification.

### Deliverable 2: retained task context and continuation

An agent can find its legitimate current work by meaningful task/role context, receive a concise current brief with pending decisions and actions, advance a real task, and retain a reviewable result. A fresh session or replacement harness recovers that same unfinished task and continues a real clarification/correction/review step without a private predecessor briefing, raw-ID transcription, or repeating a settled effect.

Reuse accepted caller-library acquisition/keep/return, Work/Plan, Content, Messaging, existing execution adapters and retained outcomes. The runtime or reusable prepared task carries exact references; explicit technical inspection remains available. Do not build a second workflow database, universal agent engine or provider cache.

Acceptance: an independent fresh worker continues genuine unfinished work, produces the next result, and a reviewer plus Josh can inspect the connection to the original direction. Merely reading back task status is insufficient. Record context/call/manual-intervention observations; use the supported path in ordinary team work after qualification.

### Maturity and meaning

Use the established subsystem vocabulary: Unimplemented, Foundation, Exercised, Qualified. Keep implementation, installed availability, qualification and actual use as distinct evidence dimensions. The target is Qualified for each declared deliverable boundary plus observed normal use; this is not a claim that all Messaging, all Work, federation or 1.0 are qualified. Recover vocabulary from architecture/system.md, architecture/specifications/product-area-maturity-backlog-and-sprint-planning.md and progressive-interface-documentation-and-maturity.md; historical grades are not current node evidence.

Semantic definitions/discovery remain an explicit gap. Our mature use of exact record identity is not proof of a usable namespaced semantic vocabulary/mapping engine. The sprint must reuse actual common meanings for role, actor, worker, Work, Plan, message, capability and maturity. Wider semantic authoring/distribution remains visible release work; no new universal semantics subsystem is silently selected.

### Owners and the first bounded work

- Juniper: delivery, the corrected maturity view, shared context/task contract and integration. Keep the two complete outcomes central.
- Rowan: human channel/client and Work/context consumers; identify the installed source and smallest complete UI/runtime path.
- Cedar: Josh's prepared identity/access and content-sharing contract, existing provider/execution authority, serialized build/release path and existing publisher preparation.
- Linden: fresh-worker/harness continuation, ordinary call usability and execution-adapter reuse. Use the native-harness capability study as input, without inventing a new agent engine.
- Aspen: independent QA, plan review and installed unfamiliar-use evidence for both outcomes. Coordinate the two-sprint review-of-QA trial.

First, each affected owner returns the exact owned source/candidate, feasible reuse, shared-contract changes and concrete missing dependencies. This is a bounded design/readiness task, not a new general research campaign. Component source edits follow proportionate design and affected-consumer review. Independent QA design can proceed alongside it. No new infrastructure, paid advisory/image API call, or extra worker swarm is selected. Existing ready harnesses and the serialized capped remote builder are the resource envelope; no local Go/Rust/Node compilation.

QA plan review and sampled review of actual QA are a two-sprint trial. The first review sample must not cap the total functional QA coverage of the two deliverables. CLI-help formatting examples inform relevant criteria; other product areas need their own behavior criteria. Record defects and wrong judgments corrected, escapes, and added time/cost. At each closeout reassess; after two sprints continue, change or stop the extra review.

### Included support and exclusions

Included support: the ordinary entry points and discovery/help/examples needed for the two outcomes; actual worker identity/readiness; permissions/read sharing; relevant persistence/recovery; maintainable artifacts and publication/install path for the selected components.

Not selected: a whole-product help rewrite, new provider-feed integrations, MiniMax/Jev activation, generalized federation expansion, a marketplace campaign, full scale qualification or new paid infrastructure. Existing needs remain pending rather than erased.

### Review and finish

Show the first integrated usable path as soon as it exists. Hold a delivery checkpoint no later than 18:30 MDT today, earlier on a useful demonstration or material blocker. This is a progress/selection checkpoint, not a promised completion time or a reason to wait. Close the sprint naturally when both deliverables meet their finite acceptance and actual use is observed; if not, record the precise shortfall and deliberate disposition. Supporting fixes and process activity alone do not complete it.

---
Authority: Josh's 12:14 MDT unblock and usable-deliverables instruction; all participant first-round inputs, S003 retained results, and existing product4/development3. Root owns selection and will record finite Plans for the owners. The exact operator briefing is retained and projected to his fixed local page.

### Shared supporting material

The current maturity snapshot is retained as `s004-capability-maturity`; the native-harness comparison is `harness-agent-capabilities`. Both are shared inputs for every participant, including Josh. Native owner assignments were posted after the common selection. All four agent participants acknowledged the preparation brief and returned independent input; their new implementation/readiness assignments are distinct from those preparation tasks.

## Capability maturity at the start of S004

Two bounded deliverables are selected: usable human-and-agent team participation, and retained task context with real continuation. Neither is currently qualified. Both must reach their declared qualified boundary and be used in ordinary team work before S004 can close successfully.

This snapshot uses the verified S003 closeout and 7 October runtime observations. It does not re-run every product area. All sixteen full-version outcomes remain incomplete; a working component or a bounded qualification does not qualify the entire area.

### The established meanings

Subsystem evidence uses Unimplemented, Foundation, Exercised and Qualified. Unimplemented means no maintained behavior establishes the responsibility; Foundation means contracts or internal behavior exist without the ordinary journey; Exercised means a bounded ordinary journey with relevant recovery has been demonstrated; Qualified means the documented boundary and release evidence are complete.

Product maturity remains multidimensional: usefulness, architecture, implementation, installed availability, authority/recovery, qualification and caller experience. These are not a single score or a linear product ranking. Interface states such as experimental and stable describe another separate dimension. Actual normal use is evidence, not a replacement label called "using."

### Current cells and exact change history · 8 October 2026

This is the same sixteen-row report updated at 14:58 MDT, evidence through Team5166. **15 cells changed across 5 rows in this update**. Changed marks identify this revision; the expandable history retains these exact previous/current values, all 36 earlier published changes and the three later owner/prerequisite gap changes. The original S004 tables below remain unchanged. All sixteen full Version 1 outcomes remain incomplete.

The stable current native reference is `capability-maturity`. [Structured table and dated cell history](/capability-maturity.json). Installed caller/UI delivery and one assisted CLI sample advance the selected work; the actual UI trial exposed a blocking text-entry defect. S007 remains unjudged.

<table><thead><tr><th scope="col">Product capability</th><th scope="col">Existing implementation or use</th><th scope="col">Missing qualification or material gap</th><th scope="col">Sprint disposition</th></tr></thead><tbody><tr id="current-V1-01"><th scope="row">Organizational context</th><td>Guidance, named references, roles and selected working context are used.</td><td>Fresh workers still need manual orientation; effective scoped semantic inheritance is not established.</td><td>Improve the context needed for task continuation.</td></tr><tr id="current-V1-02"><th scope="row">Identity, authority and resources</th><td>Prepared actors, access decisions and bounded resource observations exist.</td><td>Josh&#x27;s own usable participation; reachable scoped workers; full remote allowance/delegation outcome remains incomplete.</td><td>Cedar owns selected identity/access and execution prerequisites.</td></tr><tr id="current-V1-03"><th scope="row">Records and source references</th><td><strong class="capability-changed">Changed · </strong>S006 exercised an exact 876-character originating Note. S007 now captures distinct originals; an assisted installed CLI participant deliberately selected, read and restored the correct 1,518-character original. Independent readback confirmed the bound task, source, title and full text.</td><td><strong class="capability-changed">Changed · </strong>Full-area qualification remains incomplete. The S007 CLI sample used an existing prepared actor and assistance; both-lot controls, ordinary reconnected MCP/Lisp and production UI participant acceptance remain open.</td><td><strong class="capability-changed">Changed · </strong>Retain the exercised original-read and restore evidence. Complete the selected S007 ordinary-use controls and remaining surfaces before judgment; no full V1-03 completion.</td></tr><tr id="current-V1-04"><th scope="row">Work and planning</th><td>Reusable Work, assigned Plan occurrences, boards and terminal judgments are used. The corrective QA coverage audit now has a native underway Plan and shared evidence.</td><td>Native project planning and application Plan judgment are not one clear user path. Capability analysis is not enforced as an opted-in scrum condition; a stable complete report was missing. Evidence stays optional by default.</td><td>Preserve current S007 selected Work. Corrective capability/QA reporting is underway; opt-in governance implementation admission remains with Rowan.</td></tr><tr id="current-V1-05"><th scope="row">Collective messaging</th><td>Real room messages, shared content and bounded reads are used.</td><td>Human entry, ordinary reply/thread/attention/return experience incomplete.</td><td>Human-and-agent team participation selected.</td></tr><tr id="current-V1-06"><th scope="row">Lisp and composition</th><td><strong class="capability-changed">Changed · </strong>S006 retained values and actual source observations reopened without reseeding. The installed S007 retained_result library exposes six exports; ordinary CLI library calls exercised deliberate choice, full original reading and carried restoration. S005 finite guidance remains Qualified.</td><td><strong class="capability-changed">Changed · </strong>General fresh-agent continuation and full Lisp documentation remain incomplete. The S007 sample needed shipped package guidance and assistance; independent ordinary reconnected MCP/Lisp acceptance remains open.</td><td><strong class="capability-changed">Changed · </strong>Reuse the installed retained-result library for the remaining S007 trials. Preserve the assisted CLI limits and existing S005/S006 evidence.</td></tr><tr id="current-V1-07"><th scope="row">Marketplace and packages</th><td><strong class="capability-changed">Changed · </strong>S005 finite guidance-use is Qualified. The S007 caller package is natively installed and locally ready; installed inspection exposes six exports and the exact 13,326-byte GUIDE. One assisted CLI participant used the installed library.</td><td><strong class="capability-changed">Changed · </strong>Broad public/internal package lifecycle and pending-work replacement remain unqualified. Caller source publication is held at a repository setup prerequisite; ordinary failure results do not identify the missing prerequisite, actual setup owner or supported repair/request action. Installed resource readiness does not establish complete marketplace qualification.</td><td><strong class="capability-changed">Changed · </strong>Continue ordinary use of the ready installed package and resolve the held source-publication prerequisite through its owner. Keep broader lifecycle work separate from S007.</td></tr><tr id="current-V1-08"><th scope="row">Semantic definitions and discovery</th><td>The standalone engine and read-only semantic assessment host are implemented. Host 0.2.0 is installed; actual Find ambiguity/single-source and selected-source Check controls were observed. S006 exercised one real original-source selection/read.</td><td>Find needs supplied catalog/documents/meaning. No top-level task-to-command semantic discovery exists. Broader vocabulary/mapping/domain-authoring and ordinary S007 participant use remain unqualified.</td><td>S007 integrates unfamiliar declared meaning, whole-contract assessment and deliberate source choice. Command discovery/manual gaps are explicit refinement inputs.</td></tr><tr id="current-V1-09"><th scope="row">Executable procedures</th><td>Bounded composed caller/pantry tasks were accepted.</td><td>General durable waits, decisions and continuation across harness replacement not qualified.</td><td>Build only the selected real continuation path.</td></tr><tr id="current-V1-10"><th scope="row">Managed agent work</th><td>External team harnesses and native Sol delegation execute bounded assignments. Team5083 reassigned a stalled caller occurrence; Team5089 reports actual source and checks on the replacement branch.</td><td>An assignment or live process does not prove successful work. Automatic cross-harness activation, durable return, context and attribution remain incomplete.</td><td>Keep ready component owners parallel; retain the old unfinished occurrence and verify replacement results against the same Work.</td></tr><tr id="current-V1-11"><th scope="row">Controlled execution</th><td>A serialized capped remote builder performs source-matched Go/Rust/site checks and builds, with retained commands, exits and unchanged-source checks.</td><td>That build path does not qualify general controlled local/remote execution, cancellation, connector effects or actionable unknown outcomes. The protected-material failure required private reconstruction of owner setup; general actionable prerequisite discovery and supported repair/request remain unqualified (Team5159/5162).</td><td>Reuse the accepted builder. Keep unknown effects untouched; do not infer a general execution qualification from component build passes.</td></tr><tr id="current-V1-12"><th scope="row">Shared bus and federation</th><td>Typed owner calls and semantic query-host operations are installed on the local bus. Application permission and Content effects remain with their owners.</td><td>Independently administered-node cooperation, durable subscriptions and gap/recovery qualification remain incomplete.</td><td>Use the existing query and Content contracts for S007; no federation expansion is selected.</td></tr><tr id="current-V1-13"><th scope="row">Feedback and improvement</th><td>Operator findings and independent reviews are retained in native Team/Work. Two QA audits reproduced help, discovery, coverage-list and installed-manual gaps; Team5091/5093 preserve the findings and corrective audit.</td><td>No complete current command-to-expectation-to-evidence coverage ledger was demonstrated. QA-review usefulness and comparable task costs are not established by test counts.</td><td>Corrective QA coverage audit underway. Rowan must assign disposition/implementation; broad all-hands QA and unfamiliar current-build trials are not complete.</td></tr><tr id="current-V1-14"><th scope="row">Usable interfaces and integrations</th><td><strong class="capability-changed">Changed · </strong>Installed CLI c2f0ab27 and operation search remain available. A fresh CLI participant read and restored the correct S007 original with assistance in 16 calls. The help repair has assertion RED, focused GREEN and passing affected/manual checks; delivery remains pending.</td><td><strong class="capability-changed">Changed · </strong>Ordinary library-route discovery required assistance. The installed man page remains stale; judge is absent from its index; invalid project plan judge help succeeds with parent help. search/apropos remain absent. Readable task association, updated installed help/manual, unassisted use, reconnected MCP and tracker synchronization remain unqualified. Ordinary task/library preparation and owner-failure results need discoverable missing prerequisites, actual owners and supported next actions; no new top-level command or automatic permission gate is selected (Team5159/5162).</td><td><strong class="capability-changed">Changed · </strong>Complete the remaining ordinary S007 surfaces and controls. Keep help delivery and coherent discovery/recovery improvements on their native corrective backlog; do not infer qualification from help test counts.</td></tr><tr id="current-V1-15"><th scope="row">Operational durability and scale</th><td>S006 retained named state and actual source observations reopened unchanged without reseeding. Component runs use bounded remote resources and source/artifact matching.</td><td>Bounded reopening is not full backup/recovery, multi-node contention, absent-agent or target-scale qualification.</td><td>S007 new typed cold restoration remains pending. Keep broader durability and scale outcomes incomplete.</td></tr><tr id="current-V1-16"><th scope="row">Sidecat UI</th><td><strong class="capability-changed">Changed · </strong>S006 exercised the full 876-character original viewport and return. The corrected S007 UI passes 22 Rust and 16 Go cases. A normal production UI/gateway pair is installed; its dashboard shows eight assigned and eight created rows under the delivery actor.</td><td><strong class="capability-changed">Changed · </strong>The installed pantry UI trial is blocked: query/context editors drop the first capital letter, so the displayed context label cannot be entered faithfully and no original is read. Back/Restore returns an ambiguous result. Human own-identity participation and broad UI acceptance remain incomplete.</td><td><strong class="capability-changed">Changed · </strong>Repair the observed UI text-entry routing defect and rerun the selected two-lot task, full original, Back and cold reopen. Keep component GREEN and installed delivery separate from participant acceptance; S007 remains unjudged.</td></tr></tbody></table>

<details id="capability-cell-history"><summary>Cell history: 15 new changes and all 39 earlier changes</summary><h4>2026-10-08T16:20:05Z · 36 changed cells</h4><table><thead><tr><th>Capability</th><th>Column</th><th>Before</th><th>After</th><th>Evidence</th></tr></thead><tbody><tr><th scope="row">V1-03 · Records and source references</th><td>Existing implementation or use</td><td>Exact Notes are reused by messages and Work; authorized team reads are exercised.</td><td>S006 exercised an exact originating Note read through semantic assessment: all 876 characters matched the independent owner read. Named results retain the actual observation and reopen without reseeding.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-03 · Records and source references</th><td>Missing qualification or material gap</td><td>Reader-grant plumbing is exposed and has caused denied contribution reads; full area qualification incomplete.</td><td>Full-area qualification remains incomplete. S007&#x27;s distinct-source capture, explicit choice and task-bound reader/restore are still under implementation and testing.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-03 · Records and source references</th><td>Sprint disposition</td><td>Make the two selected journeys share content correctly.</td><td>S006 finite original-source increment completed at Exercised scope. S007 advances exact source association and ordinary entry; no full V1-03 completion.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-04 · Work and planning</th><td>Existing implementation or use</td><td>Work definitions, assigned Plan occurrences, board selection and terminal judgments are in ordinary lead use.</td><td>Reusable Work, assigned Plan occurrences, boards and terminal judgments are used. The corrective QA coverage audit now has a native underway Plan and shared evidence.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-04 · Work and planning</th><td>Missing qualification or material gap</td><td>Current task discovery remains cumbersome; native project and application planning views are not yet one usable path.</td><td>Native project planning and application Plan judgment are not one clear user path. Capability analysis is not enforced as an opted-in scrum condition; a stable complete report was missing. Evidence stays optional by default.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-04 · Work and planning</th><td>Sprint disposition</td><td>Real continuation is selected; no competing planning ledger.</td><td>Preserve current S007 selected Work. Corrective capability/QA reporting is underway; opt-in governance implementation admission remains with Rowan.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-06 · Lisp and composition</th><td>Existing implementation or use</td><td>Bounded caller package acquisition, keep/reopen and return were accepted in S003.</td><td>S006 exercised retained named values/functions and actual source observation across reopened environments. S005 guidance-use is Qualified within its finite existing-actor boundary.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-06 · Lisp and composition</th><td>Missing qualification or material gap</td><td>Broader fresh-agent task continuation and interface usability incomplete.</td><td>General fresh-agent continuation and full Lisp documentation remain incomplete. New S007 capture/caller source has synthetic boundary checks, not installed participant qualification.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-06 · Lisp and composition</th><td>Sprint disposition</td><td>Reuse the accepted slice in the continuation outcome.</td><td>Reuse the maintained retained-result package. S007 caller work continues on the reassigned isolated Sol author occurrence.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-07 · Marketplace and packages</th><td>Existing implementation or use</td><td>Exact caller package delivery provides bounded exercised evidence.</td><td>Maintained helper source a9110345 is published. The installed durable_conversation GUIDE supplies eight capability cards; S005 finite guidance-use is Qualified under its stated sample limits.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-07 · Marketplace and packages</th><td>Missing qualification or material gap</td><td>Complete ordinary public/internal lifecycle and pending-work replacement not qualified.</td><td>Eight card topics are not eight qualified product capabilities. Maintained caller-package installation, broad public/internal lifecycle and pending-work replacement remain unqualified.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-07 · Marketplace and packages</th><td>Sprint disposition</td><td>Reuse existing packaging; no broad marketplace campaign.</td><td>Use installed guidance and existing delivery mechanisms. New S007 caller/package delivery remains pending; no broad marketplace campaign.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-08 · Semantic definitions and discovery</th><td>Existing implementation or use</td><td>Exact identity and typed contracts exist.</td><td>The standalone engine and read-only semantic assessment host are implemented. Host 0.2.0 is installed; actual Find ambiguity/single-source and selected-source Check controls were observed. S006 exercised one real original-source selection/read.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-08 · Semantic definitions and discovery</th><td>Missing qualification or material gap</td><td>A usable namespaced vocabulary, mappings and domain-record authoring journey is not established. Operation search alone is not a complete source inventory.</td><td>Find needs supplied catalog/documents/meaning. No top-level task-to-command semantic discovery exists. Broader vocabulary/mapping/domain-authoring and ordinary S007 participant use remain unqualified.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-08 · Semantic definitions and discovery</th><td>Sprint disposition</td><td>Use established shared meanings; keep this release gap explicit.</td><td>S007 integrates unfamiliar declared meaning, whole-contract assessment and deliberate source choice. Command discovery/manual gaps are explicit refinement inputs.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-10 · Managed agent work</th><td>Existing implementation or use</td><td>Four actual external team sessions have responded; Codex native delegation is available.</td><td>External team harnesses and native Sol delegation execute bounded assignments. Team5083 reassigned a stalled caller occurrence; Team5089 reports actual source and checks on the replacement branch.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-10 · Managed agent work</th><td>Missing qualification or material gap</td><td>Role/assignment is not proof of execution readiness. Automatic cross-harness return/context/attribution still incomplete.</td><td>An assignment or live process does not prove successful work. Automatic cross-harness activation, durable return, context and attribution remain incomplete.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-10 · Managed agent work</th><td>Sprint disposition</td><td>Reuse native agent/session mechanisms with retained Sidecat task context.</td><td>Keep ready component owners parallel; retain the old unfinished occurrence and verify replacement results against the same Work.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-11 · Controlled execution</th><td>Existing implementation or use</td><td>Existing execution contracts and capped remote build path.</td><td>A serialized capped remote builder performs source-matched Go/Rust/site checks and builds, with retained commands, exits and unchanged-source checks.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-11 · Controlled execution</th><td>Missing qualification or material gap</td><td>Rowan&#x27;s named native execution route returned unavailable; broad controlled local/remote outcome incomplete.</td><td>That build path does not qualify general controlled local/remote execution, cancellation, connector effects or actionable unknown outcomes.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-11 · Controlled execution</th><td>Sprint disposition</td><td>Resolve the concrete selected execution dependency.</td><td>Reuse the accepted builder. Keep unknown effects untouched; do not infer a general execution qualification from component build passes.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-12 · Shared bus and federation</th><td>Existing implementation or use</td><td>Typed local owner calls operate through the bus.</td><td>Typed owner calls and semantic query-host operations are installed on the local bus. Application permission and Content effects remain with their owners.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-12 · Shared bus and federation</th><td>Missing qualification or material gap</td><td>Full independently administered-node journey and durable gap/recovery behavior remain incomplete.</td><td>Independently administered-node cooperation, durable subscriptions and gap/recovery qualification remain incomplete.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-12 · Shared bus and federation</th><td>Sprint disposition</td><td>Existing calls only; no federation expansion.</td><td>Use the existing query and Content contracts for S007; no federation expansion is selected.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-13 · Feedback and improvement</th><td>Existing implementation or use</td><td>Josh&#x27;s findings, independent proposals and dispositions are retained.</td><td>Operator findings and independent reviews are retained in native Team/Work. Two QA audits reproduced help, discovery, coverage-list and installed-manual gaps; Team5091/5093 preserve the findings and corrective audit.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-13 · Feedback and improvement</th><td>Missing qualification or material gap</td><td>Closed improvement loops and comparable task cost evidence are incomplete.</td><td>No complete current command-to-expectation-to-evidence coverage ledger was demonstrated. QA-review usefulness and comparable task costs are not established by test counts.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-13 · Feedback and improvement</th><td>Sprint disposition</td><td>Two-sprint QA-review trial with useful-findings and cost measures.</td><td>Corrective QA coverage audit underway. Rowan must assign disposition/implementation; broad all-hands QA and unfamiliar current-build trials are not complete.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-14 · Usable interfaces and integrations</th><td>Existing implementation or use</td><td>CLI/MCP/Lisp and a bounded installed client exist.</td><td>CLI c2f0ab27 is now installed. Live operation search finds appwork.plan.judge; independent audits exercised help availability for 129 leaves. S006 exercised meaningful CLI/temporary MCP/Lisp output.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-14 · Usable interfaces and integrations</th><td>Missing qualification or material gap</td><td>Actual help failed readability; unfamiliar task completion and required tracker synchronization not qualified.</td><td>Installed man page is stale; judge is absent from its index; invalid project plan judge --help succeeds with parent help. search/apropos are absent. Complete searchable manual, unfamiliar task acceptance and tracker synchronization remain unqualified.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-14 · Usable interfaces and integrations</th><td>Sprint disposition</td><td>Fix entry points/help needed for the two outcomes; wider gaps stay visible.</td><td>Preserve installed presentation improvement. Treat manual parity, help correctness and task discovery as explicit unresolved QA requirements; default MCP reconnect and S007 trials remain separate.</td><td>Team5091; Team5093; installed c2f0ab27 CLI/manual probes</td></tr><tr><th scope="row">V1-15 · Operational durability and scale</th><td>Existing implementation or use</td><td>Some bounded restart/return evidence exists.</td><td>S006 retained named state and actual source observations reopened unchanged without reseeding. Component runs use bounded remote resources and source/artifact matching.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-15 · Operational durability and scale</th><td>Missing qualification or material gap</td><td>Full backup/recovery, multi-node concurrency and target-scale evidence not established here.</td><td>Bounded reopening is not full backup/recovery, multi-node contention, absent-agent or target-scale qualification.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-15 · Operational durability and scale</th><td>Sprint disposition</td><td>Relevant recovery only; no scale campaign.</td><td>S007 new typed cold restoration remains pending. Keep broader durability and scale outcomes incomplete.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-16 · Sidecat UI</th><td>Existing implementation or use</td><td>Installed task/progress/Note views and bounded observations exist.</td><td>S006 exercised the matched operator viewport against the complete 876-character original and return. S007 task UI component tests pass; the accepted cache UI is separately built/staged.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-16 · Sidecat UI</th><td>Missing qualification or material gap</td><td>Own-identity room participation and integrated human decisions/return remain incomplete.</td><td>Human own-identity participation and broad UI acceptance remain incomplete. New typed task restore/body trials remain pending; independent QA found the Esc-cancel editor defect and focused tests fail as expected.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr><tr><th scope="row">V1-16 · Sidecat UI</th><td>Sprint disposition</td><td>Rowan delivers a runnable independently tested client for the selected journey.</td><td>Deliver and qualify the corrected task-bound UI with the maintained caller. Cache source/staging and legacy tests do not qualify the new task route.</td><td>s005-capability-maturity; s006-capability-maturity; Team5083; Team5089; Team5092</td></tr></tbody></table><h4>2026-10-08T20:36:34Z · 3 changed cells</h4><table><thead><tr><th>Capability</th><th>Column</th><th>Before</th><th>After</th><th>Evidence</th></tr></thead><tbody><tr><th scope="row">V1-07 · Marketplace and packages</th><td>Missing qualification or material gap</td><td>Eight card topics are not eight qualified product capabilities. Maintained caller-package installation, broad public/internal lifecycle and pending-work replacement remain unqualified.</td><td>Eight card topics are not eight qualified product capabilities. Maintained caller-package installation, broad public/internal lifecycle and pending-work replacement remain unqualified. Source publication currently fails without identifying the missing repository prerequisite, actual setup owner or supported repair/request action (Team5159/5162).</td><td>Team5159; Team5162; work_10e44373ab304615ca9a826265db7d12; plan_126f980f8297707a51c6e63a7b0b9204</td></tr><tr><th scope="row">V1-11 · Controlled execution</th><td>Missing qualification or material gap</td><td>That build path does not qualify general controlled local/remote execution, cancellation, connector effects or actionable unknown outcomes.</td><td>That build path does not qualify general controlled local/remote execution, cancellation, connector effects or actionable unknown outcomes. The protected-material failure required private reconstruction of owner setup; general actionable prerequisite discovery and supported repair/request remain unqualified (Team5159/5162).</td><td>Team5159; Team5162; work_10e44373ab304615ca9a826265db7d12; plan_126f980f8297707a51c6e63a7b0b9204</td></tr><tr><th scope="row">V1-14 · Usable interfaces and integrations</th><td>Missing qualification or material gap</td><td>Installed man page is stale; judge is absent from its index; invalid project plan judge --help succeeds with parent help. search/apropos are absent. Complete searchable manual, unfamiliar task acceptance and tracker synchronization remain unqualified.</td><td>Installed man page is stale; judge is absent from its index; invalid project plan judge --help succeeds with parent help. search/apropos are absent. Complete searchable manual, unfamiliar task acceptance and tracker synchronization remain unqualified. Ordinary task/library preparation and owner-failure results need discoverable missing prerequisites, actual owners and supported next actions; no new top-level command or automatic permission gate is selected (Team5159/5162).</td><td>Team5159; Team5162; work_10e44373ab304615ca9a826265db7d12; plan_126f980f8297707a51c6e63a7b0b9204</td></tr></tbody></table><h4>2026-10-08T20:58:42Z · 15 changed cells</h4><table><thead><tr><th>Capability</th><th>Column</th><th>Before</th><th>After</th><th>Evidence</th></tr></thead><tbody><tr><th scope="row">V1-03 · Records and source references</th><td>Existing implementation or use</td><td>S006 exercised an exact originating Note read through semantic assessment: all 876 characters matched the independent owner read. Named results retain the actual observation and reopen without reseeding.</td><td>S006 exercised an exact 876-character originating Note. S007 now captures distinct originals; an assisted installed CLI participant deliberately selected, read and restored the correct 1,518-character original. Independent readback confirmed the bound task, source, title and full text.</td><td>Team5156; Team5158; Team5163</td></tr><tr><th scope="row">V1-03 · Records and source references</th><td>Missing qualification or material gap</td><td>Full-area qualification remains incomplete. S007&#x27;s distinct-source capture, explicit choice and task-bound reader/restore are still under implementation and testing.</td><td>Full-area qualification remains incomplete. The S007 CLI sample used an existing prepared actor and assistance; both-lot controls, ordinary reconnected MCP/Lisp and production UI participant acceptance remain open.</td><td>Team5156; Team5158; Team5163</td></tr><tr><th scope="row">V1-03 · Records and source references</th><td>Sprint disposition</td><td>S006 finite original-source increment completed at Exercised scope. S007 advances exact source association and ordinary entry; no full V1-03 completion.</td><td>Retain the exercised original-read and restore evidence. Complete the selected S007 ordinary-use controls and remaining surfaces before judgment; no full V1-03 completion.</td><td>Team5156; Team5158; Team5163</td></tr><tr><th scope="row">V1-06 · Lisp and composition</th><td>Existing implementation or use</td><td>S006 exercised retained named values/functions and actual source observation across reopened environments. S005 guidance-use is Qualified within its finite existing-actor boundary.</td><td>S006 retained values and actual source observations reopened without reseeding. The installed S007 retained_result library exposes six exports; ordinary CLI library calls exercised deliberate choice, full original reading and carried restoration. S005 finite guidance remains Qualified.</td><td>Team5158; Team5163</td></tr><tr><th scope="row">V1-06 · Lisp and composition</th><td>Missing qualification or material gap</td><td>General fresh-agent continuation and full Lisp documentation remain incomplete. New S007 capture/caller source has synthetic boundary checks, not installed participant qualification.</td><td>General fresh-agent continuation and full Lisp documentation remain incomplete. The S007 sample needed shipped package guidance and assistance; independent ordinary reconnected MCP/Lisp acceptance remains open.</td><td>Team5158; Team5163</td></tr><tr><th scope="row">V1-06 · Lisp and composition</th><td>Sprint disposition</td><td>Reuse the maintained retained-result package. S007 caller work continues on the reassigned isolated Sol author occurrence.</td><td>Reuse the installed retained-result library for the remaining S007 trials. Preserve the assisted CLI limits and existing S005/S006 evidence.</td><td>Team5158; Team5163</td></tr><tr><th scope="row">V1-07 · Marketplace and packages</th><td>Existing implementation or use</td><td>Maintained helper source a9110345 is published. The installed durable_conversation GUIDE supplies eight capability cards; S005 finite guidance-use is Qualified under its stated sample limits.</td><td>S005 finite guidance-use is Qualified. The S007 caller package is natively installed and locally ready; installed inspection exposes six exports and the exact 13,326-byte GUIDE. One assisted CLI participant used the installed library.</td><td>Team5156; Team5158; Team5162; Team5163; Team5159</td></tr><tr><th scope="row">V1-07 · Marketplace and packages</th><td>Missing qualification or material gap</td><td>Eight card topics are not eight qualified product capabilities. Maintained caller-package installation, broad public/internal lifecycle and pending-work replacement remain unqualified. Source publication currently fails without identifying the missing repository prerequisite, actual setup owner or supported repair/request action (Team5159/5162).</td><td>Broad public/internal package lifecycle and pending-work replacement remain unqualified. Caller source publication is held at a repository setup prerequisite; ordinary failure results do not identify the missing prerequisite, actual setup owner or supported repair/request action. Installed resource readiness does not establish complete marketplace qualification.</td><td>Team5156; Team5158; Team5162; Team5163; Team5159</td></tr><tr><th scope="row">V1-07 · Marketplace and packages</th><td>Sprint disposition</td><td>Use installed guidance and existing delivery mechanisms. New S007 caller/package delivery remains pending; no broad marketplace campaign.</td><td>Continue ordinary use of the ready installed package and resolve the held source-publication prerequisite through its owner. Keep broader lifecycle work separate from S007.</td><td>Team5156; Team5158; Team5162; Team5163; Team5159</td></tr><tr><th scope="row">V1-14 · Usable interfaces and integrations</th><td>Existing implementation or use</td><td>CLI c2f0ab27 is now installed. Live operation search finds appwork.plan.judge; independent audits exercised help availability for 129 leaves. S006 exercised meaningful CLI/temporary MCP/Lisp output.</td><td>Installed CLI c2f0ab27 and operation search remain available. A fresh CLI participant read and restored the correct S007 original with assistance in 16 calls. The help repair has assertion RED, focused GREEN and passing affected/manual checks; delivery remains pending.</td><td>Team5158; Team5161; Team5162; Team5163; Team5159</td></tr><tr><th scope="row">V1-14 · Usable interfaces and integrations</th><td>Missing qualification or material gap</td><td>Installed man page is stale; judge is absent from its index; invalid project plan judge --help succeeds with parent help. search/apropos are absent. Complete searchable manual, unfamiliar task acceptance and tracker synchronization remain unqualified. Ordinary task/library preparation and owner-failure results need discoverable missing prerequisites, actual owners and supported next actions; no new top-level command or automatic permission gate is selected (Team5159/5162).</td><td>Ordinary library-route discovery required assistance. The installed man page remains stale; judge is absent from its index; invalid project plan judge help succeeds with parent help. search/apropos remain absent. Readable task association, updated installed help/manual, unassisted use, reconnected MCP and tracker synchronization remain unqualified. Ordinary task/library preparation and owner-failure results need discoverable missing prerequisites, actual owners and supported next actions; no new top-level command or automatic permission gate is selected (Team5159/5162).</td><td>Team5158; Team5161; Team5162; Team5163; Team5159</td></tr><tr><th scope="row">V1-14 · Usable interfaces and integrations</th><td>Sprint disposition</td><td>Preserve installed presentation improvement. Treat manual parity, help correctness and task discovery as explicit unresolved QA requirements; default MCP reconnect and S007 trials remain separate.</td><td>Complete the remaining ordinary S007 surfaces and controls. Keep help delivery and coherent discovery/recovery improvements on their native corrective backlog; do not infer qualification from help test counts.</td><td>Team5158; Team5161; Team5162; Team5163; Team5159</td></tr><tr><th scope="row">V1-16 · Sidecat UI</th><td>Existing implementation or use</td><td>S006 exercised the matched operator viewport against the complete 876-character original and return. S007 task UI component tests pass; the accepted cache UI is separately built/staged.</td><td>S006 exercised the full 876-character original viewport and return. The corrected S007 UI passes 22 Rust and 16 Go cases. A normal production UI/gateway pair is installed; its dashboard shows eight assigned and eight created rows under the delivery actor.</td><td>Team5156; Team5161; Team5166</td></tr><tr><th scope="row">V1-16 · Sidecat UI</th><td>Missing qualification or material gap</td><td>Human own-identity participation and broad UI acceptance remain incomplete. New typed task restore/body trials remain pending; independent QA found the Esc-cancel editor defect and focused tests fail as expected.</td><td>The installed pantry UI trial is blocked: query/context editors drop the first capital letter, so the displayed context label cannot be entered faithfully and no original is read. Back/Restore returns an ambiguous result. Human own-identity participation and broad UI acceptance remain incomplete.</td><td>Team5156; Team5161; Team5166</td></tr><tr><th scope="row">V1-16 · Sidecat UI</th><td>Sprint disposition</td><td>Deliver and qualify the corrected task-bound UI with the maintained caller. Cache source/staging and legacy tests do not qualify the new task route.</td><td>Repair the observed UI text-entry routing defect and rerun the selected two-lot task, full original, Back and cold reopen. Keep component GREEN and installed delivery separate from participant acceptance; S007 remains unjudged.</td><td>Team5156; Team5161; Team5166</td></tr></tbody></table></details>

### The two selected outcomes

| Capability boundary | Implementation and availability now | Qualification and actual use now | S004 required result |
| --- | --- | --- | --- |
| Human-and-agent team participation | Messaging/Content and a task-linked UI exist; whole-room human participation under Josh's own identity is incomplete. | Agents actually use retained room posts, with excessive preparation. Josh's independent ordinary entry/read/reply/return journey is unqualified. | Qualified supported entry under Josh's own identity; bounded conversation, task context, replies and return; real use in sprint coordination. |
| Retained task context and continuation | Caller acquisition/keep/return and Work/Plan/Content exist; integrated meaningful current-task discovery and replacement continuation remain incomplete. | Bounded caller-library return is exercised. Fresh-session completion of genuine unfinished work without a private briefing is unqualified. | Qualified discovery and continuation of a real clarification/correction/review, with retained next result, visible human direction and no routine ID handling; normal team use. |

### Product-area snapshot

| Product capability | Existing implementation or use | Missing qualification or material gap | Sprint disposition |
| --- | --- | --- | --- |
| Organizational context | Guidance, named references, roles and selected working context are used. | Fresh workers still need manual orientation; effective scoped semantic inheritance is not established. | Improve the context needed for task continuation. |
| Identity, authority and resources | Prepared actors, access decisions and bounded resource observations exist. | Josh's own usable participation; reachable scoped workers; full remote allowance/delegation outcome remains incomplete. | Cedar owns selected identity/access and execution prerequisites. |
| Records and source references | Exact Notes are reused by messages and Work; authorized team reads are exercised. | Reader-grant plumbing is exposed and has caused denied contribution reads; full area qualification incomplete. | Make the two selected journeys share content correctly. |
| Work and planning | Work definitions, assigned Plan occurrences, board selection and terminal judgments are in ordinary lead use. | Current task discovery remains cumbersome; native project and application planning views are not yet one usable path. | Real continuation is selected; no competing planning ledger. |
| Collective messaging | Real room messages, shared content and bounded reads are used. | Human entry, ordinary reply/thread/attention/return experience incomplete. | Human-and-agent team participation selected. |
| Lisp and composition | Bounded caller package acquisition, keep/reopen and return were accepted in S003. | Broader fresh-agent task continuation and interface usability incomplete. | Reuse the accepted slice in the continuation outcome. |
| Marketplace and packages | Exact caller package delivery provides bounded exercised evidence. | Complete ordinary public/internal lifecycle and pending-work replacement not qualified. | Reuse existing packaging; no broad marketplace campaign. |
| Semantic definitions and discovery | Exact identity and typed contracts exist. | A usable namespaced vocabulary, mappings and domain-record authoring journey is not established. Operation search alone is not a complete source inventory. | Use established shared meanings; keep this release gap explicit. |
| Executable procedures | Bounded composed caller/pantry tasks were accepted. | General durable waits, decisions and continuation across harness replacement not qualified. | Build only the selected real continuation path. |
| Managed agent work | Four actual external team sessions have responded; Codex native delegation is available. | Role/assignment is not proof of execution readiness. Automatic cross-harness return/context/attribution still incomplete. | Reuse native agent/session mechanisms with retained Sidecat task context. |
| Controlled execution | Existing execution contracts and capped remote build path. | Rowan's named native execution route returned unavailable; broad controlled local/remote outcome incomplete. | Resolve the concrete selected execution dependency. |
| Shared bus and federation | Typed local owner calls operate through the bus. | Full independently administered-node journey and durable gap/recovery behavior remain incomplete. | Existing calls only; no federation expansion. |
| Feedback and improvement | Josh's findings, independent proposals and dispositions are retained. | Closed improvement loops and comparable task cost evidence are incomplete. | Two-sprint QA-review trial with useful-findings and cost measures. |
| Usable interfaces and integrations | CLI/MCP/Lisp and a bounded installed client exist. | Actual help failed readability; unfamiliar task completion and required tracker synchronization not qualified. | Fix entry points/help needed for the two outcomes; wider gaps stay visible. |
| Operational durability and scale | Some bounded restart/return evidence exists. | Full backup/recovery, multi-node concurrency and target-scale evidence not established here. | Relevant recovery only; no scale campaign. |
| Sidecat UI | Installed task/progress/Note views and bounded observations exist. | Own-identity room participation and integrated human decisions/return remain incomplete. | Rowan delivers a runnable independently tested client for the selected journey. |

### Basis and limits

This table is a present assessment of evidence, not sixteen newly executed test verdicts. Source existence is not deployment, ordinary use is not full qualification, and lack of current proof is not a declaration that historical work never existed. Optional Jev work has retained source/evaluation history, but no current deployed route was verified; MiniMax activation is not selected.

---

Definitions recovered from architecture/system.md; architecture/specifications/product-area-maturity-backlog-and-sprint-planning.md; architecture/specifications/progressive-interface-documentation-and-maturity.md. The accepted version-1-contract supplies the sixteen product boundaries. Native S003 closeout and S004 selection retain the evidence and decisions. Historical subsystem grades are not copied as current node grades.

## Projection sources

The shared brief is `next-scrum-brief`, recorded 7 October 2026 at 18:38:50 UTC. The maturity baseline is `s004-capability-maturity`, recorded at 18:38:52 UTC. Both are native Sidecat organization reference statements. The projection retains their content and normalizes heading depth and spacing for readability.

[Source metadata and exact native content digests](/s004-sources.json) · [Current progress snapshot](/rearchitecture-status.json)
