Documentation Articles

This section maps the AsiBackbone documentation set for the stable 2.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. Long pages use the left navigation tree and the right In this article rail for local heading navigation. 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 2.x is the current package line. 2.1.1 is the current compatible minor release. It preserves the 2.0.0 public package and namespace boundary while adding optional policy fast-abort support, builder-style audit residue construction, benchmark guidance, custom decision-policy examples, and in-memory outbox hardening. 2.0.0 established the simplified AsiBackbone.* package and namespace identity after the 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. OpenTelemetry is the concrete released governance-emission provider. Event Hubs, Purview, Azure-specific SDK adapters, Aspire runtime packages, robotics, immutable-storage, and additional 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 now includes explicit Release Cadence and Readiness guidance for patch/minor/major release selection, early-major stabilization, package metadata assets, Source Link, SBOM/provenance, documentation links, and future package identity or namespace changes.

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

These pages cover the durability, governance-emission, signing, diagnostics, testing, and template surfaces carried forward into the current 2.x package family.

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/design material. They are not released provider packages unless a future release explicitly says so.

Advanced scenarios

Scenario pages describe applied patterns. They remain optional and do not imply current package implementation beyond the documented seams.

Quality and release process

Historical design records

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

Table of Contents