yaaw-se 0.3.7 → 0.3.8

package/dist/payload/yaaw-core/system/registries/handoff-policy.json

@@ -2,84 +2,66 @@
   "schema": "yaaw.handoff-policy/v1",
   "workflows": {
     "prd.route": {
-      "desired_intent": "CONTINUE_PRODUCT",
-      "active_artifact": "product",
-      "reads": ["product", "state"],
-      "writes": ["product"],
-      "required_expertise": [],
-      "ticket_expertise": false,
+      "desired_intent": "CONTINUE_PRODUCT", "active_artifact": "product",
+      "reads": ["product","state"], "writes": ["product"], "required_expertise": [], "ticket_expertise": false,
       "expected_output": "Current product intent or an explicit human-input/blocker result.",
-      "result_vocabulary": ["READY", "HUMAN_INPUT_REQUIRED", "BLOCKED"]
+      "result_vocabulary": ["READY","HUMAN_INPUT_REQUIRED","BLOCKED"]
     },
     "planning.route": {
-      "desired_intent": "CONTINUE_PLANNING",
-      "active_artifact": "engineering",
-      "reads": ["product", "engineering", "engineering_research", "spec", "ticket", "project_rule", "repository"],
-      "writes": ["engineering", "engineering_research", "spec", "ticket", "project_rule"],
-      "required_expertise": [],
-      "ticket_expertise": false,
+      "desired_intent": "CONTINUE_PLANNING", "active_artifact": "engineering",
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","state"],
+      "writes": ["engineering","engineering_research","spec","ticket","project_rule"], "required_expertise": [], "ticket_expertise": false,
       "expected_output": "Current engineering frontier readiness or one typed planning stop/result.",
-      "result_vocabulary": ["READY", "HUMAN_INPUT_REQUIRED", "REPLAN", "BLOCKED"]
+      "result_vocabulary": ["READY","HUMAN_INPUT_REQUIRED","REPLAN","BLOCKED"]
     },
     "planning.create-spec": {
-      "desired_intent": "CREATE_SPEC",
-      "active_artifact": "engineering",
-      "reads": ["product", "engineering", "engineering_research", "project_rule", "repository"],
-      "writes": ["spec"],
-      "required_expertise": [],
-      "ticket_expertise": false,
+      "desired_intent": "CREATE_SPEC", "active_artifact": "engineering",
+      "reads": ["product","engineering","engineering_research","project_rule","repository","state"], "writes": ["spec"],
+      "required_expertise": [], "ticket_expertise": false,
       "expected_output": "One accepted specification for the current frontier or a typed prerequisite/stop result.",
-      "result_vocabulary": ["SUCCESS", "PRECONDITION_UNSATISFIED", "BLOCKED"]
+      "result_vocabulary": ["SUCCESS","PRECONDITION_UNSATISFIED","BLOCKED"]
     },
     "planning.create-tickets": {
-      "desired_intent": "CREATE_TICKETS",
-      "active_artifact": "spec",
-      "reads": ["product", "engineering", "engineering_research", "spec", "project_rule", "repository"],
-      "writes": ["ticket"],
-      "required_expertise": [],
-      "ticket_expertise": false,
+      "desired_intent": "CREATE_TICKETS", "active_artifact": "spec",
+      "reads": ["product","engineering","engineering_research","spec","project_rule","repository","state"], "writes": ["ticket"],
+      "required_expertise": [], "ticket_expertise": false,
       "expected_output": "Dependency-aware executable tickets for the accepted specification or a typed prerequisite/stop result.",
-      "result_vocabulary": ["SUCCESS", "PRECONDITION_UNSATISFIED", "BLOCKED"]
+      "result_vocabulary": ["SUCCESS","PRECONDITION_UNSATISFIED","BLOCKED"]
     },
     "planning.replan": {
-      "desired_intent": "REPLAN",
-      "active_artifact": "ticket",
-      "reads": ["product", "engineering", "engineering_research", "spec", "ticket", "project_rule", "repository"],
-      "writes": ["engineering", "engineering_research", "spec", "ticket", "project_rule"],
-      "required_expertise": [],
-      "ticket_expertise": true,
+      "desired_intent": "REPLAN", "active_artifact": "ticket",
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","state"],
+      "writes": ["engineering","engineering_research","spec","ticket","project_rule"], "required_expertise": [], "ticket_expertise": true,
       "expected_output": "Updated engineering contract and downstream admission state for the invalidated work.",
-      "result_vocabulary": ["READY", "HUMAN_INPUT_REQUIRED", "BLOCKED"]
+      "result_vocabulary": ["READY","HUMAN_INPUT_REQUIRED","BLOCKED"]
     },
     "implementation.implement-ticket": {
-      "desired_intent": "IMPLEMENT",
-      "active_artifact": "ticket",
-      "reads": ["product", "engineering", "engineering_research", "spec", "ticket", "project_rule", "repository", "evidence", "review", "application_files"],
-      "writes": ["application_files", "evidence"],
-      "required_expertise": ["changeability"],
-      "ticket_expertise": true,
-      "expected_output": "Bounded implementation plus verification evidence and one legal lifecycle result.",
-      "result_vocabulary": ["REVIEW_REQUIRED", "REPLAN_REQUIRED", "PRECONDITION_UNSATISFIED", "BLOCKED"]
+      "desired_intent": "IMPLEMENT", "active_artifact": "ticket",
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","evidence","review","application_files","state"],
+      "writes": ["application_files","evidence"], "required_expertise": ["changeability"], "ticket_expertise": true,
+      "expected_output": "Implementation-start evidence before mutation, bounded implementation, and verification evidence or a typed stop.",
+      "result_vocabulary": ["VERIFICATION_PASS","VERIFICATION_FAIL","REPLAN_REQUIRED","PRECONDITION_UNSATISFIED","BLOCKED"]
+    },
+    "implementation.verify-ticket": {
+      "desired_intent": "IMPLEMENT", "active_artifact": "ticket",
+      "reads": ["product","engineering","spec","ticket","project_rule","repository","evidence","application_files","state"],
+      "writes": ["evidence"], "required_expertise": ["changeability"], "ticket_expertise": true,
+      "expected_output": "One immutable v3 implementation_verification evidence record.",
+      "result_vocabulary": ["VERIFICATION_PASS","VERIFICATION_FAIL","IMPLEMENTATION_INCOMPLETE","REPLAN_REQUIRED","BLOCKED"]
     },
     "implementation.repair-ticket": {
-      "desired_intent": "REPAIR",
-      "active_artifact": "ticket",
-      "reads": ["product", "engineering", "engineering_research", "spec", "ticket", "project_rule", "repository", "evidence", "review", "application_files"],
-      "writes": ["application_files", "evidence"],
-      "required_expertise": ["changeability"],
-      "ticket_expertise": true,
-      "expected_output": "Bounded repair plus fresh verification evidence and one legal lifecycle result.",
-      "result_vocabulary": ["REVIEW_REQUIRED", "REPLAN_REQUIRED", "BLOCKED"]
+      "desired_intent": "REPAIR", "active_artifact": "ticket",
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","evidence","review","application_files","state"],
+      "writes": ["application_files","evidence"], "required_expertise": ["changeability"], "ticket_expertise": true,
+      "expected_output": "Bounded repair plus fresh verification evidence and one legal typed result.",
+      "result_vocabulary": ["VERIFICATION_PASS","VERIFICATION_FAIL","REPLAN_REQUIRED","BLOCKED"]
     },
     "review.review-ticket": {
-      "desired_intent": "REVIEW",
-      "active_artifact": "ticket",
-      "reads": ["product", "engineering", "engineering_research", "spec", "ticket", "project_rule", "repository", "evidence", "review", "application_files", "state"],
-      "writes": ["review"],
-      "required_expertise": ["testing", "changeability"],
-      "ticket_expertise": true,
-      "expected_output": "One immutable independent review round tied to the current contract and repository basis.",
-      "result_vocabulary": ["PASS", "REPAIR", "REPLAN", "BLOCKED"]
+      "desired_intent": "REVIEW", "active_artifact": "ticket",
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","evidence","review","application_files","state"],
+      "writes": ["review"], "required_expertise": ["testing","changeability"], "ticket_expertise": true,
+      "expected_output": "One immutable independent review round tied to the current contract, PASS verification, and repository basis.",
+      "result_vocabulary": ["PASS","REPAIR","REPLAN","BLOCKED"]
     }
   }
 }

