jonnify·bcs /bcs/overview/identity-as-contract

B0.2 · dive 2 of 3

Identity as a contract.

The name is not a string. It is a contract with four properties — typed, ordered, placed, conformant — each answering a way the bare integer handle failed.

The name and its four guarantees. Select a property.
typednamespace = the domain class orderedmint time = the sort key placedhash32 → 234878118 conformantone canon, five runtimes USR0KHTOWnGLuC the 14-byte name
readout · Select a property. The name carries the weight a type used to: typed by namespace, ordered by time, placed by hash, conformant across runtimes.
§1

The idea

echo_data · branded_id.ex

Because the name is the entire interface, it carries the weight a type used to. A branded identity is not a string; it is a contract with four properties, and each property answers a way the bare integer handle failed.

It is typed: the three-character namespace declares the domain class on the wire and to the type system, so a portfolio id cannot be passed where an order id is required. It is ordered: the name sorts as its mint instant sorts, so a table keyed by it is a timeline. It is placed: a single function, hash32, locates a row from the identity alone — placement(USR0KHTOWnGLuC) is 234878118, the same for every holder. And it is conformant: one source of truth and one vector file make encode and decode identical across five runtimes, so which language runs is a deployment detail.

These are not aspirations; the runtime asserts them at boot. The self-check compares the native and pure code paths against the contract’s vectors and refuses to start if they disagree. The name is trustworthy because the system proves it before trusting it.

echo_data · branded_id.ex · the vectors self_check! asserts at bootverified
placement(USR0KHTOWnGLuC)        →  234878118            native and pure agree
parse(USR0NgWEfAEJfs)            →  {:ok, "USR", 320636799581945856}
decode(USRzzzzzzzzzzz)           →  :error               an overflow is refused, not wrapped
§4

The doors

the sibling courses
/echomq

EchoMQ — the protocol, in depth

The bus B3 narrates, taught rung by rung: the keyspace, the Lua inventory, and the 3.0 Stream Tier — XADD, XREADGROUP, XACK — with conformance on Valkey.

 /redis-patterns

Redis Patterns Applied

The substrate patterns under the bus: sorted sets, atomic Lua moves, locks, and streams — the judgement layer.

 /echo-persistence

Echo Persistence — the durable floor

Beneath the volatile tiers: the Graft page engine built twice, the commit-LSN loop, and the stream archive on Tigris. Where Part I says state lives somewhere, this says where it lives durably.
§2

References

sources · related

Sources

Related