For people
Learn through real use cases.
- Quickstart — compliant system in minutes
- Tutorial: your first system
- RDD Methodology — the conceptual foundation
- Reference
seiCLI — all subcommands
🟡 Partial — sei does not yet produce a complete Annex IV.
“By construction” refers to the generation mechanism — the Annex IV is assembled from the signed bundle, not hand-written; its completeness is still partial (see Status & gaps).
This documentation describes the real state of the project. The gaps towards a complete Annex IV are enumerated in Status & gaps.
seisei is the Risk-Driven Development (RDD) CLI for AI systems classified as high-risk under the EU AI Act (Art. 6 and Annex III). It operates on a standard git repository and turns each risk treatment — code, parameter, or prompt — into a versioned change, signed with ECDSA-P256+DSSE+in-toto and traceable by normative clause.
The core principle: git closes the ISO 23894 treatment loop. A treatment is a code change; the git log is the evidence register; sei reconstruct converts it into the identification→evaluation→treatment→residual cycle. The Annex IV (EU AI Act Art. 11 and ISO/IEC 42001 Annex B) is generated from the signed bundle — it is not drafted by hand.
Risk-Driven Development (RDD) is an established idea in software engineering — Boehm’s spiral model made it the driver of the process; Venturalítica specializes it for AI risk treatment — and applies TDD discipline to the compliance cycle:
sei.yaml.The cycle is orchestrated by sei run (which runs the pipeline and measures); artifact freshness is monitored by sei status, and per-clause normative compliance is emitted by sei conformance.
For people
Learn through real use cases.
sei CLI — all subcommandsFor agents
This documentation is also designed for consumption by AI agents.
/llms.txt and how to navigate/llms.txt — curated site index (auto-generated)