The packages are the Infrastructure and Build Ecosystem pillars of the Anarchy I/O Toolkit platform, each adoptable on its own. Every project under src/ is one package. Its package ID, assembly name and root namespace are all Anarchy.Toolkit.<project name> (src/Core.Events/ → Anarchy.Toolkit.Core.Events). Each package’s README, linked below, is also displayed on NuGet.org.

Stacked modular blocks forming layers, flat outline illustration, dark background with red-orange accent, wide banner

New here? The anarchy-toolkit CLI tool and the Automation.Build build components are the quickest way in; see Getting Started.

Packages are grouped by layer: a package may depend only on its own layer or the layers below it, and, in this repository, within a layer mostly on its name ancestors (Web.MockServer.Ui on Web.MockServer), with a few listed exceptions checked by make check_package_hierarchy. The dependency map draws these references.

Every package is published to NuGet.org under the anarchy-io profile; the 📦 next to each name opens its NuGet.org page.

Legend: [Abs] abstractions only · [Impl] concrete implementation. Depends on lists sibling toolkit packages only (framework and NuGet dependencies are omitted).

Which package do I need?

Packages that share a family name are split by role. The parent holds what every provider shares; the suffix or sibling adds one concern. Pick by what your project does.

If you need… Install Notes
The build and command-line operations as a library: scaffolding, layering checks, release versioning and notes, Git hooks, boilerplate Automation Referenced by the two packages below; reference it directly only to write your own tooling on top.
Build targets for a solution (compile, lint, test, layering, pack, release, Docker) Automation.Build Referenced from build/_build.csproj; brings Automation.
The anarchy-toolkit command (bootstrap, scaffold, config, skills install) Automation.Build.Cli A .NET global tool, not a project reference; it uses Automation and Automation.Build. Preferences are optional.
Relational persistence for an application: unit of work, repository bases, policies, health reports Infrastructure.Persistence.Db.Postgres, .Oracle or .Mysql One provider package per database; each brings Infrastructure.Persistence.Db. Reference Infrastructure.Persistence.Db itself only to write a new provider.
Integration tests against a real database Testing.Db.Postgres, .Oracle or .Mysql Test projects only; one per provider, matching the persistence package. They bring Testing.Db (shared cleanup and mapping helpers).
Logs and metrics through AppTelemetry, with whatever logging providers and OpenTelemetry exporters you register Core.Telemetry Already brought by Configuration, Web and Hosting.Workers. No Serilog or vendor dependency.
Serilog as your logging provider, console defaults for a tool, the correlation or structured-exception enrichers, log-based metrics Infrastructure.Telemetry.Serilog Optional, on top of Core.Telemetry. Skip it if you use the Microsoft providers or OpenTelemetry alone.

Each row’s packages work without the others. See Observability for how the telemetry packages fit together.

Core: domain and application abstractions

Package Purpose Depends on
Core 📦 Generic helpers and extensions (StringExtension, EnumExtension, DateHelper, JSON converters, …), the exception primitives, the IEntity/IPersistedEntity/IDeepCloneableEntity markers, the keyed client-resolver pattern (IClientResolver<T>, KeyedClientResolverBase<T>) and the DI module contract (IDependencyInjectionModule, UseModule<T>() and UseModule(module)). —
Core.Telemetry 📦 [Impl] Provider-neutral telemetry on the standard Microsoft logging and .NET metrics APIs: ICoreTelemetry (ILogger and IMetricRecorder), AppTelemetry (call sites, standard metric names, timers, monitored actions, log helpers, LogContext scopes), AddCoreTelemetry() and ModuleTelemetryBase. No Serilog or vendor dependency. Core
Core.Events 📦 In-process pub/sub (ILocalEvent, ILocalEventHandler<T>, LocalEventBus + AddLocalEventBus) and the generic event pipeline (EventEnvelopeBase, DomainEventEnvelope/PersistedDomainEvent, DomainEventProcessorBase<T>, DomainEventHandlerDispatcher<T>, EventEnvelopeParser). Core, Core.Telemetry, Core.Messaging.Abstractions
Core.Messaging.Abstractions 📦 [Abs] Broker-neutral IMessageBrokerPublisher, the InboundMessage/OutboundMessage broker messages and the generic OutboundMessageBuilder. This is the extension point for other transports. Core
Core.Persistence.Abstractions 📦 [Abs] Unit of work, async-local flow context, storage policy, repository contracts and exceptions. Core
Core.Health 📦 [Abs] The health model every endpoint shares: service health reports (IHealthCheck, HealthCheckBase for timed, exception-safe checks), HealthCheckOutcome, HealthCheckReport (RunAsync(reports) runs them in parallel) and ExceptionReport; plus IBuildMetadata and ApplicationRunbookUriAttribute. Core

