AsiBackbone.Core 2.2.0

AsiBackbone

Accountable Systems Infrastructure for governed .NET decision flow.

AI may provide the intellect. AsiBackbone provides the accountable spine.

The practical problem

Most software can tell you what happened. Far less can show that an action was evaluated before it executed: which rules shaped the decision, which policy version applied, whether acknowledgment was required, how follow-on authority was scoped, and where the host took responsibility for execution.

AsiBackbone is a .NET package family for that decision boundary. It helps a host application build safe policy context, evaluate constraints, return a structured decision, preserve a decision receipt, optionally scope continuation, and then let the host decide whether and how to execute.

In this software project, ASI means Accountable Systems Infrastructure.

Implementation-first mental model

A normal API adoption path looks like this:

HTTP request
  -> host builds safe evaluation context
  -> host-owned rules evaluate the request
  -> AsiBackbone returns a GovernanceDecision
  -> host writes audit residue / decision receipt
  -> host continues only when decision.CanProceed is true

Use plain engineering translations first:

First code path

The snippet below is an intentionally small README slice, not a complete Program.cs. It shows the primary governance path: build safe context, evaluate policy, write audit residue, and let the host execute only after the decision allows it. The full compile-ready walkthrough lives in First 15 Minutes: Standard API Gating.

// Registration: Core evaluator + one host-owned rule + local in-memory audit sink.
builder.Services.AddAsiBackboneAspNetCore();
builder.Services.AddSingleton<InMemoryAuditLedger>();
builder.Services.AddSingleton<IAsiBackboneAuditSink>(sp =>
    sp.GetRequiredService<InMemoryAuditLedger>());
builder.Services.AddSingleton<IAsiBackboneConstraint<AsiBackboneConstraintEvaluationContext>, AllowedRegionConstraint>();
builder.Services.AddSingleton<IAsiBackbonePolicyEvaluator<AsiBackboneConstraintEvaluationContext>>(sp =>
    new DefaultAsiBackbonePolicyEvaluator<AsiBackboneConstraintEvaluationContext>(
        sp.GetServices<IAsiBackboneConstraint<AsiBackboneConstraintEvaluationContext>>(),
        decisionPolicy: null,
        options: new AsiBackbonePolicyEvaluatorOptions { DenyWhenNoConstraints = true }));

app.MapPost("/api/orders/{region}/approve", async (
    string region,
    HttpContext httpContext,
    IAsiBackbonePolicyEvaluator<AsiBackboneConstraintEvaluationContext> evaluator,
    IAsiBackboneAuditSink auditSink,
    CancellationToken cancellationToken) =>
{
    var metadata = new Dictionary<string, string>(StringComparer.Ordinal)
    {
        ["operation"] = "orders.approve",
        ["region"] = region,
        ["risk"] = "routine-api-write"
    };

    var context = new AsiBackboneConstraintEvaluationContext(
        correlationId: httpContext.TraceIdentifier,
        policyVersion: "policy-v1",
        policyHash: "policy-hash-v1",
        metadata: metadata);

    GovernanceDecision decision = await evaluator.EvaluateAsync(context, cancellationToken);

    AuditResidue residue = AuditResidue.FromDecision(
        AsiBackboneActorContext.Human("example-user", "Example User"),
        operationName: "orders.approve",
        decision,
        metadata: context.Metadata);

    await auditSink.WriteAsync(residue, cancellationToken);

    if (!decision.CanProceed)
    {
        return Results.Json(new
        {
            allowed = false,
            decision = decision.Outcome.ToString(),
            decision.ReasonCodes,
            auditEventId = residue.EventId
        }, statusCode: StatusCodes.Status403Forbidden);
    }

    // Host-owned execution starts here. AsiBackbone does not approve the order itself.
    return Results.Ok(new
    {
        allowed = true,
        message = "Host order approval would run after this governance decision.",
        auditEventId = residue.EventId
    });
});

For production-style hosts, add durable audit/outbox persistence, signing or verification, DLP/classification, provider emission, and operational monitoring only where the host has explicitly chosen and configured those boundaries.

