What Socrates keeps, what it keeps out, and what credit adds.
Each enrolled project gets five, in your Linear, created on first write. They’re yours, and they stay if you leave.
Enrol a project by giving it the Socrates label. Remove the label to stop.
The calls later work relies on, and why.
Acme API - Load-Bearing Decisions
Linear docACME-D14 · Tenant storage is keyed by orgId
Why: Billing and auth already key by org, and a workspace can move orgs.
ACME-D9 · Tenant storage is keyed by workspaceId
Conflict · worker/export.ts keys by workspaceId, against ACME-D14 · opened Nov-03
Plus org-wide rules.
The decisions every project inherits. Contradict one and it comes up for review, never as a silent fork.
Give everyone the pen and you need a filter: left alone, one in five proposals is noise. Socrates checks each against fixed rules on your machine before a person sees it.
$ eris socrates classify
Pin wrangler to 4.42.0
dropped · the lockfile owns it
Use the in-memory queue for now
dropped · it has an end date
Every migration gets its own commit
practice · written to Practices
Tenant storage is keyed by orgId
load-bearing · proposed for review
Every seat runs the whole loop. Credit puts Socrates’ own agents on the chores, so your reviewer only has to judge.
Duplicates
Every seat:Exact matches merged
With credit:The same decision in other words, merged
Unclear proposals
Every seat:Left for the reviewer to work out
With credit:Pre-read by an agent, with its reasons; the reviewer still decides
Evidence
Every seat:A source link
With credit:A summary on every review item
Closing the review
Every seat:When you run it
With credit:The moment the review closes
Out of credit, it drops back to the baseline. Nothing stops.
Tomorrow’s review shows up in your Linear.
npx skills add sibylline-labs/eris --skill eris-socrates
$3 a seat · 14-day free trial, no card
Sign in with Linear
