For regulated industries

You work where an auditor asks which requirement a piece of code serves, which check proves it, and what the system did in operation. You also let agents write code, and you must still answer these questions.

You need to know exactly where your code and your requirements go.

• Traceability in the repository: ids, relationships, and @implements markers from code to requirement, checked by spec-editor validate.
• Acceptance with evidence: each criterion is a command with an expected result, or a judge with the evidence named.
• Run-time trace: code marked with an element writes operation events, and the trace map shows which requirements actually ran.
• Export to TRLC and to an SRS in the style of IEEE 830.
• Your code is not sent to us. Prompts go to the model provider you choose; with a local model through Ollama they stay on your machine.
• Status history in git and in the journal, so changes can be reviewed.
• Review stages decided by evidence, with risk classes A to D.Pro
• Acceptance runs on a test stand before promotion, with rollback.Pro
• spec-editor coverage: coverage of requirements by code, both ways.Pro

• Hosted view of a model coming soon
• Projects of one organisation linked together coming soon

Read the open core on your own repository first. Tell us about your constraints and we will say plainly what fits.