Infrastructure: adapters to external systems

Package Purpose Depends on
Infrastructure.Http 📦 HTTP repository and client plumbing: HttpRepositoryBase/ScopedHttpRepositoryBase, handlers (timeout, MSAL certificate authentication) and client configuration. Core, Core.Telemetry
Infrastructure.Persistence.Db 📦 [Impl] The provider-agnostic relational layer: the IDbDialect provider contract, unit of work, connection pool, resilience policy and retry builder, connection-string and options bases, repository bases (Db{Reader,Writer,BatchWriter}RepositoryBase<TConnection, TDialect, …>), AttributeIdCacheBase, DescriptionEnumTypeHandler, database health reports and the transactional outbox/event store bases. See Database Providers. Core, Core.Telemetry, Core.Persistence.Abstractions, Core.Events, Core.Health
Infrastructure.Persistence.Db.Postgres 📦 [Impl] Npgsql adapter: PostgresDbDialect, connection string, pool, unit of work, resilience, PostgresDb*RepositoryBase aliases, health reports and ModulePostgres. Core, Core.Telemetry, Infrastructure.Persistence.Db
Infrastructure.Persistence.Db.Oracle 📦 [Impl] ODP.NET (Oracle.ManagedDataAccess.Core) adapter: OracleDbDialect, connect-descriptor connection string, pool with per-connection command timeout and session time zone, unit of work, resilience, OracleDb*RepositoryBase aliases, health reports and ModuleOracle. Core, Core.Telemetry, Infrastructure.Persistence.Db
Infrastructure.Persistence.Db.Mysql 📦 [Impl] MySqlConnector adapter: MysqlDbDialect, connection string, pool, unit of work, resilience, repository bases, health reports and ModuleMysql. Core, Core.Telemetry, Infrastructure.Persistence.Db
Infrastructure.Messaging.Aws 📦 [Impl] The toolkit’s only messaging transport today: SNS and SQS publishers (AddSnsMessageBroker, AddSqsMessageBroker and their modules) over shared publisher and request-builder bases, an inbound mapper with BeginCorrelationScope (the consumer’s correlation entry point) and compression. For another broker, implement the broker-neutral contracts in Core.Messaging.Abstractions. Core, Core.Telemetry, Core.Messaging.Abstractions, Infrastructure.CorrelationId
Infrastructure.Telemetry.Serilog 📦 [Impl] Optional Serilog integration for Core.Telemetry: Serilog as one more logging provider (AddSerilogTelemetry), console defaults for tools, the correlation-ID and structured-exception enrichers and opt-in log-based metrics. No AWS or vendor dependency. Core.Telemetry, Infrastructure.CorrelationId
Infrastructure.CorrelationId 📦 [Impl] Provider-neutral correlation and attempt IDs: async-local CorrelationContext, the UseCorrelationId() ASP.NET Core middleware (X-Correlation-Id/X-Attempt-Id headers by default), CorrelationContext.BeginScope(...) for workers and consumers (ILogger scope plus activity tags) and ModuleCorrelationId. Core

Configuration: settings, secrets and telemetry bootstrap

Package Purpose Depends on
Configuration 📦 Settings and secrets, and ModuleTelemetry, which registers AppTelemetry, the metric recorder and the correlation context and takes the application’s own ModuleTelemetryBase; ModuleLibConfiguration<TAppSettingsDiModule, TAppSettings> combines them. Core, Core.Telemetry, Infrastructure.CorrelationId

Hosting: running a process

Package Purpose Depends on
Hosting 📦 The IStartup contract and UseStartup<TStartup>(appRunnerType), startups and entry points for jobs and workers (JobStartupBase, JobEntryPointBase, WorkerEntryPointBase, AppHostBuilder) with an overridable ConfigureAppConfiguration hook, and DiFactory<TAppSettingsDiModule, TAppSettings>.Build(...). Core, Configuration
Hosting.Workers 📦 [Impl] WorkerBase, MonitoredWorkerBase, ResilientWorkerBase, HeartbeatWorker and the workers’ self-hosted health API (/health/instance, /health/services, /health/status) through AddServiceHealthCheckWorker(assembly) or ModuleApplicationHealth. Core, Configuration, Core.Telemetry, Core.Health, Infrastructure.CorrelationId

Web: API and UI pipelines

