sanctor — Sept & Stone

sanctor exists to answer one question

Who can do what?

Authority runs on someone’s memory of what was agreed. Wherever people, or AI agents, act under an agreement, this question decides what happens next. It answers that, and holds everyone to the answer.

How it works

Write the book. Act by it.

Write the book.

Upload your agreements. sanctor turns each clause into a rule you approve. After that the book changes only the way it says it can, every version growing from the last. No master key, not even for us.

Act by the book.

Before acting, anyone, person or AI, consults the book. It answers with the rule that applies and sends the decision to those who can approve it. What already happened can be recorded too, once the people involved confirm it.

Kept for you.

Switch on what you need. Cap table, minute book, signing, compliance calendar, diligence room, more on the way. Each reads straight from the record, so nothing needs upkeep and nothing drifts.

Why sanctor

Fix authority at the root, and disputes have nothing to start from.

Most disputes are about who was allowed, not what happened. sanctor settles that in the book before anyone acts.

Authority from the book.

Every right, limit and signature comes from a clause you adopted. People and AI agents act under the same book.

Open any act.

See the request, the clause it rests on, who signed, and the sealed entry. Replay the book on any date to see who could do what.

Every clause is a rule.

Conditions, exceptions and cross-references compile into rules the book applies. Draft an amendment and see what it changes before anyone signs.

Where it works

BoardsQuorum, notice and recusal come from the book, not from memory. Every signature is a sealed entry.

DepartmentsA request goes to the people who can approve it, and no one else.

ShareholdersIssuances and transfers are checked against the bylaws, with pre-emption and waivers on the record.

FundsLPAs, side letters and committee approvals in one book. The audit trail is already written.

Joint venturesOne shared book no single party controls.

AI agentsAn agent acts only under the clauses it was given, and every act is checked first.

For developers

Put the book in front of your code.

Everything sanctor does is six calls. Birth a chain, propose, sign, check, do, read. Our own screens are these calls wearing clothes, so anything you see here you can build, and anything you build sits on the same record.

Open the developer console →Read the documentation →

const r = await sanctor.check({
  by: "k:a9e1",
  act: "pay",
  params: { amount: 18400, payee: "Harlow Vendor" }
});
// r.answer   → "yes, with signatures"
// r.rule     → "R-0006@2 · §4.3"
// r.requires → { threshold: "2/3", of: ["k:4f1e", "k:8c02", "k:d91a"] }
// r.usage    → { input_tokens: 211, output_tokens: 64 }

await sanctor.do({ by: "k:a9e1", act: "pay",
  params: { amount: 18400, payee: "Harlow Vendor" } });
// seals when the two sign · entry 1031

Pricing

One price.

$149

per workspace, per month

Every seat, every key, every entry

Rules, instruments, the full console

5M tokens included each month, per workspace

Need more? $25 per extra 1M tokens, metered as you go.

Number of workspaces

$149/ month

1 × $149 · 5M tokens included

Start your workspace →

14 days free. No card needed.