Vol. I · for engineering teams
A book of working spells.
The risky parts of running software — restarts, log pulls, deploys — bound into short commands anyone on the team can cast from the terminal or Slack. Warded and audited, every time.
~/anywhere ▸ /scry why did checkout 5xx
✦ correlating datadog · cloudwatch · loki
✔ payments db pool exhausted @ 14:31
4 events · 812ms · scoped to team:oncall
i · Table of spells
№ 001–002
- Scry№ 001
Scry gives engineering teams real-time, agent-native observability: trace every tool call, replay runs, and debug agents from your terminal.
- Revivify№ 002
Revivify gives developers self-service restarts for the services they own, pre-permissioned by Spellbook so there's no wait and nothing infra didn't allow.
ii · What can you cast?
Roll back before anyone notices. Rotate the leaked secret. Scale it up before the launch. Tail the incident as it happens.
Dimmed deeds are pages not yet written.
iii · How the book works
01 · Cast
A person — or an agent — invokes a spell with one short command, from the terminal or Slack.
02 · Ward
Spellbook checks the caster's scopes and holds the credentials. Nobody gets standing access.
03 · Return
The result lands where it was cast, and every action is written to the audit trail.