Documentation Articles

This section maps the AsiBackbone documentation set for the stable 3.x Accountable Systems Infrastructure package family.

Important

In this software project, ASI means Accountable Systems Infrastructure. AsiBackbone is governance infrastructure for accountable software decision flow, not an artificial superintelligence implementation. See Project Boundaries and Non-Claims for the canonical boundary reference.

Use the header search box for package names, API concepts, and article titles. Search is enabled for the published DocFX site; if a newly merged page is missing from results, wait for the documentation publish workflow to finish and refresh the browser cache. Source files live under docs/ in the repository, and the site header includes a Repository link for source review or edits.

Current stable package posture

Stable 3.2.x package family. 3.2.1 is the current patch release. The package family carries forward the governance-spine surface, including the explicit capability-grant validation profiles introduced in 3.2.0, while 3.2.1 updates the canonical repository, documentation, Source Link, citation, SBOM, validation, and package metadata following the transfer to the AsiBackbone GitHub organization.

The historical 3.0.0 release established the current major line and binary assembly identity while preserving the AsiBackbone.* package IDs and namespaces established by the 2.0.0 public rename from CDCavell.AsiBackbone.*.

Released stable package surfaces include Core, DependencyInjection, Storage.InMemory, EntityFrameworkCore, AspNetCore, Testing, Templates, Analyzers, OpenTelemetry, Signing.LocalDevelopment, and Signing.ManagedKey.

3.2.1 carries forward the explicit capability-grant validation profiles introduced in 3.2.0 for consequential execution boundaries and intentional metadata-only inspection while updating canonical repository, documentation, Source Link, citation, SBOM, validation, and package metadata following the transfer to the AsiBackbone GitHub organization.

Event Hubs, Purview, Azure-specific non-signing SDK adapters, Aspire runtime packages, robotics, immutable storage, and additional non-signing provider packages remain design-only, strategy-only, sample-only, host-owned, or future-provider work unless a later stable release explicitly ships them.

The release process includes explicit Release Cadence and Readiness guidance for patch, minor, and major release selection, package metadata, Source Link, SBOM/provenance, documentation links, and future package identity or namespace changes. The 3.2.1 Consumer Verification Guide gives consumers a conservative package-source, package ID, capability-validation, Source Link, SBOM/provenance, and deferred-signing verification path.

Start here / implementation-first usage

Core engineering concepts and domain language

Optional conceptual background

These pages remain available for readers who want the broader framing. They are not required before using the packages.

Adoption and use-case guidance

Package integration guides

Durability, observability, signing, diagnostics, and developer experience

Released provider package documentation

Security and cryptographic boundaries

These pages describe signing, verification, capability, and cryptographic-hardening posture. They do not imply production tamper-evidence unless a concrete signing, storage, verification, and key-management path is deployed by the host.

Design-only and future provider strategy

These pages remain available as strategy or design material. They are not released provider packages unless a future release explicitly says so.

Advanced scenarios

Quality and release process

Historical design records

Historical pages are retained for traceability and are separated from current stable usage.

Table of Contents