Quanta · the factory’s first primitive · ceiling walk · for red-pen

The Teammate Journey

Every moment a teammate sees, graded against the best version of that moment. The trust bones are first-class already — the gaps are voice, one name, and two missing moments of warmth. Eight small fixes, four calls that are yours.

Walked 2026-07-23 from live receipts · 0 beats below floor · awaiting Robert’s red-pen on 4 calls

Every quote below is the real, current text a teammate sees — captured this morning from a live install and tonight's fleet logs. Each beat is graded against the ceiling: the best version of that moment. Verdict language: AT CEILING · BELOW — flip-worthy, gap filed · MISSING.

Where it already feels first-class

  1. The install — AT CEILING. One command, and it answers like a product: 
    ✓ Node v25.6.1
✓ GitHub access confirmed
… downloading quanta (this takes ~a minute)
✓ quanta 0.1.0 installed and verified.
    Plain checks, honest wait note, verifies itself. One filed line: close with “You’re done on this machine, forever. Everything else is automatic.” — seal the contract at the moment they feel it.
  2. The proof — AT CEILING. quanta --version → two lines, and the second (native bindings: ok) is a real health check, not a banner. Terse and true.
  3. The doctor — NEAR CEILING. Six plain lines, one glance = whole story; “nothing shed yet — sheds on your first Claude session” is exactly the right voice. Two labels still speak our dialect (GATE-MINTING, “deposit-on-verify wrapper”) — filed for the plain-words pass: “YOUR CHECKS BANK PROOF.”
  4. Their gate afterward — AT CEILING. One quiet line on success, one honest line on failure, never fails their build. Quiet is the feature.

Where it breaks character

  1. The first-repo moment — BELOW CEILING: it answers in a different name. A teammate runs a quanta command and gets: 
    PLATO PRIME (session-start) — PLATO map @ 49609273…
MAP: 776 files / 1764 wires, 76 orphan(s)
   (blind: incomplete…) … 606 I cannot certify…
    Two breaks at once: the product speaks a different name, and the text is written for the agent, shown to the human. (It IS agent-priming text — right content, wrong audience at this moment.) Ceiling: the human gets one line in the product’s own voice — “This repo is on the grid — your work here leaves a verifiable trail” — and the machinery stays for the machines.
  2. The arriving PR — BELOW CEILING: the biggest gap. The factory’s introduction inside their repo currently opens: chore(genome): join the quanta ledger — Level 2 (regenerated, current-gen wrapper + CI banking), body full of rungs and wrappers. This is the highest-leverage moment in the whole journey and it reads like a chore. Candidate rewrite for your red-pen:
    Your repo now leaves proof behind.
    When your checks pass, this records a receipt — verifiable by anyone, stored beside your code, never in your way. It can never fail your build, never touches your branches, adds nothing you maintain.
    What to do: merge when ready. That’s it — everything after is automatic.
    ▾ machinery for the curious (collapsed)
  3. The refusals — NEAR CEILING structurally, wrong dialect. When it can’t safely wire a repo it says so and stops — the honesty is the product — but in internal words (CANNOT-CERTIFY (axis: module-exec)). Filed: same honesty, their words: “I can’t safely wire this repo automatically — its checks run in a shape I can’t verify. Here’s the guide, or ping Robert.”

What’s missing entirely

  1. The invitation. No one-breath pitch exists — the doc is good, but nobody falls in love with a doc. Filed: the Slack-sized paragraph (what you get · the one command · “everything else is automatic”), drafted for your voice pass.
  2. The arrival moment. Nothing ever tells a teammate you’re now part of something. No “you’re on the grid.” The trust bones are all there; the warmth beat was never written. Candidates: a comment on their merged onboarding PR (“Your repo is on the grid — its first receipt banks on the next green run”), a doctor line (FLEET: registered ✓ — visible on the map), or both.
The scoreboard: 3 beats at ceiling · 2 near (word-level) · 2 below (the character break, the arriving PR) · 2 missing (invitation, arrival) · 0 below floor. The honesty architecture is first-class everywhere already — every gap is voice, name, or a missing moment of warmth. One focused polish session closes all eight filed items.

Your four calls

1 · The one name.

Does quanta own every surface a teammate sees, with “plato” retired to agent-internal machinery? (My rec: yes — a first-class product never breaks character.)

2 · The PR’s voice.

Red-pen the candidate body above — it’s the factory introducing itself in someone’s home repo, so the words should be yours.

3 · The arrival moment.

Where does “you’re on the grid” live — the merged-PR comment, the doctor line, or both? And how loud?

4 · Updates.

A nudge when their install is stale (my rec — human stays in the loop), or silent auto-update?

Canonical source: docs/ai/WALK-teammate-journey-firstclass.md (receipts, filed work W1–W8, verdicts per the ratified ceiling-walk machinery). React here or in chat — both count.