AsiBackbone Documentation

Governed decisions for .NET applications

AsiBackbone is a .NET governance and policy-control package family for accountable software execution: policy context, explicit decision outcomes, decision records, scoped authority, and host-owned execution.

Most software can tell you what happened. Far less can show that an action was evaluated before it executed, under which policy, and with what evidence. Evaluate AsiBackbone when a consequential host-owned action needs policy provenance, acknowledgment, scoped continuation authority, or durable decision evidence.

AsiBackbone is not an intelligence engine. It 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. See Project Boundaries and Non-Claims for the canonical boundary reference.

Start here

Decide whether it fits Compare the product's good and poor fits, including when a simpler design is enough. Gate an API in 15 minutes Run the standard API gating path end to end in a minimal host. Adopt it in a host Install, register, and configure the package family step by step. Understand runtime decisions See how the policy evaluator pipeline produces a governance decision. Harden a deployment Persist, observe, sign, and verify decisions in production. Find a package or type Browse the generated API reference for every shipped package.

Is AsiBackbone a fit?

Consider AsiBackbone when

a consequential host-owned action needs policy provenance, acknowledgment, scoped continuation authority, or durable decision evidence.

See Good product fit for the capabilities that make it a reasonable candidate.

Prefer a simpler design when

the action is low risk and ordinary framework authorization, application services, and logs already provide the evidence you need.

See Poor product fit, and the general comparisons When ASP.NET Core Authorization Is Enough and When a Simple Application Service Is Enough.

Product documentation versus architecture education

This site is authoritative for concrete AsiBackbone package, API, configuration, runtime, integration, security, operations, compatibility, release, and maintainer behavior.

For architecture concepts, tutorials, comparisons, tradeoffs, labs, and general governed-execution education, use AsiBackbone Learning. Its Architecture Glossary is the canonical educational terminology reference, with lineage maintained in Terminology and Established Architecture Concepts. Learning does not override product API or runtime truth documented here.

See Documentation Ownership for the cross-repository ownership matrix and contribution routing rule.

More tasks

Goal Start here
Register the package family in a host AddAsiBackbone Builder Facade and Getting Started
Find articles by package or topic Documentation Articles
Run a concrete integration path Plain ASP.NET Core Host Sample and Samples & Scenarios
Check compatibility, release changes, or upgrade history Releases & Compatibility
Review readiness, benchmarks, or quality evidence Maintainer & Quality Evidence

The DocFX header search is available for package names, API concepts, and article titles. Source for every page lives under docs/, and the site header's AsiBackbone menu includes a Framework Repository link for source review or edits.

Current stable package family

Stable 7.x package family. The current release is 7.5.4.

7.5.4 adds Sigstore keyless signatures for GitHub release build packages, advances Aspire sample hosting, refreshes GitHub Actions, and strengthens package compatibility validation without changing public APIs, durable contracts, declared runtime dependency minimums, or runtime decision behavior.

Managed assemblies retain binary identity 7.0.0.0 throughout the compatible 7.x line.

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.

Product documentation map

Overview and boundaries

Get started

Packages and API

Implementation guides

Security and operations

Releases and compatibility

Historical release notes and verification records remain available under Releases & Compatibility without occupying the primary adoption path.

Maintainer and quality evidence

Historical records

Historical and superseded records remain public and searchable for traceability without being presented as current implementation guidance.

Learn the architecture

General architecture teaching is maintained in AsiBackbone Learning. Retained conceptual articles in this repository remain available for continuity and historical context, but they are intentionally separated from the main implementation/API navigation.

Learn the patterns

AsiBackbone Learning

Practical .NET architecture tutorials, labs, runnable samples, and reference patterns for governed execution, secure applications, AI integration, and policy-driven systems, including comparisons that show when these patterns are unnecessary.

Add governed decisions

AsiBackbone Current site

A .NET governance and policy-control framework for auditable decision flows: policy evaluation, auditable decision records, acknowledgment workflows, capability-based authorization, host-owned execution boundaries, and ASP.NET Core integration.

Follow the integration

AsiBackbone Reference Application

An NCAT-generated ASP.NET Core host that records the step-by-step integration of AsiBackbone, with host-specific API documentation and runnable governance examples added as the walkthrough progresses.

Design philosophy

We favor architectures where consequential operations are explicit, constrained, reviewable, and auditable.

We also document when these patterns are unnecessary: see Poor product fit, When ASP.NET Core Authorization Is Enough, and When a Simple Application Service Is Enough.

The projects focus on practical .NET engineering. They do not claim regulatory certification or automatic compliance. See Project Boundaries and Non-Claims.