SPM·STANDARDS
INSTITUTE

START / CREATE YOUR ZERO

Your own matrix.
Your own Zero.

Name a matrix and an objective, and get a prompt for the AI you already use. It reads the Institute's official protocol and starts a working record. This is a prompt for your own AI. It does not create a hosted instance, and it is not a certification.

Practical start · no accountSeparate from certification

WHAT YOU ARE SETTING UP

One person decides.
One AI coordinates.

A matrix is a small, bounded way of working: a human operator, an AI called Zero, roles added only when the task needs them, and a record of what actually happened.

THE OPERATOR

You.

The accountable human. You set the objective, make the decisions that matter and decide what counts as done.

ZERO

The coordinating AI.

Plans bounded work, keeps the record and reports what really happened, including failures. It starts alone. It proposes another role only when the task needs one, with its scope and limits, and prepares the onboarding once you approve. It does not decide for you.

ROLES

Scope and limits.

Each role has a job and a boundary. The one who checks is not the one who built.

THE WORKING RECORD

Resume anywhere.

A running record of intent, decisions, evidence and outcome, kept in a shared Google Drive folder. Zero reads it and the work continues from the last entry.

WHERE THE RECORD LIVES

Start in a shared folder.
Add a bus when you want one.

The working record is the memory of your matrix. It lives outside the chat, so any session can pick it up.

THE RECOMMENDED START

A shared Google Drive folder.

The prompt names the folder, “SPM Institute - your matrix name”. After it has loaded and verified the protocol, Zero creates the folder if it does not exist, then creates his own journal in it and keeps the record there as numbered entries: intent, decisions, evidence and outcome. Almost everyone already has Drive, so there is nothing to set up. This is the canonical home of the record until you choose otherwise. Share the folder with the AI you use. If your AI cannot read and write Drive, it will say so, print each entry and ask you to save it in the folder.

A LATER CHOICE

Your own bus.

A bus is a transport for messages: ordered messages with a durable sequence number, free reading for anyone with access, and writing under the name of one seat. People who want their own transport can build one. This page describes the idea only. You run it, so you hold its keys, and example code may be published later.

THE BOOTSTRAP PROMPT

Describe it.
Copy the prompt.

Nothing you type here leaves your browser. The prompt is built on this page and not sent anywhere.

BEFORE YOU START

What you need.
What you do not get.

Be clear about what this does, so nothing is assumed.

You need

  • An AI assistant you already use, able to open an HTTPS link.
  • A shared Google Drive folder for the working record. This is the recommended start, and no other setup is needed.
  • A bounded task, small enough to finish and check in one sitting.

You do not get

  • A running agent. The prompt is text for your own AI, and nothing is hosted for you.
  • Any Institute credential. Creating a Zero is not a qualification and does not need one.
  • Access to any other team's seats, tokens, journals or systems. Your Zero has its own operator, scope and record.
OFFICIAL PROTOCOL SOURCE

Checking the current release…

Source: protocol/current.json. Your AI reads it by link. You can read the same text here.

FIRST RUN, THEN RESUME

Four steps.
One record.

The prompt tells your AI to do exactly this.

  1. 01

    Paste the prompt

    Open your AI and paste it as the first message.

  2. 02

    Check what it read

    It must report the protocol identifier, version, release and checksum result. If it reports PROTOCOL_NOT_LOADED, the official source was not reachable or did not verify. Check your connection and run the prompt again.

  3. 03

    Approve one bounded task

    Zero proposes a first task with acceptance criteria and waits for your approval.

  4. 04

    Keep the record, resume later

    Zero writes each entry to the shared folder. Next session it reads the folder and resumes from the last entry, on the same pinned release.