Post-Phase-4: mixed execution, boundary, and blocker evidence

[Riverbraid]

Status

MIXED_EXECUTION_EVIDENCE_STATES / PLAN_ONLY_ITEMS_RESOLVED_TO_EXACT_OUTCOMES

Purpose

Track attributable execution evidence, bounded unavailable states, and source blockers without treating every repository or command as equally verified.

Current evidence states

Evaluation Kit command and environment policy

EXECUTED_BOUNDED

• Exact draft head: 868341e2a26ae1ac912be170a2930034b06623ee
• Workflow run: 30286309516
• Workflow job: 90044856022
• Evidence record: docs/evidence-plans/EVALUATION_KIT_ALLOWLIST.md

Observed bounded markers:

BASE_IMAGE_IDENTITY_LOCK_MATCH
ALLOWLIST_NEGATIVE_TEST_PASS
NPM_LIFECYCLE_SCRIPTS_DENIED
REPRODUCTION_MATCH

The Docker base-image digest issue is closed at the exact-head level. OS-package and npm dependency acquisition remain network-bound.

Refusal-Gold fail-closed behavior

EXECUTED_BOUNDED_ON_DRAFT / PENDING_MAIN_INCORPORATION

• Draft PR: Riverbraid/Riverbraid-Refusal-Gold#7
• Exact head: a05c341af05fe9b5663c5dc8d6e85084e0118cdc
• Workflow run: 30288938156
• Workflow job: 90053623558
• Evidence record: docs/evidence-plans/REFUSAL_GOLD_FAIL_CLOSED.md

The exact draft passed the real positive verifier and an isolated missing-required-file negative case that exited 1 and preserved bounded output.

Harness-Gold runtime GPG binding

BLOCKED_BY_SOURCE_CONTRACT / GPG_EXECUTION_NOT_ASSESSED

• Draft PR: Riverbraid/Riverbraid-Harness-Gold#6
• Exact head: e054407becc9d995b023042a24eaf0c7cae5e0b7
• Repaired gate run: 30289790880, job 90056469679
• Existing verifier run: 30289790890, job 90056470184
• Evidence status: docs/evidence-plans/HARNESS_GOLD_GPG_BINDING.md

The source lacks bin/verify-swarm.cjs and riverbraid-shield.js; both .js runtime-binding entrypoints also use CommonJS under a package declaring type: module.

The green blocked-state validator confirms the source contradiction; it is not GPG execution evidence.

Gold-V2 optional workspace dependency boundary

BOUNDARY_EXECUTED_BOUNDED_ON_DRAFT / REAL_WORKSPACE_EXECUTION_OPEN

• Draft PR: Riverbraid/Riverbraid-Gold-V2#3
• Exact head: 9124578dbc7ec1285accc7098df6453fbbab51ec
• Workflow run: 30289561901
• Workflow job: 90055700184
• Evidence record: docs/evidence-plans/GOLD_V2_DEPENDENCY_BOUNDARY.md

Missing optional sibling repositories are classified as WORKSPACE_DEPENDENCY_UNAVAILABLE with exit code 2. Repository-local verify and build passed. Real pinned sibling execution remains open.

Seven bounded audit_final.js scaffold checks

EXECUTED_BOUNDED

• Documentation execution head: 7ecd4231fe61c0aaa62a8b881cd0daef65b4fda4
• Workflow run: 30290915464
• Workflow job: 90060197818
• Contract: docs/evidence-plans/AUDIT_FINAL_SCAFFOLD_CONTRACT.json
• Evidence record: docs/evidence-plans/AUDIT_FINAL_SCAFFOLD_CHECKS.md

Seven exact repository commits passed their declared positive presence/parse checks and disposable missing-README exit-code-1 cases.

This remains scaffold-level evidence only.

Phase 2.6 petal depth

EXECUTED_BOUNDED_AT_PINNED_REGISTRY_COMMITS

• Evaluation Kit head/run/job: 868341e2... / 30286309516 / 90044856022
• Evidence record: docs/evidence-plans/PHASE_2_6_PETAL_DEPTH_EXECUTION.md

Depth is intentionally differentiated:

• Memory-Gold: multi-vector behavioral verifier executed;
• Judicial-Gold: canonical-vector behavioral check executed;
• Safety-Gold: canonical-vector behavioral check executed;
• Integration-Gold: canonical coherence check executed, not F3 cross-repository integration.

Remaining work represented here

No evidence-plan file listed above remains merely PLAN_ONLY.

Open work is now explicit rather than generic:

• merge/adopt draft evidence-producing changes and obtain resulting exact-main-head runs where required;
• repair the Harness runtime-binding source contract before GPG execution;
• execute Gold V2 against exact real sibling source identities if that optional workspace extension is retained;
• preserve stronger per-repository or independent evidence only when the corresponding claim requires it;
• keep network, freshness, verification-depth, F3 integration, and independence boundaries separate.

Claim rule

A successful result for one exact repository, commit, command, environment, and verification depth does not upgrade another subject or establish a broader operational claim.

A blocked-state validator is evidence of the blocker, not evidence that the blocked operation succeeded.

Boundary

This issue tracks attributable evidence states. It does not merge pull requests, mutate registry pins, alter releases or tags, configure repository settings, adopt the F0–F4 control package, or advance P0, F0, F1, F2, F3, or F4.

It does not establish certification, production readiness, external audit, independent reproduction, full-constellation operation, or absence of defects.