Mandates
Short, numbered rules such as M-001 single sign-on and M-020 the single money path.
Running inside SAIG
The Accord · part of SAIG
The rules are written down.And the codechecks them.
The mandates every SAIG app is bound by: one sign-in, one money path, one AI path, secrets never passed through chat. They are written to be checked by machines, and the conformance gate enforces them.
One SAIG account for every app. No separate sign-up.
Already doing the work inside SAIG. Opening to customers next.
Mandates in force across the estateConformance gate on every buildNext: Public Accord for Studio customersNext: Signed acceptance per app
What it does
Three jobs, done properly.
Machine-checkable
Each rule is written so a build can test it, not just a person.
Enforced
Apps that drift are flagged before they ship.
Replaces Policy documents nobody reads
How it fits
Not a tool on its own. A part of SAIG.
SAIG is a group of 66 apps that share one account, one way to pay, one AI and one record of every decision. The Accord plugs into the rest, so each app does its job once and every other app benefits.
In use
Already at work inside SAIG.
SAIG runs its own businesses on its own apps first. These are real uses, not mock-ups.
One money path
Every SAIG app takes payment through SAIG Pay, because the Accord says so and the gate checks it.
Secrets stay sealed
No app passes a key through a chat; keys are set in the vault, by rule.
For developers
Every SAIG app and engine is reached through /api/ext with its own per-app key. Health is public at /api/ext/health.
The SAIG ecosystem
66 apps. One account. One intelligence.
Travel, finance, legal, property, education and the engines underneath them, run by Skylite Group and built in the open. Start with the app you need; the rest is there when you are ready.
66apps on the grid
1SAIG account