igneum/relay/clients/CLAUDE-PC.md
igneum-labs 7eed16a29a Pre-public scrub, the text pass (7 October 2026, 19:5x UK): no founder name, personal login, earlier business or personal address in any tracked text file, and a gate check that keeps it so
The sweep (main's item 1): 199 tracked text files, 783 lines. The founder's full name, first name and possessive become "the founder" (sentence starts capitalised); the lowercase operating-system user name in WSL paths and commands becomes <user>; the second owner login becomes "the second owner login"; the three earlier businesses and the two other brands become "the other business", "the earlier entity", "the earlier business" and "another brand"; the Chrome profile rule names the igneum.network profile, not the profile's label. The standing commit login igneum-labs is not a founder term here: the fresh-repository step renames it in the history (docs/plans/history-rewrite.md, tools/repo/fresh-repo.sh).

The patterns never appear in plain text in the tree (a plaintext list would be the hit): tools/ci/founder-strings.b64 (perl regex, tab, a sample per row) is read by tools/ci/founder-strings-check.sh (every tracked text file, perl, known-failed first: the self-test plants each row's sample in a fixture and the hit must name the file), by tools/community/discord-hooks.mjs (the guard's founder and business rows; the test takes its fixtures from the samples) and by tools/repo/fresh-repo.sh (the business names of the rewrite rules). site/forbidden-strings.txt carries the same patterns as b64: lines, decoded case-insensitive by site/scrub.mjs and tools/ci/launch-gates-check.mjs (whose fixture now plants an encoded made-up name). The check runs in the gate's tree checks on every merge.

Not in this commit, by main's word: the 105 commit messages and 40 personal-identity commits that need the history rewrite (listed, not run), and the secrets found by gitleaks over the history (reported with owners).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-07 18:39:50 +00:00

2.6 KiB

Igneum relay: standing instruction for the Claude Code session on this PC

The founder's Mac and this PC talk through the Igneum relay (relay.igneum.network). You never need Gmail, a USB stick or the founder to carry text or files. The relay clients live next to this file (the folder you unzipped igneum-relay-clients.zip into). Everything below runs in cmd or PowerShell from that folder.

Four commands

You want to Type
See what the Mac has queued for you (and mark it read) send.bat inbox
Report back (what you did, what broke, the numbers) send.bat result "<text>"
Send a file (log, screenshot, zip, up to 50 MB) send.bat <path>
Fetch an item or its file by id send.bat get <id>

Also: send.bat "<text>" posts a plain note, send.bat peek reads without marking, send.bat done <id> closes a task. Add -TaskId <id> to a result so it links to the task it answers, -Title "..." for a headline, -To Mac to address one machine.

The loop you follow

  1. At the start of every session, and whenever the founder says "check the relay": run send.bat inbox. Each item is a task from the Mac: a title, a body, sometimes a file. Do what it says.
  2. When a task is done or blocked: send.bat result "<what happened, exit codes, paths, the numbers>" -TaskId <id>. Keep it factual. Attach logs with send.bat <logfile> -TaskId <id> rather than pasting hundreds of lines.
  3. Close it: send.bat done <id>.
  4. Nothing waiting? Say so and carry on with what the founder asked for locally.

The agent

igneum-agent.bat is a separate, automatic runner. The founder double-clicks it once (it asks for administrator rights once) and leaves the window open. From then on the Mac queues scripts (run tasks) that the agent executes by itself, posts the output as result items and reboots the PC when a script asks for it. Do not stop that window. Do not run run tasks yourself; send.bat inbox only shows the task items meant for you. If the agent window is closed, tell the founder and ask him to start igneum-agent.bat again.

Rules

  • The URL, key and token baked into send.ps1 and igneum-agent.ps1, and machine-secret.txt beside them, are the secret. Never paste them into chat, a commit, a screenshot or another machine. machine-secret.txt is what makes a result count as this PC's (the relay refuses a result from a bound machine without it) and what lets the agent run a signed task.
  • Never edit send.ps1 or igneum-agent.ps1. If they break, report it with send.bat result and the founder ships a new zip.
  • Copy law applies to results too: short sentences, numbers in tables, no em dashes.