Contracts
Stable abstractions
AstraFlow
A .NET package family for explicit CQRS dispatch and source-auditable mapping, extended with diagnostics, analyzers, generators, testing and CLI tooling.
CoreMediator / Mapper
ToolingAnalyzers / Generators
QualityDiagnostics / Testing
ModelOpen source
Explicit infrastructure.
A package family for CQRS dispatch, source-auditable mapping and developer tooling.
services.AddAstraFlow(); await mediator.Send(command);
00 / 09Principle
Chapter 00
03 / ASTRAFLOW
03 / ASTRAFLOW
Principle
Explicit infrastructure. Inspectable behavior.
AstraFlow starts from a preference for infrastructure that remains inspectable. Useful abstraction should reduce repetition without making behavior mysterious.
Infrastructure should be inspectable.
Explicit infrastructure. Inspectable behavior.
Explicit infrastructure. Inspectable behavior.
Chapter 01
03 / ASTRAFLOW
03 / ASTRAFLOW
Package family
Small packages keep reasons and dependencies clear.
The ecosystem separates contracts, dispatch, mapping, diagnostics, testing and tooling so consumers can compose what they actually need.
Core
Mediator / mapper
Tooling
Analyzers / generators / CLI
Integrations
Testing / ASP.NET / EF
Chapter 02
03 / ASTRAFLOW
03 / ASTRAFLOW
Mediator
CQRS is used where it clarifies responsibilities.
Request and notification dispatch provide a predictable application flow without requiring a heavyweight framework or distributed architecture.
01
Make boundaries visible
Prefer explicit modules, state and contracts over hidden magic.
02
Keep workflows operable
Architecture earns its place by helping real people use and change the system.
03
Design for change
Build enough structure to protect the product without premature complexity.
Chapter 03
03 / ASTRAFLOW
03 / ASTRAFLOW
Mapping
Source visibility is a feature.
Mapping behavior is designed to remain source-auditable. Important transformation logic should not disappear into opaque runtime behavior.
ASTRAFLOW
in use.
Interfaces, states and developer tooling are shown as evidence of product behavior rather than a technology logo collection.
03Structure
you can inspect.
The visual connects what a user touches to the decisions underneath it.
ASChapter 04
03 / ASTRAFLOW
03 / ASTRAFLOW
Diagnostics
A system is easier to trust when it can explain itself.
Diagnostics expose what infrastructure is doing so developers can reason about configuration and runtime state.
ASTRAFLOW
in use.
Interfaces, states and developer tooling are shown as evidence of product behavior rather than a technology logo collection.
03Structure
you can inspect.
The visual connects what a user touches to the decisions underneath it.
ASChapter 05
03 / ASTRAFLOW
03 / ASTRAFLOW
Analyzers
Feedback is more useful before deployment.
Static analysis shifts architecture feedback earlier, close to the code where the mistake is introduced.
01
Make boundaries visible
Prefer explicit modules, state and contracts over hidden magic.
02
Keep workflows operable
Architecture earns its place by helping real people use and change the system.
03
Design for change
Build enough structure to protect the product without premature complexity.
Chapter 06
03 / ASTRAFLOW
03 / ASTRAFLOW
Generators
Automation should reduce repetition, not ownership.
Compile-time generation removes repetitive code while keeping generated behavior deterministic and inspectable.
Contracts
Stable abstractions
Core
Mediator / mapper
Tooling
Analyzers / generators / CLI
Integrations
Testing / ASP.NET / EF
Chapter 07
03 / ASTRAFLOW
03 / ASTRAFLOW
CLI
Tooling completes the developer experience.
The CLI gives the package family an operational/developer surface beyond library APIs.
ASTRAFLOW
in use.
Interfaces, states and developer tooling are shown as evidence of product behavior rather than a technology logo collection.
03Structure
you can inspect.
The visual connects what a user touches to the decisions underneath it.
ASChapter 08
03 / ASTRAFLOW
03 / ASTRAFLOW
Testing / integrations
Infrastructure earns trust through integration quality.
Testing support and framework integrations help the package family live inside real applications instead of demos.
Core packages
Infrastructure earns trust through integration quality.
Diagnostics
Infrastructure earns trust through integration quality.
Compile-time tooling
Infrastructure earns trust through integration quality.
Integrations
Infrastructure earns trust through integration quality.
Chapter 09
03 / ASTRAFLOW
03 / ASTRAFLOW
Why open source
Software for other engineers must stand on its own.
Open source raises the bar for naming, contracts, documentation and predictability because the original application is no longer the only context.
Infrastructure should be inspectable.
Software for other engineers must stand on its own.
Software for other engineers must stand on its own.