Complete commercial evidence execution orchestration

Author: ammarheidari

README.md

@@ -72,7 +72,7 @@ The first production milestone is M3UA over a transport abstraction. SCCP, TCAP,
 | Supply-chain release execution | Phase 34 foundation-complete: final versioned SBOM, trusted timestamped package signing, provenance attestation, public API diff, artifact upload, ordered command-plan, release promotion gate, concrete workflow execution, status reporting, and final validation are available; retained release-run artifacts and commercial evidence are still required |
 | RC publish and commercial gate | Phase 35 complete: dry-run release rehearsal, gated NuGet prerelease publication, retained release notes, retained migration notes, final commercial readiness reporting, RC/stable decisioning, RC publication evidence manifest, release workflow channel wiring, status reporting, and final commercial gate report are available; stable publication remains blocked until commercial evidence is complete |
 | Commercial evidence readiness lockdown | Phase 36 foundation-complete: release target locking, protected secret readiness, evidence retention mapping, commercial evidence checklist, release preflight, protected release environments, dossier handoff, go/no-go gating, status reporting, and final validation are available; RC and stable publication remain blocked until retained commercial release evidence is complete |
-| Commercial evidence execution orchestration | Phase 37 in progress: evidence execution run identity, stage catalog, operator command plan, execution environment contract, artifact collection manifest, digest/redaction verification, blocker classification, retry/resume policy, and status reporting are available; final validation is still pending |
+| Commercial evidence execution orchestration | Phase 37 foundation-complete: evidence execution run identity, stage catalog, operator command plan, execution environment contract, artifact collection manifest, digest/redaction verification, blocker classification, retry/resume policy, status reporting, and final validation are available; real retained execution artifacts are still required before commercial publication |
 
 ## Requirements
 

docs/PHASE37_COMMERCIAL_EVIDENCE_EXECUTION_ORCHESTRATION.md

@@ -112,7 +112,18 @@ The policy prevents endless retries and keeps host capability, approval, and unk
 - Retained evidence readiness.
 - Commercial publication readiness.
 
-The status is intentionally conservative. The orchestration contracts are ready, but publication is still blocked until real retained execution artifacts exist and final validation closes the phase.
+The status is intentionally conservative. The orchestration contracts are ready, but publication is still blocked until real retained execution artifacts exist.
+
+## Unit 10 - Final Validation
+
+Final validation closes the orchestration foundation:
+
+- Build, test, and package validation are run together.
+- `final-validation` is included in the public status capability list.
+- The temporary final-validation blocker is removed.
+- The retained real execution artifact blocker remains active.
+
+This keeps the phase complete as an SDK foundation while preserving the commercial release gate until evidence is produced by real labs and release workflows.
 
 ## Validation
 

docs/PHASE37_SUMMARY.md

@@ -13,7 +13,8 @@ Phase 37 prepares the SDK to execute real commercial evidence runs after readine
 - Execution blocker classifier for readiness, environment, command, native SCTP, external peer, artifact, digest, redaction, and approval failures.
 - Retry and resume policy with bounded retries and manual-correction gates for non-retryable failures.
 - Execution orchestration status that reports completed capabilities, default blockers, orchestration readiness, retained evidence readiness, and commercial publication readiness.
+- Final validation that closes the orchestration foundation while retaining the real-evidence blocker.
 
 ## Readiness Position
 
-The phase is in progress. Execution orchestration status is now available. Final validation is still required before the phase can be closed.
+Phase 37 is foundation-complete. The SDK can describe a governed commercial evidence execution run, but commercial publication remains blocked until real retained execution artifacts are produced, verified, redacted where needed, and approved.

docs/PHASE_INDEX.md

@@ -41,7 +41,7 @@ This index is the complete phase map for Sigtran.NET. It links each phase to the
 | 34 | Supply-chain release execution | [Phase 34 Supply Chain Release Execution](PHASE34_SUPPLY_CHAIN_RELEASE_EXECUTION.md), [Phase 34 Summary](PHASE34_SUMMARY.md) | Foundation complete; retained release run pending |
 | 35 | RC publish and commercial gate | [Phase 35 RC Publish And Commercial Gate](PHASE35_RC_PUBLISH_COMMERCIAL_GATE.md), [Phase 35 Summary](PHASE35_SUMMARY.md), [Phase 35 Commercial Gate Report](PHASE35_COMMERCIAL_GATE_REPORT.md) | RC gate foundation complete; stable publication blocked |
 | 36 | Commercial evidence readiness lockdown | [Phase 36 Commercial Evidence Readiness Lockdown](PHASE36_COMMERCIAL_EVIDENCE_READINESS_LOCKDOWN.md), [Phase 36 Summary](PHASE36_SUMMARY.md) | Foundation complete; real commercial evidence still required |
-| 37 | Commercial evidence execution orchestration | [Phase 37 Commercial Evidence Execution Orchestration](PHASE37_COMMERCIAL_EVIDENCE_EXECUTION_ORCHESTRATION.md), [Phase 37 Summary](PHASE37_SUMMARY.md) | In progress; status reporting complete |
+| 37 | Commercial evidence execution orchestration | [Phase 37 Commercial Evidence Execution Orchestration](PHASE37_COMMERCIAL_EVIDENCE_EXECUTION_ORCHESTRATION.md), [Phase 37 Summary](PHASE37_SUMMARY.md) | Foundation complete; real execution artifacts still required |
 
 ## Current Commercial Gate
 

docs/SDK_ROADMAP.md

