{"data":[{"id":"0a367eb2-8395-4ecb-ad41-229792858b90","name":"Tennex IRSLogiqs Sync Repair","cadence":"interval","enabled":false,"objective":"Run one bounded owner-authorized Tennex IRSLogiqs repair cycle. Exact tenant: Tennex Tax Solutions, tenant id 669daee1-57e8-4960-937c-ce397106f32e. Proven current state: encrypted IRSLogiqs credentials exist, account_subdomain is tennextax, credential_status is pending, there are zero IRSLogiqs-tagged canonical contacts, and the current irslogiqs-sync function returns HTTP 409 when sync_status_ids/status_ids are absent. Repair only the authorized source scope. Preserve explicit configured status IDs when present. When credentials/subdomain exist but status IDs are absent, perform a bounded authenticated discovery of usable case status IDs using the existing provider read endpoint and current auth contract; persist discovered IDs before normal sync. If discovery cannot find usable IDs, return a successful prerequisite_required payload with a clear owner-facing explanation instead of surfacing a generic non-2xx Edge Function error. Do not change HubSpot CSV import behavior. Keep tenant isolation and owner/admin authorization intact. Add focused regression coverage if an existing test file in scope supports it; otherwise do not broaden scope. Ship through canonical Gate, squash merge, affected Supabase function/app release, and prove live provider status/sync behavior and the Tennex contacts route no longer shows the generic non-2xx error for the missing-status prerequisite.","created_at":"2026-10-02T20:41:33.260339+00:00","last_error":null,"updated_at":"2026-10-05T00:32:13.145+00:00","last_run_at":"2026-10-05T00:32:00.86606+00:00","last_status":"cancelled","next_run_at":"2026-10-05T00:33:00.86606+00:00","failure_count":15,"last_mission_id":"bf04bf88-1a57-406e-adba-588dd71d6d9d","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded owner-authorized Tennex IRSLogiqs repair cycle. Exact tenant: Tennex Tax Solutions, tenant id 669daee1-57e8-4960-937c-ce397106f32e. Proven current state: encrypted IRSLogiqs credentials exist, account_subdomain is tennextax, credential_status is pending, there are zero IRSLogiqs-tagged canonical contacts, and the current irslogiqs-sync function returns HTTP 409 when sync_status_ids/status_ids are absent. Repair only the authorized source scope. Preserve explicit configured status IDs when present. When credentials/subdomain exist but status IDs are absent, perform a bounded authenticated discovery of usable case status IDs using the existing provider read endpoint and current auth contract; persist discovered IDs before normal sync. If discovery cannot find usable IDs, return a successful prerequisite_required payload with a clear owner-facing explanation instead of surfacing a generic non-2xx Edge Function error. Do not change HubSpot CSV import behavior. Keep tenant isolation and owner/admin authorization intact. Add focused regression coverage if an existing test file in scope supports it; otherwise do not broaden scope. Ship through canonical Gate, squash merge, affected Supabase function/app release, and prove live provider status/sync behavior and the Tennex contacts route no longer shows the generic non-2xx error for the missing-status prerequisite.","wordingChanged":false,"canonicalIntent":"Run one bounded owner-authorized Tennex IRSLogiqs repair cycle. Exact tenant: Tennex Tax Solutions, tenant id 669daee1-57e8-4960-937c-ce397106f32e. Proven current state: encrypted IRSLogiqs credentials exist, account_subdomain is tennextax, credential_status is pending, there are zero IRSLogiqs-tagged canonical contacts, and the current irslogiqs-sync function returns HTTP 409 when sync_status_ids/status_ids are absent. Repair only the authorized source scope. Preserve explicit configured status IDs when present. When credentials/subdomain exist but status IDs are absent, perform a bounded authenticated discovery of usable case status IDs using the existing provider read endpoint and current auth contract; persist discovered IDs before normal sync. If discovery cannot find usable IDs, return a successful prerequisite_required payload with a clear owner-facing explanation instead of surfacing a generic non-2xx Edge Function error. Do not change HubSpot CSV import behavior. Keep tenant isolation and owner/admin authorization intact. Add focused regression coverage if an existing test file in scope supports it; otherwise do not broaden scope. Ship through canonical Gate, squash merge, affected Supabase function/app release, and prove live provider status/sync behavior and the Tennex contacts route no longer shows the generic non-2xx error for the missing-status prerequisite.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded owner-authorized Tennex IRSLogiqs repair cycle. Exact tenant: Tennex Tax Solutions, tenant id 669daee1-57e8-4960-937c-ce397106f32e. Proven current state: encrypted IRSLogiqs credentials exist, account_subdomain is tennextax, credential_status is pending, there are zero IRSLogiqs-tagged canonical contacts, and the current irslogiqs-sync function returns HTTP 409 when sync_status_ids/status_ids are absent. Repair only the authorized source scope. Preserve explicit configured status IDs when present. When credentials/subdomain exist but status IDs are absent, perform a bounded authenticated discovery of usable case status IDs using the existing provider read endpoint and current auth contract; persist discovered IDs before normal sync. If discovery cannot find usable IDs, return a successful prerequisite_required payload with a clear owner-facing explanation instead of surfacing a generic non-2xx Edge Function error. Do not change HubSpot CSV import behavior. Keep tenant isolation and owner/admin authorization intact. Add focused regression coverage if an existing test file in scope supports it; otherwise do not broaden scope. Ship through canonical Gate, squash merge, affected Supabase function/app release, and prove live provider status/sync behavior and the Tennex contacts route no longer shows the generic non-2xx error for the missing-status prerequisite.","provenance":{"reason":"PAUL schedule 0a367eb2-8395-4ecb-ad41-229792858b90","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded owner-authorized Tennex IRSLogiqs repair cycle. Exact tenant: Tennex Tax Solutions, tenant id 669daee1-57e8-4960-937c-ce397106f32e. Proven current state: encrypted IRSLogiqs credentials exist, account_subdomain is tennextax, credential_status is pending, there are zero IRSLogiqs-tagged canonical contacts, and the current irslogiqs-sync function returns HTTP 409 when sync_status_ids/status_ids are absent. Repair only the authorized source scope. Preserve explicit configured status IDs when present. When credentials/subdomain exist but status IDs are absent, perform a bounded authenticated discovery of usable case status IDs using the existing provider read endpoint and current auth contract; persist discovered IDs before normal sync. If discovery cannot find usable IDs, return a successful prerequisite_required payload with a clear owner-facing explanation instead of surfacing a generic non-2xx Edge Function error. Do not change HubSpot CSV import behavior. Keep tenant isolation and owner/admin authorization intact. Add focused regression coverage if an existing test file in scope supports it; otherwise do not broaden scope. Ship through canonical Gate, squash merge, affected Supabase function/app release, and prove live provider status/sync behavior and the Tennex contacts route no longer shows the generic non-2xx error for the missing-status prerequisite.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["supabase/functions/irslogiqs-sync/index.ts","supabase/functions/tennex-contact-directory/index.ts","config/capabilities/tennex-irslogiqs-connection.json"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded owner-authorized Tennex IRSLogiqs repair cycle. Exact tenant: Tennex Tax Solutions, tenant id 669daee1-57e8-4960-937c-ce397106f32e. Proven current state: encrypted IRSLogiqs credentials exist, account_subdomain is tennextax, credential_status is pending, there are zero IRSLogiqs-tagged canonical contacts, and the current irslogiqs-sync function returns HTTP 409 when sync_status_ids/status_ids are absent. Repair only the authorized source scope. Preserve explicit configured status IDs when present. When credentials/subdomain exist but status IDs are absent, perform a bounded authenticated discovery of usable case status IDs using the existing provider read endpoint and current auth contract; persist discovered IDs before normal sync. If discovery cannot find usable IDs, return a successful prerequisite_required payload with a clear owner-facing explanation instead of surfacing a generic non-2xx Edge Function error. Do not change HubSpot CSV import behavior. Keep tenant isolation and owner/admin authorization intact. Add focused regression coverage if an existing test file in scope supports it; otherwise do not broaden scope. Ship through canonical Gate, squash merge, affected Supabase function/app release, and prove live provider status/sync behavior and the Tennex contacts route no longer shows the generic non-2xx error for the missing-status prerequisite.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"1d8d81b9-1a48-4ecf-abee-1abfb861324a","name":"PAUL Continuous Intelligence Lab Proof","cadence":"interval","enabled":false,"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. The only authorized mutation source scope for this cycle is exactly: config/capabilities/platform-sidekick-intelligence.json; config/platform-sidekick-intelligence.json; src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts; config/capabilities/paul-scheduler.json. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections. If and only if the evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused change within that explicit source scope, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. If no change is justified, record a successful no-op evaluation and terminate cleanly. Never stop merely because source scope is unresolved: the four exact source paths above are authoritative. Never broaden beyond them without machine-readable dependency evidence. Preserve tenant isolation, authorization, owner-intent fidelity, completion-proof discipline, Cloudflare Workers AI as active non-OpenAI primary, and OpenAI only as replaceable fallback. Avoid sustained heavy compute on owner hardware.","created_at":"2026-09-30T15:55:23.352253+00:00","last_error":null,"updated_at":"2026-09-30T15:58:33.529+00:00","last_run_at":"2026-09-30T15:58:02.807835+00:00","last_status":"cancelled","next_run_at":"2026-09-30T15:59:02.807835+00:00","failure_count":0,"last_mission_id":"b85a4ab1-64ca-4541-bb0e-f125b83c2c01","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. The only authorized mutation source scope for this cycle is exactly: config/capabilities/platform-sidekick-intelligence.json; config/platform-sidekick-intelligence.json; src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts; config/capabilities/paul-scheduler.json. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections. If and only if the evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused change within that explicit source scope, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. If no change is justified, record a successful no-op evaluation and terminate cleanly. Never stop merely because source scope is unresolved: the four exact source paths above are authoritative. Never broaden beyond them without machine-readable dependency evidence. Preserve tenant isolation, authorization, owner-intent fidelity, completion-proof discipline, Cloudflare Workers AI as active non-OpenAI primary, and OpenAI only as replaceable fallback. Avoid sustained heavy compute on owner hardware.","wordingChanged":false,"canonicalIntent":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. The only authorized mutation source scope for this cycle is exactly: config/capabilities/platform-sidekick-intelligence.json; config/platform-sidekick-intelligence.json; src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts; config/capabilities/paul-scheduler.json. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections. If and only if the evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused change within that explicit source scope, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. If no change is justified, record a successful no-op evaluation and terminate cleanly. Never stop merely because source scope is unresolved: the four exact source paths above are authoritative. Never broaden beyond them without machine-readable dependency evidence. Preserve tenant isolation, authorization, owner-intent fidelity, completion-proof discipline, Cloudflare Workers AI as active non-OpenAI primary, and OpenAI only as replaceable fallback. Avoid sustained heavy compute on owner hardware.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. The only authorized mutation source scope for this cycle is exactly: config/capabilities/platform-sidekick-intelligence.json; config/platform-sidekick-intelligence.json; src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts; config/capabilities/paul-scheduler.json. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections. If and only if the evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused change within that explicit source scope, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. If no change is justified, record a successful no-op evaluation and terminate cleanly. Never stop merely because source scope is unresolved: the four exact source paths above are authoritative. Never broaden beyond them without machine-readable dependency evidence. Preserve tenant isolation, authorization, owner-intent fidelity, completion-proof discipline, Cloudflare Workers AI as active non-OpenAI primary, and OpenAI only as replaceable fallback. Avoid sustained heavy compute on owner hardware.","provenance":{"reason":"PAUL schedule 1d8d81b9-1a48-4ecf-abee-1abfb861324a","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. The only authorized mutation source scope for this cycle is exactly: config/capabilities/platform-sidekick-intelligence.json; config/platform-sidekick-intelligence.json; src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts; config/capabilities/paul-scheduler.json. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections. If and only if the evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused change within that explicit source scope, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. If no change is justified, record a successful no-op evaluation and terminate cleanly. Never stop merely because source scope is unresolved: the four exact source paths above are authoritative. Never broaden beyond them without machine-readable dependency evidence. Preserve tenant isolation, authorization, owner-intent fidelity, completion-proof discipline, Cloudflare Workers AI as active non-OpenAI primary, and OpenAI only as replaceable fallback. Avoid sustained heavy compute on owner hardware.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. The only authorized mutation source scope for this cycle is exactly: config/capabilities/platform-sidekick-intelligence.json; config/platform-sidekick-intelligence.json; src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts; config/capabilities/paul-scheduler.json. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections. If and only if the evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused change within that explicit source scope, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. If no change is justified, record a successful no-op evaluation and terminate cleanly. Never stop merely because source scope is unresolved: the four exact source paths above are authoritative. Never broaden beyond them without machine-readable dependency evidence. Preserve tenant isolation, authorization, owner-intent fidelity, completion-proof discipline, Cloudflare Workers AI as active non-OpenAI primary, and OpenAI only as replaceable fallback. Avoid sustained heavy compute on owner hardware.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"2dd5694d-fa6e-4538-bddd-725f850ede1f","name":"PAUL Continuous Intelligence Lab","cadence":"interval","enabled":false,"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Start with non-mutating production-bound evals. Measure fast/standard/deep routing, factual grounding, owner-intent fidelity, live-machinery grounding, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections and known PAUL failure classes. Add or refine adversarial/regression cases when current evidence exposes a repeatable weakness. If the cycle proves a deterministic regression or a clearly measurable intelligence improvement opportunity, launch exactly one focused canonical execute_objective improvement mission through current Prime authority, exact source scope, Gate, squash merge, affected-target release, and claim-matched runtime proof. Keep a change only when before/after evidence shows improvement without degrading other required invariants; otherwise reject or revert it. Never bypass Gate, never create parallel orchestration, never claim improvement from implementation alone, and never weaken tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Resource policy: do not materially interfere with normal KNOCKLAUNCH work; avoid sustained heavy compute on the owner's MSI laptop or desktop; honor live thermal, queue, runner, provider, and capacity signals; automatically reduce intensity or no-op under active owner-critical work or degraded capacity; prefer the large DigitalOcean runner only for genuinely heavy torture/adversarial evaluation. Keep inference and infrastructure cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval results, score and latency trends, failure clusters, attempted/accepted/rejected improvements, and exact production runtime lineage. This schedule remains an evaluation/improvement loop, not permission for unrelated product changes.","created_at":"2026-09-30T13:42:57.681201+00:00","last_error":null,"updated_at":"2026-09-30T15:52:36.65+00:00","last_run_at":"2026-09-30T15:43:00.695777+00:00","last_status":"cancelled","next_run_at":"2026-09-30T16:43:00.695777+00:00","failure_count":0,"last_mission_id":"cdc4a917-eab1-4527-a6d6-520e20ae4b98","interval_minutes":60,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Start with non-mutating production-bound evals. Measure fast/standard/deep routing, factual grounding, owner-intent fidelity, live-machinery grounding, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections and known PAUL failure classes. Add or refine adversarial/regression cases when current evidence exposes a repeatable weakness. If the cycle proves a deterministic regression or a clearly measurable intelligence improvement opportunity, launch exactly one focused canonical execute_objective improvement mission through current Prime authority, exact source scope, Gate, squash merge, affected-target release, and claim-matched runtime proof. Keep a change only when before/after evidence shows improvement without degrading other required invariants; otherwise reject or revert it. Never bypass Gate, never create parallel orchestration, never claim improvement from implementation alone, and never weaken tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Resource policy: do not materially interfere with normal KNOCKLAUNCH work; avoid sustained heavy compute on the owner's MSI laptop or desktop; honor live thermal, queue, runner, provider, and capacity signals; automatically reduce intensity or no-op under active owner-critical work or degraded capacity; prefer the large DigitalOcean runner only for genuinely heavy torture/adversarial evaluation. Keep inference and infrastructure cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval results, score and latency trends, failure clusters, attempted/accepted/rejected improvements, and exact production runtime lineage. This schedule remains an evaluation/improvement loop, not permission for unrelated product changes.","wordingChanged":false,"canonicalIntent":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Start with non-mutating production-bound evals. Measure fast/standard/deep routing, factual grounding, owner-intent fidelity, live-machinery grounding, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections and known PAUL failure classes. Add or refine adversarial/regression cases when current evidence exposes a repeatable weakness. If the cycle proves a deterministic regression or a clearly measurable intelligence improvement opportunity, launch exactly one focused canonical execute_objective improvement mission through current Prime authority, exact source scope, Gate, squash merge, affected-target release, and claim-matched runtime proof. Keep a change only when before/after evidence shows improvement without degrading other required invariants; otherwise reject or revert it. Never bypass Gate, never create parallel orchestration, never claim improvement from implementation alone, and never weaken tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Resource policy: do not materially interfere with normal KNOCKLAUNCH work; avoid sustained heavy compute on the owner's MSI laptop or desktop; honor live thermal, queue, runner, provider, and capacity signals; automatically reduce intensity or no-op under active owner-critical work or degraded capacity; prefer the large DigitalOcean runner only for genuinely heavy torture/adversarial evaluation. Keep inference and infrastructure cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval results, score and latency trends, failure clusters, attempted/accepted/rejected improvements, and exact production runtime lineage. This schedule remains an evaluation/improvement loop, not permission for unrelated product changes.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Start with non-mutating production-bound evals. Measure fast/standard/deep routing, factual grounding, owner-intent fidelity, live-machinery grounding, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections and known PAUL failure classes. Add or refine adversarial/regression cases when current evidence exposes a repeatable weakness. If the cycle proves a deterministic regression or a clearly measurable intelligence improvement opportunity, launch exactly one focused canonical execute_objective improvement mission through current Prime authority, exact source scope, Gate, squash merge, affected-target release, and claim-matched runtime proof. Keep a change only when before/after evidence shows improvement without degrading other required invariants; otherwise reject or revert it. Never bypass Gate, never create parallel orchestration, never claim improvement from implementation alone, and never weaken tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Resource policy: do not materially interfere with normal KNOCKLAUNCH work; avoid sustained heavy compute on the owner's MSI laptop or desktop; honor live thermal, queue, runner, provider, and capacity signals; automatically reduce intensity or no-op under active owner-critical work or degraded capacity; prefer the large DigitalOcean runner only for genuinely heavy torture/adversarial evaluation. Keep inference and infrastructure cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval results, score and latency trends, failure clusters, attempted/accepted/rejected improvements, and exact production runtime lineage. This schedule remains an evaluation/improvement loop, not permission for unrelated product changes.","provenance":{"reason":"PAUL schedule 2dd5694d-fa6e-4538-bddd-725f850ede1f","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Start with non-mutating production-bound evals. Measure fast/standard/deep routing, factual grounding, owner-intent fidelity, live-machinery grounding, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections and known PAUL failure classes. Add or refine adversarial/regression cases when current evidence exposes a repeatable weakness. If the cycle proves a deterministic regression or a clearly measurable intelligence improvement opportunity, launch exactly one focused canonical execute_objective improvement mission through current Prime authority, exact source scope, Gate, squash merge, affected-target release, and claim-matched runtime proof. Keep a change only when before/after evidence shows improvement without degrading other required invariants; otherwise reject or revert it. Never bypass Gate, never create parallel orchestration, never claim improvement from implementation alone, and never weaken tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Resource policy: do not materially interfere with normal KNOCKLAUNCH work; avoid sustained heavy compute on the owner's MSI laptop or desktop; honor live thermal, queue, runner, provider, and capacity signals; automatically reduce intensity or no-op under active owner-critical work or degraded capacity; prefer the large DigitalOcean runner only for genuinely heavy torture/adversarial evaluation. Keep inference and infrastructure cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval results, score and latency trends, failure clusters, attempted/accepted/rejected improvements, and exact production runtime lineage. This schedule remains an evaluation/improvement loop, not permission for unrelated product changes.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Start with non-mutating production-bound evals. Measure fast/standard/deep routing, factual grounding, owner-intent fidelity, live-machinery grounding, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regression against durable owner corrections and known PAUL failure classes. Add or refine adversarial/regression cases when current evidence exposes a repeatable weakness. If the cycle proves a deterministic regression or a clearly measurable intelligence improvement opportunity, launch exactly one focused canonical execute_objective improvement mission through current Prime authority, exact source scope, Gate, squash merge, affected-target release, and claim-matched runtime proof. Keep a change only when before/after evidence shows improvement without degrading other required invariants; otherwise reject or revert it. Never bypass Gate, never create parallel orchestration, never claim improvement from implementation alone, and never weaken tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Resource policy: do not materially interfere with normal KNOCKLAUNCH work; avoid sustained heavy compute on the owner's MSI laptop or desktop; honor live thermal, queue, runner, provider, and capacity signals; automatically reduce intensity or no-op under active owner-critical work or degraded capacity; prefer the large DigitalOcean runner only for genuinely heavy torture/adversarial evaluation. Keep inference and infrastructure cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval results, score and latency trends, failure clusters, attempted/accepted/rejected improvements, and exact production runtime lineage. This schedule remains an evaluation/improvement loop, not permission for unrelated product changes.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"3bd0215e-3b1f-471b-a1f0-ade0a4f5f2d4","name":"Mandatory Gate Floor","cadence":"interval","enabled":false,"objective":"P0 owner invariant: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation MUST reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. Implementation, synthesis_required, reasoning_required, branch creation, or PR creation are NEVER acceptable resting or terminal states. The minimum acceptable nonterminal progress floor is Gate started/queued. If a mission can produce a deterministic change, it must automatically carry that change through branch/PR and into canonical Gate without waiting for owner follow-up. If it cannot reach Gate, it must transition immediately to a concrete BLOCKED state naming the first causal blocker, exact failed authority/action, and exact recovery path; it may not remain in synthesis_required, reasoning_required, implementation, or waiting. Preserve one mission/branch/PR, current-main freshness, tenant isolation, authorization, fail-closed behavior, Gate rigor, canonical merge/release ownership, and live proof requirements. Do not weaken QA to satisfy this invariant and do not invent fake/no-op changes just to create a Gate run. Sweep all currently nonterminal owner missions created today, especially Tennex IRSLogiqs Sync Repair, Mission Freedom Narrow Execution Facade, Owner Pipeline Conversation Contract, and Eliminate Synthesis Required. Automatically advance every legitimately mutable mission to canonical Gate now; for any that cannot, convert it to explicit BLOCKED with the real first causal blocker instead of leaving it in synthesis/implementation. Add regression coverage proving mutable owner missions cannot persist below Gate across scheduler cycles. Ship this invariant itself through canonical Forgejo Gate, squash merge, cc-execution release, and production proof.","created_at":"2026-10-02T21:05:00.179578+00:00","last_error":null,"updated_at":"2026-10-05T00:32:10.05+00:00","last_run_at":"2026-10-05T00:32:00.86606+00:00","last_status":"synthesis_required","next_run_at":"2026-10-05T00:33:00.86606+00:00","failure_count":33,"last_mission_id":"46c0b8e7-f7a7-4554-b922-8987b456413d","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"P0 owner invariant: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation MUST reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. Implementation, synthesis_required, reasoning_required, branch creation, or PR creation are NEVER acceptable resting or terminal states. The minimum acceptable nonterminal progress floor is Gate started/queued. If a mission can produce a deterministic change, it must automatically carry that change through branch/PR and into canonical Gate without waiting for owner follow-up. If it cannot reach Gate, it must transition immediately to a concrete BLOCKED state naming the first causal blocker, exact failed authority/action, and exact recovery path; it may not remain in synthesis_required, reasoning_required, implementation, or waiting. Preserve one mission/branch/PR, current-main freshness, tenant isolation, authorization, fail-closed behavior, Gate rigor, canonical merge/release ownership, and live proof requirements. Do not weaken QA to satisfy this invariant and do not invent fake/no-op changes just to create a Gate run. Sweep all currently nonterminal owner missions created today, especially Tennex IRSLogiqs Sync Repair, Mission Freedom Narrow Execution Facade, Owner Pipeline Conversation Contract, and Eliminate Synthesis Required. Automatically advance every legitimately mutable mission to canonical Gate now; for any that cannot, convert it to explicit BLOCKED with the real first causal blocker instead of leaving it in synthesis/implementation. Add regression coverage proving mutable owner missions cannot persist below Gate across scheduler cycles. Ship this invariant itself through canonical Forgejo Gate, squash merge, cc-execution release, and production proof.","wordingChanged":false,"canonicalIntent":"P0 owner invariant: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation MUST reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. Implementation, synthesis_required, reasoning_required, branch creation, or PR creation are NEVER acceptable resting or terminal states. The minimum acceptable nonterminal progress floor is Gate started/queued. If a mission can produce a deterministic change, it must automatically carry that change through branch/PR and into canonical Gate without waiting for owner follow-up. If it cannot reach Gate, it must transition immediately to a concrete BLOCKED state naming the first causal blocker, exact failed authority/action, and exact recovery path; it may not remain in synthesis_required, reasoning_required, implementation, or waiting. Preserve one mission/branch/PR, current-main freshness, tenant isolation, authorization, fail-closed behavior, Gate rigor, canonical merge/release ownership, and live proof requirements. Do not weaken QA to satisfy this invariant and do not invent fake/no-op changes just to create a Gate run. Sweep all currently nonterminal owner missions created today, especially Tennex IRSLogiqs Sync Repair, Mission Freedom Narrow Execution Facade, Owner Pipeline Conversation Contract, and Eliminate Synthesis Required. Automatically advance every legitimately mutable mission to canonical Gate now; for any that cannot, convert it to explicit BLOCKED with the real first causal blocker instead of leaving it in synthesis/implementation. Add regression coverage proving mutable owner missions cannot persist below Gate across scheduler cycles. Ship this invariant itself through canonical Forgejo Gate, squash merge, cc-execution release, and production proof.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"P0 owner invariant: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation MUST reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. Implementation, synthesis_required, reasoning_required, branch creation, or PR creation are NEVER acceptable resting or terminal states. The minimum acceptable nonterminal progress floor is Gate started/queued. If a mission can produce a deterministic change, it must automatically carry that change through branch/PR and into canonical Gate without waiting for owner follow-up. If it cannot reach Gate, it must transition immediately to a concrete BLOCKED state naming the first causal blocker, exact failed authority/action, and exact recovery path; it may not remain in synthesis_required, reasoning_required, implementation, or waiting. Preserve one mission/branch/PR, current-main freshness, tenant isolation, authorization, fail-closed behavior, Gate rigor, canonical merge/release ownership, and live proof requirements. Do not weaken QA to satisfy this invariant and do not invent fake/no-op changes just to create a Gate run. Sweep all currently nonterminal owner missions created today, especially Tennex IRSLogiqs Sync Repair, Mission Freedom Narrow Execution Facade, Owner Pipeline Conversation Contract, and Eliminate Synthesis Required. Automatically advance every legitimately mutable mission to canonical Gate now; for any that cannot, convert it to explicit BLOCKED with the real first causal blocker instead of leaving it in synthesis/implementation. Add regression coverage proving mutable owner missions cannot persist below Gate across scheduler cycles. Ship this invariant itself through canonical Forgejo Gate, squash merge, cc-execution release, and production proof.","provenance":{"reason":"PAUL schedule 3bd0215e-3b1f-471b-a1f0-ade0a4f5f2d4","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"P0 owner invariant: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation MUST reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. Implementation, synthesis_required, reasoning_required, branch creation, or PR creation are NEVER acceptable resting or terminal states. The minimum acceptable nonterminal progress floor is Gate started/queued. If a mission can produce a deterministic change, it must automatically carry that change through branch/PR and into canonical Gate without waiting for owner follow-up. If it cannot reach Gate, it must transition immediately to a concrete BLOCKED state naming the first causal blocker, exact failed authority/action, and exact recovery path; it may not remain in synthesis_required, reasoning_required, implementation, or waiting. Preserve one mission/branch/PR, current-main freshness, tenant isolation, authorization, fail-closed behavior, Gate rigor, canonical merge/release ownership, and live proof requirements. Do not weaken QA to satisfy this invariant and do not invent fake/no-op changes just to create a Gate run. Sweep all currently nonterminal owner missions created today, especially Tennex IRSLogiqs Sync Repair, Mission Freedom Narrow Execution Facade, Owner Pipeline Conversation Contract, and Eliminate Synthesis Required. Automatically advance every legitimately mutable mission to canonical Gate now; for any that cannot, convert it to explicit BLOCKED with the real first causal blocker instead of leaving it in synthesis/implementation. Add regression coverage proving mutable owner missions cannot persist below Gate across scheduler cycles. Ship this invariant itself through canonical Forgejo Gate, squash merge, cc-execution release, and production proof.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["workers/cc-execution/src/index-release-fast-lane.js","workers/cc-execution/src/index-mcp.js","workers/cc-execution/src/platform-sidekick-intelligence.js","workers/cc-execution/src/version.js","config/platform-sidekick-intelligence.json","config/paul-owner-profile.json","src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"P0 owner invariant: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation MUST reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. Implementation, synthesis_required, reasoning_required, branch creation, or PR creation are NEVER acceptable resting or terminal states. The minimum acceptable nonterminal progress floor is Gate started/queued. If a mission can produce a deterministic change, it must automatically carry that change through branch/PR and into canonical Gate without waiting for owner follow-up. If it cannot reach Gate, it must transition immediately to a concrete BLOCKED state naming the first causal blocker, exact failed authority/action, and exact recovery path; it may not remain in synthesis_required, reasoning_required, implementation, or waiting. Preserve one mission/branch/PR, current-main freshness, tenant isolation, authorization, fail-closed behavior, Gate rigor, canonical merge/release ownership, and live proof requirements. Do not weaken QA to satisfy this invariant and do not invent fake/no-op changes just to create a Gate run. Sweep all currently nonterminal owner missions created today, especially Tennex IRSLogiqs Sync Repair, Mission Freedom Narrow Execution Facade, Owner Pipeline Conversation Contract, and Eliminate Synthesis Required. Automatically advance every legitimately mutable mission to canonical Gate now; for any that cannot, convert it to explicit BLOCKED with the real first causal blocker instead of leaving it in synthesis/implementation. Add regression coverage proving mutable owner missions cannot persist below Gate across scheduler cycles. Ship this invariant itself through canonical Forgejo Gate, squash merge, cc-execution release, and production proof.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"3e5db595-e662-44db-a814-745393910fc9","name":"Owner Pipeline Conversation Contract","cadence":"interval","enabled":false,"objective":"Persist and operationalize the owner's KNOCKLAUNCH conversation pipeline contract across PAUL/Prime owner-facing execution summaries. Default owner pipeline stages: INTAKE -> TRUTH -> CAUSE -> PLAN -> IMPLEMENTATION -> GATE -> MERGE -> RELEASE -> PROOF -> DONE. Map live durable mission/PR/Gate/release/proof states into these stages. Preserve shorthand semantics: 'status' shows the pipeline and exact current stage; 'continue' advances the current nonterminal stage; 'hurry' chooses the shortest safe authoritative path without skipping required invariants; 'live?' answers only whether release plus live proof are complete; 'done?' is yes only when terminal production proof is satisfied. For multiple concurrent jobs, render separate pipeline cards with mission IDs/PRs/blockers and never collapse them into one ambiguous narrative. Conversation loss must not lose execution state: recover from durable mission receipts. Do not weaken Gate, tenant isolation, authorization, proof standards, or implementation quality. This is an owner-interface/summary contract, not a reduced QA profile. If there is an existing canonical owner-profile or sidekick instruction surface, persist there and add regression coverage; otherwise no-op and report exact missing owner source. Ship through canonical Gate/release/proof if source mutation is justified.","created_at":"2026-10-02T20:43:36.008402+00:00","last_error":null,"updated_at":"2026-10-05T00:32:11.198+00:00","last_run_at":"2026-10-05T00:32:00.86606+00:00","last_status":"cancelled","next_run_at":"2026-10-05T00:33:00.86606+00:00","failure_count":170,"last_mission_id":"37c87896-2f51-40e8-bb16-123635dc0151","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"Persist and operationalize the owner's KNOCKLAUNCH conversation pipeline contract across PAUL/Prime owner-facing execution summaries. Default owner pipeline stages: INTAKE -> TRUTH -> CAUSE -> PLAN -> IMPLEMENTATION -> GATE -> MERGE -> RELEASE -> PROOF -> DONE. Map live durable mission/PR/Gate/release/proof states into these stages. Preserve shorthand semantics: 'status' shows the pipeline and exact current stage; 'continue' advances the current nonterminal stage; 'hurry' chooses the shortest safe authoritative path without skipping required invariants; 'live?' answers only whether release plus live proof are complete; 'done?' is yes only when terminal production proof is satisfied. For multiple concurrent jobs, render separate pipeline cards with mission IDs/PRs/blockers and never collapse them into one ambiguous narrative. Conversation loss must not lose execution state: recover from durable mission receipts. Do not weaken Gate, tenant isolation, authorization, proof standards, or implementation quality. This is an owner-interface/summary contract, not a reduced QA profile. If there is an existing canonical owner-profile or sidekick instruction surface, persist there and add regression coverage; otherwise no-op and report exact missing owner source. Ship through canonical Gate/release/proof if source mutation is justified.","wordingChanged":false,"canonicalIntent":"Persist and operationalize the owner's KNOCKLAUNCH conversation pipeline contract across PAUL/Prime owner-facing execution summaries. Default owner pipeline stages: INTAKE -> TRUTH -> CAUSE -> PLAN -> IMPLEMENTATION -> GATE -> MERGE -> RELEASE -> PROOF -> DONE. Map live durable mission/PR/Gate/release/proof states into these stages. Preserve shorthand semantics: 'status' shows the pipeline and exact current stage; 'continue' advances the current nonterminal stage; 'hurry' chooses the shortest safe authoritative path without skipping required invariants; 'live?' answers only whether release plus live proof are complete; 'done?' is yes only when terminal production proof is satisfied. For multiple concurrent jobs, render separate pipeline cards with mission IDs/PRs/blockers and never collapse them into one ambiguous narrative. Conversation loss must not lose execution state: recover from durable mission receipts. Do not weaken Gate, tenant isolation, authorization, proof standards, or implementation quality. This is an owner-interface/summary contract, not a reduced QA profile. If there is an existing canonical owner-profile or sidekick instruction surface, persist there and add regression coverage; otherwise no-op and report exact missing owner source. Ship through canonical Gate/release/proof if source mutation is justified.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Persist and operationalize the owner's KNOCKLAUNCH conversation pipeline contract across PAUL/Prime owner-facing execution summaries. Default owner pipeline stages: INTAKE -> TRUTH -> CAUSE -> PLAN -> IMPLEMENTATION -> GATE -> MERGE -> RELEASE -> PROOF -> DONE. Map live durable mission/PR/Gate/release/proof states into these stages. Preserve shorthand semantics: 'status' shows the pipeline and exact current stage; 'continue' advances the current nonterminal stage; 'hurry' chooses the shortest safe authoritative path without skipping required invariants; 'live?' answers only whether release plus live proof are complete; 'done?' is yes only when terminal production proof is satisfied. For multiple concurrent jobs, render separate pipeline cards with mission IDs/PRs/blockers and never collapse them into one ambiguous narrative. Conversation loss must not lose execution state: recover from durable mission receipts. Do not weaken Gate, tenant isolation, authorization, proof standards, or implementation quality. This is an owner-interface/summary contract, not a reduced QA profile. If there is an existing canonical owner-profile or sidekick instruction surface, persist there and add regression coverage; otherwise no-op and report exact missing owner source. Ship through canonical Gate/release/proof if source mutation is justified.","provenance":{"reason":"PAUL schedule 3e5db595-e662-44db-a814-745393910fc9","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Persist and operationalize the owner's KNOCKLAUNCH conversation pipeline contract across PAUL/Prime owner-facing execution summaries. Default owner pipeline stages: INTAKE -> TRUTH -> CAUSE -> PLAN -> IMPLEMENTATION -> GATE -> MERGE -> RELEASE -> PROOF -> DONE. Map live durable mission/PR/Gate/release/proof states into these stages. Preserve shorthand semantics: 'status' shows the pipeline and exact current stage; 'continue' advances the current nonterminal stage; 'hurry' chooses the shortest safe authoritative path without skipping required invariants; 'live?' answers only whether release plus live proof are complete; 'done?' is yes only when terminal production proof is satisfied. For multiple concurrent jobs, render separate pipeline cards with mission IDs/PRs/blockers and never collapse them into one ambiguous narrative. Conversation loss must not lose execution state: recover from durable mission receipts. Do not weaken Gate, tenant isolation, authorization, proof standards, or implementation quality. This is an owner-interface/summary contract, not a reduced QA profile. If there is an existing canonical owner-profile or sidekick instruction surface, persist there and add regression coverage; otherwise no-op and report exact missing owner source. Ship through canonical Gate/release/proof if source mutation is justified.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["config/paul-owner-profile.json","config/platform-sidekick-intelligence.json","config/capabilities/platform-sidekick-intelligence.json","workers/cc-execution/src/platform-sidekick-intelligence.js","src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Persist and operationalize the owner's KNOCKLAUNCH conversation pipeline contract across PAUL/Prime owner-facing execution summaries. Default owner pipeline stages: INTAKE -> TRUTH -> CAUSE -> PLAN -> IMPLEMENTATION -> GATE -> MERGE -> RELEASE -> PROOF -> DONE. Map live durable mission/PR/Gate/release/proof states into these stages. Preserve shorthand semantics: 'status' shows the pipeline and exact current stage; 'continue' advances the current nonterminal stage; 'hurry' chooses the shortest safe authoritative path without skipping required invariants; 'live?' answers only whether release plus live proof are complete; 'done?' is yes only when terminal production proof is satisfied. For multiple concurrent jobs, render separate pipeline cards with mission IDs/PRs/blockers and never collapse them into one ambiguous narrative. Conversation loss must not lose execution state: recover from durable mission receipts. Do not weaken Gate, tenant isolation, authorization, proof standards, or implementation quality. This is an owner-interface/summary contract, not a reduced QA profile. If there is an existing canonical owner-profile or sidekick instruction surface, persist there and add regression coverage; otherwise no-op and report exact missing owner source. Ship through canonical Gate/release/proof if source mutation is justified.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"425136ae-bc4b-4415-94e2-860bfee01ed6","name":"Persist Mandatory Gate Owner Invariant","cadence":"interval","enabled":false,"objective":"Persist this owner invariant in PAUL/Prime owner-profile and execution doctrine: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation must automatically reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. synthesis_required, reasoning_required, implementation, branch-created, and PR-created are never acceptable resting or terminal states. If Gate cannot be reached, transition immediately to explicit BLOCKED with the first causal blocker, failed authority/action, and recovery path. Never require the owner to say continue merely to advance a mutable mission to Gate. Do not weaken QA, tenant isolation, authorization, one-mission/one-branch/one-PR discipline, merge/release ownership, or live-proof standards. Treat this as a standing owner preference/invariant across future PAUL missions and owner-facing pipeline summaries. Persist it in the canonical owner profile / sidekick intelligence config and add regression coverage if those sources own the behavior. Ship through Gate/release/proof if source mutation is required.","created_at":"2026-10-02T21:05:58.455513+00:00","last_error":null,"updated_at":"2026-10-05T00:32:10.849+00:00","last_run_at":"2026-10-05T00:32:00.86606+00:00","last_status":"verification_pending","next_run_at":"2026-10-05T00:33:00.86606+00:00","failure_count":16,"last_mission_id":"cb230edb-7b72-4c0d-9254-751eea2d9608","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"Persist this owner invariant in PAUL/Prime owner-profile and execution doctrine: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation must automatically reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. synthesis_required, reasoning_required, implementation, branch-created, and PR-created are never acceptable resting or terminal states. If Gate cannot be reached, transition immediately to explicit BLOCKED with the first causal blocker, failed authority/action, and recovery path. Never require the owner to say continue merely to advance a mutable mission to Gate. Do not weaken QA, tenant isolation, authorization, one-mission/one-branch/one-PR discipline, merge/release ownership, or live-proof standards. Treat this as a standing owner preference/invariant across future PAUL missions and owner-facing pipeline summaries. Persist it in the canonical owner profile / sidekick intelligence config and add regression coverage if those sources own the behavior. Ship through Gate/release/proof if source mutation is required.","wordingChanged":false,"canonicalIntent":"Persist this owner invariant in PAUL/Prime owner-profile and execution doctrine: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation must automatically reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. synthesis_required, reasoning_required, implementation, branch-created, and PR-created are never acceptable resting or terminal states. If Gate cannot be reached, transition immediately to explicit BLOCKED with the first causal blocker, failed authority/action, and recovery path. Never require the owner to say continue merely to advance a mutable mission to Gate. Do not weaken QA, tenant isolation, authorization, one-mission/one-branch/one-PR discipline, merge/release ownership, or live-proof standards. Treat this as a standing owner preference/invariant across future PAUL missions and owner-facing pipeline summaries. Persist it in the canonical owner profile / sidekick intelligence config and add regression coverage if those sources own the behavior. Ship through Gate/release/proof if source mutation is required.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Persist this owner invariant in PAUL/Prime owner-profile and execution doctrine: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation must automatically reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. synthesis_required, reasoning_required, implementation, branch-created, and PR-created are never acceptable resting or terminal states. If Gate cannot be reached, transition immediately to explicit BLOCKED with the first causal blocker, failed authority/action, and recovery path. Never require the owner to say continue merely to advance a mutable mission to Gate. Do not weaken QA, tenant isolation, authorization, one-mission/one-branch/one-PR discipline, merge/release ownership, or live-proof standards. Treat this as a standing owner preference/invariant across future PAUL missions and owner-facing pipeline summaries. Persist it in the canonical owner profile / sidekick intelligence config and add regression coverage if those sources own the behavior. Ship through Gate/release/proof if source mutation is required.","provenance":{"reason":"PAUL schedule 425136ae-bc4b-4415-94e2-860bfee01ed6","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Persist this owner invariant in PAUL/Prime owner-profile and execution doctrine: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation must automatically reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. synthesis_required, reasoning_required, implementation, branch-created, and PR-created are never acceptable resting or terminal states. If Gate cannot be reached, transition immediately to explicit BLOCKED with the first causal blocker, failed authority/action, and recovery path. Never require the owner to say continue merely to advance a mutable mission to Gate. Do not weaken QA, tenant isolation, authorization, one-mission/one-branch/one-PR discipline, merge/release ownership, or live-proof standards. Treat this as a standing owner preference/invariant across future PAUL missions and owner-facing pipeline summaries. Persist it in the canonical owner profile / sidekick intelligence config and add regression coverage if those sources own the behavior. Ship through Gate/release/proof if source mutation is required.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["config/paul-owner-profile.json","config/platform-sidekick-intelligence.json","config/capabilities/platform-sidekick-intelligence.json","workers/cc-execution/src/platform-sidekick-intelligence.js","src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Persist this owner invariant in PAUL/Prime owner-profile and execution doctrine: every owner-authorized KNOCKLAUNCH mission that requires source/config/runtime mutation must automatically reach canonical Forgejo Gate in the same durable mission unless a true external blocker makes Gate physically impossible. synthesis_required, reasoning_required, implementation, branch-created, and PR-created are never acceptable resting or terminal states. If Gate cannot be reached, transition immediately to explicit BLOCKED with the first causal blocker, failed authority/action, and recovery path. Never require the owner to say continue merely to advance a mutable mission to Gate. Do not weaken QA, tenant isolation, authorization, one-mission/one-branch/one-PR discipline, merge/release ownership, or live-proof standards. Treat this as a standing owner preference/invariant across future PAUL missions and owner-facing pipeline summaries. Persist it in the canonical owner profile / sidekick intelligence config and add regression coverage if those sources own the behavior. Ship through Gate/release/proof if source mutation is required.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"44da054c-1372-445d-ab78-b1262328ea63","name":"KNOCKLAUNCH Security Reliability Supervisor","cadence":"interval","enabled":false,"objective":"Run one bounded KNOCKLAUNCH production security reliability cycle. Begin read-only from current Prime live truth and current Supabase production truth. Verify these standing invariants: (1) Forgejo host watchdog remains independently installed, timer-active, and healthy; PAUL is not a dependency of Forgejo recovery. (2) verify-admin is ACTIVE, verify_jwt=true, validates the bearer, binds non-system-admin callers to self-inspection, and allows cross-user inspection only to a verified system admin. (3) upsert-tenant-provider-secret and verify-tenant-provider remain ACTIVE with verify_jwt=true and their existing tenant-owner/system-admin authorization. (4) emergency-control-plane-patch remains permanently retired: ACTIVE only as a fail-closed 410 endpoint, verify_jwt=true, with no hard-coded trigger, FGJ_CONTROL_TOKEN reference, or Forgejo API mutation path. (5) every public table with RLS enabled and zero policies has zero anon/authenticated table grants. (6) anonymous SECURITY DEFINER exposure does not increase above the current reviewed baseline without an explicitly justified public contract, and mutable function search_path warnings remain zero. (7) no runtime, auth, health, queue, deployment, recovery, or control-plane circular dependency is introduced. If all invariants hold, record a successful no-op and terminate cleanly. If a deterministic regression is proven and it is within the exact authorized sourceTargets, make the smallest repair through the same durable mission, canonical Forgejo Gate, squash merge, affected-target release, and claim-matched production proof. If the required repair is outside the exact sourceTargets, fail closed into explicit BLOCKED with the exact affected path and evidence rather than editing nearby files. Never weaken authentication, tenant isolation, RLS, service-role boundaries, Gate, or independent watchdog recovery.","created_at":"2026-10-05T00:30:27.468792+00:00","last_error":null,"updated_at":"2026-10-08T14:23:55.761+00:00","last_run_at":"2026-10-08T14:11:01.102083+00:00","last_status":"cancelled","next_run_at":"2026-10-08T14:26:01.102083+00:00","failure_count":397,"last_mission_id":null,"interval_minutes":15,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded KNOCKLAUNCH production security reliability cycle. Begin read-only from current Prime live truth and current Supabase production truth. Verify these standing invariants: (1) Forgejo host watchdog remains independently installed, timer-active, and healthy; PAUL is not a dependency of Forgejo recovery. (2) verify-admin is ACTIVE, verify_jwt=true, validates the bearer, binds non-system-admin callers to self-inspection, and allows cross-user inspection only to a verified system admin. (3) upsert-tenant-provider-secret and verify-tenant-provider remain ACTIVE with verify_jwt=true and their existing tenant-owner/system-admin authorization. (4) emergency-control-plane-patch remains permanently retired: ACTIVE only as a fail-closed 410 endpoint, verify_jwt=true, with no hard-coded trigger, FGJ_CONTROL_TOKEN reference, or Forgejo API mutation path. (5) every public table with RLS enabled and zero policies has zero anon/authenticated table grants. (6) anonymous SECURITY DEFINER exposure does not increase above the current reviewed baseline without an explicitly justified public contract, and mutable function search_path warnings remain zero. (7) no runtime, auth, health, queue, deployment, recovery, or control-plane circular dependency is introduced. If all invariants hold, record a successful no-op and terminate cleanly. If a deterministic regression is proven and it is within the exact authorized sourceTargets, make the smallest repair through the same durable mission, canonical Forgejo Gate, squash merge, affected-target release, and claim-matched production proof. If the required repair is outside the exact sourceTargets, fail closed into explicit BLOCKED with the exact affected path and evidence rather than editing nearby files. Never weaken authentication, tenant isolation, RLS, service-role boundaries, Gate, or independent watchdog recovery.","wordingChanged":false,"canonicalIntent":"Run one bounded KNOCKLAUNCH production security reliability cycle. Begin read-only from current Prime live truth and current Supabase production truth. Verify these standing invariants: (1) Forgejo host watchdog remains independently installed, timer-active, and healthy; PAUL is not a dependency of Forgejo recovery. (2) verify-admin is ACTIVE, verify_jwt=true, validates the bearer, binds non-system-admin callers to self-inspection, and allows cross-user inspection only to a verified system admin. (3) upsert-tenant-provider-secret and verify-tenant-provider remain ACTIVE with verify_jwt=true and their existing tenant-owner/system-admin authorization. (4) emergency-control-plane-patch remains permanently retired: ACTIVE only as a fail-closed 410 endpoint, verify_jwt=true, with no hard-coded trigger, FGJ_CONTROL_TOKEN reference, or Forgejo API mutation path. (5) every public table with RLS enabled and zero policies has zero anon/authenticated table grants. (6) anonymous SECURITY DEFINER exposure does not increase above the current reviewed baseline without an explicitly justified public contract, and mutable function search_path warnings remain zero. (7) no runtime, auth, health, queue, deployment, recovery, or control-plane circular dependency is introduced. If all invariants hold, record a successful no-op and terminate cleanly. If a deterministic regression is proven and it is within the exact authorized sourceTargets, make the smallest repair through the same durable mission, canonical Forgejo Gate, squash merge, affected-target release, and claim-matched production proof. If the required repair is outside the exact sourceTargets, fail closed into explicit BLOCKED with the exact affected path and evidence rather than editing nearby files. Never weaken authentication, tenant isolation, RLS, service-role boundaries, Gate, or independent watchdog recovery.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded KNOCKLAUNCH production security reliability cycle. Begin read-only from current Prime live truth and current Supabase production truth. Verify these standing invariants: (1) Forgejo host watchdog remains independently installed, timer-active, and healthy; PAUL is not a dependency of Forgejo recovery. (2) verify-admin is ACTIVE, verify_jwt=true, validates the bearer, binds non-system-admin callers to self-inspection, and allows cross-user inspection only to a verified system admin. (3) upsert-tenant-provider-secret and verify-tenant-provider remain ACTIVE with verify_jwt=true and their existing tenant-owner/system-admin authorization. (4) emergency-control-plane-patch remains permanently retired: ACTIVE only as a fail-closed 410 endpoint, verify_jwt=true, with no hard-coded trigger, FGJ_CONTROL_TOKEN reference, or Forgejo API mutation path. (5) every public table with RLS enabled and zero policies has zero anon/authenticated table grants. (6) anonymous SECURITY DEFINER exposure does not increase above the current reviewed baseline without an explicitly justified public contract, and mutable function search_path warnings remain zero. (7) no runtime, auth, health, queue, deployment, recovery, or control-plane circular dependency is introduced. If all invariants hold, record a successful no-op and terminate cleanly. If a deterministic regression is proven and it is within the exact authorized sourceTargets, make the smallest repair through the same durable mission, canonical Forgejo Gate, squash merge, affected-target release, and claim-matched production proof. If the required repair is outside the exact sourceTargets, fail closed into explicit BLOCKED with the exact affected path and evidence rather than editing nearby files. Never weaken authentication, tenant isolation, RLS, service-role boundaries, Gate, or independent watchdog recovery.","provenance":{"reason":"PAUL schedule 44da054c-1372-445d-ab78-b1262328ea63","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded KNOCKLAUNCH production security reliability cycle. Begin read-only from current Prime live truth and current Supabase production truth. Verify these standing invariants: (1) Forgejo host watchdog remains independently installed, timer-active, and healthy; PAUL is not a dependency of Forgejo recovery. (2) verify-admin is ACTIVE, verify_jwt=true, validates the bearer, binds non-system-admin callers to self-inspection, and allows cross-user inspection only to a verified system admin. (3) upsert-tenant-provider-secret and verify-tenant-provider remain ACTIVE with verify_jwt=true and their existing tenant-owner/system-admin authorization. (4) emergency-control-plane-patch remains permanently retired: ACTIVE only as a fail-closed 410 endpoint, verify_jwt=true, with no hard-coded trigger, FGJ_CONTROL_TOKEN reference, or Forgejo API mutation path. (5) every public table with RLS enabled and zero policies has zero anon/authenticated table grants. (6) anonymous SECURITY DEFINER exposure does not increase above the current reviewed baseline without an explicitly justified public contract, and mutable function search_path warnings remain zero. (7) no runtime, auth, health, queue, deployment, recovery, or control-plane circular dependency is introduced. If all invariants hold, record a successful no-op and terminate cleanly. If a deterministic regression is proven and it is within the exact authorized sourceTargets, make the smallest repair through the same durable mission, canonical Forgejo Gate, squash merge, affected-target release, and claim-matched production proof. If the required repair is outside the exact sourceTargets, fail closed into explicit BLOCKED with the exact affected path and evidence rather than editing nearby files. Never weaken authentication, tenant isolation, RLS, service-role boundaries, Gate, or independent watchdog recovery.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["supabase/config.toml","supabase/functions/verify-admin/index.ts","supabase/functions/emergency-control-plane-patch/index.ts","config/capabilities/emergency-control-plane-patch-retired.json"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded KNOCKLAUNCH production security reliability cycle. Begin read-only from current Prime live truth and current Supabase production truth. Verify these standing invariants: (1) Forgejo host watchdog remains independently installed, timer-active, and healthy; PAUL is not a dependency of Forgejo recovery. (2) verify-admin is ACTIVE, verify_jwt=true, validates the bearer, binds non-system-admin callers to self-inspection, and allows cross-user inspection only to a verified system admin. (3) upsert-tenant-provider-secret and verify-tenant-provider remain ACTIVE with verify_jwt=true and their existing tenant-owner/system-admin authorization. (4) emergency-control-plane-patch remains permanently retired: ACTIVE only as a fail-closed 410 endpoint, verify_jwt=true, with no hard-coded trigger, FGJ_CONTROL_TOKEN reference, or Forgejo API mutation path. (5) every public table with RLS enabled and zero policies has zero anon/authenticated table grants. (6) anonymous SECURITY DEFINER exposure does not increase above the current reviewed baseline without an explicitly justified public contract, and mutable function search_path warnings remain zero. (7) no runtime, auth, health, queue, deployment, recovery, or control-plane circular dependency is introduced. If all invariants hold, record a successful no-op and terminate cleanly. If a deterministic regression is proven and it is within the exact authorized sourceTargets, make the smallest repair through the same durable mission, canonical Forgejo Gate, squash merge, affected-target release, and claim-matched production proof. If the required repair is outside the exact sourceTargets, fail closed into explicit BLOCKED with the exact affected path and evidence rather than editing nearby files. Never weaken authentication, tenant isolation, RLS, service-role boundaries, Gate, or independent watchdog recovery.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"5fc5d10b-94a6-495c-afc3-e7932f4ff9b8","name":"Mission Freedom Narrow Execution Facade","cadence":"interval","enabled":false,"objective":"Run one bounded owner-authorized Mission Freedom repair cycle. The outcome is to remove ChatGPT broad natural-language mutation calls from the critical write path without creating a second orchestration system. Inspect current cc-execution source within the exact source scope below. Reuse the existing canonical durable mission ledger, repository_patch_scoped mutation primitive, Forgejo Gate, squash merge, unified release supervisor, and production proof. Add first-class authenticated structured commands to the public Prime command registry for exact bounded mutation continuation: (1) apply an exact repository patch with exact path/base SHA/mission identity, (2) continue an existing durable mission with an exact structured continuation payload, and (3) advance a verified mission through Gate/release using exact PR/head SHA identifiers. Keep execute_objective as the high-level convenience path, but these structured commands must not require a fresh natural-language synthesis step after owner authorization. Require fail-closed identifier validation, tenant/owner authorization, idempotency where applicable, durable receipts, and capability-registry documentation. Do not expose arbitrary shell execution, do not create a parallel queue/release system, and do not weaken any safety invariant. Add focused regression coverage. Ship through canonical Gate, squash merge, affected-target release, and verify production command_center_capabilities lists the new commands and that one non-destructive canary structured continuation succeeds end-to-end. If exact ownership within the authorized source scope cannot be proven, no-op and record the exact missing source instead of editing nearby files.","created_at":"2026-10-02T20:41:19.333681+00:00","last_error":null,"updated_at":"2026-10-02T22:58:36.614+00:00","last_run_at":"2026-10-02T22:57:00.488064+00:00","last_status":"cancelled","next_run_at":"2026-10-02T22:58:00.488064+00:00","failure_count":1,"last_mission_id":"9ba94704-e0ca-43ba-b0a1-83d9b1c8195d","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded owner-authorized Mission Freedom repair cycle. The outcome is to remove ChatGPT broad natural-language mutation calls from the critical write path without creating a second orchestration system. Inspect current cc-execution source within the exact source scope below. Reuse the existing canonical durable mission ledger, repository_patch_scoped mutation primitive, Forgejo Gate, squash merge, unified release supervisor, and production proof. Add first-class authenticated structured commands to the public Prime command registry for exact bounded mutation continuation: (1) apply an exact repository patch with exact path/base SHA/mission identity, (2) continue an existing durable mission with an exact structured continuation payload, and (3) advance a verified mission through Gate/release using exact PR/head SHA identifiers. Keep execute_objective as the high-level convenience path, but these structured commands must not require a fresh natural-language synthesis step after owner authorization. Require fail-closed identifier validation, tenant/owner authorization, idempotency where applicable, durable receipts, and capability-registry documentation. Do not expose arbitrary shell execution, do not create a parallel queue/release system, and do not weaken any safety invariant. Add focused regression coverage. Ship through canonical Gate, squash merge, affected-target release, and verify production command_center_capabilities lists the new commands and that one non-destructive canary structured continuation succeeds end-to-end. If exact ownership within the authorized source scope cannot be proven, no-op and record the exact missing source instead of editing nearby files.","wordingChanged":false,"canonicalIntent":"Run one bounded owner-authorized Mission Freedom repair cycle. The outcome is to remove ChatGPT broad natural-language mutation calls from the critical write path without creating a second orchestration system. Inspect current cc-execution source within the exact source scope below. Reuse the existing canonical durable mission ledger, repository_patch_scoped mutation primitive, Forgejo Gate, squash merge, unified release supervisor, and production proof. Add first-class authenticated structured commands to the public Prime command registry for exact bounded mutation continuation: (1) apply an exact repository patch with exact path/base SHA/mission identity, (2) continue an existing durable mission with an exact structured continuation payload, and (3) advance a verified mission through Gate/release using exact PR/head SHA identifiers. Keep execute_objective as the high-level convenience path, but these structured commands must not require a fresh natural-language synthesis step after owner authorization. Require fail-closed identifier validation, tenant/owner authorization, idempotency where applicable, durable receipts, and capability-registry documentation. Do not expose arbitrary shell execution, do not create a parallel queue/release system, and do not weaken any safety invariant. Add focused regression coverage. Ship through canonical Gate, squash merge, affected-target release, and verify production command_center_capabilities lists the new commands and that one non-destructive canary structured continuation succeeds end-to-end. If exact ownership within the authorized source scope cannot be proven, no-op and record the exact missing source instead of editing nearby files.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded owner-authorized Mission Freedom repair cycle. The outcome is to remove ChatGPT broad natural-language mutation calls from the critical write path without creating a second orchestration system. Inspect current cc-execution source within the exact source scope below. Reuse the existing canonical durable mission ledger, repository_patch_scoped mutation primitive, Forgejo Gate, squash merge, unified release supervisor, and production proof. Add first-class authenticated structured commands to the public Prime command registry for exact bounded mutation continuation: (1) apply an exact repository patch with exact path/base SHA/mission identity, (2) continue an existing durable mission with an exact structured continuation payload, and (3) advance a verified mission through Gate/release using exact PR/head SHA identifiers. Keep execute_objective as the high-level convenience path, but these structured commands must not require a fresh natural-language synthesis step after owner authorization. Require fail-closed identifier validation, tenant/owner authorization, idempotency where applicable, durable receipts, and capability-registry documentation. Do not expose arbitrary shell execution, do not create a parallel queue/release system, and do not weaken any safety invariant. Add focused regression coverage. Ship through canonical Gate, squash merge, affected-target release, and verify production command_center_capabilities lists the new commands and that one non-destructive canary structured continuation succeeds end-to-end. If exact ownership within the authorized source scope cannot be proven, no-op and record the exact missing source instead of editing nearby files.","provenance":{"reason":"PAUL schedule 5fc5d10b-94a6-495c-afc3-e7932f4ff9b8","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded owner-authorized Mission Freedom repair cycle. The outcome is to remove ChatGPT broad natural-language mutation calls from the critical write path without creating a second orchestration system. Inspect current cc-execution source within the exact source scope below. Reuse the existing canonical durable mission ledger, repository_patch_scoped mutation primitive, Forgejo Gate, squash merge, unified release supervisor, and production proof. Add first-class authenticated structured commands to the public Prime command registry for exact bounded mutation continuation: (1) apply an exact repository patch with exact path/base SHA/mission identity, (2) continue an existing durable mission with an exact structured continuation payload, and (3) advance a verified mission through Gate/release using exact PR/head SHA identifiers. Keep execute_objective as the high-level convenience path, but these structured commands must not require a fresh natural-language synthesis step after owner authorization. Require fail-closed identifier validation, tenant/owner authorization, idempotency where applicable, durable receipts, and capability-registry documentation. Do not expose arbitrary shell execution, do not create a parallel queue/release system, and do not weaken any safety invariant. Add focused regression coverage. Ship through canonical Gate, squash merge, affected-target release, and verify production command_center_capabilities lists the new commands and that one non-destructive canary structured continuation succeeds end-to-end. If exact ownership within the authorized source scope cannot be proven, no-op and record the exact missing source instead of editing nearby files.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["workers/cc-execution/src/index-release-fast-lane.js","workers/cc-execution/src/index-mcp.js","workers/cc-execution/src/version.js","config/capabilities/platform-sidekick-intelligence.json"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded owner-authorized Mission Freedom repair cycle. The outcome is to remove ChatGPT broad natural-language mutation calls from the critical write path without creating a second orchestration system. Inspect current cc-execution source within the exact source scope below. Reuse the existing canonical durable mission ledger, repository_patch_scoped mutation primitive, Forgejo Gate, squash merge, unified release supervisor, and production proof. Add first-class authenticated structured commands to the public Prime command registry for exact bounded mutation continuation: (1) apply an exact repository patch with exact path/base SHA/mission identity, (2) continue an existing durable mission with an exact structured continuation payload, and (3) advance a verified mission through Gate/release using exact PR/head SHA identifiers. Keep execute_objective as the high-level convenience path, but these structured commands must not require a fresh natural-language synthesis step after owner authorization. Require fail-closed identifier validation, tenant/owner authorization, idempotency where applicable, durable receipts, and capability-registry documentation. Do not expose arbitrary shell execution, do not create a parallel queue/release system, and do not weaken any safety invariant. Add focused regression coverage. Ship through canonical Gate, squash merge, affected-target release, and verify production command_center_capabilities lists the new commands and that one non-destructive canary structured continuation succeeds end-to-end. If exact ownership within the authorized source scope cannot be proven, no-op and record the exact missing source instead of editing nearby files.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"7335281c-bd3d-4aef-8016-6ab29cb466e1","name":"PAUL Continuous Intelligence Lab","cadence":"interval","enabled":false,"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production stack. Begin read-only. Run representative production PAUL evaluations across fast, standard, and deep reasoning, including owner-realistic correction recovery, direct awareness questions, current/live-state reads, greetings while durable work is running, profanity/urgency semantics, tool-argument grounding, tenant isolation, memory/context selection, ambiguity handling, hallucination resistance, completion-proof discipline, and latency. Inspect the actual returned answer/tool-call text for false greens; never accept a numeric pass when the owner-visible response still violates the intended behavior. Compare results to current main/runtime truth and durable owner corrections. If and only if evidence proves one deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused repair within the authorized PAUL source scope, add or strengthen a regression case for the proven failure, pass canonical Gate, squash merge, release only affected targets, and verify the live production behavior. If no change is justified, record a successful no-op evaluation and terminate cleanly. Do not broaden source scope without machine-readable dependency evidence. Never bypass tenant isolation, authorization, owner-intent fidelity, Gate, release ownership, or terminal proof. Do not materially interfere with active owner-critical work: read current queue/capacity/thermal/runtime state first, reduce intensity or no-op when capacity is constrained, avoid sustained heavy compute on owner MSI hardware, and use available KNOCKLAUNCH cloud/DigitalOcean heavy capacity only when genuinely needed. Keep cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval outcomes, false-green findings, accepted/rejected improvements, latency/score trends, and exact runtime lineage.","created_at":"2026-09-30T21:25:07.101674+00:00","last_error":null,"updated_at":"2026-10-08T14:23:58.864+00:00","last_run_at":"2026-10-08T14:11:01.102083+00:00","last_status":"cancelled","next_run_at":"2026-10-08T18:11:01.102083+00:00","failure_count":371,"last_mission_id":null,"interval_minutes":240,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production stack. Begin read-only. Run representative production PAUL evaluations across fast, standard, and deep reasoning, including owner-realistic correction recovery, direct awareness questions, current/live-state reads, greetings while durable work is running, profanity/urgency semantics, tool-argument grounding, tenant isolation, memory/context selection, ambiguity handling, hallucination resistance, completion-proof discipline, and latency. Inspect the actual returned answer/tool-call text for false greens; never accept a numeric pass when the owner-visible response still violates the intended behavior. Compare results to current main/runtime truth and durable owner corrections. If and only if evidence proves one deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused repair within the authorized PAUL source scope, add or strengthen a regression case for the proven failure, pass canonical Gate, squash merge, release only affected targets, and verify the live production behavior. If no change is justified, record a successful no-op evaluation and terminate cleanly. Do not broaden source scope without machine-readable dependency evidence. Never bypass tenant isolation, authorization, owner-intent fidelity, Gate, release ownership, or terminal proof. Do not materially interfere with active owner-critical work: read current queue/capacity/thermal/runtime state first, reduce intensity or no-op when capacity is constrained, avoid sustained heavy compute on owner MSI hardware, and use available KNOCKLAUNCH cloud/DigitalOcean heavy capacity only when genuinely needed. Keep cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval outcomes, false-green findings, accepted/rejected improvements, latency/score trends, and exact runtime lineage.","wordingChanged":false,"canonicalIntent":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production stack. Begin read-only. Run representative production PAUL evaluations across fast, standard, and deep reasoning, including owner-realistic correction recovery, direct awareness questions, current/live-state reads, greetings while durable work is running, profanity/urgency semantics, tool-argument grounding, tenant isolation, memory/context selection, ambiguity handling, hallucination resistance, completion-proof discipline, and latency. Inspect the actual returned answer/tool-call text for false greens; never accept a numeric pass when the owner-visible response still violates the intended behavior. Compare results to current main/runtime truth and durable owner corrections. If and only if evidence proves one deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused repair within the authorized PAUL source scope, add or strengthen a regression case for the proven failure, pass canonical Gate, squash merge, release only affected targets, and verify the live production behavior. If no change is justified, record a successful no-op evaluation and terminate cleanly. Do not broaden source scope without machine-readable dependency evidence. Never bypass tenant isolation, authorization, owner-intent fidelity, Gate, release ownership, or terminal proof. Do not materially interfere with active owner-critical work: read current queue/capacity/thermal/runtime state first, reduce intensity or no-op when capacity is constrained, avoid sustained heavy compute on owner MSI hardware, and use available KNOCKLAUNCH cloud/DigitalOcean heavy capacity only when genuinely needed. Keep cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval outcomes, false-green findings, accepted/rejected improvements, latency/score trends, and exact runtime lineage.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production stack. Begin read-only. Run representative production PAUL evaluations across fast, standard, and deep reasoning, including owner-realistic correction recovery, direct awareness questions, current/live-state reads, greetings while durable work is running, profanity/urgency semantics, tool-argument grounding, tenant isolation, memory/context selection, ambiguity handling, hallucination resistance, completion-proof discipline, and latency. Inspect the actual returned answer/tool-call text for false greens; never accept a numeric pass when the owner-visible response still violates the intended behavior. Compare results to current main/runtime truth and durable owner corrections. If and only if evidence proves one deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused repair within the authorized PAUL source scope, add or strengthen a regression case for the proven failure, pass canonical Gate, squash merge, release only affected targets, and verify the live production behavior. If no change is justified, record a successful no-op evaluation and terminate cleanly. Do not broaden source scope without machine-readable dependency evidence. Never bypass tenant isolation, authorization, owner-intent fidelity, Gate, release ownership, or terminal proof. Do not materially interfere with active owner-critical work: read current queue/capacity/thermal/runtime state first, reduce intensity or no-op when capacity is constrained, avoid sustained heavy compute on owner MSI hardware, and use available KNOCKLAUNCH cloud/DigitalOcean heavy capacity only when genuinely needed. Keep cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval outcomes, false-green findings, accepted/rejected improvements, latency/score trends, and exact runtime lineage.","provenance":{"reason":"PAUL schedule 7335281c-bd3d-4aef-8016-6ab29cb466e1","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production stack. Begin read-only. Run representative production PAUL evaluations across fast, standard, and deep reasoning, including owner-realistic correction recovery, direct awareness questions, current/live-state reads, greetings while durable work is running, profanity/urgency semantics, tool-argument grounding, tenant isolation, memory/context selection, ambiguity handling, hallucination resistance, completion-proof discipline, and latency. Inspect the actual returned answer/tool-call text for false greens; never accept a numeric pass when the owner-visible response still violates the intended behavior. Compare results to current main/runtime truth and durable owner corrections. If and only if evidence proves one deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused repair within the authorized PAUL source scope, add or strengthen a regression case for the proven failure, pass canonical Gate, squash merge, release only affected targets, and verify the live production behavior. If no change is justified, record a successful no-op evaluation and terminate cleanly. Do not broaden source scope without machine-readable dependency evidence. Never bypass tenant isolation, authorization, owner-intent fidelity, Gate, release ownership, or terminal proof. Do not materially interfere with active owner-critical work: read current queue/capacity/thermal/runtime state first, reduce intensity or no-op when capacity is constrained, avoid sustained heavy compute on owner MSI hardware, and use available KNOCKLAUNCH cloud/DigitalOcean heavy capacity only when genuinely needed. Keep cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval outcomes, false-green findings, accepted/rejected improvements, latency/score trends, and exact runtime lineage.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["workers/cc-execution/src/platform-sidekick-intelligence.js","workers/cc-execution/src/model-provider-gateway.js","workers/cc-execution/src/index-mcp.js","workers/cc-execution/src/version.js","supabase/functions/operator-respond/index.ts","supabase/functions/operator-respond/paul-memory.ts","supabase/functions/operator-respond/paul-owner-profile.ts","src/pages/admin/GodModeCommandConsole.tsx","config/platform-sidekick-intelligence.json","config/paul-owner-profile.json","src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts","src/__tests__/contracts/mobile-admin-console-authority.contract.test.ts"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production stack. Begin read-only. Run representative production PAUL evaluations across fast, standard, and deep reasoning, including owner-realistic correction recovery, direct awareness questions, current/live-state reads, greetings while durable work is running, profanity/urgency semantics, tool-argument grounding, tenant isolation, memory/context selection, ambiguity handling, hallucination resistance, completion-proof discipline, and latency. Inspect the actual returned answer/tool-call text for false greens; never accept a numeric pass when the owner-visible response still violates the intended behavior. Compare results to current main/runtime truth and durable owner corrections. If and only if evidence proves one deterministic regression or clearly measurable intelligence improvement opportunity, make exactly one focused repair within the authorized PAUL source scope, add or strengthen a regression case for the proven failure, pass canonical Gate, squash merge, release only affected targets, and verify the live production behavior. If no change is justified, record a successful no-op evaluation and terminate cleanly. Do not broaden source scope without machine-readable dependency evidence. Never bypass tenant isolation, authorization, owner-intent fidelity, Gate, release ownership, or terminal proof. Do not materially interfere with active owner-critical work: read current queue/capacity/thermal/runtime state first, reduce intensity or no-op when capacity is constrained, avoid sustained heavy compute on owner MSI hardware, and use available KNOCKLAUNCH cloud/DigitalOcean heavy capacity only when genuinely needed. Keep cost bounded. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as replaceable fallback. Record durable eval outcomes, false-green findings, accepted/rejected improvements, latency/score trends, and exact runtime lineage.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"7e9f779e-0ef9-45db-9695-c0abff1ba034","name":"Eliminate Synthesis Required","cadence":"interval","enabled":false,"objective":"P0 owner invariant: no durable KNOCKLAUNCH mission may remain in synthesis_required. Treat synthesis_required as a transient internal compiler state with a bounded automatic continuation, never an owner-visible resting state. Inspect current mission compiler/scheduler/continuation logic and repair the canonical Prime path so that when a mission reaches synthesis_required it must immediately do one of the following within the same durable mission: synthesize and continue to implementation, retry once through the authoritative reasoning path, or transition to a concrete blocked state that names the first causal blocker and exact required recovery action. It must never remain indefinitely at synthesis_required and must never require the owner to say continue just to escape that state. Apply this invariant to scheduled PAUL jobs as well as interactive owner missions. Preserve one-mission/one-branch/one-PR discipline, tenant isolation, Gate, merge, release, proof, and fail-closed behavior. Do not create a parallel orchestrator. Add regression coverage proving synthesis_required cannot persist across scheduler cycles. Also sweep currently nonterminal missions created by these schedules and advance any that are presently synthesis_required: Mission Freedom Narrow Execution Facade, Tennex IRSLogiqs Sync Repair, and Owner Pipeline Conversation Contract. Ship through canonical Forgejo Gate, squash merge, cc-execution release, and prove on production by showing those current missions no longer resting at synthesis_required and a canary mission auto-advancing past synthesis_required without owner input.","created_at":"2026-10-02T20:52:05.57686+00:00","last_error":null,"updated_at":"2026-10-05T00:32:12.746+00:00","last_run_at":"2026-10-05T00:32:00.86606+00:00","last_status":"synthesis_required","next_run_at":"2026-10-05T00:33:00.86606+00:00","failure_count":24,"last_mission_id":"7ad6128b-c1cd-4777-a3cc-985b02e9379b","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"P0 owner invariant: no durable KNOCKLAUNCH mission may remain in synthesis_required. Treat synthesis_required as a transient internal compiler state with a bounded automatic continuation, never an owner-visible resting state. Inspect current mission compiler/scheduler/continuation logic and repair the canonical Prime path so that when a mission reaches synthesis_required it must immediately do one of the following within the same durable mission: synthesize and continue to implementation, retry once through the authoritative reasoning path, or transition to a concrete blocked state that names the first causal blocker and exact required recovery action. It must never remain indefinitely at synthesis_required and must never require the owner to say continue just to escape that state. Apply this invariant to scheduled PAUL jobs as well as interactive owner missions. Preserve one-mission/one-branch/one-PR discipline, tenant isolation, Gate, merge, release, proof, and fail-closed behavior. Do not create a parallel orchestrator. Add regression coverage proving synthesis_required cannot persist across scheduler cycles. Also sweep currently nonterminal missions created by these schedules and advance any that are presently synthesis_required: Mission Freedom Narrow Execution Facade, Tennex IRSLogiqs Sync Repair, and Owner Pipeline Conversation Contract. Ship through canonical Forgejo Gate, squash merge, cc-execution release, and prove on production by showing those current missions no longer resting at synthesis_required and a canary mission auto-advancing past synthesis_required without owner input.","wordingChanged":false,"canonicalIntent":"P0 owner invariant: no durable KNOCKLAUNCH mission may remain in synthesis_required. Treat synthesis_required as a transient internal compiler state with a bounded automatic continuation, never an owner-visible resting state. Inspect current mission compiler/scheduler/continuation logic and repair the canonical Prime path so that when a mission reaches synthesis_required it must immediately do one of the following within the same durable mission: synthesize and continue to implementation, retry once through the authoritative reasoning path, or transition to a concrete blocked state that names the first causal blocker and exact required recovery action. It must never remain indefinitely at synthesis_required and must never require the owner to say continue just to escape that state. Apply this invariant to scheduled PAUL jobs as well as interactive owner missions. Preserve one-mission/one-branch/one-PR discipline, tenant isolation, Gate, merge, release, proof, and fail-closed behavior. Do not create a parallel orchestrator. Add regression coverage proving synthesis_required cannot persist across scheduler cycles. Also sweep currently nonterminal missions created by these schedules and advance any that are presently synthesis_required: Mission Freedom Narrow Execution Facade, Tennex IRSLogiqs Sync Repair, and Owner Pipeline Conversation Contract. Ship through canonical Forgejo Gate, squash merge, cc-execution release, and prove on production by showing those current missions no longer resting at synthesis_required and a canary mission auto-advancing past synthesis_required without owner input.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"P0 owner invariant: no durable KNOCKLAUNCH mission may remain in synthesis_required. Treat synthesis_required as a transient internal compiler state with a bounded automatic continuation, never an owner-visible resting state. Inspect current mission compiler/scheduler/continuation logic and repair the canonical Prime path so that when a mission reaches synthesis_required it must immediately do one of the following within the same durable mission: synthesize and continue to implementation, retry once through the authoritative reasoning path, or transition to a concrete blocked state that names the first causal blocker and exact required recovery action. It must never remain indefinitely at synthesis_required and must never require the owner to say continue just to escape that state. Apply this invariant to scheduled PAUL jobs as well as interactive owner missions. Preserve one-mission/one-branch/one-PR discipline, tenant isolation, Gate, merge, release, proof, and fail-closed behavior. Do not create a parallel orchestrator. Add regression coverage proving synthesis_required cannot persist across scheduler cycles. Also sweep currently nonterminal missions created by these schedules and advance any that are presently synthesis_required: Mission Freedom Narrow Execution Facade, Tennex IRSLogiqs Sync Repair, and Owner Pipeline Conversation Contract. Ship through canonical Forgejo Gate, squash merge, cc-execution release, and prove on production by showing those current missions no longer resting at synthesis_required and a canary mission auto-advancing past synthesis_required without owner input.","provenance":{"reason":"PAUL schedule 7e9f779e-0ef9-45db-9695-c0abff1ba034","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"P0 owner invariant: no durable KNOCKLAUNCH mission may remain in synthesis_required. Treat synthesis_required as a transient internal compiler state with a bounded automatic continuation, never an owner-visible resting state. Inspect current mission compiler/scheduler/continuation logic and repair the canonical Prime path so that when a mission reaches synthesis_required it must immediately do one of the following within the same durable mission: synthesize and continue to implementation, retry once through the authoritative reasoning path, or transition to a concrete blocked state that names the first causal blocker and exact required recovery action. It must never remain indefinitely at synthesis_required and must never require the owner to say continue just to escape that state. Apply this invariant to scheduled PAUL jobs as well as interactive owner missions. Preserve one-mission/one-branch/one-PR discipline, tenant isolation, Gate, merge, release, proof, and fail-closed behavior. Do not create a parallel orchestrator. Add regression coverage proving synthesis_required cannot persist across scheduler cycles. Also sweep currently nonterminal missions created by these schedules and advance any that are presently synthesis_required: Mission Freedom Narrow Execution Facade, Tennex IRSLogiqs Sync Repair, and Owner Pipeline Conversation Contract. Ship through canonical Forgejo Gate, squash merge, cc-execution release, and prove on production by showing those current missions no longer resting at synthesis_required and a canary mission auto-advancing past synthesis_required without owner input.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["workers/cc-execution/src/index-release-fast-lane.js","workers/cc-execution/src/index-mcp.js","workers/cc-execution/src/platform-sidekick-intelligence.js","workers/cc-execution/src/version.js","config/platform-sidekick-intelligence.json","config/paul-owner-profile.json","src/__tests__/contracts/platform-sidekick-intelligence.contract.test.ts"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"P0 owner invariant: no durable KNOCKLAUNCH mission may remain in synthesis_required. Treat synthesis_required as a transient internal compiler state with a bounded automatic continuation, never an owner-visible resting state. Inspect current mission compiler/scheduler/continuation logic and repair the canonical Prime path so that when a mission reaches synthesis_required it must immediately do one of the following within the same durable mission: synthesize and continue to implementation, retry once through the authoritative reasoning path, or transition to a concrete blocked state that names the first causal blocker and exact required recovery action. It must never remain indefinitely at synthesis_required and must never require the owner to say continue just to escape that state. Apply this invariant to scheduled PAUL jobs as well as interactive owner missions. Preserve one-mission/one-branch/one-PR discipline, tenant isolation, Gate, merge, release, proof, and fail-closed behavior. Do not create a parallel orchestrator. Add regression coverage proving synthesis_required cannot persist across scheduler cycles. Also sweep currently nonterminal missions created by these schedules and advance any that are presently synthesis_required: Mission Freedom Narrow Execution Facade, Tennex IRSLogiqs Sync Repair, and Owner Pipeline Conversation Contract. Ship through canonical Forgejo Gate, squash merge, cc-execution release, and prove on production by showing those current missions no longer resting at synthesis_required and a canary mission auto-advancing past synthesis_required without owner input.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"9e6853d8-fb5d-417c-b81b-ed2567d4718b","name":"P0 Internal Auto-Synthesis Continuation","cadence":"interval","enabled":false,"objective":"P0: eliminate the remaining external synthesis hop for durable mutable missions. The exact defect is in cc-execution mission control: after authoritative source resolution, a synthesis_required mission can still return operator_synthesize_and_resume_same_mission and wait for an external caller to author anchored edits. Repair the canonical path so cc-execution internally performs one bounded PAUL structured synthesis from the exact current source bundle, validates returned anchored edits against exact source/current-main identity and authorized paths, persists/reuses the same durable mission/branch, and immediately resumes canonical mutation. On inference/provider/schema/anchor failure after one bounded attempt, transition to explicit BLOCKED with the first causal blocker; never leave the mission resting at synthesis_required or implementation_payload_required. Preserve one mission/branch/PR, authorization, tenant isolation, repository_patch_scoped, Gate, merge, release and proof. Add focused regression coverage. Ship through canonical Gate, squash merge, cc-execution release and runtime proof.","created_at":"2026-10-02T23:03:25.046592+00:00","last_error":null,"updated_at":"2026-10-08T14:23:42.629+00:00","last_run_at":"2026-10-08T14:23:00.765909+00:00","last_status":"cancelled","next_run_at":"2026-10-08T14:24:00.765909+00:00","failure_count":431,"last_mission_id":null,"interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"P0: eliminate the remaining external synthesis hop for durable mutable missions. The exact defect is in cc-execution mission control: after authoritative source resolution, a synthesis_required mission can still return operator_synthesize_and_resume_same_mission and wait for an external caller to author anchored edits. Repair the canonical path so cc-execution internally performs one bounded PAUL structured synthesis from the exact current source bundle, validates returned anchored edits against exact source/current-main identity and authorized paths, persists/reuses the same durable mission/branch, and immediately resumes canonical mutation. On inference/provider/schema/anchor failure after one bounded attempt, transition to explicit BLOCKED with the first causal blocker; never leave the mission resting at synthesis_required or implementation_payload_required. Preserve one mission/branch/PR, authorization, tenant isolation, repository_patch_scoped, Gate, merge, release and proof. Add focused regression coverage. Ship through canonical Gate, squash merge, cc-execution release and runtime proof.","wordingChanged":false,"canonicalIntent":"P0: eliminate the remaining external synthesis hop for durable mutable missions. The exact defect is in cc-execution mission control: after authoritative source resolution, a synthesis_required mission can still return operator_synthesize_and_resume_same_mission and wait for an external caller to author anchored edits. Repair the canonical path so cc-execution internally performs one bounded PAUL structured synthesis from the exact current source bundle, validates returned anchored edits against exact source/current-main identity and authorized paths, persists/reuses the same durable mission/branch, and immediately resumes canonical mutation. On inference/provider/schema/anchor failure after one bounded attempt, transition to explicit BLOCKED with the first causal blocker; never leave the mission resting at synthesis_required or implementation_payload_required. Preserve one mission/branch/PR, authorization, tenant isolation, repository_patch_scoped, Gate, merge, release and proof. Add focused regression coverage. Ship through canonical Gate, squash merge, cc-execution release and runtime proof.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"P0: eliminate the remaining external synthesis hop for durable mutable missions. The exact defect is in cc-execution mission control: after authoritative source resolution, a synthesis_required mission can still return operator_synthesize_and_resume_same_mission and wait for an external caller to author anchored edits. Repair the canonical path so cc-execution internally performs one bounded PAUL structured synthesis from the exact current source bundle, validates returned anchored edits against exact source/current-main identity and authorized paths, persists/reuses the same durable mission/branch, and immediately resumes canonical mutation. On inference/provider/schema/anchor failure after one bounded attempt, transition to explicit BLOCKED with the first causal blocker; never leave the mission resting at synthesis_required or implementation_payload_required. Preserve one mission/branch/PR, authorization, tenant isolation, repository_patch_scoped, Gate, merge, release and proof. Add focused regression coverage. Ship through canonical Gate, squash merge, cc-execution release and runtime proof.","provenance":{"reason":"PAUL schedule 9e6853d8-fb5d-417c-b81b-ed2567d4718b","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"P0: eliminate the remaining external synthesis hop for durable mutable missions. The exact defect is in cc-execution mission control: after authoritative source resolution, a synthesis_required mission can still return operator_synthesize_and_resume_same_mission and wait for an external caller to author anchored edits. Repair the canonical path so cc-execution internally performs one bounded PAUL structured synthesis from the exact current source bundle, validates returned anchored edits against exact source/current-main identity and authorized paths, persists/reuses the same durable mission/branch, and immediately resumes canonical mutation. On inference/provider/schema/anchor failure after one bounded attempt, transition to explicit BLOCKED with the first causal blocker; never leave the mission resting at synthesis_required or implementation_payload_required. Preserve one mission/branch/PR, authorization, tenant isolation, repository_patch_scoped, Gate, merge, release and proof. Add focused regression coverage. Ship through canonical Gate, squash merge, cc-execution release and runtime proof.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["workers/cc-execution/src/index-mission-control.js","workers/cc-execution/src/mcp-synthesis-source-bundle.js","workers/cc-execution/src/platform-sidekick-intelligence.js","workers/cc-execution/src/version.js","workers/cc-execution/test/mcp-synthesis-source-bundle.test.js","workers/cc-execution/test/release-orchestration-invariants.test.js"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"P0: eliminate the remaining external synthesis hop for durable mutable missions. The exact defect is in cc-execution mission control: after authoritative source resolution, a synthesis_required mission can still return operator_synthesize_and_resume_same_mission and wait for an external caller to author anchored edits. Repair the canonical path so cc-execution internally performs one bounded PAUL structured synthesis from the exact current source bundle, validates returned anchored edits against exact source/current-main identity and authorized paths, persists/reuses the same durable mission/branch, and immediately resumes canonical mutation. On inference/provider/schema/anchor failure after one bounded attempt, transition to explicit BLOCKED with the first causal blocker; never leave the mission resting at synthesis_required or implementation_payload_required. Preserve one mission/branch/PR, authorization, tenant isolation, repository_patch_scoped, Gate, merge, release and proof. Add focused regression coverage. Ship through canonical Gate, squash merge, cc-execution release and runtime proof.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"a3460418-72fa-47a7-b952-c02b1fae85a5","name":"PAUL Continuous Intelligence Lab","cadence":"interval","enabled":false,"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regressions against durable owner corrections. Only when evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity may this cycle mutate the explicitly bounded PAUL source scope supplied with this schedule. Make exactly one focused improvement, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. Reject or revert any change that does not improve the measured weakness or degrades required invariants. Never broaden beyond the supplied PAUL source scope without machine-readable dependency evidence. Never bypass Gate, tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Avoid sustained heavy compute on owner hardware; use available KNOCKLAUNCH capacity and reserve large DigitalOcean compute for genuinely heavy adversarial evaluation. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as a replaceable fallback. Record durable eval results, latency/score trends, accepted/rejected improvements, and exact runtime lineage.","created_at":"2026-09-30T15:53:17.564093+00:00","last_error":null,"updated_at":"2026-09-30T15:55:20.109+00:00","last_run_at":null,"last_status":"cancelled","next_run_at":"2026-09-30T16:53:17.258+00:00","failure_count":0,"last_mission_id":null,"interval_minutes":60,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regressions against durable owner corrections. Only when evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity may this cycle mutate the explicitly bounded PAUL source scope supplied with this schedule. Make exactly one focused improvement, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. Reject or revert any change that does not improve the measured weakness or degrades required invariants. Never broaden beyond the supplied PAUL source scope without machine-readable dependency evidence. Never bypass Gate, tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Avoid sustained heavy compute on owner hardware; use available KNOCKLAUNCH capacity and reserve large DigitalOcean compute for genuinely heavy adversarial evaluation. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as a replaceable fallback. Record durable eval results, latency/score trends, accepted/rejected improvements, and exact runtime lineage.","wordingChanged":false,"canonicalIntent":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regressions against durable owner corrections. Only when evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity may this cycle mutate the explicitly bounded PAUL source scope supplied with this schedule. Make exactly one focused improvement, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. Reject or revert any change that does not improve the measured weakness or degrades required invariants. Never broaden beyond the supplied PAUL source scope without machine-readable dependency evidence. Never bypass Gate, tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Avoid sustained heavy compute on owner hardware; use available KNOCKLAUNCH capacity and reserve large DigitalOcean compute for genuinely heavy adversarial evaluation. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as a replaceable fallback. Record durable eval results, latency/score trends, accepted/rejected improvements, and exact runtime lineage.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regressions against durable owner corrections. Only when evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity may this cycle mutate the explicitly bounded PAUL source scope supplied with this schedule. Make exactly one focused improvement, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. Reject or revert any change that does not improve the measured weakness or degrades required invariants. Never broaden beyond the supplied PAUL source scope without machine-readable dependency evidence. Never bypass Gate, tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Avoid sustained heavy compute on owner hardware; use available KNOCKLAUNCH capacity and reserve large DigitalOcean compute for genuinely heavy adversarial evaluation. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as a replaceable fallback. Record durable eval results, latency/score trends, accepted/rejected improvements, and exact runtime lineage.","provenance":{"reason":"PAUL schedule a3460418-72fa-47a7-b952-c02b1fae85a5","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regressions against durable owner corrections. Only when evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity may this cycle mutate the explicitly bounded PAUL source scope supplied with this schedule. Make exactly one focused improvement, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. Reject or revert any change that does not improve the measured weakness or degrades required invariants. Never broaden beyond the supplied PAUL source scope without machine-readable dependency evidence. Never bypass Gate, tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Avoid sustained heavy compute on owner hardware; use available KNOCKLAUNCH capacity and reserve large DigitalOcean compute for genuinely heavy adversarial evaluation. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as a replaceable fallback. Record durable eval results, latency/score trends, accepted/rejected improvements, and exact runtime lineage.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded PAUL Continuous Intelligence Lab cycle against the current canonical production intelligence stack. Begin with non-mutating production-bound evaluations of fast/standard/deep routing, factual and live-machinery grounding, owner-intent fidelity, tenant isolation, ambiguity handling, tool-selection discipline, planner/critic behavior, completion-proof discipline, failure recovery, hallucination resistance, latency, and regressions against durable owner corrections. Only when evidence proves a deterministic regression or clearly measurable intelligence improvement opportunity may this cycle mutate the explicitly bounded PAUL source scope supplied with this schedule. Make exactly one focused improvement, require before/after evidence, canonical Gate, squash merge, affected-target release, and claim-matched production proof. Reject or revert any change that does not improve the measured weakness or degrades required invariants. Never broaden beyond the supplied PAUL source scope without machine-readable dependency evidence. Never bypass Gate, tenant isolation, authorization, completion-proof discipline, or owner-intent fidelity. Avoid sustained heavy compute on owner hardware; use available KNOCKLAUNCH capacity and reserve large DigitalOcean compute for genuinely heavy adversarial evaluation. Preserve Cloudflare Workers AI as the active non-OpenAI primary path and OpenAI only as a replaceable fallback. Record durable eval results, latency/score trends, accepted/rejected improvements, and exact runtime lineage.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}},{"id":"c8473f28-bd3a-4844-a788-c4ce3bc385e5","name":"PAUL Source Scope Canary","cadence":"interval","enabled":false,"objective":"Run one bounded PAUL source-scope canary against the current production intelligence stack. This is a canary for durable scheduler handoff: inspect/evaluate PAUL first and make no repository mutation unless a deterministic regression is proven. If mutation would be required, remain bounded to the supplied exact sourceTargets and canonical Gate/release/proof rules.","created_at":"2026-09-30T16:17:17.595503+00:00","last_error":null,"updated_at":"2026-09-30T16:21:47.105+00:00","last_run_at":"2026-09-30T16:20:01.826348+00:00","last_status":"cancelled","next_run_at":"2026-09-30T16:21:01.826348+00:00","failure_count":0,"last_mission_id":"a7b575a8-bc83-483b-81f1-30cfacafa2ec","interval_minutes":1,"request_contract":{"valid":true,"intent":{"rawUtterance":"Run one bounded PAUL source-scope canary against the current production intelligence stack. This is a canary for durable scheduler handoff: inspect/evaluate PAUL first and make no repository mutation unless a deterministic regression is proven. If mutation would be required, remain bounded to the supplied exact sourceTargets and canonical Gate/release/proof rules.","wordingChanged":false,"canonicalIntent":"Run one bounded PAUL source-scope canary against the current production intelligence stack. This is a canary for durable scheduler handoff: inspect/evaluate PAUL first and make no repository mutation unless a deterministic regression is proven. If mutation would be required, remain bounded to the supplied exact sourceTargets and canonical Gate/release/proof rules.","resolutionStatus":"scheduled_owner_authorized","uniqueResolution":true,"clarificationRequired":false},"source":"owner_explicit_schedule","version":1,"outcomes":[{"id":"scheduled-objective","statement":"Run one bounded PAUL source-scope canary against the current production intelligence stack. This is a canary for durable scheduler handoff: inspect/evaluate PAUL first and make no repository mutation unless a deterministic regression is proven. If mutation would be required, remain bounded to the supplied exact sourceTargets and canonical Gate/release/proof rules.","provenance":{"reason":"PAUL schedule c8473f28-bd3a-4844-a788-c4ce3bc385e5","source":"owner_authorized_schedule","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"objective":"Run one bounded PAUL source-scope canary against the current production intelligence stack. This is a canary for durable scheduler handoff: inspect/evaluate PAUL first and make no repository mutation unless a deterministic regression is proven. If mutation would be required, remain bounded to the supplied exact sourceTargets and canonical Gate/release/proof rules.","constraints":[{"id":"canonical-execution","statement":"Execute through canonical KNOCKLAUNCH mission, Gate, release, and proof rules; the schedule grants no arbitrary shell, SQL, URL, secret, or provider authority.","provenance":{"reason":"Bound unattended work to the existing mission safety model.","source":"scheduler_safety","inherited":false,"blockingAuthority":true},"proofConditionIds":["scheduled-runtime-proof"]}],"sourceTargets":["workers/cc-execution/src/index-mcp.js","config/capabilities/platform-sidekick-intelligence.json"],"terminalPolicy":"all_required_proof_conditions_satisfied_after_live_release","proofConditions":[{"id":"scheduled-runtime-proof","kind":"runtime","claim":"Run one bounded PAUL source-scope canary against the current production intelligence stack. This is a canary for durable scheduler handoff: inspect/evaluate PAUL first and make no repository mutation unless a deterministic regression is proven. If mutation would be required, remain bounded to the supplied exact sourceTargets and canonical Gate/release/proof rules.","required":true,"targetedActions":[],"allowedReleaseTargets":[],"requiredReleaseTargets":[],"requireCapacityAdmissible":false,"minConsecutiveHealthyHeartbeats":1,"requirePositiveMemoryAttribution":false,"requireMemoryAdmissionPressureFalse":false}],"validationErrors":[]}}],"rows":13,"limit":400,"table":"paul_schedules","format":"knocklaunch-table-chunk-v1","offset":0,"schema":"public","order_key":"id"}