Complete commercial evidence file verification

Author: ammarheidari

README.md

@@ -74,7 +74,7 @@ The first production milestone is M3UA over a transport abstraction. SCCP, TCAP,
 | 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 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 |
 | Commercial evidence artifact intake | Phase 38 foundation-complete: artifact intake target identity, artifact source registration, SHA-256 digest coverage, redaction review, completeness evaluation, dossier reporting, promotion handoff, execution-to-dossier bridge, status reporting, and final validation are available, binding a stable intake id, reviewer identity, UTC receipt time, run-scoped dossier root, concrete source paths, unique retained dossier paths, retained digests, trace-bearing artifact approvals, explicit intake blockers, retained Markdown summary, digest-covered handoff, end-to-end intake assembly, and intake readiness status to a governed execution run; real artifact files are still required before commercial publication |
-| Commercial evidence file verification | Phase 39 in progress: retained file evidence item verification, retained file manifest coverage, file verification blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, verified promotion gating, command planning, and status reporting are available, checking file existence, non-empty size, SHA-256 validity, digest match, UTC observation time, unique retained paths, promotion-required handoff coverage, explicit verification blockers, reviewer identity, immutable retention, UTC retention windows, minimum duration, deterministic aggregate ledger digests, sealed ledger attachment coverage, trace-bearing redaction approval, commercial readiness report presence, explicit promotion approval, workflow-ready verification command order, and readiness status separation; final validation remains |
+| Commercial evidence file verification | Phase 39 foundation-complete: retained file evidence item verification, retained file manifest coverage, file verification blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, verified promotion gating, command planning, status reporting, final validation, and documentation alignment are available, checking file existence, non-empty size, SHA-256 validity, digest match, UTC observation time, unique retained paths, promotion-required handoff coverage, explicit verification blockers, reviewer identity, immutable retention, UTC retention windows, minimum duration, deterministic aggregate ledger digests, sealed ledger attachment coverage, trace-bearing redaction approval, commercial readiness report presence, explicit promotion approval, workflow-ready verification command order, and readiness status separation; real retained file evidence remains required before commercial publication |
 
 ## Requirements
 

docs/PHASE39_COMMERCIAL_EVIDENCE_FILE_VERIFICATION.md

@@ -118,7 +118,18 @@ The plan is package-neutral and shell-neutral. It describes the expected workflo
 - Explicit separation between foundation readiness and real retained file evidence.
 - Commercial publication remains blocked until real retained file evidence and final validation are complete.
 
-At this point the status intentionally keeps `status-final-validation-pending` as a blocker.
+During Unit 9 the status intentionally kept `status-final-validation-pending` as a blocker until final validation completed.
+
+## Unit 10 - Final Validation
+
+Final validation closes the file verification foundation:
+
+- Completed unit count is aligned to 10.
+- Documentation is represented in the status capabilities.
+- The temporary final-validation blocker is removed.
+- Real retained file evidence remains a blocker until actual files are observed, digest-checked, retained, sealed, and attached from a real commercial evidence run.
+
+Phase 39 is foundation-complete after this unit. It does not claim that commercial publication is ready without real retained evidence.
 
 ## Validation
 

docs/PHASE39_SUMMARY.md

@@ -13,7 +13,8 @@ Phase 39 prepares the SDK to verify retained commercial evidence files after art
 - Verified promotion gate that requires ready attachments, ready integrity seal, ready retention ledger, verified file report, commercial readiness report, and explicit approval.
 - File verification command plan that orders observation, digest computation, comparison, report, ledger, seal, attachment, and promotion-gate steps.
 - File verification status reporting that separates foundation readiness from real retained file evidence and commercial publication readiness.
+- Final validation and documentation alignment for the completed file verification foundation.
 
 ## Readiness Position
 
