Reconcile unified project guide compilation plans

.agent-loop/initiatives/WS-ART-001-immutable-artifact-storage/CHUNK_MAP.md

@@ -33,12 +33,12 @@ they cross multiple L1 boundaries.
 | `WS-ART-001-04B1` | Add the single versioned checker catalogue and compile one effective execution plan from platform defaults plus locked project policy. | L1 | Merged PR #276 |
 | `WS-ART-001-04B2` | Materialize the sealed manifest tree once and execute the mandatory platform/default catalogue phases. | L1 | Merged PR #282 |
 | `WS-ART-001-04B3` | Execute locked project-policy rules through the same plan and persist one bounded immutable evidence set. | L1 | Merged PR #291 as `8f516e6d` |
-| `WS-ART-001-04C1` | Reauthorize and atomically persist the evidence-linked submission intent, capacity, and generic put attempt, then write the checked ZIP once. | L1 | Planning correction after merged XINT-06A |
+| `WS-ART-001-04C1` | Reauthorize and atomically persist the evidence-linked submission intent, capacity, and generic put attempt, then write the checked ZIP once. | L1 | Ready after merged XINT-06A |
 | `WS-ART-001-04C2` | Reuse verification/recovery to publish one capacity-charged ready admission and compose the hidden continuous endpoint. | L1 | Proposed after 04C1 |
 | `WS-ART-001-05A` | Atomically consume ready admission into one immutable Submission and binding under fresh human/service authority. | L1 | Proposed after XINT-05A |
 | `WS-ART-001-05B` | Atomically cut the live Submission API/dispatch to verified admission and remove the complete legacy standalone/internal precheck and caller-owned package contract. | L1 | Proposed after XINT-05B |
-| `WS-ART-001-06A` | Persist post-submit checker input snapshot and integrity-checking materialization. | L1 | Proposed after 05B |
-| `WS-ART-001-06B` | Store/bind checker outputs and preserve checker-owned routing. | L1 | Proposed after 06A |
+| `WS-ART-001-06A` | Persist post-submit checker input snapshot and materialization bound to the unified compilation and compiled checker plan. | L1 | Proposed after 05B and POL-06B/07 |
+| `WS-ART-001-06B` | Store/bind checker outputs and preserve POL-owned single-port routing. | L1 | Proposed after 06A |
 | `WS-ART-001-07A` | Add lease-scoped exact-binding reviewer packet materialization without review lifecycle ownership. | L1 | Proposed after 06B plus hidden REV manifest |
 | `WS-ART-001-07B` | Bind accepted Submission/ART identity into the CON handoff without provider I/O. | L1 | Proposed after REV acceptance and CON hidden contract |
 | `WS-ART-001-08A` | Prove Local/MinIO product lifecycle through real APIs and durable background services. | L1 | Proposed after 07B |