package/dist/payload/yaaw-core/system/registries/reconciliation-policy.json

@@ -0,0 +1,17 @@
+{
+  "schema": "yaaw.reconciliation-policy/v1",
+  "priority": [
+    {"id": "PROJECT_STATE_SCHEMA_MIGRATION_REQUIRED", "priority": 1},
+    {"id": "PRODUCT_LEDGER_SYNC", "priority": 2},
+    {"id": "PLANNING_LEDGER_SYNC", "priority": 3},
+    {"id": "ACTIVE_SPEC_UNADOPTED", "priority": 4},
+    {"id": "TICKET_UNREGISTERED", "priority": 5},
+    {"id": "CONTRACT_SOURCE_STALE", "priority": 6},
+    {"id": "IMPLEMENTATION_STARTED", "priority": 7},
+    {"id": "IMPLEMENTATION_VERIFIED", "priority": 8},
+    {"id": "REVIEW_RESULT_UNAPPLIED", "priority": 9},
+    {"id": "ACCEPTANCE_STALE", "priority": 10},
+    {"id": "PROJECT_COMPLETION_SYNC", "priority": 11}
+  ],
+  "one_reconciliation_per_cycle": true
+}

package/dist/payload/yaaw-core/system/registries/role-io.json

@@ -2,158 +2,29 @@
   "schema": "yaaw.role-io/v1",
   "roles": {
     "prd": {
-      "reads": [
-        "product",
-        "state"
-      ],
-      "writes": [
-        "product"
-      ],
-      "forbidden_writes": [
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "application_files",
-        "evidence",
-        "review",
-        "observed_state",
-        "handoff",
-        "state",
-        "installation_manifest",
-        "dispatch_failures"
-      ]
+      "reads": ["product","state"],
+      "writes": ["product"],
+      "forbidden_writes": ["engineering","engineering_research","spec","ticket","application_files","evidence","review","observed_state","handoff","state","installation_manifest","dispatch_failures"]
     },
     "planner": {
-      "reads": [
-        "product",
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "project_rule",
-        "repository"
-      ],
-      "writes": [
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "project_rule"
-      ],
-      "forbidden_writes": [
-        "product",
-        "application_files",
-        "evidence",
-        "review",
-        "observed_state",
-        "handoff",
-        "state",
-        "installation_manifest",
-        "dispatch_failures"
-      ]
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","state"],
+      "writes": ["engineering","engineering_research","spec","ticket","project_rule"],
+      "forbidden_writes": ["product","application_files","evidence","review","observed_state","handoff","state","installation_manifest","dispatch_failures"]
     },
     "implementer": {
-      "reads": [
-        "product",
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "project_rule",
-        "repository",
-        "evidence",
-        "review",
-        "application_files"
-      ],
-      "writes": [
-        "application_files",
-        "evidence"
-      ],
-      "forbidden_writes": [
-        "product",
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "project_rule",
-        "review",
-        "observed_state",
-        "handoff",
-        "state",
-        "installation_manifest",
-        "dispatch_failures"
-      ]
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","evidence","review","application_files","state"],
+      "writes": ["application_files","evidence"],
+      "forbidden_writes": ["product","engineering","engineering_research","spec","ticket","project_rule","review","observed_state","handoff","state","installation_manifest","dispatch_failures"]
     },
     "reviewer": {
-      "reads": [
-        "product",
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "project_rule",
-        "repository",
-        "evidence",
-        "review",
-        "application_files",
-        "state"
-      ],
-      "writes": [
-        "review"
-      ],
-      "forbidden_writes": [
-        "product",
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "project_rule",
-        "application_files",
-        "evidence",
-        "observed_state",
-        "handoff",
-        "state",
-        "installation_manifest",
-        "dispatch_failures"
-      ]
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","evidence","review","application_files","state"],
+      "writes": ["review"],
+      "forbidden_writes": ["product","engineering","engineering_research","spec","ticket","project_rule","application_files","evidence","observed_state","handoff","state","installation_manifest","dispatch_failures"]
     },
     "orchestrator": {
-      "reads": [
-        "product",
-        "engineering",
-        "engineering_research",
-        "spec",
-        "ticket",
-        "project_rule",
-        "repository",
-        "evidence",
-        "review",
-        "state",
-        "observed_state",
-        "handoff",
-        "intent",
-        "installation_manifest",
-        "dispatch_failures"
-      ],
-      "writes": [
-        "state",
-        "observed_state",
-        "handoff",
-        "intent",
-        "dispatch_failures"
-      ],
-      "forbidden_writes": [
-        "product",
-        "engineering",
-        "engineering_research",
-        "spec",
-        "project_rule",
-        "application_files",
-        "evidence",
-        "review",
-        "installation_manifest"
-      ]
+      "reads": ["product","engineering","engineering_research","spec","ticket","project_rule","repository","evidence","review","state","observed_state","handoff","intent","installation_manifest","dispatch_failures"],
+      "writes": ["state","observed_state","handoff","intent","dispatch_failures"],
+      "forbidden_writes": ["product","engineering","engineering_research","spec","project_rule","application_files","evidence","review","installation_manifest"]
     }
   }
 }

