Adopt Standards v1

This guide creates a consumer repository that follows the dotnet-nextjs profile.

This guide creates a consumer repository that follows the dotnet-nextjs profile. Replace every placeholder with the consumer's project name and paths. Read V1 Release Scope before adopting the profile.

Sequence

Create the repository and add the standards submodule at standards/. Pin the v1 tag or commit and add standards.project.json from standards/templates/docs/standards.project.json.
Copy standards/templates/docs/project-agents.md to the repository root as AGENTS.md. Fill in the solution name, frontend names, and local commands.
Create the root global.json, central package and lock configuration, and optional pnpm workspace. Pin .NET, Node.js, pnpm, NuGet, and npm from standards.manifest.json.
Create apps/api/{ProjectName}.slnx and the Domain, Application, Infrastructure, WebApi, AppHost, ServiceDefaults, and four baseline test projects under the paths in Repository Structure. Add Worker only when an extension requires it.
Add the project references from Dependencies. Keep Domain free of provider packages and keep provider registration in Infrastructure and hosts.
Configure PostgreSQL, Marten, LiteBus, health checks, diagnostics, and the commit post-handler. Add the Infrastructure and WebApi registration entry points, endpoint discovery, Problem Details handler, authentication, authorization, and build-time OpenAPI generation.
Create the product brief, domain index, capability document, and one use-case specification from the templates. Select only the extensions activated by the primary journey.
Implement one complete slice through Domain, Application, Infrastructure, WebApi, optional frontend, tests, generated contracts, and operating instructions. Use the real PostgreSQL integration harness and cite each acceptance ID in automated tests.
Add CI, branch protection, backup and restore evidence, schema review, deployment, rollback, and primary-journey smoke testing before calling v1 complete.
Run the release gates from Release Standard and record exact commands and skipped checks in the release evidence.

Bootstrap evidence

Before feature work expands beyond the first slice, confirm these outputs exist:

Concern	Required output
Toolchain	SDK and package-manager pins, central NuGet versions, NuGet lock files, and the root pnpm lockfile when TypeScript exists
Composition	One visible WebApi composition root, Infrastructure registration, deterministic endpoint mapping, and no service locator
Persistence	Real Marten configuration, one scoped session, one command commit post-handler, explicit aliases and JSON contracts, and a reviewed schema plan
HTTP	Stable routes, actor mapping, target authorization, Problem Details, pagination, OpenAPI operation IDs, and every documented response
Testing	Four baseline test projects, PostgreSQL container fixture, real API factory, database reset, architecture rules, and acceptance-ID references
Frontend	Generated transport types, one typed client, normalized errors, serializable action results, and explicit route states when a frontend exists
Operations	Health endpoints, W3C-correlated diagnostics, bounded metrics, baseline alerts, required runbooks, and release evidence
Delivery	Required CI jobs, immutable artifact identity, deployment, smoke test, restore exercise, and rollback exercise

First-slice defaults

Use Marten document persistence, one aggregate repository per command-loaded aggregate, direct IQuerySession projections for baseline reads, and one LiteBus commit after a successful command. Enable persistence-ef-core, api-compatibility, scheduled-jobs, data-lifecycle, or another extension only after its activation criteria and decision are recorded.

Verification

Confirm the consumer configuration validates against the standards project schema.
Confirm the solution and project paths match the repository structure convention.
Confirm the primary use case has domain, persistence, API, test, generated-contract, and operating evidence.
Confirm every bootstrap output that applies has an owner and automated or recorded evidence.
Run the complete baseline and enabled-extension checks before the first deployment.

Adopt Standards v1

This guide creates a consumer repository that follows the dotnet-nextjs profile.

Sequence

Create the repository and add the standards submodule at standards/. Pin the v1 tag or commit and add standards.project.json from standards/templates/docs/standards.project.json.
Copy standards/templates/docs/project-agents.md to the repository root as AGENTS.md. Fill in the solution name, frontend names, and local commands.
Create the root global.json, central package and lock configuration, and optional pnpm workspace. Pin .NET, Node.js, pnpm, NuGet, and npm from standards.manifest.json.
Create apps/api/{ProjectName}.slnx and the Domain, Application, Infrastructure, WebApi, AppHost, ServiceDefaults, and four baseline test projects under the paths in Repository Structure. Add Worker only when an extension requires it.
Add the project references from Dependencies. Keep Domain free of provider packages and keep provider registration in Infrastructure and hosts.
Configure PostgreSQL, Marten, LiteBus, health checks, diagnostics, and the commit post-handler. Add the Infrastructure and WebApi registration entry points, endpoint discovery, Problem Details handler, authentication, authorization, and build-time OpenAPI generation.
Create the product brief, domain index, capability document, and one use-case specification from the templates. Select only the extensions activated by the primary journey.
Implement one complete slice through Domain, Application, Infrastructure, WebApi, optional frontend, tests, generated contracts, and operating instructions. Use the real PostgreSQL integration harness and cite each acceptance ID in automated tests.
Add CI, branch protection, backup and restore evidence, schema review, deployment, rollback, and primary-journey smoke testing before calling v1 complete.
Run the release gates from Release Standard and record exact commands and skipped checks in the release evidence.

Bootstrap evidence

Before feature work expands beyond the first slice, confirm these outputs exist:

Concern	Required output
Toolchain	SDK and package-manager pins, central NuGet versions, NuGet lock files, and the root pnpm lockfile when TypeScript exists
Composition	One visible WebApi composition root, Infrastructure registration, deterministic endpoint mapping, and no service locator
Persistence	Real Marten configuration, one scoped session, one command commit post-handler, explicit aliases and JSON contracts, and a reviewed schema plan
HTTP	Stable routes, actor mapping, target authorization, Problem Details, pagination, OpenAPI operation IDs, and every documented response
Testing	Four baseline test projects, PostgreSQL container fixture, real API factory, database reset, architecture rules, and acceptance-ID references
Frontend	Generated transport types, one typed client, normalized errors, serializable action results, and explicit route states when a frontend exists
Operations	Health endpoints, W3C-correlated diagnostics, bounded metrics, baseline alerts, required runbooks, and release evidence
Delivery	Required CI jobs, immutable artifact identity, deployment, smoke test, restore exercise, and rollback exercise

First-slice defaults

Verification

Confirm the consumer configuration validates against the standards project schema.
Confirm the solution and project paths match the repository structure convention.
Confirm the primary use case has domain, persistence, API, test, generated-contract, and operating evidence.
Confirm every bootstrap output that applies has an owner and automated or recorded evidence.
Run the complete baseline and enabled-extension checks before the first deployment.

Sequence

Bootstrap evidence

First-slice defaults

Verification

On this page

Adopt Standards v1

Sequence

Bootstrap evidence

First-slice defaults

Verification

On this page