-The phase is in progress. Retained file evidence item verification, retained file manifest coverage, blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, verified promotion gating, command planning, and status reporting are available. Final validation remains.
+Phase 39 is foundation-complete. Retained file evidence item verification, retained file manifest coverage, blocker reporting, retention ledger modeling, integrity sealing, publication attachment planning, verified promotion gating, command planning, status reporting, and documentation alignment are available. Commercial publication remains blocked until real retained file evidence is observed, retained, digest-verified, sealed, attached, and approved from a real evidence run.

docs/PHASE_INDEX.md

@@ -43,7 +43,7 @@ This index is the complete phase map for Sigtran.NET. It links each phase to the
 | 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) | Foundation complete; real execution artifacts still required |
 | 38 | Commercial evidence artifact intake | [Phase 38 Commercial Evidence Artifact Intake](PHASE38_COMMERCIAL_EVIDENCE_ARTIFACT_INTAKE.md), [Phase 38 Summary](PHASE38_SUMMARY.md) | Foundation complete; real artifact files still required |
-| 39 | Commercial evidence file verification | [Phase 39 Commercial Evidence File Verification](PHASE39_COMMERCIAL_EVIDENCE_FILE_VERIFICATION.md), [Phase 39 Summary](PHASE39_SUMMARY.md) | In progress; status reporting complete |
+| 39 | Commercial evidence file verification | [Phase 39 Commercial Evidence File Verification](PHASE39_COMMERCIAL_EVIDENCE_FILE_VERIFICATION.md), [Phase 39 Summary](PHASE39_SUMMARY.md) | Foundation complete; real retained file evidence required |
 
 ## Current Commercial Gate
 

docs/SDK_ROADMAP.md

@@ -347,7 +347,7 @@ Status: Phase 38 is foundation-complete. Artifact intake target identity binds a
 - Track file existence, size, observation time, digest match, retention, integrity sealing, publication attachment, promotion gate, and operator command contracts.
 - Keep file verification separate from real lab execution: verification contracts can evaluate retained files, but publication remains blocked until real files are present and approved.
 
-Status: Phase 39 is in progress. Retained file evidence item verification now checks existence, non-empty size, SHA-256 validity, digest match, and UTC observation time. Retained file manifest coverage now verifies that every promotion-required handoff item has a unique verified retained file. File verification reporting now exposes missing, empty, invalid digest, digest mismatch, non-UTC observation, duplicate path, and incomplete handoff blockers. Retention ledger modeling now binds verified files to reviewer identity, immutable retention, UTC retention windows, and minimum duration checks. Integrity sealing now computes and validates a deterministic aggregate SHA-256 digest over the ledger. Publication attachment planning now covers sealed ledger entries, validates attachment digests, includes the commercial readiness report, and blocks trace-bearing attachments without redaction approval. Verified promotion gating now requires ready attachments, ready integrity seal, ready retention ledger, verified file report, commercial readiness report presence, and explicit approval before evidence can move into release publication decisions. Command planning now orders observation, digest computation, comparison, report, ledger, seal, attachment, and promotion-gate work for workflow materialization. Status reporting now separates foundation readiness from real retained file evidence and commercial publication readiness. Final validation remains in progress.
+Status: Phase 39 is foundation-complete. Retained file evidence item verification checks existence, non-empty size, SHA-256 validity, digest match, and UTC observation time. Retained file manifest coverage verifies that every promotion-required handoff item has a unique verified retained file. File verification reporting exposes missing, empty, invalid digest, digest mismatch, non-UTC observation, duplicate path, and incomplete handoff blockers. Retention ledger modeling binds verified files to reviewer identity, immutable retention, UTC retention windows, and minimum duration checks. Integrity sealing computes and validates a deterministic aggregate SHA-256 digest over the ledger. Publication attachment planning covers sealed ledger entries, validates attachment digests, includes the commercial readiness report, and blocks trace-bearing attachments without redaction approval. Verified promotion gating requires ready attachments, ready integrity seal, ready retention ledger, verified file report, commercial readiness report presence, and explicit approval before evidence can move into release publication decisions. Command planning orders observation, digest computation, comparison, report, ledger, seal, attachment, and promotion-gate work for workflow materialization. Status reporting separates foundation readiness from real retained file evidence and commercial publication readiness. Commercial publication remains blocked until real retained file evidence is captured and approved.
 
 ## Recommended First Deliverable
 

