REQUEST TO EVIDENCE01Ingress02Translation03Coherence04Transport05Persistence

SYSTEM VOCABULARY / PURPOSE + BOUNDARY

Terms define responsibility.

The same acronym can name a client contract, memory tier, network behavior, storage mechanism, or operational signal. Start with where a term appears in the request path, then inspect what it does and where its responsibility stops.

CONCEPT ATLAS / REQUEST TO EVIDENCE

Place the term before defining it.

Vocabulary becomes easier when every term is anchored to the stage where it changes the request, the bytes, or the proof.

01Ingress

TLS, API token, and HAProxy establish the service boundary.

Authorize
02Translation

OpenAI/OpenAPI requests become logical Coherence operations.

Normalize
03Coherence

Ownership, policy, and memory locality determine where work lives.

Place
04Transport

RoCEv2, RDMA, DPUs, and NVMe-oF carry registered data.

Move
05Persistence

Mirrored OpenZFS commits durable state and returns evidence.

Prove
Definition testWhat does it carry?Who owns it?What completes it?What can fail independently?Which signal proves its state?

61 terms visible

ControlSystem vocabulary

Coherence-CE

Oracle Coherence Community Edition

WHAT IT DOES

Acts as the actor-visible memory mesh for partition ownership, cache identity, placement, durability policy, and metrics.

WHERE IT STOPS

It is the contract firewall that hides lower-layer storage and fabric identity.

Read it in the architecture

This term governs logical identity, policy, or admission.

Locate this layer ->