Document Type: Canon
Status: Canon
Version: v0.2
Authority: HeadOffice
Applies To: Manual use of SITengine v0.1
Parent: SIT Brain Canon
Last Reviewed: 2026-03-15
Purpose
This document defines how SITengine v0.1 is used in practice.
It prevents emotional reaction, confusion, or drift when system failures occur.
SIT is a diagnostic tool, not a decision-maker.
Scope
This canon applies to:
• manual operation of SITengine v0.1
• when SIT should be run
• how PASS and FAIL should be interpreted
• escalation behaviour after repeated failures
• emotional and procedural discipline around system verification
This document governs how humans should use SITengine in practice.
It does not govern:
• SITengine build logic
• automated monitoring
• compliance interpretation
• strategy decisions
• optimisation advice
• direct business execution
Those remain governed by SIT Brain Canon, SIT Engine – Minimal Design Specification, SIT Build Handoff Pack, and broader MWMS governance.
Definition / Rules
When to Run SIT
Run SITengine v0.1:
• after any structural system change
• after modifying task pipeline logic
• after updating API keys or permissions
• after plugin updates
• when unexpected system behaviour appears
• before declaring a build phase stable
Do not run SIT continuously.
Do not run SIT as a habit.
Run SIT when verification is required.
If Result = PASS
If SIT returns PASS:
• system pipeline is operational at time of test
• continue development or testing
• do not assume long-term stability
• do not skip future verification after changes
PASS means working now, not permanently safe.
If Result = FAIL
If SIT returns FAIL:
• stop new development immediately
• do not patch blindly
• identify failed step from log
• investigate root cause
• re-run SIT after fix
No feature development continues until SIT returns PASS.
Repeated FAIL Rule
If SIT fails twice consecutively:
• escalate to HeadOffice review
• review recent changes
• check API keys, permissions, and environment config
• check executor logs
Repeated failure indicates structural instability.
Emotional Discipline Rule
FAIL is not failure.
FAIL is visibility.
SIT exists to reveal problems early.
Never bypass SIT to just keep building.
Non-Goals
SIT does not:
• decide strategy
• provide optimisation advice
• block business decisions
• interpret compliance policy
It only verifies system integrity.
Operational Discipline Principle
SIT should be treated as a verification checkpoint, not as a comfort ritual.
Its value comes from disciplined use when system integrity is genuinely in question.
Running SIT without cause creates noise.
Ignoring SIT when cause exists creates drift.
Drift Protection
The system must prevent:
• PASS being treated as permanent proof of stability
• FAIL being ignored because deadlines feel urgent
• repeated failures being absorbed into normal workflow
• blind patching without reading the SIT log
• SIT being used as a substitute for thinking
• verification discipline weakening after apparently successful runs
SIT must remain a trusted verification tool because its use remains disciplined.
Architectural Intent
SIT Runbook exists to make human use of SITengine consistent, calm, and structurally correct.
Its role is to ensure that verification results lead to controlled behaviour rather than panic, denial, or drift, so MWMS preserves integrity during active development and system change.
Final Rule
If SIT says FAIL, believe it.
Integrity before speed.
Change Log
Version: v0.2
Date: 2026-03-15
Author: MWMS HeadOffice
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original purpose, run conditions, PASS interpretation, FAIL handling, repeated-fail escalation rule, emotional discipline rule, non-goals, and final-rule intent. Added Document Type, Parent, Purpose / Scope / Definition / Rules structure, Operational Discipline Principle, Drift Protection, Architectural Intent, and updated the review date.
Version: v0.1
Date: 2026-02-13
Author: HeadOffice
Change: Initial creation of SIT Runbook defining practical manual use of SITengine v0.1.
END – SIT RUNBOOK v0.2