AsiBackbone.Storage.InMemory 2.1.1

AsiBackbone.Storage.InMemory

Non-durable in-memory storage helpers for Accountable Systems Infrastructure local validation, samples, and tests.

This package provides non-durable storage implementations that make it easy to exercise ASI Backbone governance flows without requiring a database, EF Core provider, or host infrastructure.

New to AsiBackbone? Start with the concept, not this package: Intent to Execution: An Accountability Pattern and the documentation site. This README covers one package in the family.

Important: This package is not durable storage. Do not use it as a production audit ledger, compliance archive, tamper-evident store, or long-term accountability store.

What this package provides

• In-memory audit ledger behavior for local validation and tests.
• In-memory governance outbox behavior for local validation, samples, and integration tests.
• Storage implementations that depend on AsiBackbone.Core only.
• A simple bridge for samples that need audit or outbox records without introducing EF Core or a database.

Intended usage

Use this package when:

• writing unit tests or integration tests around policy evaluation;
• building sample applications;
• validating audit residue and audit ledger behavior locally;
• validating governance outbox state transitions locally;
• demonstrating host-neutral ASI Backbone flows before adding durable storage.

For production persistence, use a host-owned durable storage strategy such as AsiBackbone.EntityFrameworkCore or a custom implementation of the Core storage contracts.

In-memory outbox concurrency semantics

InMemoryGovernanceOutboxStore is single-process and non-durable. It does not claim work across replicas, coordinate distributed workers, or provide exactly-once provider delivery.

Within that single process, same-entry outbox status transitions use compare-and-swap updates so local tests do not accidentally observe last-write-wins behavior. Delivered and dead-lettered entries are treated as terminal for subsequent in-memory state updates, and retryable failure updates against the same entry advance from the latest observed entry state.

Boundary

The in-memory package should remain lightweight and host-neutral. It should not select a database provider, own migrations, expose ASP.NET Core middleware, or imply durable compliance-grade audit storage.