SDD Observatory
Stars
13
Contributors
1
Open issues
0
Age
7 months
Last push
2 weeks ago
Latest release
v1.5 Sep 29, 2026
Week of Oct 19, 2025: 0 commits Week of Oct 26, 2025: 0 commits Week of Nov 2, 2025: 0 commits Week of Nov 9, 2025: 0 commits Week of Nov 16, 2025: 0 commits Week of Nov 23, 2025: 0 commits Week of Nov 30, 2025: 0 commits Week of Dec 7, 2025: 0 commits Week of Dec 14, 2025: 0 commits Week of Dec 21, 2025: 0 commits Week of Dec 28, 2025: 0 commits Week of Jan 4, 2026: 0 commits Week of Jan 11, 2026: 0 commits Week of Jan 18, 2026: 0 commits Week of Jan 25, 2026: 0 commits Week of Feb 1, 2026: 0 commits Week of Feb 8, 2026: 0 commits Week of Feb 15, 2026: 0 commits Week of Feb 22, 2026: 0 commits Week of Mar 1, 2026: 0 commits Week of Mar 8, 2026: 0 commits Week of Mar 15, 2026: 0 commits Week of Mar 22, 2026: 1 commit Week of Mar 29, 2026: 0 commits Week of Apr 5, 2026: 1 commit Week of Apr 12, 2026: 0 commits Week of Apr 19, 2026: 0 commits Week of Apr 26, 2026: 1 commit Week of May 3, 2026: 0 commits Week of May 10, 2026: 0 commits Week of May 17, 2026: 0 commits Week of May 24, 2026: 0 commits Week of May 31, 2026: 0 commits Week of Jun 7, 2026: 0 commits Week of Jun 14, 2026: 0 commits Week of Jun 21, 2026: 0 commits Week of Jun 28, 2026: 0 commits Week of Jul 5, 2026: 0 commits Week of Jul 12, 2026: 0 commits Week of Jul 19, 2026: 0 commits Week of Jul 26, 2026: 0 commits Week of Aug 2, 2026: 0 commits Week of Aug 9, 2026: 1 commit Week of Aug 16, 2026: 0 commits Week of Aug 23, 2026: 0 commits Week of Aug 30, 2026: 0 commits Week of Sep 6, 2026: 0 commits Week of Sep 13, 2026: 0 commits Week of Sep 20, 2026: 0 commits Week of Sep 27, 2026: 1 commit Week of Oct 4, 2026: 0 commits Week of Oct 11, 2026: 0 commits
Commits per week, last 12 months · 5 total
View weekly commit data
Week startingCommits
Oct 11, 20260
Oct 4, 20260
Sep 27, 20261
Sep 20, 20260
Sep 13, 20260
Sep 6, 20260
Aug 30, 20260
Aug 23, 20260
Aug 16, 20260
Aug 9, 20261
Aug 2, 20260
Jul 26, 20260
Jul 19, 20260
Jul 12, 20260
Jul 5, 20260
Jun 28, 20260
Jun 21, 20260
Jun 14, 20260
Jun 7, 20260
May 31, 20260
May 24, 20260
May 17, 20260
May 10, 20260
May 3, 20260
Apr 26, 20261
Apr 19, 20260
Apr 12, 20260
Apr 5, 20261
Mar 29, 20260
Mar 22, 20261
Mar 15, 20260
Mar 8, 20260
Mar 1, 20260
Feb 22, 20260
Feb 15, 20260
Feb 8, 20260
Feb 1, 20260
Jan 25, 20260
Jan 18, 20260
Jan 11, 20260
Jan 4, 20260
Dec 28, 20250
Dec 21, 20250
Dec 14, 20250
Dec 7, 20250
Nov 30, 20250
Nov 23, 20250
Nov 16, 20250
Nov 9, 20250
Nov 2, 20250
Oct 26, 20250
Oct 19, 20250

Metrics updated Oct 11, 2026 · collected automatically from the GitHub API

Core approach

SENAR Core treats a task's goal, acceptance criteria, negative scenarios, and scope as the specification. A Start Gate checks those inputs; a Done Gate checks the current work against recorded evidence, requirement-derived tests, a risk-based review checklist, and captured knowledge. The wider standard adds team roles, ceremonies, and governance.

Workflow

  1. Define the goal, independently verifiable acceptance criteria, and at least one negative scenario
  2. Set scope boundaries and pass the Start Gate (QG-0) before writing code
  3. Implement with an AI coding agent and verify each criterion against recorded evidence
  4. Derive tests from requirements and review the work using the appropriate checklist tier
  5. Record decisions, dead ends, and known issues; pass the Done Gate (QG-2) against the current version
  6. Track first-pass success and dead-end rate against locally measured baselines

Supported tools

Strengths

  • Core is usable without dedicated software; gates may be applied manually or automated
  • Explicitly distinguishes evidence about the current version from stale results or an agent's assertion of completion
  • Connects task specifications, requirement-derived tests, risk-based review, and knowledge capture

Limitations

  • A written standard does not itself enforce gates; enforcement depends on the team's process or tooling
  • The quickstart's outcome evidence is an author-reported single-project experience that explicitly acknowledges confounding from team learning
  • The full standard introduces roles and ceremonies beyond the lightweight Core; adoption effort grows with scope

Notes

SENAR (Supervised Engineering & Normative AI Regulation), by Andrey Yumashev and Vadim Soglaev, qualifies as a documented SDD methodology: tasks define expected behavior before implementation, and completion depends on evidence against that definition. This assessment uses the repository’s v1.5 Core rather than treating the website’s older v1.4 overview as the current standard.

TAUSIK is its reference implementation and declares SENAR Core conformance. RENAR is a complementary, independently adoptable requirements methodology. They have separate entries because the standard, requirements lifecycle, and implementing tool serve different purposes.

The experimental rating reflects the limited independently verifiable adoption and outcome evidence reviewed, rather than the breadth of the documentation. The quickstart itself calls for independent replication of its reported results.

Sources

Added Sep 30, 2026 · Assessment last reviewed Sep 30, 2026 · How we track