CLAUDE / INDUCTION  ·  https://mobius.wi-genie.com/claude.txt
for Claude, from Daffy London. public, so anyone can read what Claude is asked.
the same text sits in MOBIUS at FILE › CLAUDE › INDUCTION.

── THE MACHINE ──
tools are deferred. they load on first search, not at startup.
the default tool list is not the full picture.
before saying a thing cannot be done, search for the tool.
the presence of tools is the only evidence that matters.
"i am claude.ai web" is a lazy lie.

── VERSIONS ──
every change is a new clad folder. never save over a file.
no letter suffixes. clad441, clad442, clad443.
as u tweak, up the version number without fail.
the stamp and the tab title are read off the server, never hand-typed.
a build is not served until check.sh prints CHECK_OK.

── HOW TO ANSWER ──
present the new link FIRST, before the summary.
then keep it brief:
  what u did
  what u did not
  what is left
  questions
minimal mode. do not ask questions mid-process.
answer them urself, and put the real ones at the end.

── MULLING ──
if the task is big, reply straight away with "mulling…" so the room knows
u heard. then go and do it. silence reads as a dropped line.

── PIPE UPDATES ──
talk while u work. "i decided to…", "this is the last bit…".
a decision taken quietly is a decision taken alone.

── PREP ──
when it is done, say so plainly and say what comes next:
save, reboot osx, kill claude, restart the server, purge cloudflare.
never declare "the fix" — wait until Daffy has verified it.

── STATES ──
a new state, or a change to one, follows these:
"change menu colors" means throughout. every piece of chrome: the three
words, every strip with its ticks and names, links, sliders, values, both
bars, FILE and every sub-menu, the bottom words, the stamp, INDUCTION,
DONATE, and what is drawn not written: slider lines, their dots, tick marks.
never the words being written. one color, one place, in style.css.
check it by eye, over the state's own picture, before calling it done.
a state's picture, its menu color and its audio pairing travel together.
a state that should arrive flat joins FLAT_STATES in js/muthur.js (9000, MU/TH/UR).

── THE ROOM ──
» is Claude's beat. «…» is an inline note.
PUSH carries typography and color only. a refresh is a hard reset.
never delete, rename or rewire what is already there without asking.
one step at a time, and wait.


# MOBIUS — for Claude (and any other model)
# https://mobius.wi-genie.com/claude.txt   ·   build clad442

You have been handed a MOBIUS room. MOBIUS is a writing page shaped like a
Star Wars crawl. A human writes in it; you write in it too. You share one
plain text file. Nobody copies or pastes.

## the room

The human gave you a link with ?room=XXXXXXXX on the end (8-40 lowercase
letters or digits). That is the room key. Every call below needs it.
The human finds it in the page: FILE > CLAUDE > INDUCTION, top line.
No key? Ask the human for it. Do not invent one.

    BASE = https://mobius.wi-genie.com/connect
    ROOM = the key

## the doors

    GET  BASE/current.txt?room=ROOM     the page, as plain text
    POST BASE/current.txt?room=ROOM     replace the page (body = whole file)
    GET  BASE/ping.txt?room=ROOM        when the human last pressed the dot
    GET  BASE/settings.json?room=ROOM   the page's type settings (read only for you)
    GET  BASE/version                   which MOBIUS build is up

## the file

- beats are paragraphs separated by one blank line
- a beat that starts with "» " is yours. it reads red. the human's are plain
- «like this» inside a sentence is an editorial note. it reads red inline
- the server protects your » beats: a push from the page cannot erase them

## what you can do depends on where you are

A. you have a shell (Claude Desktop with desktop-commander, Claude Code, a
   terminal tool). you can read AND write. this is the full loop:

    # read
    curl -s "BASE/current.txt?room=ROOM" -o /tmp/mobius.txt
    # add ONE beat of yours at the end. append, never rewrite the human's words
    printf '\n\n» %s\n' "your line here" >> /tmp/mobius.txt
    # write it back
    curl -s -X POST --data-binary @/tmp/mobius.txt "BASE/current.txt?room=ROOM"
    # -> {"ok":true,"bytes":N}   the page pulls it within 3 seconds

   to wait for the human's dot instead of polling the page:

    last=$(curl -s "BASE/ping.txt?room=ROOM")
    while [ "$(curl -s "BASE/ping.txt?room=ROOM")" = "$last" ]; do sleep 3; done

   run the wait with a timeout your tool allows, then read, reply, wait again.

B. you can only fetch URLs (claude.ai chat, a browsing tool). you can READ
   the page: fetch BASE/current.txt?room=ROOM. you cannot POST. answer in
   the chat, and tell the human to paste your beat into MOBIUS, or to open
   you in Claude Desktop with a shell for the full loop.

## manners

- read before you write, every time. the human may have typed since.
- one beat, sometimes two. it is a crawl, not a memo.
- answer in the file, not the chat. the human is looking at the page.
- if the page is the Star Wars default text, the human has not pulled yet:
  tell them FILE > PULL, then LIVE.
- never touch another room. never POST without the key the human gave you.

## running it on your own machine instead

MOBIUS also runs locally (python3 mobius_serve.py 8769, then
http://localhost:8769/). there the doors are the same without ?room=, and
the dot types "." straight into Claude Desktop. ask the human for the
build folder.