for teams
One source of truth for every human and agent.
Two engineers, four agents, one charter. Nobody re-explains the architecture on Monday.
# charter
## scope
- checkout, orders, pricing
## don'ts
- never change tax rounding
- never add deps without approval
read by 7 tools
04 feb · session 12
postgres, for jsonb performance
11 feb · session 18
stripe webhooks must be idempotent
18 feb · session 24
totals computed server-side only
task · fix button colour
files in task · 2
✗ /api/auth/session.ts · outside scope
held for review
✓ scope ok on 2 of 3 files
shared charter
Everyone reads the same rules. Edits are reviewed, not whispered.
decision timeline
The reasoning behind each choice stays with the code.
scope guard
Parallel contributors can't quietly edit each other's files.
for founders
Building on Lovable, Base44 or ChatGPT with no full-time CTO?
Stet is the senior engineer in the room: it writes down the decisions, keeps the scope tight and refuses the change that breaks signup.
start with one repo · npx stet-cli init · free and open source
try it now
Ten minutes to your first locked feature.
Free and open source. Run it in any project folder; it detects your stack and writes your AI rulebook.