Add native SCTP lab verification framework

Author: ammarheidari

README.md

@@ -46,6 +46,7 @@ The first production milestone is M3UA over a transport abstraction. SCCP, TCAP,
 | Performance and capacity | Phase 14 foundation-ready: performance capability catalog, benchmark scenario catalog, capacity profile, throughput targets, latency budgets, load-test plan, resource budget, readiness report, performance CI profile, and status report added; production performance claims still require representative benchmark evidence |
 | API lifecycle | Phase 15 foundation-ready: API surface catalog, stability contracts, version matrix, deprecation policy, migration guide catalog, breaking-change review policy, public API baseline, readiness report, API lifecycle CI profile, and status report added; stable API lifecycle claims still require commercial readiness and validation evidence |
 | Configuration readiness | Phase 16 foundation-ready: configuration schema, validation helpers, environment matrix, secret policy, transport configuration, routing configuration, readiness report, configuration CI profile, commercial configuration gate, and status report added; production configuration still requires commercial readiness and deployment review |
+| Native SCTP lab verification | Phase 17 foundation-ready: Linux SCTP lab scenario catalog, artifact manifest, run plan, command set, run reports, evidence registry, readiness report, lab CI profile, commercial gate, and status report added; production verification still requires complete passing Linux SCTP evidence |
 | Package governance | Phase 7 policy added: current package metadata is tracked; commercial target still requires package signing and SBOM automation |
 | Security governance | Phase 7 security policy added with private disclosure and severity response targets |
 | Compatibility policy | Phase 7 policy added: net10.0 target, SemVer, pre-stable breaking-change allowance, and stable major-version rule |
