Changelog
Version history of the SENAR standard.
v1.4
Latest 2026-09-04The standard norms its own gate. Until 1.4 the quality gates listed criteria and none of them named the effect the gate prevents, so a gate could be placed anywhere and conform everywhere — and the prohibition on bypass had no subject, because a bypass is undefinable until placement is defined.
Added
- Section 8.6 — Gate Properties — five properties every gate SHALL have: declared prevented effect, preventive placement, correspondence of the verdict to state, binding to a measured digest, fail-closed
- A declared prevented effect for every gate — QG-0 through QG-4 each name the change that does not occur while the verdict is negative
- 8.6(j) — direct modification of an artifact is a Gate Bypass and is recorded as one; a regulated exception with a mandatory record, not a prohibition
- Section 13.7 — Mechanically Checkable Clauses — what a claimant presents per property and how it is checked
- Coverage Limitations — a bound on the survey, next to the existing bound on the data: what was read, what was seen only in structure, and what was not examined at all
Changed
- Breaking for existing conformance claims — gate properties scale by configuration, and 13.6 now requires reassessment rather than recommending it. A gate placed after the effect it declares is a detective control and does not satisfy 8.6(b)
- Metric 8 derived from records — Manual Intervention Rate is computed from recorded Gate Bypasses instead of self-report, and says plainly that it measures what was recorded, not what occurred
- The producer qualifier is gone — rules no longer say "AI-generated code", because the same file changed the same way was outside the requirement whenever the change arrived by another route
- Positioning restated through properties — "first methodology" and "the missing layer" removed from every address; the claim is now checkable and says how to refute it
Open
- QG-3 at Foundation — 8.7 and Sections 3, 8.4, 8.9, 8.10 and 11.1 disagree on whether QG-3 is owed at Foundation for security-sensitive systems. This revision states the conflict rather than settling it, and carries it to the next
v1.3
2026-03-25Added
- Rule 15: AI Output Quality Verification — three verification levels (L1 Automated, L2 Self-Review, L3 Adversarial Review) with risk-based scoping
- Metric 10: Adversarial Detection Rate (ADR) — measures CRITICAL findings per L3-reviewed task (renamed from Vibe Code Rate)
- S5.5 Structured Tool Protocol — protocol-agnostic requirement for agent-platform interaction
- S5.6 Agent Dispatch and Execution Isolation — risks, mandatory practices, canonical pattern
- S5.7 Federation — scaling SENAR across projects: independence, coordination, knowledge routing, federated metrics
- 23-item AI Review Checklist — expanded from 13 items with 3 priority tiers; latent defect patterns from adversarial audits
- Code Standards Template — evidence-based template for organizational code standards
- 8 new term definitions: Adversarial Review, Agent Dispatch, Latent Defect, ADR, and more
- KCR calibration guidance, no-epoch filtering policy, multi-session metrics disclaimer
Changed
- Rule 12 Context Hygiene — upgraded to SHALL for credentials/PII at ALL configurations
- Stack neutrality — removed all vendor/product names from normative text
- QG-2: “types clean” → “static analysis passes”
- Configuration counts: 15 rules (was 14), 10 metrics (was 9)
Reviewed
- 3 rounds of adversarial review by 9 independent reviewers (methodology critic, security expert, practitioner)
- All CRITICAL findings resolved including stack neutrality, human-in-the-loop, federation security
v1.2
2026-03-23Added
- S5 Agent Instrumentation — new section: control levels, agent profiles, script governance, programmatic interface, portability
- Rule 14: Script Change Management — version-controlled, reviewed, rollbackable
- Guide: Agent Configuration in Practice — new chapter with examples for Claude Code, Codex, Cursor
- Context Architect role expanded: agent profile design, script management
- Tooling Requirements: agent configuration management section
- Changelog (this document)
- Site: mobile navigation, changelog page
Changed
- Sections renumbered: S5→S6, S6→S7, ... S12→S13
- All cross-references updated
Fixed
- Navigation 404 on Standard link
- Literary Russian improvements
v1.1
2026-03-22Added
- Requirements hierarchy: BR → SR → TR
- QG-0 strengthened: requirement traceability
- QG-1: Requirements Gate (Team+ only)
- Rule 10: Requirement Traceability
- Rule 11: Code Documentation as Context
- Rule 12: Context Hygiene
- Rule 13: AI Model Governance
- Guide chapters: Quick Start, Requirements Engineering, Legacy Adoption, Worked Example, Tool Integration
- Conformance clause (self-declared, peer, audited)
- Enterprise roles (Portfolio Manager, Chief Supervisor)
v1.0
2026-03-21Initial Release
- 12 sections, 5 roles, 5 units of work
- 7 procedures, 5 quality gates, 9 metrics, 11 rules
- 3 configurations: Essential, Team, Enterprise
- Guide: 6 chapters
- Reference: glossary, scaling, efficiency, governance, tooling