Examples
Examples
Eight complete example domains from the library's own test suite, each with annotated tests.
The easiest way to choose a pattern is to see it in a scenario that resembles your own. These examples cover eight small domains in tests/Zeeq.Biome.Tests, each with a seed, blueprints, scenario chains, and tests that run in CI.
Start with the domain closest to your app. Each page highlights the choices that matter and compares the setup with a hand-written version, so you can see what moves into the blueprints.
Code reviews
Repository → pull request → review → lock. Re-anchoring, ancestors, PR numbering, transients, time.
Membership
Users and aliases (fan-out per parent), invitations with derived expiry, and an organization aggregate.
Custom seed
A plain record seed, an interface default, save hooks, frozen options and parallel safety.
| Domain | Seed | Shows |
|---|---|---|
| CodeReviews | org + owner | re-anchoring, ctx.Ancestor, .Per<T> sequence, helper, time |
| Membership | owner | fan-out per parent, fill-only Derive, InputBlueprint |
| Board | a string | .PerParent rank sequence, .Under siblings |
| CustomSeed | plain record | Default<TBase,…>, hooks, freeze, parallel |
| Commerce | store name | mixed scopes, AsTransient, deep tree |
| ProjectManagement | owner | three rank scopes, workspace tickets |
| Learning | district | roster across sections, shared fake clock |
| DocsIngest | owner | per-library versions, aggregate, transient |
The same layout works in your app: one folder per area, with
Blueprints.cs (annotated with [BiomeGraft]), optional Traits.cs, ContextExtensions.cs for repeated context overloads, and ScenarioHelpers.cs for named multi-step chains. See Generated grafts and scenario helpers.