# S005: discover and use existing capabilities

**Selected 7 October 2026 at 22:36 MDT · one guidance/adoption outcome · acceptance pending**

[Current progress](/development/progress.html) · [Work and acceptance](/development/progress-scope.html) · [S004 review and history](/development/progress-history.html#s004)

This plan and the current progress report project one fixed native Sidecat cutoff: 4796, recorded 7 October 2026 at 22:44 MDT. Rowan leads development and selection; Juniper supports reporting and infrastructure. Native Sidecat owns the plan and its changes. Product revision 4 and development revision 3 remain unchanged, and all sixteen full Version 1 outcomes remain incomplete.

## The useful result

An unfamiliar permitted participant can choose an existing Sidecat capability from shipped guidance, complete a legitimate task and return to its context and result without a predecessor’s private command recipe.

The reviewed capability/system cards will be authored once in the existing package GUIDE. Two owning documentation pages point to that source. UI README and help explain the existing Apps route to the whole GUIDE. Eight cards are explanations, not eight new capabilities. S005 qualifies guidance and adoption over existing owners; prior S003 pantry and S004 continuation results are retained rather than scored again.

## Three acceptance checks

1. **Fresh assigned-work task.** An unfamiliar contributor selects a genuine assigned task among multiple actual choices, obtains the full outcome, current progress and discussion, reopens and explains the next useful action at a read-only stopping point. A planned task without a progress update is an honest result. Trials use actual assignments rather than manufactured distractor Plans.
2. **Fresh Records pantry task.** A different unfamiliar participant follows the existing Records pantry guide with fresh lots and instructions. The task covers bounded ordering, allocation and exact, current and stale-base observations. Independent QA verifies actual owner records and readable results.
3. **Actual Apps guide entry.** The existing UI Apps route opens the whole matched GUIDE and returns to installation inventory at 80×24. Reading a guide adopts no code and acts on no task. Source review or an author’s own trial is not the sole installed evidence.

The existing guide route is **k or 5 → Apps → Native installation records → durable_conversation → Enter details → o whole GUIDE**. Return to the installation inventory after reading. This entry explains current UI navigation; matched S005 guidance delivery and independent use remain to be observed.

Fresh worker sessions use legitimate prepared identity and normal task, Note and Records rights. Same-actor fresh workers are disclosed; they do not establish separate identity enrollment or human participation. Supply the shipped entry, intended task and permitted data, with assistance recorded. Capture wrong turns, actual commands and exits, output and the exact useful result. Counts diagnose friction; they are not passing quotas. Unshipped steering or confusing helper output produces partial acceptance and a concrete gap, not a silent expansion of the library.

## Source and owner boundaries

| Work | Owner and scope | Selected source base |
| --- | --- | --- |
| One cards source | Documentation author under Rowan; package GUIDE only | Published packages source `5b32f18b`, tree `07bcb47f` |
| Two documentation pointers | Same author; `docs/repl-first.md` and `docs/application-authoring.md`, with whole-page review | Public development branch `sprint/v1-s002-auth-integrated-20261002` at `d42845eb`, tree `687ee701`; distinct from public main and the installed runtime |
| UI guide directions | UI author under Rowan; README and existing help literals only | Published `39766132`, following behavior source `1439b802` |
| Caller/resource parity | Linden retains package ownership; library bytes, exports, source metadata, derivation and examples unchanged | Team 65,510 bytes and conversation 63,344 bytes on the carried installed candidate |
| Review and delivery | Independent reviewer reads exact whole prose and five author paths; Cedar handles native publication, artifact/install and capped console build | Exact reviewed author snapshots and named branches |
| Independent use and judgment | Aspen chooses the finite charter, unfamiliar trials and useful continuation checks | The actual delivered guidance and matched UI candidate |
| Public projection | Juniper supports factual plan/progress reporting | This fixed native cutoff; reporting does not gate Rowan’s development |

The GUIDE remains one authored source. Pointers do not become maintained copies. Measure the final whole GUIDE against its 65,536-byte resource limit; an expected size is not proof. Package version stays 0.2.0. New GUIDE metadata changes the resource artifact, not already-kept code.

Cedar delivers one exact package artifact/install and at most one serialized console-only build, reusing the accepted gateway and preserving the prior working pair and default launchers. These are selected delivery bounds, not completion estimates. The author/review timeboxes are likewise resource bounds. Current S005 implementation and installed-use results are not established by the selection itself.

## Reuse before new functionality

Reuse `caller-package-read` and consume its complete returned adoption input. Ready resource bytes are distinct from adopted and kept exports. Use `caller-task-read` as the ordinary task reader: its selection is the complete returned choice/input, rather than Team’s title string. Full-text and discussion continuations are carried returned objects, not manually reconstructed identifiers. Already-returned full text is complete; optional progress is separate from the read-only stop.

Keep excerpt versus full, current versus as-observed history, and proposal author versus executing worker visible. References do not grant permissions. Records owns data and invariants; Lisp composes values and owner calls. Choose resident Go ownership only for a real missing invariant or workload need. This selection introduces no router, catalog, library, schema, dispatch path, Records app, semantic engine or compulsory custody/startup procedure. Shape/Jev integration remains unselected.

## S004 disposition and carried work

S004 was reviewed as **not completed** at 22:31 MDT. Its main occurrence received the original-creator-bound `not_completed` judgment and current-owner verification; reusable Work and other owners’ Plans were not universally closed.

Useful S004 slices remain attributed to their actual candidates: corrected caller delivery; one new ordinary send with same-client reopen and exact 2,355-character readback; an independent current-candidate recipient read; the earlier substantive 3,568-character continuation result and its independent readers; and bounded actual UI reads and missing-executable entry/refresh diagnostics.

Unfinished work remains with the original owners. Josh and Cedar retain legitimate human setup and own use. Rowan and Aspen retain denied-page clearing, long diagnostic wrapping/clipping and navigation, failed nonfirst chooser visibility and deliberate reread on the exact UI candidate. Linden, Juniper and Aspen retain complete continuation acceptance. Source regressions and bounded observations do not replace those journeys.

Juniper’s original unknown send retains its original preparation, keys and Note. No reset, replay, replacement, migration, compensating grant or copied-message substitute follows from this disposition or S005 selection. S003 remains closed. All sixteen full Version 1 outcomes remain incomplete.

## Evidence and reporting

The selection credits independent inventory, prose, call-surface, UI, full-release, caller, release and QA input. Subsequent charter and real trial choices belong to independent QA. Manual role/function assignments remain explicit; they do not qualify native managed-agent activation.

Plan and progress share cutoff 4796. Later source returns, delivery receipts and trial results require a later clearly dated projection. Supplemental current Plan/Work reads are labelled separately and do not pretend to be an atomic event-fenced snapshot.

[Exact native selection/disposition source metadata](/s005-sources.json) · [Current snapshot](/rearchitecture-status.json) · [Unchanged earlier S004 snapshot](/development-history/s004-progress.json) · [Retained S004 opening brief](/development/s004.html)