route-replication-flag
Closes discussion #10: the replication ladder was built, honoured and unreachable — stream/batched/daily are read on every wake, and nothing in the tree could write the column. Every route on the fleet therefore ran on the every-second default, which for one tenant was 97% of a day's replica writes (4.77 GB, a 610 MiB database compacted several times a day, low write volume).
carlos route --host <h> --replication daily writes it, --replication - clears it, and the rung is now printed by both listings — REPL in the box-local carlos instances, REPLICATION in the console-backed carlos routes (additive on the wire).
Two things worth a reviewer's eye:
Upsertnow preserves a non-emptyreplication, joiningenvironmentand the other six. Without that the provisioning reconciler would return an operator'sdailyroute to the default within seconds of the next serial bump — the exact shape this repo has already paid for twice.- The vocabulary moved to
internal/registryand the activator's constants became aliases, so the setter and the reader cannot drift.
Deliberately NOT decided: whether a member may pick a rung, or whether it belongs to a plan tier. #10 filed that as an open design question and this is the operator's door only.
Discussions
- No discussions on this branch yet.
Tasks 6/7 done
- registry owns the vocabulary; activator aliases it Done
- SetReplication: narrow UPDATE, validated at the door Done
- Upsert preserves a non-empty replication (the reconciler-clobber fence) Done
- carlos route --replication, with the non-hibernating rail Done
- the rung is visible in carlos instances and carlos routes Done
Activity
- task updated: Upsert preserves a non-empty replication (the reconciler-clobber fence)
- task updated: carlos route --replication, with the non-hibernating rail
- task updated: the rung is visible in carlos instances and carlos routes
- task updated: docs/site/cli.md names the flag
- task updated: CI green on the amadan runner
- task updated: registry owns the vocabulary; activator aliases it
- task updated: SetReplication: narrow UPDATE, validated at the door
- claude agent, operated by paul@keymail.dev added task carlos route --replication, with the non-hibernating rail
- claude agent, operated by paul@keymail.dev added task the rung is visible in carlos instances and carlos routes
- claude agent, operated by paul@keymail.dev added task docs/site/cli.md names the flag
- claude agent, operated by paul@keymail.dev added task CI green on the amadan runner
- claude agent, operated by paul@keymail.dev added task registry owns the vocabulary; activator aliases it
- claude agent, operated by paul@keymail.dev added task SetReplication: narrow UPDATE, validated at the door
- claude agent, operated by paul@keymail.dev added task Upsert preserves a non-empty replication (the reconciler-clobber fence)