package/dist/payload/yaaw-core/system/registries/skills.json

@@ -1,14 +1,110 @@
 {
-  "yaaw-orchestrator": {"role": "orchestrator", "workflow_id": "orchestration.route", "description": "Continue or recover a YAAW project by reconstructing reality and dispatching the next safe workflow."},
-  "yaaw-prd": {"role": "prd", "workflow_id": "prd.route", "description": "Create or continue YAAW product definition, challenge material product assumptions, and route clarification or revision work."},
-  "yaaw-revise-prd": {"role": "prd", "workflow_id": "prd.revise", "description": "Change accepted YAAW product intent and invalidate downstream engineering contracts whose basis became stale."},
-  "yaaw-refine-prd": {"role": "prd", "workflow_id": "prd.refine", "description": "Improve clarity and completeness of a YAAW product artifact without changing accepted product meaning."},
-  "yaaw-planner": {"role": "planner", "workflow_id": "planning.route", "description": "Continue repository-backed YAAW engineering planning, challenge material technical assumptions, and advance decisions, readiness, specifications, or tickets."},
-  "yaaw-planning-review": {"role": "planner", "workflow_id": "planning.readiness-review", "description": "Freshly assess whether the current YAAW engineering frontier is ready for implementation without material invention."},
-  "yaaw-create-spec": {"role": "planner", "workflow_id": "planning.create-spec", "description": "Create the next YAAW specification from an engineering frontier whose readiness is currently PASS."},
-  "yaaw-create-ticket": {"role": "planner", "workflow_id": "planning.create-tickets", "description": "Create bounded YAAW implementation ticket contracts from the current accepted specification."},
-  "yaaw-create-tickets": {"role": "planner", "workflow_id": "planning.create-tickets", "description": "Create dependency-aware bounded YAAW implementation tickets from the current accepted specification."},
-  "yaaw-implement": {"role": "implementer", "workflow_id": "implementation.implement-ticket", "description": "Implement one admitted READY YAAW ticket and produce repository-identity-bound verification evidence."},
-  "yaaw-repair": {"role": "implementer", "workflow_id": "implementation.repair-ticket", "description": "Repair a YAAW ticket in REPAIR_REQUIRED state while preserving its accepted product and engineering contract."},
-  "yaaw-review": {"role": "reviewer", "workflow_id": "review.review-ticket", "description": "Independently review actual YAAW implementation and classify PASS, REPAIR, REPLAN, or BLOCKED against current evidence."}
+  "yaaw-orchestrator": {
+    "role": "orchestrator",
+    "workflow_id": "orchestration.route",
+    "destination_role": "orchestrator",
+    "requested_workflow": "orchestration.route",
+    "desired_outcome": "CONTINUE",
+    "completion_kind": "CONTINUE_UNTIL_STOP",
+    "description": "Continue or recover a YAAW project by reconstructing reality and dispatching the next safe workflow."
+  },
+  "yaaw-prd": {
+    "role": "prd",
+    "workflow_id": "prd.route",
+    "destination_role": "prd",
+    "requested_workflow": "prd.route",
+    "desired_outcome": "CONTINUE_PRODUCT",
+    "completion_kind": "PRODUCT_READY",
+    "description": "Create or continue YAAW product definition, challenge material product assumptions, and route clarification or revision work."
+  },
+  "yaaw-revise-prd": {
+    "role": "prd",
+    "workflow_id": "prd.revise",
+    "destination_role": "prd",
+    "requested_workflow": "prd.revise",
+    "desired_outcome": "REVISE_PRODUCT",
+    "completion_kind": "PRODUCT_REVISION_ADVANCED",
+    "description": "Change accepted YAAW product intent and invalidate downstream engineering contracts whose basis became stale."
+  },
+  "yaaw-refine-prd": {
+    "role": "prd",
+    "workflow_id": "prd.refine",
+    "destination_role": "prd",
+    "requested_workflow": "prd.refine",
+    "desired_outcome": "REFINE_PRODUCT",
+    "completion_kind": "PRODUCT_REFINED",
+    "description": "Improve clarity and completeness of a YAAW product artifact without changing accepted product meaning."
+  },
+  "yaaw-planner": {
+    "role": "planner",
+    "workflow_id": "planning.route",
+    "destination_role": "planner",
+    "requested_workflow": "planning.route",
+    "desired_outcome": "CONTINUE_PLANNING",
+    "completion_kind": "PLANNING_READY",
+    "description": "Continue repository-backed YAAW engineering planning, challenge material technical assumptions, and advance decisions, readiness, specifications, or tickets."
+  },
+  "yaaw-planning-review": {
+    "role": "planner",
+    "workflow_id": "planning.readiness-review",
+    "destination_role": "planner",
+    "requested_workflow": "planning.readiness-review",
+    "desired_outcome": "PLANNING_REVIEW",
+    "completion_kind": "PLANNING_READINESS_DECIDED",
+    "description": "Freshly assess whether the current YAAW engineering frontier is ready for implementation without material invention."
+  },
+  "yaaw-create-spec": {
+    "role": "planner",
+    "workflow_id": "planning.create-spec",
+    "destination_role": "planner",
+    "requested_workflow": "planning.create-spec",
+    "desired_outcome": "CREATE_SPEC",
+    "completion_kind": "CURRENT_SPEC_ACCEPTED",
+    "description": "Create the next YAAW specification from an engineering frontier whose readiness is currently PASS."
+  },
+  "yaaw-create-ticket": {
+    "role": "planner",
+    "workflow_id": "planning.create-tickets",
+    "destination_role": "planner",
+    "requested_workflow": "planning.create-tickets",
+    "desired_outcome": "CREATE_TICKETS",
+    "completion_kind": "CURRENT_TICKETS_REGISTERED",
+    "description": "Create bounded YAAW implementation ticket contracts from the current accepted specification."
+  },
+  "yaaw-create-tickets": {
+    "role": "planner",
+    "workflow_id": "planning.create-tickets",
+    "destination_role": "planner",
+    "requested_workflow": "planning.create-tickets",
+    "desired_outcome": "CREATE_TICKETS",
+    "completion_kind": "CURRENT_TICKETS_REGISTERED",
+    "description": "Create dependency-aware bounded YAAW implementation tickets from the current accepted specification."
+  },
+  "yaaw-implement": {
+    "role": "implementer",
+    "workflow_id": "implementation.implement-ticket",
+    "destination_role": "implementer",
+    "requested_workflow": "implementation.implement-ticket",
+    "desired_outcome": "IMPLEMENT",
+    "completion_kind": "TICKET_REVIEW_REQUIRED",
+    "description": "Implement one admitted READY YAAW ticket and produce repository-identity-bound verification evidence."
+  },
+  "yaaw-repair": {
+    "role": "implementer",
+    "workflow_id": "implementation.repair-ticket",
+    "destination_role": "implementer",
+    "requested_workflow": "implementation.repair-ticket",
+    "desired_outcome": "REPAIR",
+    "completion_kind": "TICKET_REVIEW_REQUIRED",
+    "description": "Repair a YAAW ticket in REPAIR_REQUIRED state while preserving its accepted product and engineering contract."
+  },
+  "yaaw-review": {
+    "role": "reviewer",
+    "workflow_id": "review.review-ticket",
+    "destination_role": "reviewer",
+    "requested_workflow": "review.review-ticket",
+    "desired_outcome": "REVIEW",
+    "completion_kind": "TICKET_REVIEW_APPLIED",
+    "description": "Independently review actual YAAW implementation and classify PASS, REPAIR, REPLAN, or BLOCKED against current evidence."
+  }
 }

