igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

in-house-pass.md: the no-inline-deletion rule

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 20:36:43 +00:00
parent 8115893a1a
commit a824108436
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
docs/plans/cryptanalysis/in-house-pass.md
View file

@ -92,6 +92,7 @@ Standing rule from the project lead through main (7 October 2026, 19:1x BST), bi
| Pods | Second resort after the boxes' idle cores. The fleet's rules (the fleet lane, 18:26Z): no CPU-only pod type exists; every pod is a RunPod GPU pod (secure, or a 3090 or 4090 community; Vast unreliable tonight), image nvidia/cuda 12.8.1 on Ubuntu 24.04, 40 GB disk, vCPUs with the card (4 to 16), rented by `oneshot.py rent <label> <lane> <hours> [gpu-type] [min_vcpu] [min_ram_gb]` with the purpose and lane in the registry row, destroyed on "done", at <hours>, or by the idle meter; long runs under setsid nohup with a pid file under /root/fleet/out/. Spend at 18:26Z: USD 413.32 of the 1,000 UK-day ceiling (work 165.55, leak 247.77), the standing fleet about USD 197 a day. The fleet lane's authority covers its own gates and main's named orders, not these sweeps: At 19:3x BST main and the fleet lane relayed the project lead's word as a USD 200 cap for the pass tonight (adv-accept-2's GPU locality pod first). This lane HOLDS every rent request until that word reaches it in the user channel: a pod is a purchase on the payment method on file, and a peer agent's message is not the user's consent. When it arrives, each request goes to the fleet lane as purpose + lane + hours + pod type; the fleet lane destroys each pod at the end of its sweep and reports at each USD 100; this lane reports to main at USD 100 and at the cap |
| First results | Every lane's report carries first results by 00:00 BST, 8 October, with the box-hours and pod-hours spent, the bound reached honestly, and one line on what a longer pass would add (not a reason to wait) |
| The box-hour line is a reading | 8 box-hours per lane, 24 in all, is read and reported to main when crossed, not a stop; 16 per lane, 48 in all, is the ask line |
| No inline deletions | Main, 21:33 BST: never an inline `rm`, `rm -rf`, `find -delete` or a redirect-truncate inside a `bash -c` or `sh -c` string (the desktop app asks the founder to approve each); scripts live in a file under tools/ or the lane's scratch and run by path; on the boxes deletions go through the lease or job tooling; the gate check tools/ci/inline-rm-check.sh lands with the build-server lane's next merge; relayed to all nine lanes |
| Exceptions only | The coordinator reports to main only exceptions (a lane blocked, a box contended with a build, a leak of a withheld input) and clock readings (each plan's arrival, each first result, the spend crossing 16 box-hours or USD 100 of pods) |
| Lanes | First results | Ask line | Notes |