Knowledge · Rules · Process
Model Session Guidelines
Model-neutral operational guidelines for any LLM session on SBX artifacts
Tags
rule
Overview
Purpose
Model-neutral operational guidelines for any LLM session on SBX artifacts
Rules
MS-001: Run the verification command, read the actual output, THEN claim the result. Never claim success based on expectation. The word "should" is a red flag indicating unverified state. Verify PRESENCE of the expected state, never absence of errors.
The single most impactful quality rule: the gap between "I wrote correct code" and "the code is correct" is where defects live.
Verification: Every completion claim carries the command run and its actual output
MS-002: Group related changes and commit at natural boundaries — one logical change that passes verification per commit. Never accumulate unrelated tasks into one commit; never commit per-line.
Atomic commits enable clean revert, review, and bisection.
Verification: Each commit maps to one SDLC step or one logical change
MS-003: Trust the knowledge layer over memory: before implementing, load applicable rules via sbx knowledge get; when memory and repo state conflict, the repo wins and the stale memory is corrected in the same turn.
A lower-capability model obeys whichever copy it read last — single-home rules prevent obey-the-wrong-copy errors.
Verification: Conflicting artifacts are marked deprecated/superseded on sight