Skip to content

About

The reusable Purview engineering conventions - repository shape, architecture as tests, verification tiers, contracts and data exchange, testing, and agent enablement.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Engineering Playbook

The reusable engineering conventions behind the Purview projects — how a repository is shaped, how architecture is held by tests, how a change is verified in tiers, how data crosses a boundary, and how coding agents are enabled to work in a codebase without hand-holding.

Documentation-first. This repository ships no library and no NuGet package. It contains the conventions themselves, ready-to-copy templates, and a small in-repo reference implementation whose only job is to prove the conventions compile, run, and fail when they should.

What's inside

Area Question it answers
Engineering principles What are the non-negotiable rules, and who owns them?
Repository shape Where does a file go, and what is it called?
Architecture as tests How does the build refuse a dependency that points the wrong way?
Verification model Which checks run, in which tier, for which change?
Contracts and data exchange How do value objects, schemas and results cross a boundary?
Testing and test data How are tests written, and where does their data come from?
Agent enablement How is a repository made legible to a coding agent?
Documentation convention How is the wiki written, structured and published?
Adopting this at your scale Which parts apply to a small, medium or large repository?

Start here

Repository layout

Path Purpose
docs/wiki The playbook. Aggregated by the purview-dev website.
templates/ Ready-to-copy starter files for a repository adopting the playbook.
src/ The reference implementation: a layered repository whose architecture rules are tests.
mkdocs.yml Wiki site configuration (docs_dir: docs/wiki).
.config/purview-build.json Pipeline configuration for the shared Purview build workflow.
Justfile Supported local workflow commands.
package.json Authoritative version for the repository.

Local workflow

just build              # dotnet build (Debug)
just test               # run the unit tests
just lint-check         # CSharpier check
just pipeline-pr        # restore, build, lint, test through the shared Purview.Build tool
just scrub              # reset bin/obj, forced restore, build-server shutdown

License

MIT.

About

The reusable Purview engineering conventions - repository shape, architecture as tests, verification tiers, contracts and data exchange, testing, and agent enablement.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages