A golden path for enterprise .NET, not another framework

Context#

Every enterprise .NET team builds the same things again: idempotency, locking, an audit trail, background jobs, messaging, bulk processing. Each version has its own bugs. And the spec, the contracts and the code drift apart the moment the first deadline arrives.

Goldpath is a paved road for that. It is not a framework: it configures Microsoft's own building blocks instead of wrapping them, so a team can leave the road at any point.

GitHub

The decisions#

• The manifest is the single source of truth. Contracts, checks and generated docs all follow from it.
• Configure Microsoft, never wrap it. Less to learn, nothing to unlearn.
• AI stays in the development layer. It helps write and change code. The runtime libraries contain no AI; that is an opt-in module.
• Standards are executable. A rule that isn't checked by a tool is a suggestion. The docs are generated, so they can't go stale.
• Three approvals no tool can skip. The spec is approved by the business, the merge request by a developer, the cut-over by operations. Everything an agent produces arrives as a merge request.

One proof, in detail#

The question every payments architect asks first: what happens when a node dies in the middle of a batch? A test in CI answers it on every pull request, with two real executor processes and a real PostgreSQL.

No payment goes out twice. The test proves it; nobody has to believe it.

How I built it#

I wrote it with AI, inside the same rules it gives to its users: a manifest first, deterministic checks, tests that must fail before the change, and mutation testing to show the tests actually catch mistakes.