Cratis.Arc.Swagger 22.4.0

Cratis Arc

Arc is an opinionated CQRS application framework for ASP.NET Core with commands, queries, validation, authorization, and TypeScript proxy generation.

Arc hosts application behavior, executes command and query pipelines, exposes recognized contracts over HTTP, and generates TypeScript clients for them. Its packages also cover observable queries, validation, identity and tenancy, React integration, current-state persistence, OpenAPI, analyzers, and testing. Chronicle event sourcing and Cratis Components are optional integrations.

Start here

• Browse the Arc documentation
• Choose a documented application path
• Understand Arc's independent boundary
• Start an Arc host
• Inspect packages and repository layout

What Arc owns

Each row is a documented capability area, not a promise of compatibility with every package, host, provider, browser, or product version.

Choose a path

Arc documentation is organized around the job you need to complete:

• Execute commands — model-bound or controller-based changes, pipelines, validation, authorization, filters, and response handling.
• Expose queries and observable results — request/response reads, paging, sorting, streaming updates, diagnostics, and generated clients.
• Build the frontend — TypeScript runtimes, React hooks and forms, dialogs, identity, messaging, and optional MVVM packages.
• Configure identity and access — authentication, identity details, authorization, roles, and frontend visibility boundaries.
• Resolve tenants — request resolvers, scoped tenant context, and provider-specific database or namespace mapping.
• Use current-state persistence — application services, MongoDB, or Entity Framework Core without requiring an event log.
• Add Chronicle event sourcing — events, projections, reducers, aggregates, reactors, concurrency, and Chronicle-specific testing.
• Inspect and verify the application boundary — introspection, OpenAPI, analyzers, generated metadata, and command scenarios.

The canonical Arc page remains the front door; product-owned documentation and source carry the detail.

Arc does not require event sourcing

Arc.Core does not depend on Chronicle. Commands and queries can use current-state persistence or application services without an event log. Choose the persistence and integrations that fit each application boundary.

The Chronicle integration is optional and supplies event-sourced behavior when configured. Arc retains its command, query, validation, authorization, and generated-contract boundary.

Relationship to Components

Components is a React component library aligned with Arc application patterns. See the Components documentation for its packages and setup.

Applications may use Arc without Components and remain responsible for their own frontend, accessibility, browser, and design-system verification.

Start an Arc host

Arc's .NET packages embed this product-family README. The example below uses the umbrella Cratis.Arc package to start an Arc host; when viewing this README from a specialized package page, use that package's manifest and reference documentation for its own installation scope.

Use the .NET SDK declared by Arc's current global.json. Install the host package:

dotnet add package Cratis.Arc

Create and run an Arc host:

using Cratis.Arc;

var builder = ArcApplication.CreateBuilder(args);
builder.AddCratisArc();

var app = builder.Build();
app.UseCratisArc();
await app.RunAsync();

Starting the host confirms the basic Arc setup. Continue with the Arc documentation, and use GitHub Issues when the observed behavior does not match the documentation.

Packages and repository layout

Package existence does not imply compatibility with every frontend, runtime, persistence provider, or product version. Check the package manifests and documentation for the versions you use.

Documentation map

• Arc documentation
• Product-owned documentation source
• Arc releases
• Arc issues

Contributing

Arc is a framework-library repository. Changes to public APIs, analyzers, generated output, and package shapes can affect consumers and require the owning repository's compatibility and release review.

Repository development currently requires the SDK and toolchain versions declared by global.json and package.json. Follow the Cratis contribution guide and the framework instructions before changing public surfaces.

Before submitting documentation-only work, verify its links, anchors, and examples explicitly; current automated documentation checks are path-scoped. Source changes must pass the owning repository's applicable build, specification, TypeScript, and documentation gates.

Community and repository