Numbered requirements
Every change gets an ID and acceptance criteria before a line of code is written.
Running inside SAIG
SAIG Blueprint · part of SAIG
Say “build”.The plan isalready written.
Every SAIG app keeps its blueprint here: numbered requirements with acceptance criteria, sprints, testing and close-out. The team and its AI agents keep it current, so work starts from the plan, not from a meeting.
One SAIG account for every app. No separate sign-up.
Already doing the work inside SAIG. Opening to customers next.
Blueprints for every estate appRequirement IDs used across the CouncilNext: Customer workspaces in SAIG StudioNext: Board view for teams
What it does
Three jobs, done properly.
Sprints with dates
What ships when, per app, in one place the founder can read on a phone.
Close-out with proof
An item closes with the commit and the read-back, never on a promise.
Replaces Jira, Linear and task spreadsheets
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. SAIG Blueprint 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.
The Ask bar
The search-and-ask field in the top bar of every SAIG app was planned as requirement CON-R-084, built, tested and closed against that entry.
Cross-app asks
When one app needs another, the ask lands in the other app's blueprint with a date, so nothing lives only in a chat.
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