Introduction
Download the Manual as PDF — the printable book version, regenerated at every release (FR-17.7).
Key Concepts
REQQA organises everything you do around a small, consistent domain model. Understand
Requirements
A requirement is the central object in REQQA. Everything else — the analysis you run, the stories you generate, the glossary terms you reference — orbits the requirement. This chapter explains how REQQA models a requirement: the fields it carries, the structure that shapes its content, how it is versioned and audited, how requirements form a hierarchy, and the single, deliberate path by which requirements are written.
The Mission
Every application in REQQA begins with a mission statement. It is not a description you write once and forget — it is the anchor of the entire requirements hierarchy. Every requirement you create, and every story generated beneath those requirements, sits underneath the mission and inherits its context. When REQQA analyses a requirement or generates stories, it reads the mission to understand what the application is for.
Stories and Features
In REQQA, a requirement says what the system must do. A feature is a discrete
The Analysis Engine
The analysis engine is the heart of REQQA. It is what turns a requirement or a user
Synthesis and Cleanup
Analysis is only half the loop. Once REQQA has analysed a requirement and surfaced a
The Glossary
Every project develops its own vocabulary. The same word can mean different things to
Releases and Scopes
A release is the unit of delivery in REQQA — a named, bounded slice of an
Static Analysis Policy
A requirement describes what a system must do. A Static Analysis Policy describes how clean
Access and Onboarding
REQQA is invite-only. There is no public sign-up button, no self-service
Background Jobs and the Queue
Most of the work REQQA does on your behalf is slow. Running the DeFOSPAM analysers
The Dark Factory
The Dark Factory is REQQA's longer-term vision: a requirements-driven, increasingly autonomous software development lifecycle, where a well-specified application in REQQA becomes the input to an AI builder that produces working software with progressively fewer human stops along the way.