# S2_00 hybrid handoff v2 implementation plan

## Purpose

Revise the S2_00 specification, asset ledger, executable Agent YAML, and deployed S2_00 assets so that C15 hands S2_10 structured legal context and opaque Agent/binding digests instead of materialized P00/P10 prompt bytes or downstream model settings. Preserve the existing deterministic ingress, conservation, clustering, DAG, slice, atomic-publish, and direct MCP Code Executor architecture.

## Scope

- Create `YAML_Prompts/2. Stage_2/S2_00_SOW_v.2.md`.
- Create `YAML_Prompts/2. Stage_2/S2_00_assets_v.2.md`.
- Create `YAML_Prompts/2. Stage_2/Stage_2_S2_00_v.2.yml`.
- Update affected deployment assets under `YAML_Prompts/2. Stage_2/Default_Agent/Stage_2_Clean/` and preserve `.py`/`.txt` byte parity.
- Append a concise completion record to `YAML_Prompts/2. Stage_2/MEMORY.md`.
- Do not depend on Stage 2 v0-v3 YAML specifications.

## Contract decisions

- S2_00 remains one deterministic `code-executor.run_code` task with full inline Python and direct localdocs MCP calls.
- C00, C05, C10, Stage 1 conservation, cluster DAG, cluster slices, output root, and atomic publication semantics remain unchanged.
- C15 no longer materializes or hashes P00/P10 prompt bytes and no longer owns S2_10 model/effort/verbosity.
- Each bundle cohort carries release-sealed `s2_10_agent_sha256`, `s2_10_llm_binding_sha256`, ordered selected-context refs/hash, cluster-slice refs/hash, cohort membership, and an embedded closed `context_materialization_receipt`.
- Deprecated `static_prefix_refs`, `expected_prefix_sha256`, materialized static-prefix fields, and downstream model settings are removed from the new schema version rather than silently coexisting.
- Offline/static verification, downstream S2_10 hybrid admission, live adapter/model execution, and legal sign-off remain distinct statuses.

## Work breakdown and dependencies

1. Inspect the current SOW/assets/YAML and deployed runtime/schema/workflow/cache/binding/fixtures/manifests/builders/tests.
2. Produce SOW v2 and assets v2 from the v5-1 contract; independently review each once and apply one correction pass.
3. Implement the new bundle-plan contract in the authoring YAML and affected deployment assets. Independent schema/workflow/policy/test edits may proceed in parallel; generated runtime mirrors and receipts follow the authoring YAML; release manifests are resealed last.
4. Review every changed logical asset once in maximally parallel waves, then apply one correction pass.
5. Run YAML/JSON parsing, Python compile, `.py`/`.txt` parity, projection checks, targeted S2_00 tests, full S2_00 offline validation, stale-field scans, hash/receipt consistency checks, and `git diff --check`.
6. Update project MEMORY with exact artifact paths, decisions, test evidence, and remaining live/downstream admission boundary.

## Validation acceptance criteria

- New authoring and deployment Agent YAML parse and contain exactly one deterministic Code Executor task with no LLM task.
- Inline Python equals deployed `runtime/s2_00_ingress.py` and `.txt` mirror byte-for-byte.
- New bundle-plan schema and runtime agree on all required and forbidden fields.
- S2_00 tests cover hybrid handoff success and reject legacy static-prefix/model-owner fields.
- Builders/receipts/manifests contain current hashes after all edits.
- No affected S2_00 artifact references Stage 2 v0-v3 YAML.
- Results are reported as offline/static only unless live evidence actually exists.

## Progress

- [x] Read root rules, Stage 2 MEMORY, local YAML skill, Python workflow guidance, and MCP Code Executor notebook.
- [x] Identify the v5-1 hybrid handoff contract and current legacy C15 fields.
- [x] Draft and review SOW v2.
- [x] Draft and review assets v2.
- [x] Implement and review authoring YAML v2.
- [x] Update and review deployed assets.
- [x] Reseal hashes/manifests and run validation.
- [x] Append project MEMORY and hand off results.

## Discoveries and decision log

- The worktree contains unrelated user edits and untracked files. Preserve them and scope all changes to the requested S2_00 v2 package plus this plan and MEMORY.
- Existing S2_10 deployment artifacts are a separate workstream. S2_00 v2 may implement the hybrid handoff contract, but live/downstream admission must remain pending until a matching S2_10 hybrid release is built and sealed.