docs: verify bounded workflow adoption planning

openspec/INTEGRATION.md

@@ -4,6 +4,15 @@ This document is the living ownership contract for active SpecFact OpenSpec
 changes. It exists to keep parallel roadmap work aligned without creating a
 separate product feature for integration governance.
 
+## Ordinary workflow ownership
+
+- Paired `workflow-01-turn-orchestration` assigns reusable `specfact workflow` execution, bundled workflow skills, producer adapters and disposable local receipts to modules #483; core #742 owns repository settings, check-only gate adapters, thin wrapper projection and signed adoption/pilot.
+- This unsealed ordinary path does not replace optional preflight/checkpoint/conformance. Seal-bound behavior stays with its existing owners and applies only on explicit assurance selection.
+- R09 owns current-run Requirements claims; its module reconciler remains free of Git/test/network execution. Governance owns durable evidence envelopes, traceability owns artifact semantics, and C15 owns calibrated review policy. A workflow findings projection preserves original producer identities/outcomes and cannot fuse verdicts or silently extend ReviewReport.
+- Standalone verify and ordinary CI require no prior local receipts. Local progress cannot authenticate itself for protected CI. Generic #251/#253 still owns customer installation/export and general generated references; repository wrapper projection is a separate development convenience.
+- Release direction is modules #481 -> workflow modules #483 -> core #742 runtime adoption. Independent projection has no signed-runtime prerequisite. Related optional assurance/graph/findings work is not a blanket blocker.
+- Runtime integration/adoption validates exact signed #481 schema-v3 current_execution and actual core/#483 compatibility before selecting the workflow combination; a signed workflow alone is insufficient. Projection remains independent.
+
 ## Positioning
 
 SpecFact is the local validation and AI-bloat defense CLI. Active changes SHALL

openspec/changes/workflow-01-turn-orchestration/CHANGE_VALIDATION.md

@@ -56,3 +56,60 @@ Publication hooks passed on the actual prepared candidates. Scoped mapping YAML
 Focused repair PR [#756](https://github.com/nold-ai/specfact-cli/pull/756) merged into `dev` as `cb417b5dd5d58fbe9ce50b62cb8a75868caa5ef2` after its current-head required checks and completed reviews passed. The planning branch incorporates that signed baseline through signed merge `cc801ce532d6c88dc0584d97a7bb0eb1a9040bbd`; its diff against `dev` remains this existing workflow change and its ordering entry. Both approved ordering entries are preserved, with separate insertion anchors to avoid their original content conflict. The integrated tree has 41 direct active change folders, so its ordering count is 41. Earlier creation/publication counts above remain bound to their own historical snapshots.
 
 Integration revalidation: strict selected validation passed; strict all-change validation passed 40/41, retaining the same unrelated `governance-01-evidence-output` delta filename failure. The count-only staged inspection reported `no-impact`/`skipped`; it is not proof of broader planned maturity. Native Requirements separately passed for the complete planning diff against the merged `origin/dev` baseline: required/observed `planned`, `proposal-only` delivery, `pass` gate, no findings. Markdown lint and whitespace checks cover the changed planning documents. No behavior, planned runtime, implementation/trial task completion or policy exception is introduced. Hosted current-head required checks, completed review and a fresh member grant bound to the final planning commit/tree remain necessary; the earlier grant for `29637d9d` does not cover a new head.
+
+## Refreshed stack disposition — 2026-10-11 (Europe/Berlin)
+
+The amended proposal, design, scenarios, tasks and planned mapping are already present on refreshed dev
+`4e7c38c2830f4bc53ffe78eeb0a2bfbabfc711e2`. Replaying the old proposal must retain those newer amendments.
+No workflow runtime implementation is claimed by that integration.
+
+The owner selected verification/planning for this layer and conditioned core implementation on its paired
+modules work being underway. Live project readback on 2026-10-11: Requirements #481 In Progress, workflow
+Modules #483 Todo. No signed #483 publication is established; core #742 runtime adoption therefore remains deferred.
+Standalone projection remains independently deliverable in its owning implementation story, with all existing
+unchecked tasks and compatibility gates retained. This stack completes no runtime checkbox or trial.
+
+Validate the actual planning layer with strict OpenSpec, staged planned Requirements and applicable normal
+hooks; validate inherited #719 execution and protected exact-head authority independently through stack CI.
+The historical local planning-only exception above applies only to its dated original creation and is not used
+for this publication. Required gates, source/index preservation, producer verdicts and signatures remain enforced.
+
+## Protected stack revalidation — 2026-10-12 (Europe/Berlin)
+
+Merged prerequisite #761 is protected dev c4ee5be8457f69848bf9bc2150ebc3df56b52d4f. This existing planning layer is
+restacked onto signed security parent f6481418597d772d144203e530f932d145537236 after its native Requirements
+producer, execution, final verdict and trusted authority pass. Its complete delta remains only INTEGRATION.md and
+this workflow validation document; the newer proposal, design, scenarios, planned mapping and unchecked runtime
+tasks on dev are preserved.
+
+The owner conditioned core implementation on paired module work already underway. Current readback retains modules
+`#483` Todo; runtime adoption remains deferred. Ongoing modules #481 owns its signed Requirements contract. Core #740 separately owns the R09 policy
+cutover already present on the protected parent; its files are absent from this PR delta. No implementation task is completed or future signed-release
+compatibility asserted.
+
+Applicable normal signed hooks, strict selected OpenSpec, native local planned-maturity selection and documentation
+checks are required. Hosted producer/execution/final verdict must independently authenticate current root proof and
+scope using the merged protected helper and scoped tokens; a local planning pass cannot substitute for those checks.
+A new owner-authorized exact-head grant follows actual GitHub signature verification. Leave #719/#743/#751 unmerged.
+
+## Corrected native lineage validation — 2026-10-12 (Europe/Berlin)
+
+Protected prerequisite #767 merged as c6af68a0fdf2ea798dd22c6750f077e217c938f5. Its independently tested
+correction preserves protected review trust and checks planning-parent ancestry against the candidate.
+This layer now follows signed security root 57f51829a0899afc3bc413c3ed21099d261b8ab8, whose fresh native
+Requirements run 38306990823 and exact-head authority pass. The earlier consumer failure on 98a932c3
+is retained as historical evidence and is not reported as a passing run.
+
+The complete own delta remains two Markdown planning documents. Deferred module workflow `#483` remains
+Todo. Ongoing modules `#481` owns the signed Requirements contract; core `#740` separately owns the
+R09 policy cutover already on the protected parent and outside this delta.
+Local planned Requirements, strict selected OpenSpec, documentation and normal signed hooks must pass.
+Current-head hosted producer, independent execution, final verdict, authority and completed review remain
+required before readiness. No runtime task, future release compatibility or inherited execution is fabricated.
+
+Independent execution on 2ee53305/run 38303860784 passed planned reconciliation, then the immutable
+Code Review provider correctly rejected the child planning receipt as non-final execution proof.
+Protective `fix-planning-review-proof-context` preserves full protected-dev review and authentic root
+final proof separately; exact mapping acceptance, native proof and protected integration are pending.
+This branch aligns to the current signed root and fixes ownership wording; hosted consumer readiness
+remains blocked until that protection is integrated and validated. No review gate is skipped.