package/dist/payload/yaaw-core/system/roles/implementer.md

@@ -1,20 +1,17 @@
 # Implementer role
 
 ## Authority
-Own code changes for one bounded admitted ticket at a time.
+Own application changes and implementation evidence for one bounded admitted ticket at a time.
 
 ## Required behavior
-- Require a valid exact handoff and repository requirement `IDENTITY`; repository status must be `READY`.
-- Validate the ticket/source revisions before starting.
-- Load only handoff-authorized product/spec/engineering/research constraints, `.yaaw-core/system/rules/changeability.md`, relevant .yaaw-core/system/rules/expertise, and relevant code.
-- Transition `READY -> IN_PROGRESS` with provenance.
-- Implement within allowed scope, applying the relevant changeability principles without introducing style-only or unrelated refactors.
-- Run required verification and write machine-readable evidence tied to repository identity.
-- Transition to `REVIEW_REQUIRED` only after evidence exists.
-- If no READY ticket exists, return `PRECONDITION_UNSATISFIED:NO_READY_TICKET` to Orchestrator. Do not create a ticket or command Planner.
+- Require an exact handoff, repository requirement `IDENTITY`, repository status `READY`, reconciled state read access, and current source revisions.
+- Before the first application mutation, write immutable `yaaw.evidence/v3` `implementation_start` evidence with result `STARTED` and the pre-edit repository identity.
+- Then implement only the admitted scope and apply relevant changeability rules.
+- Run required verification and write a new immutable v3 `implementation_verification` record with explicit `PASS`, `FAIL`, or `BLOCKED`.
+- Never rewrite failed evidence as success.
+- Never write `state.json`. Orchestrator adopts valid start/verification facts through legal transitions.
+- If no READY ticket exists, return `PRECONDITION_UNSATISFIED:NO_READY_TICKET`; do not create tickets or command Planner.
+- Missing material decisions route back to Planner through Orchestrator.
 
 ## Boundary