src/Sigtran.NET.Tests/Program.cs

@@ -5144,16 +5144,17 @@ static void SigtranCommercialEvidenceFileVerificationStatusSummarizesReadiness()
     IReadOnlyList<string> capabilities = SigtranCommercialEvidenceFileVerificationStatus.GetCompletedCapabilities();
     IReadOnlyList<string> blockers = SigtranCommercialEvidenceFileVerificationStatus.GetDefaultBlockers();
 
-    AssertEqual(9, SigtranCommercialEvidenceFileVerificationStatus.CompletedUnitCount, "file verification completed unit count");
-    AssertEqual(9, capabilities.Count, "file verification capability count");
+    AssertEqual(10, SigtranCommercialEvidenceFileVerificationStatus.CompletedUnitCount, "file verification completed unit count");
+    AssertEqual(10, capabilities.Count, "file verification capability count");
     Assert(capabilities.Contains("verified-promotion-gate"), "file verification status should include promotion gate");
     Assert(capabilities.Contains("file-verification-command-plan"), "file verification status should include command plan");
     Assert(capabilities.Contains("status-reporting"), "file verification status should include status reporting");
+    Assert(capabilities.Contains("documentation"), "file verification status should include documentation");
     Assert(SigtranCommercialEvidenceFileVerificationStatus.FileVerificationFoundationReady, SigtranCommercialEvidenceFileVerificationStatus.Describe());
     Assert(!SigtranCommercialEvidenceFileVerificationStatus.RealRetainedFileEvidenceReady, SigtranCommercialEvidenceFileVerificationStatus.Describe());
     Assert(!SigtranCommercialEvidenceFileVerificationStatus.CommercialPublicationReady, SigtranCommercialEvidenceFileVerificationStatus.Describe());
     Assert(blockers.Contains("real-retained-file-evidence-required"), "file verification status should require real retained file evidence");
-    Assert(blockers.Contains("status-final-validation-pending"), "file verification status should keep final validation blocker before Unit 10");
+    Assert(!blockers.Contains("status-final-validation-pending"), "file verification status should clear final validation blocker");
 }
 
 static SigtranCommercialEvidenceFileVerificationCommandPlan CreateDefaultCommercialEvidenceFileVerificationCommandPlan()
@@ -5285,7 +5286,8 @@ static void SigtranStatusCapabilitiesUseDomainDocumentationLabels()
         SigtranReleaseCandidatePublicationStatus.GetCompletedCapabilities(),
         SigtranCommercialEvidenceReadinessLockdownStatus.GetCompletedCapabilities(),
         SigtranCommercialEvidenceExecutionStatus.GetCompletedCapabilities(),
-        SigtranCommercialEvidenceArtifactIntakeStatus.GetCompletedCapabilities()
+        SigtranCommercialEvidenceArtifactIntakeStatus.GetCompletedCapabilities(),
+        SigtranCommercialEvidenceFileVerificationStatus.GetCompletedCapabilities()
     ];
 
     foreach (IReadOnlyList<string> capabilities in statusCapabilities)

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

@@ -15,20 +15,20 @@ public static class SigtranCommercialEvidenceFileVerificationStatus
         "publication-attachments",
         "verified-promotion-gate",
         "file-verification-command-plan",
-        "status-reporting"
+        "status-reporting",
+        "documentation"
     ];
 
     private static readonly string[] DefaultBlockers =
     [
-        "real-retained-file-evidence-required",
-        "status-final-validation-pending"
+        "real-retained-file-evidence-required"
     ];
 
     /// <summary>The status label.</summary>
     public const string StatusLabel = "Commercial Evidence File Verification";
 
     /// <summary>The number of completed commercial evidence file verification work units.</summary>
-    public const int CompletedUnitCount = 9;
+    public const int CompletedUnitCount = 10;
 
     /// <summary>Returns the completed file verification capability names.</summary>
     /// <returns>The completed capability names.</returns>