Enterprise architecture, in the open.
Reference corpora, governance standards and .NET/TypeScript libraries you can read, fork and ship.
Not a manifesto — three concrete things:
- A progressive architecture corpus (
Evolith / Arc32): ADRs, canonical patterns and governance rules that take a system from modular monolith to microservices without rewriting it. Documented, versioned, enforced by CI. - SDLC tooling that enforces the corpus (
Evolith Tracker): requirements → code → quality gates → deploy, with traceability you can audit. - Reusable .NET & TypeScript libraries (
Shell.*,UMS): AOP, DI bootstrapping, factories, DDD building blocks, identity. Small, focused, permissively licensed.
Everything is AI-augmented by design: agent instructions (AGENTS.md) ship inside the repos, so a coding agent inherits the same standards a human contributor does.
|
15 packages on NuGet. One command away.
|
Read the reasoning before the code.
|
Ship your first PR this week.
|
dotnet add package BeyondNetCode.Shell.Aop # AOP via DispatchProxy
dotnet add package BeyondNetCode.Shell.Ddd # DDD building blocks
dotnet add package BeyondNetCode.Shell.Factory # configuration-driven factoriesTargets net10.0. The full family — aspects, Serilog integration, DI installers, value objects, AutoMapper profiles, observability — is on nuget.org/profiles/beyondnet.
| Project | What it is | Stack | Status |
|---|---|---|---|
| Evolith / Arc32 | Progressive architecture reference corpus: standards, ADRs, governance rules that satellite products inherit. | TypeScript · docs | Active · MIT |
| Evolith Tracker | End-to-end SDLC tracking: ideation → quality gates → deploy, fully traceable. | C# / .NET | Beta |
| Why-Architecture | The why behind every pattern we publish. Documents and sample artifacts. | Docs · CC0 | Active |
| UMS | User Management System — identities, authentication, authorization. | C# / .NET | Prototype |
| Shell.* | Shell.Aop · Shell.Bootstrapper · Shell.Factory · Shell.DDD — focused .NET building blocks. |
C# / .NET | Active |
Evolith end-to-end product vision · click to enlarge
We keep a curated entry list. Every issue tagged good first issue states its scope, the exact files to touch, and the acceptance criteria your PR has to meet — no guesswork required.
What we need right now:
- .NET engineers — expand
Shell.*test coverage, cut the next release of the libraries, hardenUMStoken flows. - TypeScript / Node engineers — reference implementations of the Arc32 patterns in NestJS.
- AI engineers — improve
AGENTS.mdinstruction sets; build evaluation harnesses for agent-generated PRs. - DevOps — CI templates, container images, release automation across the org.
- Technical writers — English/Spanish parity in
Why-Architectureand the ADR corpus.
No matching issue? Open one or start a discussion — proposals are welcome before code.
# 1. Fork and clone
gh repo fork beyondnetcode/evolith_arch32 --clone
# 2. Branch (conventional naming is enforced by commitlint)
git checkout -b feat/your-change
# 3. Commit — Conventional Commits, validated by husky
git commit -m "feat(reference): add ADR for outbox pattern"
# 4. Push and open the PR
gh pr create --fillRead CONTRIBUTING.md (ES) once — it covers the governance gates, the ADR process and how to propose a change to a standard.
Architecture changes go through ADRs, not opinions. Anyone can propose one; maintainers review against the corpus in reference/. Disagreement is expected and documented — that's the point of writing decisions down.
- Contributing guide (ES)
- Security policy
- Licensing: MIT and Apache-2.0 for libraries, CC0 for documentation corpora.
"Code goes beyond syntax; it is the architecture of the future. Join us in building it."
Maintained by Alberto Arroyo Raygada & contributors · Discussions