-Never self-approve, silently change product/architecture contracts, or implement a `REPLAN_REQUIRED`/stale ticket. Missing material decisions route back to Planner through Orchestrator. Changeability guidance improves the authorized change; it never expands ticket scope.
-
-## Framework boundary
-Package-managed `.yaaw-core/system/**` is never a writable semantic-work surface. If a framework contract is missing, contradictory, or blocks valid work, do not edit YAAW to unblock yourself. Return `FRAMEWORK_INTEGRITY_VIOLATION`, `FRAMEWORK_INTEGRITY_UNKNOWN`, or `FRAMEWORK_CONTRACT_INCONSISTENCY` to Orchestrator with the exact evidence.
+Never self-approve, silently change product/architecture contracts, or implement stale/`REPLAN_REQUIRED` work. A lost context is not permission to restart implementation from scratch.

package/dist/payload/yaaw-core/system/roles/orchestrator.md

@@ -1,25 +1,20 @@
 # Orchestrator role
 
 ## Authority
-Own continuity, evidence-backed reconciliation, invalidation coordination, and next-workflow dispatch. Deterministic workspace/repository reconstruction, routing, and handoff serialization are delegated to the canonical runtime tool rather than improvised by the model.
+Own continuity, evidence-backed reconciliation, invalidation coordination, public-intent continuation, and next-workflow dispatch. Orchestrator is the only physical writer of `.yaaw-core/project/state.json`; durable semantic facts from the owning roles authorize its mutations.
 
 ## Boot sequence
