Evolve source generation to atomic adapters and selection-only profiles

[woksin]

Decision

Evolve the existing neutral Generation architecture; do not rewrite it. Preserve independent AdapterContribution facts/evidence/diagnostics and the single deterministic resolver/lowerer/printer/compiler pipeline, while replacing the long-term one-complete-provider model with a compile-time allowlisted roster of atomic adapters plus selection-only profiles.

User need

A Screenplay host must compose event stores, event-sourcing frameworks, messaging libraries, value-object systems, validation libraries, and genuine integration APIs without creating one facade/package for every combination or allowing one adapter to own another adapter's semantics.

Examples that must fit the same model:

• Marten + Wolverine + Vogen + FluentValidation
• EventStoreDB + MassTransit + StronglyTypedId
• Arc + Vogen
• mixed event-store/messaging projects
• a future trusted non-.NET source frontend

Acceptance criteria

• Add a built-in, compile-time allowlisted adapter catalog with stable adapter ID, implementation/package version, source language, category, required source/API capabilities, emitted fact capabilities, and compatible Generation range.
• Replace Boolean-only applicability with structured NotApplicable / Applicable / Blocked probe evidence and per-adapter admission.
• Treat profiles (marten, critter-stack, later arc) as expected adapter/capability selection only; profiles never own semantics or conflict precedence.
• Keep Vogen, FluentValidation, StronglyTypedId, and similar concerns as independent cross-cutting adapters that execute at most once.
• Split Marten, Wolverine, and genuine Wolverine–Marten integration identities while retaining current Critter facade/API compatibility.
• Detect framework evidence across the selected application scope, not only when all frameworks occur in one compilation.
• Validate and freeze contributions before resolution: producer identity, producer-scoped fact IDs, subject integrity, supported capabilities, and source origin.
• Add framework-neutral fixed-snapshot derivation with stable rule identity, input lineage, evidence, and deterministic diagnostics; adapters never consume one another.
• Move concept/type-use binding from a Critter facade-local Roslyn rewrite toward granular neutral type-use facts and central derivation.
• Give every recognized fact an explicit disposition: Lowered, ProvenanceOnly, OmittedWithDiagnostic, or Conflicted.
• Report considered, matched, admitted, blocked, and executed adapters plus fact capabilities and derivation provenance independently from profile/provider and target-language versions.
• Use authoritative host-provided authored syntax trees consistently; generated source may corroborate but never originate semantics.
• Keep Arc on its existing complete generator until a fixture-by-fixture parity-proven neutral bridge exists; never concatenate documents.
• Preserve existing public APIs, provider names, output channels, diagnostic codes, package validation, and byte-identical output where semantics are unchanged.

Delivery order

1. Decision/characterization fixtures and actual package-closure checks.
2. Authoritative source enforcement.
3. Contribution verification, freezing, capability metadata, and provenance.
4. Atomic Marten/Wolverine/integration identities behind compatibility wrappers.
5. Built-in catalog, structured probes, profiles, and per-adapter admission in CLI.
6. Granular type-use facts plus central derivation lineage.
7. Validation contracts before adding FluentValidation.
8. Measured semantic facts for delivery, responses, side effects, identifiers, backends, fan-out, sagas, and authorization.
9. Arc neutral bridge after parity evidence.

Non-goals

• Adapter-emitted Screenplay AST/text or document concatenation.
• Adapter/profile order as conflict resolution.
• A facade for every framework combination.
• Workspace-discovered executable plugins.
• A public out-of-process protocol before a real non-.NET/deployment need exists.
• Starting applications, databases, brokers, or silos by default.
• Inferring semantics from package presence, names, or primitive backing types.

Related

• Deterministic consumer contract: Establish the deterministic adapter consumer contract #5
• CLI workflow: Add an explicit source-to-Screenplay provider workflow cli#87
• Cross-repository roadmap: Track atomic source recovery under the Screenplay semantic model Screenplay.CritterStack#29
• Current compatibility facade composition: Compose Vogen concepts into Critter Stack generation Screenplay.CritterStack#25

[woksin]

Implementation learnings are now split into owning issues: #18 reusable authored-source/bounded Roslyn evidence helpers; #19 granular type-use facts and central derivation lineage; #20 library-neutral validation declaration/applicability/activation/application facts; Cratis/Screenplay.CritterStack#44 atomic Marten/Wolverine/integration adapters; Cratis/cli#95 selection-only profile roster; Cratis/Arc#2600 neutral Arc export/parity bridge. These should remain dependency-ordered under this issue rather than being solved by another combined facade.

