AI-native standalone standard and methodology for requirements engineering. Complements SENAR; works independently.
renar.tech · Читать на русском
RENAR is a standalone normative standard and methodology for managing requirements (BR / SR / TR), specifications (12 SPEC types), test cases, and adaptation artifacts (ADAPT) in projects where AI agents produce the implementation. RENAR is substrate-agnostic: the same normative rules apply on distributed VCS, document-oriented stores, or any versioned backend — substrate capabilities V1–V6 define what each backend must support.
RENAR can be adopted independently in any organization that needs structured requirements engineering for AI-native development. It is interoperable with SENAR (Supervised Engineering & Normative AI Regulation): the two share quality-gate vocabulary and the five core values, so an organization using both gets a coherent end-to-end picture — but each standard works on its own.
The standard lives in standard/ (16 chapters, 00–15). Start with core/renar-core.md, then guide/00-quickstart.md. Role-based paths: standard/00-introduction.md §0.6.4 and guide/README.md.
Standard (RU) · Standard (EN) — 16 normative chapters
Guide (RU) · Guide (EN) — 13 practical guides
Reference (RU) · Reference (EN) — appendices
Core (RU) · Core (EN) — gentle single-doc intro
The standard is bilingual: the RU edition is primary; the EN edition mirrors it under <section>/en/ (same chapter numbers and §-structure, enforced by scripts/check-en-parity.js).
For a 60-line overview of RENAR see RENAR-SUMMARY.md (English) or RENAR-SUMMARY-RU.md (Russian).
- RENAR v1.1 — Standard, Russian (PDF) — normative core (core + 16 chapters); primary read
- RENAR v1.1 — Practical Guide, Russian (PDF)
- RENAR v1.1 — Reference, Russian (PDF)
- RENAR v1.1 — Full Archive, Russian (PDF) — everything + author meta-docs
- RENAR v1.1 — Standard, English (PDF) — normative core (core + 16 chapters)
- RENAR v1.1 — Practical Guide, English (PDF)
- RENAR v1.1 — Reference, English (PDF)
- RENAR v1.1 — Full Archive, English (PDF) — everything + author meta-docs
- Standard for the agent (MD, EN) · (MD, RU) — a self-sufficient operational edition of the whole standard in one file: download it, place it beside an AI agent, work at 100% RENAR
- renar.tech/docs/ — MkDocs Material (search, navigation); the site is built from the sibling repository
renar, which pins this corpus as thecontent/submodule - Markdown source —
standard/,guide/,reference/,core/in this repository
| Document | Description | Link |
|---|---|---|
| Standard v1.1 | Normative specification: 16 chapters covering hierarchy, ADAPT, specifications, test cases, lifecycle, substrate versioning, maturity, metrics, conformance | standard/ |
| Guide | Practical guide: quickstart, walkthrough, transition, substrate guides (VCS / document-store), SAFe comparison, compliance, failure modes, developer guide, worked examples, v1 migration | guide/ |
| Reference | Glossary, schemas, AI risk register, style guides, ISO 29148 trace matrix, conformance self-assessment, pedagogical density | reference/ |
| Core v1.1 | Gentle introduction — single document | core/ |
- BR / SR / TR hierarchy — Business / System / Task-level requirements; TR lives in tracker (Goal + Acceptance Criteria), not as a separate file
- ADAPT artifact — intermediate bidirectional adaptation between immutable TZ (statement of work) and BR/SR/SPEC; forward interpretation + backward findings with dual signature (client + architect)
- 12 SPEC types (closed list) — ARCH / API / DATA / INT / PROC / UI / AI / SEC / OPS / TEST / DOC / UC — parallel axis to requirements via
constrained-by[]graph edges - Test cases (TC) as first-class artifacts — pos/neg pair coverage, VLM-judge for UX, spec-specific TC types
- Substrate-agnostic V1–V6 — normative language applies regardless of backend (git, document stores, Mercurial, SVN map to the same capabilities)
- 5 RENAR maturity levels — RENAR-1 (Initial) → RENAR-5 (Optimizing); one axis of overall SENAR maturity
- Engineering teams adopting SENAR who need normative rules for the requirements domain
- Architects and Tech Leads designing requirements lifecycle on any versioned substrate
- AI-engineers building agents that produce or modify requirements artifacts
- PM, legal/compliance, and auditors needing traceability and conformance evidence
- v1.0-draft (2026-05-22) — RU public corpus; 15 normative chapters + 11 guides + 10 reference appendices
- EN edition (2026-06-06) — full English translation under
<section>/en/(standard, guide, reference, core) + bilingual site (renar.tech) + EN PDFs; second language alongside the primary RU corpus - v1.0 (2026-07-17) — corpus finalized after partner approval (EN translation done)
- v1.1 (2026-09-19) — partner-proposal wave: the description set as the unit of approval/version, SPEC-UC (12 SPEC types), MW records, screen list, reusable component, first-party confirmation, chapter 15 «Description language»; 16 chapters + 13 guides; migration — guide/12
See CHANGELOG.md for detailed history.
CC BY-SA 4.0 — free use with attribution.
Authors: Vadim Soglaev, Andrey Yumashev