ASI Backbone Documentation
Welcome to the AsiBackbone documentation site.
In this software project, ASI means Accountable Systems Infrastructure. AsiBackbone is a .NET governance and policy-control package family implemented as practical software infrastructure. The project is a governance spine, not an intelligence engine.
Important
AsiBackbone provides framework-neutral building blocks and host integration seams for governing consequential actions in software systems. Host applications remain responsible for authentication, authorization, execution, persistence, deployment, monitoring, compliance review, and operational controls. For the canonical boundary reference, see Project Boundaries and Non-Claims.
Search, navigation, and source links
The documentation site uses the DocFX search box in the header. Source for every page lives in the repository under docs/, and the site header includes a Repository link for viewing or editing documentation files.
Start here
These pages are the best first stops for implementation-first adoption.
- Implementation-First Adoption Path
- First 15 Minutes: Standard API Gating
- AddAsiBackbone Builder Facade
- dotnet new Templates
- Reference Deployment: Plain ASP.NET Core Host Evidence
- Terminology Map
- Project Boundaries and Non-Claims
- Progressive Adoption Ladder
- Getting Started
- Documentation Articles
- Security Policy and Vulnerability Disclosure
Current stable package family
Stable 2.x is the current release 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.
AsiBackbone.Core
AsiBackbone.DependencyInjection
AsiBackbone.Storage.InMemory
AsiBackbone.EntityFrameworkCore
AsiBackbone.AspNetCore
AsiBackbone.Testing
AsiBackbone.Templates
AsiBackbone.Analyzers
AsiBackbone.OpenTelemetry
AsiBackbone.Signing.LocalDevelopment
AsiBackbone.Signing.ManagedKey
Package-specific READMEs and release notes define which surfaces are stable, optional, local-only, or future-facing. A design page being present in the documentation does not mean the corresponding provider package has shipped as stable.
Core documentation areas
Implementation-first adoption
- Implementation-First Adoption Path
- First 15 Minutes: Standard API Gating
- AddAsiBackbone Builder Facade
- dotnet new Templates
- Reference Deployment: Plain ASP.NET Core Host Evidence
- Plain ASP.NET Core Host Sample
- Aspire AppHost Sample
- NetCoreApplicationTemplate Host Validation
Core concepts and domain language
- Core Governance Flow Diagrams
- Core Domain Language
- Policy Evaluator Pipeline
- Custom Decision Policy Examples
- Host-Owned Execution Enforcement
- Dynamic Liability Handshake
- Glossary
Package integration, observability, and signing
- EF Core Integration Boundary
- ASP.NET Core Integration Boundary
- ASP.NET Core Endpoint Governance
- Testing Harness
- Schema Versioning
- API Compatibility and SemVer
- Observability and Governance Emission Architecture
- Governance Emission Contract
- Durable Audit and Outbox Persistence
- Hosted Governance Outbox Drain
- OpenTelemetry Governance Emission Provider
- Signing Provider Package Boundary
- Managed-Key Signing Provider
Optional conceptual and scenario background
- Intent to Execution: An Accountability Pattern
- ASI Backbone Concept Synopsis
- Gateway and Regional Policy Flow
- Equations and Toy Models
- Governance Tool Comparisons
- Adoption and Target Use Cases
- Enterprise Adoption Personas
- Government and Regulated Systems
Security and cryptographic boundaries
- Project Boundaries and Non-Claims
- Production Wording and Stable Signing Boundaries
- Supply-Chain Provenance and Package SBOMs
- Signing-Ready Receipts and Key Handling
- Signed Audit and Outbox Records
- Verification Policy and Result Handling
- Key Rotation and Retired-Key Verification
- Capability Grant Hardening
- Audit Integrity Chain Model
- Cryptographic Security Posture and Production Guidance
- Cryptographic Security Hardening Roadmap