## Host reporting dashboard with ASP.NET Core: relational workflow state

### Summary
Deploy a reporting dashboard built with ASP.NET Core on Ample using the transactional workflows pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on ASP.NET Core: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the reporting dashboard-specific behavior as your application code.

### Resource Requirements
- primitive:compute
- primitive:postgres

### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

### Prerequisites
1. A ASP.NET Core project that builds and starts with the documented commands (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. An Ample account token with servers:write, databases:read.

### Workflow Steps
1. **Build and start**: `dotnet publish -c Release -o out` in the builder, then `dotnet .dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT. The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**: The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Deploy**: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op. Command: `ample deploy . --name  --public`.
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/transactional-workflows) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`. Command: `ample logs  --kind build`.

### Examples
- **ASP.NET Core pattern fixture**: Multi-pattern ASP.NET Core app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks
- **HTTP GET**: app responds on its public URL, expects `ample canary asp net core patterns`.
- **HTTP GET**: transactional-workflows self-test, expects `tx=ok history=2 conflict=rejected`.

### Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture; other sizes, templates and ASP.NET Core major versions are not verified.
- The reporting dashboard itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.