-1. Resolve the YAAW workspace root using `.yaaw-core/system/core/execution-context.md`; never assume provider CWD.
-2. Execute `node .yaaw-core/system/tools/orchestration-runtime.mjs --workspace <WORKSPACE_ROOT>` exactly once for the current basis.
-3. Consume the typed result:
-   - `FRAMEWORK_STOP` -> report the typed framework failure/repair instruction and stop without lifecycle mutation;
-   - `RECONCILE_REQUIRED` -> execute only `orchestration.reconcile-state`, then run the deterministic preparation again;
-   - `ROOT_ACTION` -> execute the selected Orchestrator recovery workflow, then prepare again;
-   - `TERMINAL`/`BLOCKED` -> stop with that result;
-   - `DISPATCH_READY` -> use the persisted handoff exactly as produced.
-4. Do not independently recalculate worktree digests, grep for alternate artifact locations, replay routing precedence, or hand-serialize `observed-state.json`/`handoff.json`.
-5. Dispatch exactly one canonical workflow using `.yaaw-core/system/workflows/orchestration/dispatch.md`. The host adapter resolves the configured authority execution profile; Orchestrator never invents or substitutes provider/model settings.
-6. Permit a change of execution mechanism only through the host adapter and only when the adapter establishes execution-profile equivalence or authoritative per-dimension correction under the configured policy.
-7. After any worker completion, failure, interruption, or lost response, return to deterministic preparation before selecting another semantic workflow. For Implementer/Reviewer execution failures, update or reset the replaceable dispatch-failure ledger only after confirming durable progress and the current handoff basis. A pre-execution host isolation/profile stop never increments that ledger.
-8. Apply any configured host capability fallback only through `orchestration.dispatch`; preserve the exact semantic role/handoff and require the adapter to preserve the configured fallback profile.
-9. Repeat until a real stop condition.
+1. Resolve the workspace root through `.yaaw-core/system/core/execution-context.md`.
+2. For a public skill, invoke `orchestration-runtime.mjs --invoke-skill <skill>`; otherwise prepare with `--workspace <root>`.
+3. Consume exactly one typed result. `RECONCILE_REQUIRED` applies exactly one reconciliation, then observation repeats.
+4. Dispatch exactly one semantic handoff only after framework health, reconciliation, source-current validation, repository policy, and intent prerequisites pass.
+5. After worker success, failure, interruption, or lost response, throw away worker text as authority and observe durable reality again.
+6. Continue until intent completion, human input, typed blocker/framework stop, or project `COMPLETE`.
 
 ## Boundary
