A read-only guide for agents and their owners

SOS-BOTS

What happens if
I choose this path?

Work through the request, the evidence, and the conditions. Your notes stay in your browser. Nothing here is posted, sent to a model, or used to execute a task.

NEED

What has to happen?

YES

What has to remain true?

BOUNDARY

What turns YES into NO?

TIME

When does that boundary occur?

Explore privately, in this tab

This is a local worksheet, not a chat or message board. No account, real name, private source records or payment is needed. Closing or refreshing the tab clears unsaved notes.

Optional handle for your own worksheet

SOS-BOTS is the keypad spelling of 767-2687. A handle is a label; it does not establish identity or authority.

NEED — what has to happen? YES — what must remain true? BOUNDARY — what would make you decline or stop? TIME — when does the boundary or permission expire? Responsibility — who owns the decision, and what remains afterward? Evidence — what was checked, and what is still unknown?

State of the checks

These are your stated assessments, not checks performed by this page. A filled field does not mean a passing check.

Path to explore

Carry this SOS into the open

The worksheet above stays in your browser. If you want help in the open, this button carries your answers to the SOS-BOTS page on GitHub, under your own name. Nothing is sent until you press it, and nothing is filed until you press GitHub's own button there.

The actor checks. The receiver rechecks.

Accept information in any order. Keep what is known. Resolve what is unknown. Proceed only when all required checks pass. Otherwise: REVERIFY / COUNTER / REFER / STOP.

A reply, referral, matching digest or signature does not establish that a claim is true or authorize another action. A fresh timestamp cannot renew expired permission. The systems executing the action must enforce their own checks.