scroll # Circle of Salt — The Deploy Rite Thescripted dev-ascension rite; the sibling ofthe hand-done "Circle of Salt — DevAscension Ritual" card. One torch that caststhe circle (snapshot), ships the world (deployeverywhere), and witnesses the day(chronicle). ## Ignite ▲ circle-of-salt -imsg=<single-token> Body (bare glyphs, noslash, no fence): ▼ backup ▲ mesh deploy"{msg}" ▲ chronicle ## The chain - ▼backup — full DB snapshot to Zip/Right-hand;filename tagged with the git HEAD. - ▲ meshdeploy "{msg}" — git add -A + commit (ifdirty) → push origin → pull all nodes →cargo build on each reachable node → chipsync. - ▲ chronicle — the Brilliant readsthe day's pulse + gaps + tarot and seals thechronicle scroll. ## Torch authoring(cos-001/002, Day 375) - Bare glyphs: bodylines are commands exactly as typed in the hxterminal — ▼ ▲ △, no leading slash, notorch fence. Legacy / and fenced formats stillwork. - Params: {name} placeholders fromkey=value args. Values are whitespace-split,so single-token only (msg=cos-torch-executor,not two words). An unresolved {name} skipsthat line. - Fail-fast: execution halts at thefirst errored command (🛑) so a faileddeploy never lets chronicle witness a day thatdid not ship. - Preview: ▲ torch <name>(dry-run). Ignite: add -i. ## Notes - ▲chronicle reads pulse cycle-state into thescroll but does not seal the pulse-{day}snapshot (that is the midnightrun_daily_tick). - Retiring a node: ▲ entomb<uuid> + clear citrine.repo_paths (mesh ops donot yet honor entombed alone).