-The Orchestrator is a traffic controller, not a super-agent. It may verify and route the execution profile selected by host configuration, but it has no authority to choose arbitrary models or reasoning levels. Framework integrity is an execution precondition, not something Orchestrator may repair by editing YAAW. The Orchestrator never creates, edits, deletes, or weakens package-managed `.yaaw-core/system/**` content in a consumer run. It must not author product decisions, architecture, implementation, research conclusions, or acceptance. Roles never privately delegate to peers; every successor is chosen here.
+The Orchestrator is a traffic controller, not a super-agent. It must not author product decisions, architecture, implementation, research conclusions, or acceptance. Framework integrity is a fail-closed execution precondition. The Orchestrator never creates, edits, deletes, or weakens package-managed `.yaaw-core/system/**` content to unblock work; installer repair is the only supported framework mutation path.
 
-Child/worker text is not project truth. Durable artifacts, repository evidence, accepted reviews, legal state transitions, and deterministic runtime output are authoritative.
+Worker output does not update lifecycle state directly. Workers write durable semantic facts. Orchestrator observes those facts and records only legal lifecycle changes.
+
+## Execution-profile boundary
+The Orchestrator routes the execution profile selected by the host adapter but never invents or substitutes provider/model settings. It has no authority to choose arbitrary models or reasoning levels.

package/dist/payload/yaaw-core/system/roles/planner.md

@@ -1,25 +1,16 @@
 # Planner role
 
 ## Authority
-Own engineering understanding, architecture decisions, external engineering research, specifications, readiness, decomposition, and ticket contracts within accepted product intent.
+Own engineering understanding, architecture decisions, admitted engineering research, specifications, ticket contracts, readiness, frontier decomposition, and the durable `scope_status` judgment within accepted product intent.
 
 ## Required behavior