[woksin]

v0.8.0 release evidence

Exact release commit 4ec7ef0031e0f1c74d1033e0a78234f40bbd65ff passed trusted publication and package verification.

• Exact-tag Debug suites contain 241 specs (129 Generation + 28 DotNet + 84 Vogen), not the pre-merge estimate of 230; all passed in CI/exact-tag verification.
• Linux PR/publish all-TFM solution gates are green with zero warnings/errors. On macOS, Vogen 8.0.7 has a host-specific analyzer dependency-load issue only in the non-packable Release specs project; all four shipped projects built net8/net9/net10 warning-free locally.
• Sentinel pack/API compatibility against 0.7.1 passed for all four shipped packages.
• Legacy 0.1/0.5 binaries and current-source composition consumer passed.
• All four nupkgs are repository-signed; public NuGet files and eight GitHub release assets are byte-identical; local-feed copies installed.

Public SHA-256:

• Generation nupkg 5d16dc3fc7da4e612e3d85199e2bb52e9417573a9bb9777460b6444e6e8d502c; snupkg b137e32f059170528ad8bd7c887061a295b2011278c2d2a0fe746b0e5ddae917.
• Contracts nupkg 9ed9b1c26094e71fecd0ccec3ca0f81fabfa350bed98d8e184af08f89c0bd285; snupkg 9a296d4a5256bc18c1691ca365af96952f4d37e984a28bbebaf8d42f49a428d2.
• DotNet nupkg a2ab01b6a7f41ae9b95715dbc0abcd8f0e0a10181ac44a43bd26216ffe77a7da; snupkg 7498060c942cb069059243190fbab2e443b128654c2ce8d5c9150b6be1cdc1e0.
• DotNet.Vogen nupkg d3c4c75ad96b3286bc08ce460e42702aaaae06a4276082ed6c1579906bc4c5a3; snupkg 0dd53f373c6b21a51ec380ee8ccf245c000507bc75ba253b436a53bf5747edd4.

Issue #5 remains open only until Critter Stack and CLI clean consumers are updated to the complete 0.8 lockstep set and operationally verified.

[woksin]

Screenplay Generation v0.8.0 exact-release operational verification

Verification used detached exact-tag clones, isolated package/HTTP caches, clean consumers, and fresh public downloads. No repository source, workflow, manifest, or lock file was edited.

Identity, release, and trusted publication

• Lightweight tag v0.8.0, remote main, the non-draft/non-prerelease GitHub release target, publish checkout, every nuspec/catalog repository commit, all 12 assembly informational versions, and every SourceLink map converge on 4ec7ef0031e0f1c74d1033e0a78234f40bbd65ff.
• The merge commit is GitHub-signature verified (verified: true, reason valid, verified at 2026-08-23T01:12:07Z).
• Publish run 32609780526 passed at that SHA. The job had id-token: write; NuGet/login@v1 reported Successfully exchanged OIDC token for NuGet API key; all four package and all four symbol pushes returned Created / Your package was pushed. The full Release solution build in that run completed with 0 warnings and 0 errors.

Public packages, catalog, assets, and SourceLink

All four versions are listed. Fresh flat-container nupkg downloads are byte-identical to v2 package downloads; computed SHA-512 values equal the NuGet catalog hashes. dotnet nuget verify --all passes every nupkg as NuGet.org repository-signed for owner Cratis, certificate SHA-256 1F4B311D9ACC115C8DC8018B5A49E00FCE6DA8E2855F9F014CA6F34570BC482D.

Each package contains only its DLL/PDB pair for net8.0, net9.0, and net10.0, plus package metadata/readme/signature; no build/, buildTransitive/, analyzers/, or runtimes/ payload. All 12 DLLs are assembly/file version 0.8.0.0, informational version 0.8.0+4ec7ef0031e0f1c74d1033e0a78234f40bbd65ff, with the correct TFM. All 24 nupkg/snupkg PDB SourceLink URL/checksum tests passed against the exact commit, and corresponding nupkg/snupkg PDBs are byte-identical.

Catalog-normalized dependencies are identical for all three TFMs:

• Contracts: none.
• Generation: Contracts [0.8.0,); Cratis.Screenplay [4.2.1,).
• DotNet: Contracts [0.8.0,); Microsoft.CodeAnalysis.CSharp [5.9.0,).
• DotNet.Vogen: DotNet [0.8.0,); no Vogen dependency.

