Release 1.1.0
Summary
AsiBackbone 1.1.0 is an additive minor release over 1.0.0 that expands the package family from the first stable governance foundation into a broader Accountable Systems Infrastructure release line.
This release keeps the project boundary clear: AsiBackbone remains governance infrastructure for accountable .NET decision flow. It does not implement artificial superintelligence, host AI models, control robots, certify compliance, or provide production tamper-evidence, immutability, or legal non-repudiation by default.
Highlights
- Promotes package version metadata to
1.1.0. - Preserves
AssemblyVersionas1.0.0.0for compatible1.xbinary identity. - Expands the stable package family to include analyzers, OpenTelemetry projection, and signing-provider boundaries.
- Adds release validation improvements for version metadata, generated package versions, and NuGet package metadata.
- Updates README, changelog, citation metadata, Zenodo metadata, documentation index, getting started guidance, release validation guidance, and release readiness checklist.
Stable Package Family
The 1.1.0 release includes:
CDCavell.AsiBackbone.CoreCDCavell.AsiBackbone.Storage.InMemoryCDCavell.AsiBackbone.EntityFrameworkCoreCDCavell.AsiBackbone.AspNetCoreCDCavell.AsiBackbone.AnalyzersCDCavell.AsiBackbone.OpenTelemetryCDCavell.AsiBackbone.Signing.LocalDevelopmentCDCavell.AsiBackbone.Signing.ManagedKey
Added
- Provider-neutral governance emission contracts and envelope/result/error primitives.
- Durable governance outbox and audit residue lifecycle release surfaces.
CDCavell.AsiBackbone.OpenTelemetryas the first concrete governance emission provider package.CDCavell.AsiBackbone.Analyzersfor Roslyn analyzer safety rails around governance persistence and continuation flows.- Signing-ready receipt, canonical hashing/signing, and verification-policy seams.
CDCavell.AsiBackbone.Signing.LocalDevelopmentfor local-development RSA signing and verification in tests, samples, and proof paths.CDCavell.AsiBackbone.Signing.ManagedKeyas a provider-neutral managed-key signing adapter boundary.- ASP.NET Core endpoint governance metadata and hosted outbox drain integration.
Changed
- Updated central release metadata from
1.0.0to1.1.0. - Updated
FileVersionto1.1.0.0. - Updated
CITATION.cffand.zenodo.jsonfor the1.1.0release. - Updated release-facing documentation to describe the expanded
1.1.0package family. - Updated NuGet metadata validation to expect all eight release package artifacts.
- Updated README validation anchors for the
1.1.0stable package family. - Updated release validation workflow to run version metadata checks before build and generated package-version checks after package creation.
- Expanded stable package integration smoke testing to reference all eight package artifacts.
Boundary Notes
The following remain outside the 1.1.0 stable package boundary unless separately reviewed and released:
- Event Hubs provider implementation
- Purview provider implementation
- Azure-specific SDK adapters
- Azure Key Vault or Managed HSM live integration
- Robotics or physical execution
- Immutable storage
- External anchoring
- Production tamper-evidence or non-repudiation guarantees
The managed-key signing adapter does not ship a live Azure Key Vault, Managed HSM, cloud KMS, HSM, certificate-store, or credential-provider implementation by default. The host supplies the actual managed-key client, credentials, key operations, verification path, monitoring, and operational policy.
Validation
Release validation should confirm:
- version metadata consistency;
- restore, build, format, and test pass;
- DocFX documentation builds;
- all package projects pack successfully;
- generated package versions match
1.1.0; - NuGet package metadata validation passes;
- external consumer smoke test passes;
- stable package integration smoke test passes.