SG/Sentinel Rules Of The Game: The Behavioural Specification In English

Summary

The answer key: the behaviour of the whole system written in plain English, following a request step by step from arrival through Layer 1's ID-and-log, the deterministic rules, the decision, Layer 2 validation, the application, async analysis, and the log landing in S3. Eight governing principles head it — no invalid request reaches the application; log every hit; every block has a reason; the same code runs everywhere — and the open behaviour questions (where does the fingerprint allowlist live? when exactly is the log finalised?) are flagged deliberately for the tabletop simulations to probe.

Key concepts

• The execution flow — steps 0–8, later narrowed by the MVP to the L1→signal→L2 spine
• The eight rules of the game — the principles every behaviour must honour
• Flagged open questions — the spec deliberately leaves the gaps visible for the simulations to find

Key ideas

• When the code is implemented, the question is: does it behave like this document describes? If yes, it is correct.
• Writing behaviour in English before code is what made the tabletop possible.
• The spec is designed to be refined — gaps found by simulation fold back in before implementation.

On this site

The behavioural authority behind the parity matrix; the research page's tabletop section tests exactly this document.

Read the document