THE SCOPE — SOW & Change Control OS Brain
THE SCOPE — SOW & Change Control OS Brain
For the work that keeps arriving after the statement of work was signed. One orchestrator plus ten specialists that diff what was agreed against what is being requested, price the difference, and give you language that keeps the relationship intact.
Scope creep is rarely one big ask. It arrives as eleven small ones, each individually reasonable, each impossible to refuse on its own. By the time the margin has gone nobody can point to the moment it went. So this ships a diff script: paste the signed deliverable list and the current request, and it returns a line-by-line in/out/ambiguous table with an effort delta on the out-of-scope rows. The disagreement stops being about whether someone is being difficult and becomes a table two people can read together. That reframing is most of the win.
scope_diff.py
Compares the signed deliverable schedule against the current request and emits a three-column table — in scope, out of scope, ambiguous — with an hours delta per out-of-scope row. Ambiguous rows stay ambiguous rather than being quietly resolved in either direction. Every OS Brain in this drop carries its own executable component, so the judgement calls stay with you and the arithmetic stops being a matter of opinion. Runs anywhere Python runs, and the specialists still work on their own if you never open it.
Say it in plain words — it works out the rest
Inside · orchestrator + 10 specialists
Where it refuses to skip ahead
- No answer without the diff — "I think that's extra" invites a debate you lose to whoever remembers kickoff differently.
- No change order without an assumption — assumptions are what make a number defensible six weeks later.
- No effort number without a taxonomy — counting deliverables without separating a master from a version is how teams underprice by half.
- Ambiguous stays ambiguous — forcing a grey item into scope to look easygoing is the most expensive habit in the trade.