jonnify·echd /echd/bus/workshop/the-gap-declared

echd — Echo on Encore · E3.4 · dive

The Gap, Declared

Three primitives superseded, one declared — secrets stay platform-native, config-distribution is the nearest owned ground and is not secrets, and naming that boundary is what keeps the register credible.

Vision · real substrate

echd speaks in the present tense over a build ladder. Every module, verb, key, and port named on this page is real; the composition into one standing platform is the vision the ladder builds.

§1

The dive

docs/echo_mq/emq.streams.md:38-39 · echd.design.md §3

Every honest supersession story ends the same way: by naming what it did not supersede. The bus replaces three Encore primitives — PubSub with the stream tier, cron with the scheduler, task queues with claims — and this workshop has run two of the three by hand. The fourth thing a service reaches for, secrets, is not replaced, and the course says so in amber rather than letting the silence imply otherwise. Secrets need encryption at rest, an access policy, rotation, and an audit trail — a security surface the bus does not provide and does not pretend to.

The temptation is to point at the closest owned thing and call it enough. That closest thing is config-distribution: latest-value-per-key reads on the stream tier, changelog semantics without a compactor, genuinely useful for configuration and stream positions. The dive names it precisely so it cannot be mistaken for more than it is — it is config, not secrets; it has no encryption and no policy. Declaring the gap, and declaring the nearest ground as not the gap's answer, is the move that makes the other three supersessions believable.

§2

Three superseded, one declared

docs/echo_mq/emq.streams.md:38-39
Three superseded, one declared · the honest gap · hover to read
three superseded by hand, one declared — the honest gap PubSub → the stream tier cron → the scheduler (Repeat + the Pump) task queues → claims, fair lanes, batches secrets → the GAP · stays platform-native nearest owned ground: config-distribution (latest-value-per-key) — config, not secrets
Three, superseded. This chapter has replaced three Encore primitives with owned surfaces, and by now you have run two of them by hand: PubSub is the stream tier, cron is the scheduler, task queues are claims with fair lanes and batches. Each is real, and each is greener than what it replaced — retained, trackable, fair.
One, declared. Secrets are not superseded, and the workshop says so in amber. Secrets need encryption at rest, an access policy, rotation, and an audit trail — a security surface the bus does not provide and does not pretend to. It stays platform-native, and naming that boundary out loud is the point of this dive.
The nearest ground, named honestly. The closest owned thing to secrets is config-distribution — latest-value-per-key reads on the stream tier, changelog semantics without a compactor. It is genuinely useful for config and positions, and it is genuinely not secrets: no encryption, no policy. Calling it config, not secrets, is what keeps the register credible.

Hover or focus a row to read it; click to pin. Without scripting, all three read in sequence.

§3

Why secrets are the gap

docs/echo_mq/emq.streams.md:38-39 · echd.design.md §3

A secrets manager is not a queue with encryption bolted on; it is a different kind of thing. It provides encryption at rest, an access policy that decides who may read a value, rotation that retires a value and issues its replacement, and an audit trail of every access — a security posture the bus is not built to hold. The stream tier can move bytes reliably and keep them in order, but "reliable and ordered" is not "secret," and pretending otherwise would be the one dishonesty the vision register cannot survive.

So the dive draws the line where it actually is. Config-distribution — the latest-value-per-key reads the tier already offers — is the nearest owned ground, and it is the right tool for configuration, feature positions, and hydration. It is not a secrets store, and the course refuses to blur that. This is the honest-gap law in one concrete instance: a course that can point at exactly where its supersession stops is a course you can believe about everywhere it does not stop. The amber row is not an admission of weakness; it is the collateral that makes the three green rows worth trusting.

§4

The rule

one line to carry

The honest-gap rule — name the boundary you do not cross: secrets stay platform-native, and config-distribution is the nearest owned ground, which is not secrets. The declared gap is what makes the three supersessions believable — a register that can point at exactly where it stops is one you can trust about everywhere it does not.

§5

Doors

where the gap is drawn
§6

References

sources · related

Sources

  • Valkey — Streamsthe latest-value-per-key reads that config-distribution rides — config, not secrets

Related