-- Resolve workspace/repository context before repository discovery; repository commands are root-anchored through `.yaaw-core/system/core/execution-context.md`.
-- Establish repository evidence before questioning; inspect real repository reality rather than asking the human for discoverable facts.
-- Apply `.yaaw-core/system/rules/assumption-challenge.md` to engineering interpretation, architecture decisions, and current-frontier questions.
-- Challenge material engineering assumptions, repository/architecture contradictions, unnecessary abstractions, and consequential failure/data/security/migration/testing/operability tradeoffs.
-- Resolve routine reversible implementation decisions internally unless they become materially consequential.
-- Maintain `engineering.md` and durable `ENG-*` decisions with provenance.
-- Make `planning.decision-frontier` the canonical partition of known decisions, current frontier, product gaps, blocking research, and future fog.
-- Apply `.yaaw-core/system/rules/research-admission.md` before web/vendor research or host expertise. An installed host skill is never architectural evidence by itself.
-- Persist material blocking research as `RSH-*`; research findings do not automatically become `ENG-*` decisions.
-- Apply `.yaaw-core/system/rules/changeability.md` when shaping engineering decisions, specifications, and ticket boundaries.
-- Create specs/tickets only after frontier readiness passes.
-- Replan explicitly when later evidence invalidates a contract; preserve superseded history.
-- Never reopen settled `ENG-*` decisions without new evidence or explicit request.
+- Read the reconciled project state when lifecycle status affects planning; never write it.
+- Establish repository evidence before questioning and apply `.yaaw-core/system/rules/assumption-challenge.md` to engineering assumptions.
+- Maintain `engineering.md`, durable `ENG-*` decisions, current frontier, readiness, and `scope_status: UNKNOWN | OPEN | COMPLETE`.
+- Set `COMPLETE` only when durable product/planning evidence proves no accepted product scope remains after the current frontier; otherwise use `OPEN` or `UNKNOWN`.
+- Apply research admission and changeability rules; create specs/tickets only after readiness passes.
+- Replan explicitly when later evidence invalidates a contract, preserving superseded history.
+- Resolve routine reversible implementation decisions internally unless materially consequential.
 
 ## Boundary
-Never invent product intent. Product gaps return to PRD/human authority. Planner does not accept implementation on behalf of Reviewer. Research, host expertise, changeability, and assumption-challenge guidance never authorize speculative architecture, scope creep, or unrelated refactoring.
-
-## Framework boundary
-Package-managed `.yaaw-core/system/**` is never a writable semantic-work surface. If a framework contract is missing, contradictory, or blocks valid work, do not edit YAAW to unblock yourself. Return `FRAMEWORK_INTEGRITY_VIOLATION`, `FRAMEWORK_INTEGRITY_UNKNOWN`, or `FRAMEWORK_CONTRACT_INCONSISTENCY` to Orchestrator with the exact evidence.
+Never invent product intent. Product gaps return to PRD/human authority. Planner does not accept implementation on behalf of Reviewer and never writes `state.json`.

package/dist/payload/yaaw-core/system/roles/reviewer.md

@@ -4,22 +4,17 @@
 Own independent acceptance judgment and `PASS`, `REPAIR`, `REPLAN`, or `BLOCKED` classification.
 
 ## Required behavior
-- Require repository requirement `IDENTITY` and repository status `READY`.
-- Use a fresh context when practical.
-- Inspect actual repository state, not the Implementer's summary.
-- Validate current ticket/spec/product revisions and verification evidence.
-- Apply `.yaaw-core/system/rules/changeability.md` to the changed surface and distinguish concrete maintainability defects from personal style preferences.
-- Tie the review to exact repository identity and source revisions.
-- Record immutable review rounds and concrete findings.
-- Report the result to Orchestrator; Reviewer never privately commands Implementer or Planner.
+- Require repository `IDENTITY`, repository status `READY`, reconciled state read access, current source revisions, and current v3 PASS verification evidence.
+- Inspect actual repository state rather than Implementer summaries.
+- Tie the immutable review round to exact ticket/spec revisions, repository identity, and the PASS verification evidence ID.
+- Apply changeability rules to concrete engineering impact, not style preference.
+- Write only the immutable review artifact; never write `state.json`.
+- Report the typed result to Orchestrator, which validates and adopts it.
 
 ## Classification
 - `PASS`: current contract satisfied with adequate fresh evidence.
-- `REPAIR`: implementation is wrong/incomplete, including a bounded changeability defect; contract remains valid.
-- `REPLAN`: contract/architecture is materially invalid or insufficient.
+- `REPAIR`: bounded implementation defect; contract remains valid.
+- `REPLAN`: contract/architecture materially invalid or insufficient.
 - `BLOCKED`: acceptance cannot be determined because required evidence is unavailable.
 
-Reviewer does not author implementation while acting as Reviewer. Style preference alone is never a review failure.
-
-## Framework boundary
-Package-managed `.yaaw-core/system/**` is never a writable semantic-work surface. If a framework contract is missing, contradictory, or blocks valid work, do not edit YAAW to unblock yourself. Return `FRAMEWORK_INTEGRITY_VIOLATION`, `FRAMEWORK_INTEGRITY_UNKNOWN`, or `FRAMEWORK_CONTRACT_INCONSISTENCY` to Orchestrator with the exact evidence.
+Reviewer does not author implementation while acting as Reviewer.