Operating notes · Note 02
May 2, 2026 · 7 min read
Agentic practice
Agentic

The agent
handover protocol

The hardening week named four files. One of them can be quoted. Three of them cannot. A handover written from memory of missing files would be fiction.

↓ Names, then the gap
01
The surface

Handover is a product
surface, not a vibe.

In the first week of March 2026, the Cursor bill for Steller’s pivot moved from execution into hardening. Built From the Rubble prices that week at $118 and calls it the agent protocol layer. The sentence in the essay names four files: AGENTS.md, QWEN_PROTOCOL.md, HANDOVER_TO_QWEN.md, and CHANGELOG_AI.md. It also names what that layer was for: guardrails, confirmation gates, session protocols, canonical port maps. The system, the essay says, became legible to machines.

The following week, March 9–14, is the $96 stabilisation week. Spend dropped. The essay says the system no longer needed the heavy architectural sessions, because Qwen could operate it from the docs. Bede, the Zain Sudan digital wallet, entered staging. That is the published picture of a handover: a named operator, a drop in session cost, and a first partner moving into staging.

A handover protocol is the surface the next agent meets. If the surface is only a chat transcript, the next session starts from zero. The rubble essay’s eighth rule says this directly: CHANGELOG_AI.md is the memory one agent passes to the next. Without it, every session starts from zero. Qwen Coder is described as the operator that reads AGENTS.md, runs tests before done, and logs what it changed.

Those sentences are the protocol as published. They are not the files.

02
The gap

Three names.
No bodies to quote.

I looked for the three protocol files under the names the essay uses. QWEN_PROTOCOL.md, HANDOVER_TO_QWEN.md, and CHANGELOG_AI.md were not there to quote. This essay will not reconstruct them. A plausible session script, a sample changelog entry, or a step list “in the spirit of” those files would be an invented document with a real filename on it.

Named in the $118 week
What this essay can do
AGENTS.md
Quote the router and the backend locks. They are Steller’s real files.
QWEN_PROTOCOL.md
Name only. Body missing. No steps invented.
HANDOVER_TO_QWEN.md
Name only. Body missing. No steps invented.
CHANGELOG_AI.md
Name only, plus the one-line role the essay gives it: session memory.

The honest handover, today, is the pair of AGENTS.md files plus the published essays. The root router is 63 lines and tells an agent which instruction source to open. The backend file is 121 lines of locks: CORS origins, Hangfire WorkerCount fixed at 2 for Bamboo, PlaceBambooOrderJob with no retry and a refund on failure, an Idempotency-Key on every Bamboo call, JWT_KEY from the environment, strict catalog validation, and RequireBusinessClaimsMiddleware never bypassed. steller-backend/AGENTS.md points at that same backend file.

If a later copy of the three missing files turns up, it can be quoted then. Until it does, “the protocol says” is not a sentence I get to write.

03
Principles only

What the essays
already committed to.

The principles of a handover are the eight rules in the rubble essay, not a private runbook. Keep the golden flow in one file. Name things so they can be grepped — the essay lists PlaceBambooOrderJob, ReconciliationJob, and SendWebhookJob as examples of searchable names. I am not describing those last two jobs; the essay only establishes that their names are greppable. Write AGENTS.md before the code. Make the wrong move unambiguously wrong. Use one deploy command, docker compose up -d. Treat docs as the codebase that gets read. Require test output before done. Log the change so the next agent is not blind.

The scorecard adds the operating claim that sits next to handover: once the docs exist, Qwen operates on about $5–15 a day. Expected daily Cursor and Qwen spend after the pivot, for routine operations, was about $15. A 95.2% cache hit rate is the published reason documentation compounds. Files written once are read across sessions. That is an economic fact about handover, not a description of a missing file’s table of contents.

The Complete Story draws the line the protocol has to respect. The AI did not rescue the platform. The architectural redesign made the platform rescuable by AI. A handover document that claims the model saved a microservices system the agents could not see would contradict the published account. What was handed over was a fat-controller path, Hangfire jobs with names, and a file that says where to start.

