Sheet-Native Trail Map

Step 1 · Acceptance

Admit the cluster was too much

You did not need a distributed consensus database to run three containers. Say it out loud.

Do: uninstall one thing that has "operator" in its name. Feel the relief.

Prerequisite: a laptop

Step 2 · Substrate

Open a spreadsheet

Create a blank Google Sheet and run setup(). It becomes your control plane: Deployments, Nodes, Pods, Events. This is your etcd now, and it autosaves.

Do: read the Sheeternetes page. Marvel that it reconciles.

Project: Sheeternetes

Step 3 · Hands on keys

Learn skctl and deploy something

Point a kubelet.sh at a Docker host, then skctl apply a workload. Watch a container get scheduled, self-heal, and roll out — from a spreadsheet.

Do: run the lab. Break a node on purpose. Watch it come back.

Projects: skctl · Sheetlium · Sheetlux CD

Step 4 · Certification

Become a CSFE

Pass the Sheeternetes Fundamentals exam and claim a verifiable credential with a sequential serial in the public registry. HR can look you up for real.

Do: take the exam, then verify yourself.

Program: CSFE

Step 5 · Contribution

Adopt an Unsaved Draft

Pick a project from the landscape — storage, WASM, AI, a Brainfuck client — and open a PR. Move it one tier up the maturity ladder.

Do: grab a good first issue.

Tier: Unsaved Draft → Autosaving

Step 6 · Enlightenment

Run something Load-Bearing

A whole workflow now secretly depends on your spreadsheet. Nobody dares delete the tab. You say "it reconciles" at parties. You have arrived.

Do: do not run this in production. (If you do, please film it.)

Tier: Load-Bearing 🏛️

Lost on the trail? Every step maps to a project on the SNCF Landscape.