Skip to content
Litenova Solutions

Engineering Standards

How we design, build, and operate software at Litenova Solutions — published openly for clients, contributors, and anyone evaluating our approach.

Where you are

You are on the public standards site hosted at litenova.solutions/Standards/. It is a read-only mirror of our Engineering Standards repository: the same markdown our teams use internally, formatted for the web.

This is not the main Litenova marketing site. Use the sidebar or search to move within the standards. The link at the top of the sidebar returns to litenova.solutions.

What to expect

These documents are normative where they say MUST or MUST NOT: they describe how we structure solutions, write APIs, test, secure, and deploy. Some sections are written with AI-assisted workflows in mind; they are still useful for human readers and explain why rules exist, not only checklists.

If you want to…Start here
Join a project that uses these standardsOnboarding
See the full map of topicsDocumentation map
Understand architectural intentPhilosophy · Clean architecture
Look up a term (ADDD, use case, tiers, etc.)Glossary
Implement a feature end to endADDD overview · Add a use case
Copy starter files (CI, Docker, domain docs)Templates
See full reference implementationsBlueprints
Understand why we chose a technology or patternDecisions (ADRs)
Operate production systemsRunbooks

How the docs are organized

  • Guides — Narrative playbooks (onboarding, new projects, use case docs, definition of done).
  • Conventions — Layer rules (backend, frontend, shared) with examples; start from Principles.
  • Architecture — Structural model (Clean Architecture, dependencies, CQRS placement).
  • Blueprints — Full-file reference code to copy, not fragments in convention text.
  • Templates — Scaffolds for consumer repos (domain docs, CI, config).
  • Decisions — Architecture decision records (context and rationale).
  • Runbooks — Operational procedures (deploy, incidents, migrations).
  • Governance — Exceptions and how standards evolve.

Many convention pages open with a short Agent Quick Rules section: a dense summary for tooling and experienced readers. The rest of each page is the full human-readable convention.

Search and navigation

Use Search in the header (Ctrl+K) to find a topic across all pages. The sidebar groups the same content by area; nested sections can be expanded for blueprints, decisions, runbooks, and templates.

Standards change in the GitHub repository; this site is rebuilt when that content is updated in the public site repo. For the latest source or to propose edits, use the Engineering Standards repository.