@@ -331,7 +331,7 @@ Status: Phase 36 is foundation-complete. The release target lock binds an RC ver
 - Define execution stages, operator commands, environment contracts, artifact collection, digest and redaction verification, blocker handling, retry/resume behavior, and execution status.
 - Keep the phase separate from real passing evidence: orchestration can prepare a run, but publication remains blocked until retained artifacts prove execution success.
 
-Status: Phase 37 is in progress. Evidence execution run identity now binds a locked release target to a stable run id, operator identity, UTC start time, and run-scoped artifact root. The stage catalog now covers readiness preflight, native SCTP lab, external peer interoperability, protocol validation, performance benchmark, supply-chain evidence, release workflow dry-run, and dossier assembly with run-scoped artifact roots. The operator command plan now maps every stage to an ordered run-id-aware command and requires protected approval for supply-chain, workflow, and dossier assembly execution. The environment contract now binds run identity, lab inputs, and protected secrets while preventing fixed secret values from being stored. Artifact collection now maps all checklist artifacts to known stage roots and retained output paths. Digest and redaction verification now requires digest coverage for every artifact and redaction review for trace-bearing evidence. Blocker classification now categorizes readiness, environment, command, native SCTP, external peer, artifact, digest, redaction, and approval failures with retryability guidance. Retry/resume now applies bounded retries and manual-correction gates for non-retryable failures. Status reporting now exposes completed capabilities, orchestration readiness, retained evidence readiness, publication readiness, and current blockers. Final validation remains in progress.
+Status: Phase 37 is foundation-complete. Evidence execution run identity binds a locked release target to a stable run id, operator identity, UTC start time, and run-scoped artifact root. The stage catalog covers readiness preflight, native SCTP lab, external peer interoperability, protocol validation, performance benchmark, supply-chain evidence, release workflow dry-run, and dossier assembly with run-scoped artifact roots. The operator command plan maps every stage to an ordered run-id-aware command and requires protected approval for supply-chain, workflow, and dossier assembly execution. The environment contract binds run identity, lab inputs, and protected secrets while preventing fixed secret values from being stored. Artifact collection maps all checklist artifacts to known stage roots and retained output paths. Digest and redaction verification requires digest coverage for every artifact and redaction review for trace-bearing evidence. Blocker classification categorizes readiness, environment, command, native SCTP, external peer, artifact, digest, redaction, and approval failures with retryability guidance. Retry/resume applies bounded retries and manual-correction gates for non-retryable failures. Status reporting exposes completed capabilities, orchestration readiness, retained evidence readiness, publication readiness, and current blockers. Final validation is complete. Commercial publication remains blocked until real retained execution artifacts are produced, verified, redacted where needed, and approved.
 
 ## Recommended First Deliverable
 

src/Sigtran.NET.Tests/Program.cs

@@ -4769,15 +4769,16 @@ static void SigtranCommercialEvidenceExecutionStatusSummarizesOrchestrationReadi
     IReadOnlyList<string> capabilities = SigtranCommercialEvidenceExecutionStatus.GetCompletedCapabilities();
     IReadOnlyList<string> blockers = SigtranCommercialEvidenceExecutionStatus.GetDefaultBlockers();
 
-    AssertEqual(9, SigtranCommercialEvidenceExecutionStatus.CompletedUnitCount, "commercial evidence execution completed unit count");
-    AssertEqual(9, capabilities.Count, "commercial evidence execution capability count");
+    AssertEqual(10, SigtranCommercialEvidenceExecutionStatus.CompletedUnitCount, "commercial evidence execution completed unit count");
+    AssertEqual(10, capabilities.Count, "commercial evidence execution capability count");
     Assert(capabilities.Contains("retry-resume-policy"), "execution status should include retry and resume policy");
+    Assert(capabilities.Contains("final-validation"), "execution status should include final validation");
     Assert(capabilities.Contains("documentation"), "execution status should include documentation");
     Assert(SigtranCommercialEvidenceExecutionStatus.ExecutionOrchestrationReady, SigtranCommercialEvidenceExecutionStatus.Describe());
     Assert(!SigtranCommercialEvidenceExecutionStatus.RetainedExecutionEvidenceReady, SigtranCommercialEvidenceExecutionStatus.Describe());
     Assert(!SigtranCommercialEvidenceExecutionStatus.CommercialPublicationReady, SigtranCommercialEvidenceExecutionStatus.Describe());
     Assert(blockers.Contains("real-execution-artifacts-required"), "execution status should require real retained artifacts");
-    Assert(blockers.Contains("status-final-validation-pending"), "execution status should retain final validation blocker before phase closeout");
+    Assert(!blockers.Contains("status-final-validation-pending"), "final validation should no longer be a blocker");
 }
 
 static void SigtranStatusCapabilitiesUseDomainDocumentationLabels()

src/Sigtran.NET/Core/Utilities/SigtranCommercialEvidenceExecutionStatus.cs

@@ -15,20 +15,20 @@ public static class SigtranCommercialEvidenceExecutionStatus
         "digest-redaction-verification",
         "blocker-classification",
         "retry-resume-policy",
+        "final-validation",
         "documentation"
     ];
 
     private static readonly string[] DefaultBlockers =
     [
-        "real-execution-artifacts-required",
-        "status-final-validation-pending"
+        "real-execution-artifacts-required"
     ];
 
     /// <summary>The status label.</summary>
     public const string StatusLabel = "Commercial Evidence Execution Orchestration";
 
     /// <summary>The number of completed commercial evidence execution orchestration work units.</summary>
-    public const int CompletedUnitCount = 9;
+    public const int CompletedUnitCount = 10;
 
     /// <summary>Returns the completed execution orchestration capability names.</summary>
     /// <returns>The completed capability names.</returns>