Package Purpose Depends on
Web 📦 REST API pipeline: startups and entry points (RestApiWebAppStartupBase, WebAppEntryPoint, AwsWebAppEntryPointBase), middleware, authentication with generic scopes, Swagger, JSON converters, validation attributes and the health controller. Hosting, Infrastructure.Http, Core.Health, Core.Persistence.Abstractions, Core.Telemetry
Web.GraphQL 📦 Generic GraphQL wiring (AddToolkitGraphQl<TSchema>, UseToolkitGraphQl<TSchema>, SchemaBase, GraphQlRoutes). Web
Web.Ui 📦 Interactive-server Blazor pipeline: AddToolkitUi/UseToolkitUi on any host or UiWebAppStartupBase, an opt-in cookie-session OAuth login against an application-supplied environment catalog, UiApiClientBase for downstream APIs and reusable components. Only domain-free plumbing: pages, API clients and environment URLs belong to the application. See Building UIs. Core.Telemetry, Web
Web.MockServer 📦 HTTP mock server for integration and end-to-end tests: MockServer-compatible JSON expectations, consumer middlewares (MockServerEntryPoint.RunAsync(args, …)), request recording to JSON lines, a /__mock control API, verbosity levels and port 6001 or the next free one. Run by IMockServerBuild, by hand, or in-process with MockServerHost. Keeps an in-memory log (/__mock/logs) and lists its middlewares (/__mock/middlewares). Core
Web.MockServer.Ui 📦 Browser UI for the mock server at /__mock/ui, built on Web.Ui: loaded expectations (with reload), received requests, plugged-in middlewares and a live log. Standalone executable, or UseUi() in a host of your own; --no-ui (or UI=false with the Make targets) turns it off. Web.MockServer, Web.Ui

Automation: build tooling

At the top of the chain, so nothing that ships can depend on it. Fallout is the current build engine behind these packages; the public surface is the build components, the operations and the CLI.

Package Purpose Depends on
Automation 📦 The build and command-line operations behind the components and the tool: optional automation preferences, scaffolding, layering checks, releases, Git hooks, and the distributed Makefile, scripts and agent skills. Core
Automation.Build 📦 Anarchy build components, the MTP-aware test runner, packaging and local automation, including preference targets. See Anarchy Automation Builds. Automation, Infrastructure.Telemetry.Serilog
Automation.Build.Cli 📦 The anarchy-toolkit .NET global tool: bootstrap, scaffold and explicit preference editing for the optional root overrides file. Automation, Automation.Build, Hosting, Web, Web.Ui

Testing kits: reusable test helpers

Outside the layer chain: they may reference any layer, but no production package may reference them. See Testing Conventions.

Package Purpose Depends on
Testing 📦 TestCaseBase / TestCaseBase<TAppSettings>, TestHelper, EntityFixtureBase, API Gateway assertions and TestTelemetry: an AppTelemetry whose logs and metrics are captured in memory (FixtureTelemetry, AddTestTelemetry). Core, Core.Telemetry, Configuration
Testing.Db 📦 DbTestHelper (RegisterEnumTypeHandler<TEnum>(), TruncateTableAsync<TConnection, TDialect>, ClearTableAsync) and DbOptionsMapper. Configuration, Infrastructure.Persistence.Db
Testing.Db.Postgres 📦 PostgresHelper/SingletonPostgresHelper, PostgresOptionsMapper and enum type handlers. Core.Telemetry, Testing, Testing.Db, Infrastructure.Persistence.Db.Postgres
Testing.Db.Oracle 📦 OracleHelper/SingletonOracleHelper, OracleOptionsMapper and enum type handlers. Core.Telemetry, Testing, Testing.Db, Infrastructure.Persistence.Db.Oracle
Testing.Db.Mysql 📦 MysqlHelper/SingletonMysqlHelper, MysqlOptionsMapper, IMysqlAppSettings, enum type handlers and table cleanup. Core.Telemetry, Testing, Testing.Db, Infrastructure.Persistence.Db.Mysql
Testing.Aws 📦 AWS-specific messaging tests for the toolkit’s only messaging transport today: LocalStack SNS/SQS helpers (SqsHelper, AwsMessageBrokerHelper) and SqsMessageFixture. Other transports can add a matching test kit against Core.Messaging.Abstractions. Testing, Infrastructure.Messaging.Aws
Testing.Web 📦 RestApiTestCaseBase<TStartup, TAppSettings> (native and Lambda pipelines), TestableLambdaEntrypoint and MockAuthorizationToken<TAppSettings>(scopes). Testing, Web
Testing.MockServer 📦 MockServerClient for the mock server’s control API, received-request assertions (AssertReceivedAsync, ShouldHaveReceived), RecordedRequestsFile and MockServerFixture, which connects to MOCKSERVER_URL or spawns a MockServerProcess. Testing, Web.MockServer