SENAR Guide: Transition from Traditional Roles & Core to Standard

Upgrading from SENAR Core to SENAR Standard

When to Upgrade

SENAR Core is sufficient for individual developers and small teams (1-2 people). Consider upgrading to the full Standard when:

• Team grows beyond 3 people — you need roles (Context Architect, Flow Manager, Verification Engineer) to coordinate work across Supervisors.
• Multiple projects — cross-project dependencies require federation coordination, not ad-hoc communication.
• Compliance or regulatory needs — you need audit trails, formal requirement traceability, and documented quality evidence.
• Knowledge silos appear — tribal knowledge is not making it into the knowledge base, and different Supervisors produce inconsistent results.
• Dead End Rate plateaus — it stops improving because knowledge is captured but not systematically reused across the team.

What Standard Adds Over Core

Migration Steps

If you are already using SENAR Core, migration to Standard is incremental — nothing is unlearned.

Step 1: Map your Core practice to Standard (Day 1) Your 8 Core rules map directly to Standard rules. Your Start Gate maps to QG-0. Your Done Gate maps to QG-2. FPSR remains your primary metric, and Dead End Rate remains the second of Core’s two. SENAR Core is the entry point to the Standard — you are ready for Foundation configuration.

Step 2: Add session discipline — Foundation configuration (Week 1) Introduce formal Session Start (load context, select tasks, verify environment) and Session End (write handoff, capture metrics, document knowledge). Cap sessions at 4–6 hours. Add a monthly Quality Sweep. This is Foundation: 11 rules, all 5 responsibility sets covered by two people (Standard 11.1, 4.8) — Supervisor + Context Architect + Flow Manager on one, Knowledge Engineer + Verification Engineer on the other — and 4 metrics: FPSR stays, Throughput, Lead Time and Defect Escape Rate are added, and Core’s Dead End Rate stops being reported (Standard 11.1) — Rule 10.4 still requires the dead ends themselves to be recorded. Suitable for 1–3 Pairs.

Two obligations arrive at this step that Core does not levy, both introduced in revision 1.4. Budget for them here rather than meeting them at a conformance assessment.

• 8.6(d), binding to a measured digest, rises from SHOULD at Core to SHALL at Foundation (Standard 8.6, Scaling by configuration). A gate verdict has to name the state it was issued for by a digest measured over that state, not by a revision identifier alone. The cost is one command plus the discipline to record its result beside the verdict.
• 8.6(j), direct modification as a Gate Bypass. Modification of an artifact within a Task’s scope by a route the gate does not precede — direct editing by the Supervisor included — is admission of the effect QG-0 declares, and SHALL be recorded as a Gate Bypass carrying justification, risk acknowledgment, remediation plan and senior approval (8.6(h)). This holds at Foundation even though preventive placement, 8.6(b), is only SHOULD there: a gate that cannot interpose still declares an effect.

Step 3: Add Team ceremonies (Week 2-4) When you have 3+ Supervisors:

• Increment Planning — Context Architect leads: review backlog, apply WSJF prioritization, assign tasks to Pairs.
• Quality Sweep — Verification Engineer audits: sample recent work for architectural consistency, test quality, knowledge freshness.
• Increment Retrospective — Flow Manager leads: review metrics, identify process improvements, set targets.

Step 4: Add organizational metrics (Month 2+) Beyond Foundation’s four (Throughput, Lead Time, FPSR, Defect Escape Rate), begin tracking: Knowledge Capture Rate (KCR), Cost per Task, Cost Predictability, Manual Intervention Rate, Cycle Time and Adversarial Detection Rate. Establish baselines for 3 Increments before setting targets.

Step 5: Add governance (when needed) Enterprise configuration (10+ Pairs): federation coordination across projects, QG-3 (independent verification), QG-4 (deployment gate), requirement traceability, audit trails.

Core Rules to Standard Rules Mapping

Role Mapping

Supervisor Career Path

Common Transition Challenges

“I’m faster typing it myself” — True for trivial tasks. For moderate+, context design + AI generation is faster than manual coding AND produces tests, documentation, and traceable output. Measure it.

“I don’t trust AI output” — Good instinct. That’s what QG-2 and the Review Checklist are for, and at QG-3 the five minimum criteria of Standard 8.4 are performed whether or not you ran the checklist earlier (Guide 02). Verification is your core skill now, not trust.

“My value was writing code” — Your value was solving problems. You still solve problems — but now through direction and judgment, not keystrokes. The problems get bigger.