systems42

Where AI meets engineering discipline.

Built on the pragmatic, field-proven discipline of req42 and arc42, extended to AI-native systems. Proven templates, AI-powered execution.

Open source · built on req42 and arc42 · public release planned early 2027
systems42 logo: two strokes, green and blue, converging on a spiral

Proven templates. AI-powered execution.

Requirements and architecture specs are not afterthoughts. They are living contracts that agents reference during generation and testing.

Our templates de-risk the agentic cycle, and AI-powered execution makes that cycle run at machine speed. Management gains traceability: every line of code can be mapped back to documented requirements and architectural decisions.

Where human judgment defines the guardrails, agentic execution fills the lanes. The templates keep both in sync.

Strategic decisions stay human. Tactical execution goes agentic. The templates are the handshake that makes both possible.The systems42 idea in one sentence

Three loops keep the spec alive.

AI fills and checks the spec. Humans decide where it matters.

Ingest loop: Markdownify, Cross-check + Link, Ask Questions Ingest M Markdownify Cross-check+ Link ? AskQuestions

Ingest

Humans provide raw input. AI turns it into clean markdown, files it into the matching spec sections, cross-links it and asks when something does not fit.

AI, started by a human
Audit loop: Detect Issues, Flag Gaps, Update Backlog Audit DetectIssues FlagGaps UpdateBacklog

Audit

Time-triggered or on demand, AI checks the spec against rules, guardrails and constraints and adds every finding to the backlog.

AI, scheduled or on demand
Clarify loop: Pick Topic, Discuss, Write Back Clarify PickTopic Discuss WriteBack

Clarify

Humans pick an open point, discuss it with the AI, and have the outcome written back into the spec or the rules.

Humans and AI together

One spec. Eighteen drawers.

req42 for requirements, arc42 for architecture, six sections they share. Together they are the single source of truth from which code is generated and tested.

Both templates have been used for more than 20 years, in many countries and domains. systems42 does not replace them. It makes them executable.

req42 · requirements arc42 · architecture shared by both

req42

R1Vision & Goals
R2Resources & Staff
R3Functional Requirements
R4Supporting Models
R5Team Structure
R6Roadmap

arc42

A1Solution Strategy
A2Building Block View
A3Deployment View
A4Runtime View
A5Crosscutting Concepts
A6Architecture Decisions

Common

C1Quality Requirements
C2Constraints
C3Scope & Context
C4Stakeholders
C5Domain Terms
C6Risks & Assumptions

Stay tuned. Public release early 2027.

We are testing the approach with many examples. As soon as we have solid results we will publish systems42 so that you can start directly with your own projects.

First seminar, Jan 26–28, 2027