RENAR

Requirements Engineering & Normative Adaptive Regulation

A standalone standard and methodology for requirements engineering in AI-native development.

Complements SENAR; works independently.

Full Standard Practical Guide Download PDF · Standard
PDF · Guide PDF · Reference PDF · Full Archive MD · Standard for agent (1 file)
v1.0-draft · 06.06.2026
15 normative chapters · 11 practical guides · 11 references
CC BY-SA 4.0
EN · RU also available

What RENAR Is

RENAR is a standalone normative standard and methodology for managing requirements, specifications, and test cases in projects where implementation is carried out by AI agents. The rules are formulated independently of any specific storage (substrate): the same norms apply on version control systems (git, Mercurial, SVN) or on document stores — as long as capabilities V1–V6 are supported.

RENAR can be applied independently in any organization that needs structured requirements engineering. It is compatible with SENAR: both standards share a common quality gate vocabulary and the same five values.

Its relationship to SENAR is a peer complement, the way ISO 29148 complements ISO/IEC 12207: independent documents that fit together well.

Key Concepts

BR → SR → TR Hierarchy

Three levels: BR (business — who, what, why) → SR (system — what it does) → TR (task — goal and acceptance criteria in the tracker, not a file).

ADAPT Artifact

Two-way adaptation between an immutable TZ and BR/SR/SPEC: forward interpretation + backward findings (7 categories) with a dual signature.

9 SPEC Types (closed list)

ARCH / API / DATA / INT / PROC / UI / AI / SEC / OPS — a parallel axis via constrained-by[]. A new type requires a standard amendment.

Test Cases (TC)

First-class artifacts: paired positive and negative scenarios, UX evaluation via VLM, TC types bound to SPEC; the [test-spec-change] tag guards against tailoring tests to pass.

Substrate Capabilities V1–V6

V1 immutable history · V2 atomic change unit · V3 diff & review · V4 branching and drafts · V5 version pin · V6 author + timestamp.

5 RENAR Maturity Levels

RENAR-1 (Ad-hoc) → RENAR-2 (Documented) → RENAR-3 (Tracked) → RENAR-4 (Verified) → RENAR-5 (Optimized). A dedicated requirements maturity dimension within the SENAR family.

Four Documents

Standard

Normative specification

  • 15 chapters (00–14)
  • MUST / SHOULD / MAY
  • BR/SR/TR + 9 SPEC + V1–V6
  • 4 quality gates (QG)
  • RENAR-1..5 maturity

Guide

Practical application

  • Quickstart (30 min)
  • End-to-end example
  • Transition from current practice
  • Example library
  • Migration to v1.0-draft

Reference

Glossary and schemas

  • Canonical terms
  • JSON schemas for artifacts
  • AI risk register
  • ISO 29148 matrix
  • Conformance self-assessment kit

Core

Gentle introduction

  • Single document
  • For first acquaintance
  • Without all the formalities

Reference Implementation: TAUSIK

TAUSIK is an open-source framework that applies the SENAR rules (and, when extended, RENAR). RENAR remains a standalone standard; TAUSIK is one of the possible runtime environments, not part of the normative text.

Start Wherever Fits

Open the Core for a gentle introduction, or go straight to the full standard if you already know SENAR.

Start with the Core Full Standard

RENAR v1.0-draft · CC BY-SA 4.0 · Normative language per RFC 2119 (EN UPPERCASE keywords, Style Guide §2)