@@ -156,6 +157,8 @@ if (!M3uaTypedMessageParser.TryParseSignallingCongestion(
 - [Phase 15 Summary](docs/PHASE15_SUMMARY.md)
 - [Phase 16 Configuration](docs/PHASE16_CONFIGURATION.md)
 - [Phase 16 Summary](docs/PHASE16_SUMMARY.md)
+- [Phase 17 Native SCTP Lab Verification](docs/PHASE17_NATIVE_SCTP_LAB_VERIFICATION.md)
+- [Phase 17 Summary](docs/PHASE17_SUMMARY.md)
 - [Continuous Integration](docs/CI.md)
 - [SCTP Transport](docs/SCTP_TRANSPORT.md)
 - [Compatibility policy](docs/COMPATIBILITY.md)
@@ -185,6 +188,7 @@ The roadmap is intentionally conservative:
 14. Complete performance, capacity, and benchmark readiness foundations.
 15. Complete API stability, deprecation, and migration readiness foundations.
 16. Complete configuration, policy, and environment readiness foundations.
+17. Complete native SCTP lab verification framework and capture Linux SCTP evidence.
 
 ## License
 

docs/CI.md

@@ -67,3 +67,9 @@ The profile reuses build, test, and pack commands and requires public API diff r
 Phase 16 adds `SigtranConfigurationCi.CreateDefault()` as the metadata contract for validating configuration readiness.
 
 The profile reuses build, test, and pack commands, requires configuration readiness, and rejects production plaintext secrets.
+
+## Native SCTP Lab CI
+
+Phase 17 adds `SigtranNativeSctpLabCi.CreateDefault()` as the metadata contract for native SCTP verification.
+
+The profile is opt-in, Linux-only, and enabled by `SIGTRAN_NATIVE_SCTP_LAB`. Real runs must retain artifacts under `SIGTRAN_NATIVE_SCTP_ARTIFACT_ROOT`.

docs/MAP.md

@@ -149,6 +149,6 @@ The facade hides TCAP transaction-id, invoke-id, dialogue portion, and component
 
 ## Readiness
 
-`MapSmsPhase5Readiness.GetReport()` reports the current MAP SMS profile status. The foundation is complete when operation metadata, address primitives, ForwardSM codecs, SRI-SM, delivery status, AlertServiceCentre, errors/extensions, and the TCAP client facade are present.
+`MapSmsReadiness.GetReport()` reports the current MAP SMS profile status. The foundation is complete when operation metadata, address primitives, ForwardSM codecs, SRI-SM, delivery status, AlertServiceCentre, errors/extensions, and the TCAP client facade are present.
 
 Production readiness remains false until external MAP SMS interoperability vectors and operator-profile validation are added.

docs/PHASE10_RELEASE_AUTOMATION.md

@@ -70,6 +70,6 @@ Required secret names are recorded as metadata only: `NUGET_API_KEY` and `SIGNIN
 
 ## Phase Status
 
-`SigtranPhase10Status.Describe()` summarizes the completed Phase 10 units.
+`SigtranReleaseAutomationStatus.Describe()` summarizes the completed Phase 10 units.
 
 The phase foundation can be ready while stable commercial publication remains blocked by wider commercial gates such as real signing, SBOM generation, native SCTP lab evidence, and external interoperability evidence.

docs/PHASE10_SUMMARY.md

@@ -19,7 +19,7 @@ Phase 10 adds the release automation and supply-chain foundation for SIGTRAN.NET
 
 The Phase 10 SDK foundation is complete.
 
-`SigtranPhase10Status.FoundationReady` is expected to be true. `CommercialStableReleaseReady` remains false until the wider commercial gates are satisfied, including native SCTP lab verification, external interoperability evidence, real signing, and real SBOM generation.
+`SigtranReleaseAutomationStatus.FoundationReady` is expected to be true. `CommercialStableReleaseReady` remains false until the wider commercial gates are satisfied, including native SCTP lab verification, external interoperability evidence, real signing, and real SBOM generation.
 
 ## Production Gate
 

docs/PHASE11_DEVELOPER_EXPERIENCE.md

@@ -72,4 +72,4 @@ Developer documentation is ready when roadmap, quickstart, API index, and troubl
 
 ## Phase Status
 
-`SigtranPhase11Status.Describe()` summarizes the completed Phase 11 units and separates developer adoption readiness from enterprise production readiness.
+`SigtranDeveloperExperienceStatus.Describe()` summarizes the completed Phase 11 units and separates developer adoption readiness from enterprise production readiness.

docs/PHASE11_SUMMARY.md

@@ -19,4 +19,4 @@ Phase 11 adds the developer experience and adoption foundation for SIGTRAN.NET.
 
 The Phase 11 SDK foundation is complete.
 
-`SigtranPhase11Status.FoundationReady` is expected to be true. `EnterpriseProductionReady` remains false until commercial readiness is complete, including native SCTP evidence, external interoperability evidence, real signing, and real SBOM generation.
+`SigtranDeveloperExperienceStatus.FoundationReady` is expected to be true. `EnterpriseProductionReady` remains false until commercial readiness is complete, including native SCTP evidence, external interoperability evidence, real signing, and real SBOM generation.

docs/PHASE12_OPERATIONS.md

@@ -52,4 +52,4 @@ Production operations remain blocked until wider commercial readiness is complet
 
 ## Phase Status
 
-`SigtranPhase12Status.Describe()` summarizes the completed Phase 12 units and separates operations foundation readiness from production operations readiness.
+`SigtranOperationsStatus.Describe()` summarizes the completed Phase 12 units and separates operations foundation readiness from production operations readiness.

docs/PHASE12_SUMMARY.md

@@ -19,4 +19,4 @@ Phase 12 adds the production operations and support foundation for SIGTRAN.NET.
 
 The Phase 12 operations foundation is complete.
 
-`SigtranPhase12Status.FoundationReady` is expected to be true. `ProductionOperationsReady` remains false until wider commercial readiness is complete, including native SCTP evidence, external interoperability evidence, real signing, and real SBOM generation.
+`SigtranOperationsStatus.FoundationReady` is expected to be true. `ProductionOperationsReady` remains false until wider commercial readiness is complete, including native SCTP evidence, external interoperability evidence, real signing, and real SBOM generation.

docs/PHASE13_COMPLIANCE.md

@@ -67,4 +67,4 @@ The current gate should report compliance foundation readiness as true, while en
 
 ## Phase Status
 
-`SigtranPhase13Status.Describe()` summarizes the completed Phase 13 units and separates compliance foundation readiness from enterprise compliance production claims.
+`SigtranComplianceStatus.Describe()` summarizes the completed Phase 13 units and separates compliance foundation readiness from enterprise compliance production claims.