Package family

Stable 2.2.x package family. 2.2.0 is the current compatible minor release. 2.0.0 began the current major release line after the public package and namespace identity moved from CDCavell.AsiBackbone.* to AsiBackbone.*. The package family carries forward the governance-spine surface with builder-facade, analyzer, OpenTelemetry, signing-provider, testing-harness, template package, endpoint diagnostics, endpoint reduced metadata mode, sample, Source Link metadata, package SBOM/provenance artifacts, benchmark guidance, custom decision-policy examples, and documentation-alignment surfaces.

Future Event Hubs, Purview, Azure-specific, gateway, robotics, immutable-storage, or additional provider packages are not part of the stable contract unless separately reviewed and released.

Start here

For implementation-first adoption:

• Implementation-First Adoption Path — plain engineering translations and the recommended first reading path.
• First 15 Minutes: Standard API Gating
• AddAsiBackbone Builder Facade
• dotnet new Templates
• Reference Deployment: Plain ASP.NET Core Host Evidence
• Testing Harness
• Project Boundaries and Non-Claims
• Terminology Map
• Progressive Adoption Ladder

For optional conceptual background:

• Intent to Execution: An Accountability Pattern
• Core Governance Flow Diagrams
• ASI Backbone Concept Synopsis
• Dynamic Liability Handshake
• Core Domain Language
• Host-Owned Execution Enforcement

The full, categorized documentation set lives at the documentation site.

Current status

Stable 2.2.x is the current released line, with 2.2.0 as the current compatible minor release. This release preserves the simplified AsiBackbone.* package and namespace identity established by 2.0.0 while carrying forward the Core foundation, builder-facade registration surface, in-memory validation storage, EF Core host-owned persistence, ASP.NET Core integration, test harness helpers, dotnet new templates, analyzers, the OpenTelemetry provider, local-development signing, the managed-key signing adapter boundary, samples, release validation, package SBOM/provenance artifacts, benchmark guidance, custom decision-policy examples, Source Link metadata validation, endpoint-governance reduced metadata mode, and host-validation documentation.

The stable API contract is documented in API Compatibility and SemVer; the original 1.0.0 baseline, 1.1.0 addendum, 1.2.0 minor release boundary, 1.2.1 patch release boundary, 2.0.0 package/namespace migration boundary, 2.0.1 patch release boundary, 2.0.2 package-icon correction boundary, 2.1.0 minor release boundary, and 2.2.0 minor release boundary are recorded in the Historical Stable API Review, 1.1.x Release Notes, 1.2.0 Release Notes, 1.2.1 Release Notes, 2.0.0 Release Notes, 2.0.1 Release Notes, 2.0.2 Release Notes, 2.1.0 Release Notes, and 2.2.0 Release Notes.

Security and vulnerability reporting

Please report sensitive concerns through the repository Security Policy.

Relationship to NetCoreApplicationTemplate

NetCoreApplicationTemplate may be used as a preferred host baseline during development and validation, but AsiBackbone does not require it.

NetCoreApplicationTemplate = preferred host baseline
AsiBackbone               = optional governance/module package family
Consumer application      = chooses whether to use either or both

A consumer should be able to use AsiBackbone in an application generated from NetCoreApplicationTemplate, in an existing ASP.NET Core application, or in a custom host that provides the required infrastructure. See NetCoreApplicationTemplate Host Validation.

Alignment boundary

AsiBackbone is a governance spine, not an intelligence engine. It implements governance-oriented software primitives for accountable decision flow and keeps execution authority with the host application. See Project Boundaries and Non-Claims for the full scope statement and safe wording guidance.

Current NuGet packages are not signed release artifacts from the project maintainer. Package signing may be adopted later through .NET Foundation-supported infrastructure or another reviewed release-signing process.

Design principles

• Keep Core small.
• Keep Core dependency-light.
• Avoid hidden host assumptions.
• Prefer explicit integration over magic.
• Let the host own infrastructure.