Documentation
Documentation
I keep documentation with the project it describes, then bring it together here so you can search and explore it in one place — 203 pages across 13 projects.
Telemetry SourceGenerator
Interface-based telemetry for .NET with zero boilerplate.
23 pages →
Event Sourcing
Aggregate-based event sourcing for .NET across any store.
20 pages →
ZodSharp
Zero-allocation schema validation for C# — a Zod port.
27 pages →
Value Objects
Source-generated scalar and complex value objects for .NET.
5 pages →
SourceGenerator Framework
A typed framework for building incremental C# source generators.
14 pages →
Results
Result for .NET — expected failures as values the caller must handle.
15 pages →
Aspire ResourceKit
Strongly typed, source-generated resource kits for .NET Aspire.
17 pages →
AspireC4
Live LikeC4 architecture diagrams from the Aspire resource graph.
12 pages →
Build
The shared build, test, and release system for purview-dev.
11 pages →
Build SDK
Convention-driven MSBuild SDK for .NET project defaults.
16 pages →
Architests
Enforce a repository's architecture policy as TUnit tests.
9 pages →
Containers
Throwaway Linux containers for .NET integration tests — on WSL Containers with no Docker installation, or on Docker.
17 pages →
Engineering Playbook
The reusable Purview engineering conventions — repository shape, architecture as tests, verification tiers, and agent enablement.
17 pages →
Kept close to the code
- Each page identifies its owning project, lifecycle status, and last review date.
- Source links take you back to the repository where an issue or edit can be raised.
- Search spans the full site, including projects, releases, and documentation.
Machine-readable documentation
Each project's documentation is also published as a single llms.txt bundle for
language models and other tooling. The whole site is available as
llms.txt,
llms-small.txt
, and
llms-full.txt
.