Bind default policy custody and prospective allocation normalization

[adrianwebb]

Outcome

Bind canonical default-policy custody (criterion50) and prospective allocator normalization (criterion47) to the existing SDK campaign path. The freeze checks the current owning SDK function's normalized project/class targets for every held campaign input; this projection does not create future assignments, usage or passing portfolio receipts.

Work authority

• Work item / Issue: Complete capacity-provider and Agent acceptance — continuation of #339 #368 and Continue strict acceptance bindings: current checklist and native reconciliation delivery sdk#401.
• Proposal / decision: Explicit user-authorized strict capacity-provider and agent-execution acceptance implementation plan.
• Assignment / checkpoint: Wave2 Agent campaign freeze and Wave3 integrator-owned acceptance bindings.
• Actor: Codex through provider-authenticated adrianwebb.
• Human authority: adrianwebb, explicit implementation authorization.
• Agent / capacity provider: Codex in authorized local workspace.
• Exact base ref: staging ca643dc3fda822c471300ee7b0a338c1e9f32ca1.
• Exact head ref: codex/agent-policy-binding-401 ac15293b65a4967d4ec05b5d753982d4d054fe77.
• Exact proposed merge: a3bca083438445893cdfc10b57de7504cb0ddf3b.

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Retain fixed inputs, original normal SDK scene ordering, all selected/deferred identities and earlier failures. Strengthen the existing campaign freeze; use owning API and SDK proof through their existing components. Criterion47 uses delivered SDK406 sourced486e74d and the current API536 staging archive; criterion50 separately holds API537 source379c5266 pending its longer native CI. All archive adoption is explicit. Fresh full Agent/Reviewer prerequisites and component scenes for this replacement candidate have now passed.

Changes and commits

• 3356b26 → dd5d543: criterion50 mapping RED (8pass/2fail), then exact preflight/campaign/native policy binding and selected component assertion.
• 3fba5244b20834b1b0fa91caa629697d8c8fc253: criterion47 guard/binding RED (20pass/2fail). Classified IMPLEMENTATION_DEFECT before guard repair: the prospective validator never invoked the owning SDK normalizer.
• ac15293b65a4967d4ec05b5d753982d4d054fe77: use the existing public SDK normalizer with frozen policy/overrides and a clearly prospective ready-node projection. Reject absent/malformed results, foreign identities, missing/nonfinite/coerced/wrong targets and raw portfolio weights substituted for normalized targets, while preserving caller bytes. Bind exact criterion47 to the existing campaign-freeze verifier and register its two unit assertions in the existing component scene.
• API537 proves original native preflight revision/resolved policy, version-checked default updates and unchanged issued authority. SDK406 proves seventeen equal project targets100/17%, eight class targets12.5%, and all136 controlled distinct selections through the owning unit and production-installed package.
• No SDK src repair, duplicate allocator, product authority, runner, deadline or allowance change. Future actual portfolio outcomes remain required. Normal SDK scene remains21steps; component scene739steps.

Verification

Pinned Node24.12.0 and original development authoritye4c4cad1. Changed freeze/binding and real native pre-run reader tests29/29passed; strict TypeScript, file architecture/length and whitespace checks pass. Original native pre-run denial cases and unchanged-retry/file-byte assertions remain intact. Intermediate unknown-readiness typing error was repaired with explicit string validation; no type check was disabled.

Earlier Verify38184448791 on old sourcedd5d543 passed989Agent+200Reviewer and737component assertions, with original artifacts independently checked. That receipt remains historical and does not certify the changed source above. Fresh Verify38188525564 passed991Agent+200executingReviewer assertions (zero failed/skipped/todo) before739component steps. Independently audited739assertion receipts/118native source file digests and11selected archive assets against tested mergea3bca083438445893cdfc10b57de7504cb0ddf3b. ArchiveSHA858da74ccf197875cd521b528db2cb3340f5fbf0a7e940ddb2d8b2773182d847; reportSHAbcb839c4368884b36bae46dcc7b7ec8675f50e77ae53de292134cb514994b3eb. Original sceneZIP11720638352 SHA4ae97da1ecd9b91a63d6cde932fb41ff46b7fadfe7155a3ae3d65c9c856e8c70; packageZIP11721381502 SHA2575f1e1533479d596fe5f1fd266c4d09acdbe6f86e1c386f4d123164176bd24. Actual six-owner production installation and protected staging read-back follow; no scene prerequisite is reused. No local or managed scene was launched from focused receipts.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

Acceptance guard and binding changes only. No runtime selection, external publication, product source change or campaign activation. Ordinary revert restores prior guard/bindings while preserving RED and failed observations.

Completion summary

Criterion47 remains unchecked until its Agent/SDK native Actions, installed read-back and protected staging delivery are complete. Criterion50 remains independently unchecked until API537 also passes native Actions, installed policy custody and protected staging delivery. SDK401 remains31completed/146open. SDK launch readiness and managed SDK success remain unproven.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.