infotradescout · Sep 17, 2026 · Sep 17, 2026 · Sep 17, 2026 · Sep 17, 2026 · Sep 17, 2026
@@ -7,7 +7,7 @@
   "adapter_path": "adapters/chatgpt/selective-intelligence",
   "transformation": "runtime_only_with_nested_role_entrypoints_as_role_references",
   "single_skill_entrypoint": "SKILL.md",
-  "runtime_file_count": 59,
+  "runtime_file_count": 61,
   "role_path_map": {
     "subskills/si-aligner/SKILL.md": "subskills/si-aligner/ROLE.md",
     "subskills/si-intake/SKILL.md": "subskills/si-intake/ROLE.md",
@@ -18,9 +18,9 @@
     "subskills/si-worker/SKILL.md": "subskills/si-worker/ROLE.md"
   },
   "behavioral_contract": "source_preserved_not_installed_behavior_proof",
-  "source_manifest_sha256": "3eb375527a741dd34be9bd63d18c82edd182823ebc3fdd9d16228eaceec4ae7b",
+  "source_manifest_sha256": "0797e9d318206258af21b0152dcb61949c2478fab2837ecdb9bcc67e67f66c89",
   "source_file_sha256": {
-    "SKILL.md": "afb4c6e096aa83683105c45b5525ac34ee436654be4dacc9c2a44f01bf2033b1",
+    "SKILL.md": "87eb73b0792238f5e909b20bee3ddfc3c0740ee40471874fc76e877dd765d2e5",
     "VERSION": "326dd5d8641f399990de42def50ac29eb4c9222601c0a0a3fc3c947dd3bec65d",
     "agents/openai.yaml": "5090139b222271205759e9c1cd34fbe154a0aae91221cb9fea47e7ecaf29e56c",
     "assets/icon.svg": "bbd2fc7be4ae81f8ff16bd26e26eab6d8547ef3ba1d6d7e49ba970c9a28fc77f",
@@ -33,7 +33,7 @@
     "references/architecture-reuse.md": "5d1c4d09ca8e7407d19c7fc9d68587b2ea0b61be61e5c3448890af2c8766138d",
     "references/continuity-and-impact.md": "78f93ccaaed14e58544c5a0c78b6bf933922b4c576a597b13d63ac74d0de53e0",
     "references/durable-progress-and-recovery.md": "1457eed72572aa6e0f34ab6773b81735e3f1ee22e5427e44a238619b034a609d",
-    "references/evidence-and-completion.md": "f05424d0e1b8c68624aab05d3e03361e312a08a92bc3b3338b86e29a1971569f",
+    "references/evidence-and-completion.md": "a72baee12b008168f6dc38d734fb2e4e5ce0e4a5d05345a82282337a045ca7f7",
     "references/failure-patterns-and-gates.md": "90b4b2fc15069a33cdef3fc39d653b718f4ef4e27345c0db5dab3d7fca5408b5",
     "references/feedback-and-learning-loop.md": "5e25a722d5f28b4a91f5d29d1e623c8a3c182057ce671cdc3e94bb3fd3cf7db9",
     "references/first-checkpoint.md": "383ca9161be9cc93878354bbbb5a15ced98752a5d352f7d0dd6fa6243ea64724",
@@ -78,10 +78,12 @@
     "subskills/si-planner/SKILL.md": "5c36d354272e89e1c26dc15a236b4af183ca55d7494b2a8023259dcb08c6b8fa",
     "subskills/si-queue-manager/SKILL.md": "89881a69484d5bce571cd9ac886fc75c367ad1352aa121b02a6315d4b0a39930",
     "subskills/si-verifier/SKILL.md": "24188bbe576fdf18d05b4ac4cce4d4976ce95de41f3c446b0c81384c101b378d",
-    "subskills/si-worker/SKILL.md": "d53d69ba98c734aa6e035a119e42cbf3b353fd9652c7d40d8937412415a0c1bc"
+    "subskills/si-worker/SKILL.md": "d53d69ba98c734aa6e035a119e42cbf3b353fd9652c7d40d8937412415a0c1bc",
+    "scripts/delivery_acceptance.py": "e8749f4141f7397fc42458400e90b87256f429c4963832bbf920dbb8837d40f9",
+    "references/product-delivery-acceptance.md": "574643b517d7a39d5146142bec2bbbaa8a47f5869ad3a021f9fbd271b8fb47f2"
   },
   "projected_file_sha256": {
-    "SKILL.md": "f034d6a4ff310d8bbb95a27a792f9b0b2e21acdab1db348f7859d8258fd32b86",
+    "SKILL.md": "69752eee3760c835ede48f3d49a9590a76cb63ade977ca647196f85aebc37c8c",
     "VERSION": "326dd5d8641f399990de42def50ac29eb4c9222601c0a0a3fc3c947dd3bec65d",
     "agents/openai.yaml": "5090139b222271205759e9c1cd34fbe154a0aae91221cb9fea47e7ecaf29e56c",
     "assets/icon.svg": "bbd2fc7be4ae81f8ff16bd26e26eab6d8547ef3ba1d6d7e49ba970c9a28fc77f",
@@ -94,7 +96,7 @@
     "references/architecture-reuse.md": "5d1c4d09ca8e7407d19c7fc9d68587b2ea0b61be61e5c3448890af2c8766138d",
     "references/continuity-and-impact.md": "78f93ccaaed14e58544c5a0c78b6bf933922b4c576a597b13d63ac74d0de53e0",
     "references/durable-progress-and-recovery.md": "1457eed72572aa6e0f34ab6773b81735e3f1ee22e5427e44a238619b034a609d",
-    "references/evidence-and-completion.md": "f05424d0e1b8c68624aab05d3e03361e312a08a92bc3b3338b86e29a1971569f",
+    "references/evidence-and-completion.md": "a72baee12b008168f6dc38d734fb2e4e5ce0e4a5d05345a82282337a045ca7f7",
     "references/failure-patterns-and-gates.md": "90b4b2fc15069a33cdef3fc39d653b718f4ef4e27345c0db5dab3d7fca5408b5",
     "references/feedback-and-learning-loop.md": "5e25a722d5f28b4a91f5d29d1e623c8a3c182057ce671cdc3e94bb3fd3cf7db9",
     "references/first-checkpoint.md": "383ca9161be9cc93878354bbbb5a15ced98752a5d352f7d0dd6fa6243ea64724",
@@ -139,7 +141,9 @@
     "subskills/si-planner/ROLE.md": "5c36d354272e89e1c26dc15a236b4af183ca55d7494b2a8023259dcb08c6b8fa",
     "subskills/si-queue-manager/ROLE.md": "89881a69484d5bce571cd9ac886fc75c367ad1352aa121b02a6315d4b0a39930",
     "subskills/si-verifier/ROLE.md": "24188bbe576fdf18d05b4ac4cce4d4976ce95de41f3c446b0c81384c101b378d",
-    "subskills/si-worker/ROLE.md": "d53d69ba98c734aa6e035a119e42cbf3b353fd9652c7d40d8937412415a0c1bc"
+    "subskills/si-worker/ROLE.md": "d53d69ba98c734aa6e035a119e42cbf3b353fd9652c7d40d8937412415a0c1bc",
+    "scripts/delivery_acceptance.py": "e8749f4141f7397fc42458400e90b87256f429c4963832bbf920dbb8837d40f9",
+    "references/product-delivery-acceptance.md": "574643b517d7a39d5146142bec2bbbaa8a47f5869ad3a021f9fbd271b8fb47f2"
   },
   "execution_entrypoint": "scripts/build_engine.py",
   "execution_dependencies": [

@@ -59,6 +59,8 @@ Never collapse:
 
 Bind claims to revision/environment/scope/evidence. Production finishes at required live behavior unless the user specifies otherwise. Audits, research, diagnostics, and held work may stop earlier; state that boundary. See [evidence and completion](references/evidence-and-completion.md).
 
+Product handoff requires [delivery acceptance](references/product-delivery-acceptance.md).
+
 ## Product identity before templates
 
 Software does not imply SaaS; management authority cannot invent product behavior. Current governing intent defines identity; correct assumptions, plans, handoffs, and proof. Preserve approved language, design, responsibilities, memberships, fees, providers, and services. Invent rules only for actual gaps.

@@ -1,6 +1,6 @@
 # Evidence and Completion Model
 
-Use this reference when the output contains public factual claims, identity information, sensitive fields, or conflicting sources.
+Use this reference when the output contains public factual claims, identity information, sensitive fields, conflicting sources, or a product-delivery claim.
 
 ## Governing authority order
 
@@ -96,6 +96,8 @@ A result is complete when it performs its intended job without placeholders or i
 
 Closed builds do not imply a closed release. Release completion additionally requires every included requirement, critical journey, prohibition, necessary actor, operational gate, and invalidated prior proof to reconcile at the current baseline.
 
+Before promoting a user-facing product to ready for review, apply [product-delivery-acceptance.md](product-delivery-acceptance.md) through the canonical quality CLI's `--delivery` mode. Preserve automatic versus optional-manual requirements and require one intended product owner, actual workflow evidence and rendered interaction review. Source tests alone remain source validation. A screenshot, imported history, working URL or unstarted observer cannot substitute for the primary workflow. Unresolved user rejection keeps delivery open. The gate never declares user acceptance or proves that all installed clients enforce it.
+
 **Cross-runtime equivalence:** Given the same task, context, and evidence, completion means an equivalently correct user outcome across models and environments—not merely fluent prose from the current runtime. Different wording is fine; different intent, scope, product truth, workflow, quality threshold, or final outcome is not. A runtime that cannot meet the bar must be corrected, retried, or blocked before side effects land. See [model-neutral-execution.md](model-neutral-execution.md#governing-requirement-model-interchangeability). One strong benchmark demonstrates that the quality bar is achievable; repeating that bar without heavy user repair is what counts as reliability.
 
 ## Council provenance

@@ -0,0 +1,27 @@
+# Product delivery acceptance
+
+A successful component test is not a successful product delivery. Preserve the user's primary job, interaction mode, desired finish, prohibitions and existing canonical owner before implementation. Do not redefine an automatic product as a manual notebook when telemetry work is unfinished. Manual tools can be optional without becoming the main workflow. A small first delivery must close a real user loop, not merely expose internal records.
+
+## Required acceptance packet
+
+Use the canonical `scripts/quality_gate.py --delivery --contract <contract.json> --evidence <evidence.json> --artifact-root <evidence-directory>` at a product delivery boundary. This is agent/adapter work, not an instruction for the user to run a command. Preserve the complete product scope while selecting a bounded delivery. Requirements must state `automatic`, `interactive`, `manual`, or `optional_manual`, identify primary outcomes, and state whether proof must be synthetic, native or live. Do not reduce native/live requirements to synthetic to obtain a pass.
+
+Bind evidence to the current contract hash, source revision, canonical code root, application entrypoint and data owner. Preserve unresolved user rejection as a blocker until its specific defects have been resolved and rechecked; an agent's confidence cannot substitute for the user's acceptance. Verify exactly one intended delivery target. Explicitly account for old installations and existing data before replacing or redirecting them. Never delete an old journal to make duplication disappear.
+
+An automatic workflow must show its triggering change and resulting user-visible state without a manual-entry step. Prove startup, update, persistence and recovery in the required environment. Retain the distinction between synthetic replay, native observation and a live external event. An initial historical import is not a newly observed event. A working URL alone is not installation proof.
+
+For primary user-facing work, require a rendered screen, actual interaction review and disposition of blocking usability findings. Review discoverability, data relevance, density, legibility, empty/error/loading/stale states and the amount of user effort. Test counts and attractive colors are not substitutes. Screenshots alone are insufficient. No numerical aesthetic score or model self-approval establishes acceptance.
+
+## Enforcement and honest boundaries
+
+`delivery_acceptance.py` validates the packet and referenced artifact bytes. The integrated quality CLI returns nonzero for missing, stale, wrong-mode or conflicting proof. Its strongest result is `ready_for_review`, never `user_accepted`. The original five-stage SI source gate remains separate and reports `productDelivery: not_evaluated`.
+
+These checks cannot authenticate fabricated reports, infer a correct product definition from an arbitrary string, intercept ungoverned tool calls, or force an external client to adopt them. An adapter must invoke the gate before promoting product-delivery state. Source publication is not runtime installation. Complete adapter/distribution regeneration, full repository validation and an installed-client forward test before claiming system-wide enforcement. Keep this work unmerged while those gates are outstanding.
+
+## Repeated discovery failures
+
+The `admit_discovery` helper caps equivalent searches for one unresolved question and target, rejects searching a known path, and requires polling an existing search handle. The caller must persist its returned ledger. Query rewording and context reset must retain the same question identity. It is not yet a universal interceptor of connector calls. A safety denial is never made retryable by this helper.
+
+## Regression fixture
+
+The test suite models a failed automatic companion: two competing app targets, manual input substituted for automatic capture, many passing component tests, a screenshot without interaction review, an unstarted collector, old evidence after a correction, and unresolved dissatisfaction. Every case must remain blocked. The fixtures are synthetic validator tests, not evidence that a real game or product passed acceptance.