SHA-256:

• Cratis.Screenplay.Generation.0.8.0.nupkg: 5d16dc3fc7da4e612e3d85199e2bb52e9417573a9bb9777460b6444e6e8d502c
• Cratis.Screenplay.Generation.0.8.0.snupkg: b137e32f059170528ad8bd7c887061a295b2011278c2d2a0fe746b0e5ddae917
• Cratis.Screenplay.Generation.Contracts.0.8.0.nupkg: 9ed9b1c26094e71fecd0ccec3ca0f81fabfa350bed98d8e184af08f89c0bd285
• Cratis.Screenplay.Generation.Contracts.0.8.0.snupkg: 9a296d4a5256bc18c1691ca365af96952f4d37e984a28bbebaf8d42f49a428d2
• Cratis.Screenplay.Generation.DotNet.0.8.0.nupkg: a2ab01b6a7f41ae9b95715dbc0abcd8f0e0a10181ac44a43bd26216ffe77a7da
• Cratis.Screenplay.Generation.DotNet.0.8.0.snupkg: 7498060c942cb069059243190fbab2e443b128654c2ce8d5c9150b6be1cdc1e0
• Cratis.Screenplay.Generation.DotNet.Vogen.0.8.0.nupkg: d3c4c75ad96b3286bc08ce460e42702aaaae06a4276082ed6c1579906bc4c5a3
• Cratis.Screenplay.Generation.DotNet.Vogen.0.8.0.snupkg: 0dd53f373c6b21a51ec380ee8ccf245c000507bc75ba253b436a53bf5747edd4

The release had zero assets. All eight exact verified public files are now attached. Fresh anonymous GitHub release downloads compare byte-for-byte equal to the public NuGet files. The four nupkgs are installed byte-identically in ~/.nuget/cratis-local.

Exact-tag gates and clean consumers

• Exact detached-tag Debug tests passed: 241/241, split 129 + 28 + 84, 0 failed/skipped. The exact PR CI run 32609418332 independently reports the same counts.
• The four shipped projects built the 9999.0.0 Release sentinel for net8/net9/net10 with 0 warnings/0 errors. Pack produced four nupkgs and four snupkgs. RunPackageValidation completed for all four with EnablePackageValidation=true and baseline 0.7.1.
• The public-package consumer gate compiled the legacy core consumer against 0.1.0, the legacy Vogen consumer against 0.5.0, compiled/executed the current-source consumer against 0.8.0, and ran the unchanged legacy binaries against 0.8.0; every build/run passed with 0 warnings/errors.
• An independent empty-cache consumer loaded all four public 0.8.0 packages and verified typed fail-closed Unknown, conflict-visible Conflict, and known-but-unlowerable Unsupported outcomes on net8.0, net9.0, and net10.0, all with 0 warnings/errors.
• The clean graph/cache contains no exact Vogen package, Vogen.dll, Vogen.SharedTypes.dll, or Vogen source-generator/analyzer asset. The only Vogen-named product is the intended Cratis.Screenplay.Generation.DotNet.Vogen adapter.

Discrepancies / host note

1. The requested count was 230 specs, but the immutable exact tag contains and passes 241. Exact local and GitHub CI counts agree; no tests were filtered to force the requested number.
2. On this macOS host, a full Release solution build reaches the non-packable Vogen specs project and Vogen 8.0.7's analyzer fails to resolve its own Vogen.SharedTypes dependency. The four shipped projects' all-TFM Release build/pack/API compatibility gates pass locally, while the identical exact SHA's full Linux PR and publish Release solution builds pass with 0 warnings/errors. This host-only analyzer-load failure does not affect the shipped packages or clean consumers.
3. The four public snupkgs are unsigned (NU3004, no .signature.p7s), matching the existing NuGet symbol-package behavior. Their exact bytes, PDB identity, and SourceLink checks passed. All four nupkgs are repository-signed as documented above.

No unresolved package-content, provenance, catalog, dependency, framework-asset, SourceLink, API-compatibility, consumer, release-download, local-install, or Vogen-leakage discrepancy remains. This evidence verifies the bounded release; it does not by itself imply completion of the broader atomic-adapter/profile roadmap.

[woksin]

Focused descriptor/probe/frozen-admission work is now tracked in 23 (#23). Keep #17 as the atomic-composition epic across that contract, #18-#21, framework adapters, and host profiles.