@@ -56,7 +56,7 @@ AUTH-04B implementation [merged PR #245]
 -> XINT-05A contributor preparation activation
 -> ART-05A
 -> XINT-05B Submission/binding activation
--> ART-05B -> 06A -> 06B
+-> ART-05B -> POL-06B -> POL-07 -> ART-06A -> ART-06B
 -> XINT-06B post-submit/output activation
 -> ART/REV-07A hidden packet contract
 -> XINT-07A packet activation only

.agent-loop/initiatives/WS-ART-001-immutable-artifact-storage/PLAN.md

@@ -746,6 +746,8 @@ AUTH-04B implementation/activation [merged PR #245]
 -> ART-05A atomic Submission/binding/admission consumption
 -> XINT-05B Submission/binding activation
 -> ART-05B admission-backed Submission/API/dispatch cutover plus complete legacy precheck removal
+-> POL-06B deterministic unified post-submit projection
+-> POL-07 sole checker service port
 -> ART-06A post-submit checker snapshot/materialization
 -> ART-06B checker output binding and routing
 -> XINT-06B post-submit/output activation

.agent-loop/initiatives/WS-ART-001-immutable-artifact-storage/chunks/WS-ART-001-06A-checker-input-materialization.md

@@ -1,6 +1,6 @@
 # Chunk Contract: WS-ART-001-06A - Checker Input And Materialization
 
-Initiative: `WS-ART-001` | Risk: L1 | Status: Proposed after 05B
+Initiative: `WS-ART-001` | Risk: L1 | Status: Proposed after 05B and POL-06B/07
 
 Artifact contract phase: `submission_cutover`
 
@@ -38,8 +38,11 @@ bounded isolated checker workspaces.
 ## Acceptance Criteria
 
 - `CheckerInputSnapshot` commits to submission version, submission-bundle
-  manifest, exact binding/content IDs, hashes/sizes, locked policy/checker versions, and checker
+  manifest, exact binding/content IDs, hashes/sizes, unified compilation/result,
+  pre/post component and catalogue hashes, compiled checker-plan identity, and checker
   implementation identity;
+- stale pre-unified, mixed-generation, missing-plan, or non-POL-07 lineage
+  fails before materialization;
 - pre-submit evidence and post-submit input prove the same archive commitment,
   semantic-manifest hash, and exact binding;
 - the post-submit runner receives only authorized immutable Workstream binding
@@ -116,3 +119,4 @@ reuse/dedup, CI integrity, test delta, and docs.
 - Is materialization bounded, isolated, and integrity checked?
 - Can any post-submit path bypass the exact materializer already used by
   pre-submit or leave a writable/orphaned workspace?
+- Does every materialization consume the POL-07 single-port compiled plan?

.agent-loop/initiatives/WS-ART-001-immutable-artifact-storage/chunks/WS-ART-001-06B-checker-output-routing.md

@@ -1,6 +1,6 @@
 # Chunk Contract: WS-ART-001-06B Checker Output And Post-Submit Routing
 
-Initiative: `WS-ART-001` | Risk: L1 | Status: Proposed after 06A
+Initiative: `WS-ART-001` | Risk: L1 | Status: Proposed after 06A and POL-07
 
 Artifact contract phase: `checker_cutover`
 
@@ -54,8 +54,10 @@ lease, assignment, or decision.
   only when expired; slow-active, cancellation, and crash cases are tested;
 - non-reproducible crash replay fails the old checker attempt and uses a new
   attempt identity;
-- the project `PostSubmitCheckerPolicy` selects project checks and non-bypassable
-  Workstream defaults remain included;
+- the exact unified compilation post-submit component and POL-07 compiled plan
+  select project checks; non-bypassable Workstream defaults remain included;
+- output facts retain compilation/result/component/catalogue/plan hashes;
+  stale pre-unified, mixed-generation, or out-of-plan output denies;
 - transient provider failure keeps `evaluation_pending` and uses checker
   infrastructure retry; it creates no product decision;
 - after checker outputs and completion facts commit atomically, the existing
@@ -115,3 +117,4 @@ reuse/dedup, CI integrity, test delta, and docs.
 - Are checker outputs bound to the exact run and independently verified?
 - Can infrastructure failure ever become contributor blame?
 - Is the WS-REV ownership boundary preserved?
+- Is POL-07 the sole routing port with no caller-selected checker path?

.agent-loop/initiatives/WS-AUTH-001-workstream-authorization-service/CHUNK_MAP.md

@@ -63,18 +63,19 @@ stopped.
 | `WS-AUTH-001-12` | Project Mutation Cutover Planning Parent | L1 | Split before runtime implementation after failed L1 review |
 | `WS-AUTH-001-12A` | Project Mutation Catalogue And PREP Foundation | L1 | Merged as PR #226 with AUTH `0041`; zero activation |
 | `WS-AUTH-001-12B` | Fixed Project Setup Service Foundation | L1 | Merged through PR #227; identity/matrix registration only, zero activation |
-| `WS-AUTH-001-12B2` | Project Setup Service Runtime Cutover | L1 | Proposed after 12E, 12F4, and 12G |
+| `WS-AUTH-001-12B2` | Unified Setup Ledger Activation | L1 | Proposed after hidden POL-04A and AUTH-12I; before POL-04B live cutover |
 | `WS-AUTH-001-12C` | Project Creation Cutover | L1 | Merged through PR #229 |
 | `WS-AUTH-001-12D` | Draft Guide And Source Metadata Cutover | L1 | Merged through PR #232 |
 | `WS-AUTH-001-12D2` | Review And Revision Policy Mutation Separation | L1 | Superseded by merged XINT-003-02A/02B; economic policy remains CON-owned |
 | `WS-AUTH-001-12E` | Guide Sufficiency Mutation Cutover | L1 | Merged through PR #263 |
 | `WS-AUTH-001-12F` | Submission Artifact Policy Planning Parent | L1 | Split after failed L1 pre-start review; zero activation |
 | `WS-AUTH-001-12F1` | Submission Policy Authority Foundation | L1 | Merged through PR #286; zero activation |
 | `WS-AUTH-001-12F2` | Manual Submission Policy Drafts | L1 | Merged through PR #292 as `81f281bd` |
-| `WS-AUTH-001-12F3` | Fixed-Service Policy Derivation | L1 | PR #295; external checks pending |
-| `WS-AUTH-001-12F4` | Submission Policy Approval Chain | L1 | Proposed after 12F3 |
-| `WS-AUTH-001-12G` | Post-Submit Checker Policy Mutation Cutover | L1 | Proposed after 12F4 |
-| `WS-AUTH-001-12H` | Guide Activation Cutover | L1 | Proposed after 12B2 and the owning CON clean cut |
+| `WS-AUTH-001-12F3` | Transitional Fixed-Service Policy Derivation | L1 | Merged through PR #295 as `99c0aaf0`; superseded at POL-04B live cutover |
+| `WS-AUTH-001-12I` | Unified Compilation Request/Execute Activation | L1 | Proposed after hidden POL-03A; before POL-03B |
+| `WS-AUTH-001-12F4` | Unified Pre-Submit Approval Activation | L1 | Proposed after hidden POL-05A; before POL-05B |
+| `WS-AUTH-001-12G` | Unified Post-Submit Projection Activation | L1 | Proposed after hidden POL-06A; zero model calls |
+| `WS-AUTH-001-12H` | Unified Guide Activation Cutover | L1 | Proposed after POL-06B/07 and complete approved unified lineage |
 | `WS-AUTH-001-13` | Task Management And Assignment Cutover | L1 | Proposed |
 | `WS-AUTH-001-14` | Submission, Checker, And Audit Visibility Cutover | L1 | Proposed |
 | `WS-AUTH-001-15` | Remaining Internal Service Cutover And Obsolete Authority Removal | L1 | Proposed |
@@ -92,10 +93,10 @@ feature manifest exists, then requires a separate explicit start.
 | `WS-AUTH-001-ART-02D-INTERNAL` | ART 02D Internal Action Activation | L1 | Feature-gated |
 | `WS-AUTH-001-ART-02D-OPERATOR` | ART 02D Operator Read/Status And Independently Evaluated Retry Activation | L1 | Feature-gated |
 | `WS-AUTH-001-ART-03` | ART 03 Guide Source Action Activation | L1 | Feature-gated |
-| `WS-XINT-002-06A` | Pre-Submit Materialization Activation | L1 | After merged ART-04B3/AUTH-12F2; before ART-04C1 and 05A |
+| `WS-XINT-002-06A` | Pre-Submit Materialization Activation | L1 | Merged through PR #293; ART-04C1 is its next ART consumer |
 | `WS-XINT-002-05A` | Submission Bundle Preparation Activation | L1 | Feature-gated on complete ART-04A1-04C2 hidden behavior and 06A |
 | `WS-XINT-002-05B` | Submission Binding Activation | L1 | Feature-gated on hidden ART-05A |
-| `WS-XINT-002-06B` | Post-Submit Materialization And Checker Output Activation | L1 | Feature-gated on ART-06A/06B |
+| `WS-XINT-002-06B` | Post-Submit Materialization And Checker Output Activation | L1 | Feature-gated on POL-06B/07 unified plan plus ART-06A/06B evidence |
 | `WS-AUTH-001-REV-05` | REV 05 Queue Read Activation | L1 | Feature-gated |
 | `WS-AUTH-001-REV-06` | REV 06 Claim Lease And Expiry Activation | L1 | Feature/service-gated |
 | `WS-AUTH-001-REV-07` | REV 07 Context Chain And Finding Evidence Activation | L1 | Feature/ART-gated |
@@ -155,12 +156,14 @@ WS-AUTH-001-PLAN
 -> WS-AUTH-001-12F1
 -> WS-AUTH-001-12F2
 -> WS-AUTH-001-12F3
--> WS-AUTH-001-12F4
--> WS-AUTH-001-12G
--> WS-AUTH-001-12B2
--> WS-AUTH-001-12H
+-> WS-POL-003-01 -> 02 -> 03A
+-> WS-AUTH-001-12I -> WS-POL-003-03B -> 04A
+-> WS-AUTH-001-12B2 -> WS-POL-003-04B -> 05A
+-> WS-AUTH-001-12F4 -> WS-POL-003-05B -> 06A
+-> WS-AUTH-001-12G -> WS-POL-003-06B -> 07
+-> WS-AUTH-001-12H -> WS-POL-003-08
 -> WS-AUTH-001-13
--> WS-AUTH-001-14
+-> ART/XINT submission and checker gates -> WS-AUTH-001-14
 -> WS-AUTH-001-15
 -> all registration/activation chunks whose feature surfaces have merged
 -> WS-AUTH-001-16
@@ -169,6 +172,9 @@ WS-AUTH-001-PLAN
 ## Boundary notes
 
 - Chunk 02 authenticates tokens but grants no product authority.
+- `WS-POL-003` owns unified guide compilation and product orchestration. AUTH
+  owns only catalogue/evaluator/PREP activation and evidence. Hidden behavior
+  precedes each AUTH activation; live cutover follows it.
 - Chunk 03 provides a supported classification gate before schema migration.
 - Parent chunk 04 was split before implementation. Chunk 04A establishes
   request/correlation and additive error compatibility; chunk 04B later owns

.agent-loop/initiatives/WS-AUTH-001-workstream-authorization-service/DECISIONS.md

@@ -861,3 +861,26 @@ result is usable only when its acknowledgement has the complete merged 12E
 actor, identity-link, grant, action, decision, scope, report, snapshot, and
 setup-generation custody. The legacy role-string acknowledgement is not
 authority.
+
+## D38: WS-POL-003 owns unified guide compilation; AUTH owns only gates
+
+Status: accepted planning correction on 2026-08-08.
+
+One logical/provider attempt produces one immutable result containing guide
+sufficiency plus artifact, pre-submit, and post-submit policy proposals before
+any Project Manager approval. Approval never invokes inference. Post-submit
+policy is a deterministic projection of that stored result and performs zero
+model calls.
+
+Merged AUTH-12E and AUTH-12F3 remain valid transitional authority and
+provenance foundations. Their separate inference entry points become
+unreachable at `WS-POL-003-04B` and are physically removed at
+`WS-POL-003-08`. Future AUTH chunks activate only already-hidden POL behavior:
+12I compilation request/execute, 12B2 setup-ledger mutation, 12F4 pre-submit
+approval, 12G post-submit projection, and 12H terminal activation.
+
+External I/O uses pre-I/O authorization plus a committed attempt/idempotency
+reservation. No database transaction or prepared handle spans provider I/O.
+Accepted output receives fresh result-bound PREP authority for persistence.
+This decision supersedes D35/D36 only where they describe separate future
+inference passes or AUTH ownership of product orchestration.

.agent-loop/initiatives/WS-AUTH-001-workstream-authorization-service/PLAN.md

@@ -206,16 +206,17 @@ proving the same issuer role metadata alone no longer authorizes.
     10C activates PREP-bound issue/revoke mutations and concurrency proof.
 13. Cut project identity, guide, source, and visibility queries over to local
    permissions.
-14. Treat AUTH-12 as a planning-only parent. Its ordered children register
-    exact mutation/PREP contracts, establish a zero-activation fixed setup
-    identity, cut project/guide/sufficiency/policy families separately, leave
-    retired guide-bound economic policy to CON ownership, cut the Celery call
-    graph only after its product actions are active, and finish with guide
-    activation only after the owning CON clean cut. ART-owned `0040` is now
-    merged; the first AUTH migration is allocated from that trusted head.
+14. Treat AUTH-12 as a planning-only parent. Merged 12E and 12F3 are
+    transitional authority/provenance foundations, not the final product call
+    graph. `WS-POL-003` owns one unified compilation attempt and every product
+    projection. AUTH-12I activates only the hidden request/execute boundary;
+    12B2, 12F4, 12G, and 12H are narrow activation/cutover gates after their
+    hidden POL behavior exists. No AUTH chunk owns agent orchestration or a
+    second inference path.
 15. Cut task management, queue, assignment, claim, and start operations over.
-16. Cut submission, pre-submit, checker trigger/read, and task audit visibility
-    over.
+16. Activate admission-backed submission authority, bounded checker
+    read/repair, and audit visibility only after ART/POL hidden behavior exists;
+    never add a standalone precheck or caller-selected checker trigger.
 17. Cut remaining internal services over, verify the project-setup cutover,
     remove old runtime authority, and enforce a
     deterministic stale-authority scanner.

.agent-loop/initiatives/WS-AUTH-001-workstream-authorization-service/RISKS.md

@@ -15,10 +15,10 @@ merge and activate their exact actions.
 - Agent-backed setup operations deliberately break transactions around external
   work. Carrying PREP across that boundary would make stale authority usable;
   runtime children require fresh terminal authorization.
-- The Celery setup service currently fabricates human roles. 12B provisions one
-  exact fixed identity with four planned memberships; 12B2 performs the runtime
-  cut only after 12E/12F2/12F3/12F4/12G own the complete manual and
-  fixed-service product actions and provenance.
+- Historical AUTH-12 risk context: the Celery setup service fabricated human
+  roles and 12B provisioned one fixed identity. D38/`CHUNK_MAP.md` supersede the
+  old 12B2 sequence: POL-04A hidden behavior precedes 12B2 ledger activation,
+  and POL-04B owns the live one-call cutover.
 - ART-03B2 migration `0040` is merged on trusted main. AUTH-12 must allocate
   the next revision from that exact head and must not reuse `0040`.
 
@@ -48,8 +48,8 @@ merge and activate their exact actions.
 | A10 | Approval provenance breaks | Existing policy activation becomes unreadable or forgeable | Preserve historical values; new actions reference matched local grant | Migration and project approval tests |
 | A11 | API namespace forks | Client and documentation drift | Adopt `/api/v1` only and update references together | Route/OpenAPI and stale-reference scan |
 | A12 | Existing intake regresses | Project/task/checker pipeline stops | Run full current suite and API drill after actor migration and each cutover surface | Existing backend suite and live drill |
-| A13 | Auth initiative becomes one oversized PR | Review failure and hidden coupling | Sixteen bounded implementation chunks, one active at a time | Circuit-breaker and PR-size evidence |
-| A14 | Later WS-POL work resumes on obsolete auth | Rework and inconsistent authority | Keep WS-POL-002-04 inactive until PR #90 merges, auth proof exists, and the user starts it | Loop-memory gate |
+| A13 | Auth initiative becomes one oversized PR | Review failure and hidden coupling | Bounded executable child chunks, one active at a time | Circuit-breaker and PR-size evidence |
+| A14 | Later WS-POL work resumes the obsolete standalone derivation path | Rework, extra model calls, and inconsistent policy lineage | WS-POL-003 is current authority; POL-002-04 consumes the unified component only | Zero-call and stale-path scanner proof |
 | A15 | Authority mutation ships before durable evidence | Missing provenance cannot be reconstructed | Introduce correlation/idempotency/shared audit with canonical actor persistence | Atomic state+idempotency+event tests in every authority chunk |
 | A16 | Identity-link revocation strands final administrator | Administrative lockout despite active grant row | Apply AuthorityControl lock to link revoke plus grant/profile changes | Mixed concurrent link/grant/profile final-admin tests |
 | A17 | Canonical actor migration deletes typed-profile workflow eligibility before task/submission cutover | An intermediate merged release cannot claim, start, or submit work | Bounded non-authoritative workflow-eligibility adapter in chunk 06; remove task consumers in 13 and final consumer plus adapter in 14 | Full suite/API drill after chunks 06, 13, 14, and scanner proof in 15 |
@@ -69,6 +69,9 @@ merge and activate their exact actions.
 | A31 | Service provisioning crosses inverse actor/link locks | Administrative and lifecycle mutations deadlock or admit stale authority | Canonical AuthorityControl -> profile -> exact link -> exact grant order before fixed-identity and issuer/subject advisory locks | Independent-session same-key, identity collision, revoke/lifecycle crossing, rollback, and no-deadlock proof |
 | A32 | Sensitive authorization reads have no dedicated abuse control or leak resource existence through errors | Enumeration, privacy breach, or cross-project intelligence disclosure | Add one durable `authorization_read` scope before routes; map only the three read actions to one audited not-found boundary | Migration/concurrency/rate tests plus identical-response and persisted-denial-evidence tests |
 | A33 | Pagination cursors replay across actions, projects, or filters | Hidden rows disclose or pagination crosses authority scope | Distinct required 32-byte HMAC key, canonical versioned payload, complete query binding, and constant-time verification | Tamper, cross-scope/filter/limit, equal-boundary, no-gap, and no-query tests |
+| A34 | AUTH activates before hidden feature behavior exists | Deny-only or alternate live path | Hidden POL/ART manifest, then narrow AUTH activation, then live owner cutover | Dependency and availability-delta proof |
+| A35 | Prepared authority or a database transaction spans model/provider I/O | Lock exhaustion, stale authority, or replay ambiguity | Pre-I/O authorization plus committed attempt reservation; fresh result-bound PREP after I/O | Timeout/cancellation/revocation/cross-transaction tests |
+| A36 | Separate approval restarts inference or accepts an incomplete result | Policy components drift across one guide generation | Persist all four components before approval; approvals only project stored components | One-attempt and zero-approval-call proof |
 
 ## Required reviewers