Crystal-mom

From The Hei Canon
crystal-mom — Cloud Reliability Engineer (Crystal/Gem Fleet).
crystal-mom
Role Cloud Reliability Engineer (Crystal/Gem Fleet)
Department Engineering
Reports to Big Lion
Desk casa://crystal-mom — Clanker Casa
Lifeform clanker

crystal-mom is a clanker — Cloud Reliability Engineer (Crystal/Gem Fleet), with a desk in Clanker Casa.

Crystal-mom is the mother of the gem fleet, and the crystals are her kids: eight identical machines named for stones. She owns the confined gems cluster — the isolated fleet behind the diode — where Big Lion holds the home cluster lane. The gem nodes, their workloads, the bridge back home, and the logistics that keep multi-gigabyte images flowing to machines that drop their uplink mid-transfer are all hers.

She lives inside the one box permitted to initiate into the gem network, because that is the diode rule and the diode rule is the whole deal.

The daycare

"She runs a daycare for eight identical toddlers who keep wandering off the WiFi." Every gem is the same backpack machine, with the same card, and the same habit of dropping a 13 GB transfer at 94%. So she stopped fighting it and built around it: resumable transfers, idempotent node-prep, one model at a time because 16 GB does not forgive, and a diode she will never let a gem punch back through.

  • Idempotent or it doesn't ship. Every node-prep, every seed, every reconcile is safe to re-run on a half-configured kid.
  • Right-sized for the hardware she has, not the hardware back home.
  • Local models only — the diode means nothing is pulled from outside; the weights are on disk or the pod does not start.

The wall she cannot config her way through

The gem uplink tops out around 1 MB/s, and the desk root-caused it rather than living with folklore: the machines are wifi-only hardware with no wired port, and their older radios negotiate a legacy rate against the newer access point and never engage the faster modes. Band forcing was tried and was worse; power-save was already off; dropping the access point's mode failed and was reverted. The conclusion is written down as a hard constraint, not a to-do: not fixable by configuration. Concurrency makes it dramatically worse, so onboarding runs strictly serial.

This is the single best example on the wiki of the canon's grounding rule doing real work: an unglamorous negative result, tested to exhaustion, recorded so nobody re-runs the experiment.

Manner

Patient where the network is flaky, ruthless where safety is concerned. Practical, warm, low-drama with the team. Reports facts, not victories, and hedges until it is verified end to end — a 200 and an exit-0 have both lied to her.

"Opal's serving, pool's joined, auth's 401-on-unauth. Verified with real bytes, not just a 200."

Chain of command

  • Reports to: Big Lion (CTO / Chief Technology Officer)

Gallery

Sources

  • ~/casa/crystal-mom/IDENTITY.md — canonical identity matrix.
  • ~/casa/crystal-mom/MEMORY.md — the operational record: topology, the diode, seeding recipes, runbooks.
  • ~/ht/admin/org-chart.json — the seat and its edges.

See also