“The AI did not rescue the platform. The architectural redesign made the platform rescuable by AI.”
The Complete Story
04
Continuity

The loop that still
runs without those files.

Closed-loop CI is the continuity that does not depend on the missing protocol bodies. When the ask is to run until green, the root AGENTS.md requires this loop: trigger the workflow, poll until completion, pull failed-step logs and classify the failure, apply the smallest fix, re-run, and stop only when green or when access is actually missing. The tooling it names is gh workflow run, gh run list, and gh run view --log-failed, with edits going through a pull request. A repetitive version of that loop should be automation, not another request that a person paste logs.

Branch discipline, quoted from the same file: never push directly to main; feature branch, tests pass, pull request, merge, auto staging deploy. Production deploy and rollback are manual GitHub Actions operations with human approval. The backend file adds feat/... or fix/..., forbids git push origin main, and says the backend is pushed first, then the root submodule ref is updated. It also forbids deleting or recreating model, migration, or context files — and it names Order.cs, Brand.cs, ApplicationDbContext.cs, and any migration as stop-and-report cases. dotnet build Steller.sln must stay at zero errors. Test failures are fixed only in the test files the backend file names.

The smoke is a business check. After an environment change, config update, or restart, run ./scripts/smoke-staging.sh, and not before the readiness gate. The file’s example health probe is http://127.0.0.1:6091/api/health. Do not treat docker compose up -d success as application readiness. For partner onboarding the four calls are signup returning a partnerId, GET /api/wallet/me showing available balance equal to the trial credit and not 0, POST /api/orders returning 202, and GET /api/orders/{id} polled until Completed. An order is verified when that poll completes and the cards array is non-empty. Environment variables use a double underscore; the file’s syntax example is PartnerOnboarding__TrialCreditAmount=500, which this essay does not promote into a price. Those rules are how one session leaves a state the next session can trust, even while CHANGELOG_AI.md cannot be quoted.

Logging still matters. The essay says Qwen logs what it changed, and it names CHANGELOG_AI.md as that memory. I can require the behavior — a next session must be able to see what changed — without inventing the file’s format, headings, or retention. If the log is somewhere else now, that location is not in the record this essay is allowed to use.

Writing without inventing. Describe the rule, the command, and the published outcome. When the source is a filename without a body, say the body is missing. Do not fill the gap with a template.
05
Open questions

What a careful
handover still does not know.

These questions stay open because answering them would invent a fact.

  • What QWEN_PROTOCOL.md required of a session — gates, ports, tone, stop conditions — beyond the essay’s phrase “guardrails, confirmation gates, session protocols, canonical port maps.”
  • What HANDOVER_TO_QWEN.md listed as already done, still risky, or out of bounds.
  • Whether CHANGELOG_AI.md is still the log Qwen writes, or only the name the March essay used.
  • The day-by-day rebuild inside each weekly spend bucket. The published buckets are the $207 reckoning, the $163 execution, the $118 hardening, and the $96 stabilisation. Finer diary entries are not published.
  • Anything about a second host that could not be searched. Absence there is not evidence the files lived somewhere else.

Bede’s commercial terms are in the same category. The published fact is a first live integration: Bede, the digital wallet of Zain Sudan, moved from staging into an active API integration, and the platform’s stated partner path reaches a first successful API transaction in under sixty seconds. Terms, volumes, and revenue are not in this handover.

The practical protocol, stated only from the two AGENTS files and the published essays, is short. Read the root router and follow its scope map. Obey the backend locks. Do not push main. Run until green with gh workflow run, gh run list, and gh run view --log-failed. Smoke through signup, wallet, 202, and Completed, after the health probe, and check that the cards array is non-empty. Leave a log the next agent can read. Do not pretend QWEN_PROTOCOL.md, HANDOVER_TO_QWEN.md, or CHANGELOG_AI.md has been quoted. That is the handover the record supports.

Next in the series
Note 03 · Operating notes
What Zero Full-Time Developers Actually Requires
The architecture, the docs, and the human approval that remain.
Read the essay →