Tasks
Signer · 11
Sign set
Dimension setnone
Humainary · Specification 3.15.3
Give software a shared language for what happens.
Serventis defines small vocabularies for reporting actions and results. A service reports a failed call. A lock reports a timed-out acquisition. A consumer can interpret both as degraded operation and bring them into one view. Each domain keeps its own vocabulary; consumers choose what to conclude from the reports.
40
Registry entries
237
Sign slots
161
Distinct lexemes
18
Sign families
51
Dimension slots
One service
Checkout reports each step as a sign from the Services vocabulary. It pairs each sign with CALLER to show its perspective. Together, they form a signal.
What a consumer receives, and the status it reads from each
A consumer subscribed to checkout reads each signal into a status. FAIL and EXPIRE read DEGRADED. Some observations support no conclusion: starting a call does not, by itself, tell us whether a service is operating well, so the consumer produces no status reading for CALL, and none for RETRY.
DEGRADED is itself a sign, from the Statuses vocabulary, so the consumer can report it for payments just as checkout reported the call. A second consumer weighs that status against the deployment: checkout depends on payments, and payments has read DEGRADED for ten minutes. It reports WARNING, from the Situations vocabulary.
A second domain
Inventory guards its stock records with a lock. When an acquisition waits too long, the lock reports TIMEOUT, from the Locks vocabulary. The consumer that read checkout’s FAIL reads TIMEOUT as DEGRADED too.
| Payments, from checkout | FAIL | → | DEGRADED |
| Stock lock | TIMEOUT | → | DEGRADED |
So payments and the stock lock appear side by side in one view, although Services and Locks share no words and the consumer holds no translation between them. Each domain needs one path up to Statuses, not a path to every other domain.
The reports themselves are unchanged. A consumer that needs to tell a failed call from a timed-out lock still has both signs, and can draw a different conclusion from them.
What you can build
Each consumer subscribes to reports and produces something of its own. The first two read the same checkout signals and come away with different answers.
An operational view
One status per subject, whatever its domain.
A diagnostic trail
The story of one request, step by step.
Agent oversight
Whether coordinating agents keep their promises.
The oversight consumer reads FULFILL as STABLE and BREACH as DEGRADED.
A first step
Reference · Scope
A working system involves three separable things. Only the first is normative, so the specification says only what is true of Serventis rather than of its first implementation.
Normative
The language
What a sign is, what a dimension is, that vocabularies are finite and fixed, that a signal is a qualified sign, that translation is partial, so some observations support no reading. Two implementations that disagree here are not implementing the same thing.
Documented
The policy
Which status a sign indicates, which episode role it takes, whether it reports an act or a result. These are judgments; a consumer that reads a sign differently holds a different opinion within the language, not a misunderstanding of it.
Per runtime
The affordances
Precomputed lookup, interned signal spaces, ordinal addressing. How one runtime makes the model cheap. Another language may find them wrong, so none is imposed.
| Conformance tier | Obligation | Entries |
|---|---|---|
| Universal | Required. Every projection provides all of them; without them a projection cannot take part in ascent. | 8 |
| Registered domain | Optional to provide, but fixed in membership, meanings and primary/derived classification once provided. | 32 |
| Projection-specific | Unconstrained in membership; must satisfy the design rules. | open |
A minimal conformant projection provides the observation model, the two set types, the two instrument protocols, the six universal vocabularies and both vocabulary templates.
A projection is an implementation of the specification in one programming language; Java is the reference projection. Projections preserve the registered vocabularies and their meanings across languages; consumers choose their interpretation policies.
Design principles
The observation model
An observation is atomic, a bare sign, or qualified: a sign together with a dimension, called a signal. Every observation exposes its sign, so a consumer that needs only the classification reads both alike.
One vocabulary, its whole signal space
Guards: four signs, two criterion dimensions, eight signals. The same sign under two dimensions is two different observations, which is what earns a dimension its place.
Dimensions are perspective, not location. Host, region, shard and tenant are properties of the subject and belong to its name, not to the observation.
Translation
No reading and UNKNOWN
No reading means the observation supports no conclusion in the target vocabulary. UNKNOWN is an explicit verdict: a determination was attempted but remained inconclusive. It belongs to Outcomes, not to Statuses.
Act or result
Every sign reports an operation, an act performed, or an outcome, a result observed. One outcome often supports a reading on its own; one operation rarely does. A sign with no reading of its own can still matter by its position in a sequence.
The readings in the opening sections come from the documented policy for Services and Locks. A consumer may adopt another policy and remain conformant.
Instruments and classification
Signer
Emits bare signs
For a vocabulary with no dimension set: Locks, Queues, Caches, Processes. 19 of the 32 domain vocabularies.
Signaler
Emits signals
For a vocabulary with a dimension set: Services, Leases, Messages, Evals. 13 of the 32.
An instrument exposes exactly one vocabulary and adds no runtime: it does not buffer, coalesce, reorder or accumulate. Emission, ordering, subscription and lifecycle belong to Substrates, the companion specification for circuits that carry values from emitters to subscribers in a guaranteed order. Serventis presupposes it and never reinterprets it; Substrates knows nothing of Serventis.
Primary
A lock reports TIMEOUT
It received the unsuccessful result of its blocking acquisition and reports that result directly. Every component of every observation is chosen from a current act or result.
Derived
A timer reports MISS
It received an elapsed duration and a configured threshold, and had to compare them to choose between MEET and MISS. One derived component makes the whole vocabulary derived.
The boundary is who performs the work. If the mechanism observed has already compared or measured and hands the result over, reporting it is direct observation. The names alone do not reveal the difference.
Universal vocabularies · Required
Six shared vocabularies and two templates. Statuses and Situations are the readings and interpretations every domain ascends into; Operations, Outcomes, Systems and Trends are shared signs any domain can be read through. Every projection provides all eight, in every language.
Statuses
7 × 3 · derived
The operational reading, offered with a stated confidence and read from domain signs. Not an HTTP status, not an exit code, not a state machine’s state.
Situations
3 × 3 · derived
The situational interpretation: what a state of things means for action. Not an incident, an alert or a page: what to do about it is somebody else’s decision.
Operations
3 · primary
Episode roles, witnessed as they happen. Not a method call or a unit of work.
Outcomes
3 · primary
Verdicts, witnessed as they are reached. UNKNOWN is a verdict; no reading is not one.
Systems
4 × 4 · derived
Pressure against a limit, by the class of limit: room, throughput, connectivity or time.
CategorySPACE · FLOW · LINK · TIME
Trends
5 · derived
The shape of a series, read from history rather than from one moment.
Surveys
template × 3
Agreement among observers. Fixes the dimension set; the caller supplies the sign set.
Cycles
template × 3
How a sign recurred in the stream: first time, again at once, or back after others.
CategorySINGLE · REPEAT · RETURN
The catalog · 32 domains
A domain describes one kind of subject — a lock, a pool, a conversation — in a finite sign set of its own, with a dimension set only where the same sign genuinely means something different from each side.
Each domain is optional to provide and fixed once provided: ship none, or ship Locks with exactly its registered signs. A projection that ships a registered domain, in any language, is legible to every consumer written against it anywhere.
Each domain shows its instrument and shape, its sign set in registry order, and its dimension set where it has one, named by dimension family. All dimension sets here are categories. Unmarked domains are primary.
Execution
6 domains
Signer · 11
Sign set
Dimension setnone
Signaler · 16 × 2
Sign set
Dimension set · PerspectiveCALLER · CALLEE
Signer · 9
Sign set
Dimension setnone
Signaler · 8 × 2
Sign set
Dimension set · PerspectiveCOORDINATOR · PARTICIPANT
Signaler · 2 × 2
Derived
Sign set
Dimension set · Reference pointDEADLINE · THRESHOLD
Signer · 6
Sign set
Dimension setnone
Synchronization
3 domains
Signer · 10
Sign set
Dimension setnone
Signer · 6
Sign set
Dimension setnone
Signer · 8
Sign set
Dimension setnone
Pooling
4 domains
Signer · 6
Sign set
Dimension setnone
Signaler · 9 × 2
Sign set
Dimension set · PerspectiveLESSOR · LESSEE
Signer · 4
Sign set
Dimension setnone
Signaler · 2 × 2
Sign set
Dimension set · PerspectivePROVIDER · RECEIVER
Data
5 domains
Signer · 4
Sign set
Dimension setnone
Signer · 4
Sign set
Dimension setnone
Signer · 7
Sign set
Dimension setnone
Signer · 12
Derived
Sign set
Dimension setnone
Signaler · 7 × 3
Sign set
Dimension set · PerspectivePRODUCER · BROKER · CONSUMER
Flow control
5 domains
Signaler · 2 × 3
Sign set
Dimension set · StageINGRESS · TRANSIT · EGRESS
Signer · 9
Derived
Sign set
Dimension setnone
Signer · 6
Sign set
Dimension setnone
Signer · 6
Sign set
Dimension setnone
Signaler · 4 × 2
Sign set
Dimension set · CriterionIDENTITY · PERMISSION
Instrumentation
6 domains
Signer · 3
Sign set
Dimension setnone
Signer · 5
Sign set
Dimension setnone
Signaler · 6 × 2
Sign set
Dimension set · PerspectiveOUTBOUND · INBOUND
Signaler · 3 × 3
Derived
Sign set
Dimension set · Reference pointBASELINE · THRESHOLD · TARGET
Signer · 4
Derived
Sign set
Dimension setnone
Signaler · 5 × 8
Derived
Sign set
Dimension set · CriterionCORRECTNESS · COMPLETENESS · GROUNDEDNESS · HELPFULNESS · ADHERENCE · TOOLING · ROUTING · SAFETY
Coordination
3 domains
Signaler · 10 × 2
Sign set
Dimension set · PerspectivePROMISER · PROMISEE
Signer · 11
Sign set
Dimension setnone
Signaler · 7 × 2
Sign set
Dimension set · PerspectiveSELF · PEER
Shape is signs, or signs × dimensions. Membership, meanings and primary/derived classification are normative; each entry is addressed as registry:<name>, and an entry is never renamed, because a rename would be a different vocabulary.
Cross-reference · Sign families
Read across the domains above, a sign family groups the lexemes that answer the same kind of question about a subject. Membership is assigned per slot, one sign in one vocabulary, so every slot belongs to exactly one family.
01
18 · 32
Requesting, holding and giving up a scarce thing. The most reused family: a request that may be refused, opened by an attempt, decided by a grant or denial, closed by a release.
Drawn on byAtomics, Latches, Leases, Locks, Pools, Resources
02
9 · 15
The existence and running state of a long-lived subject: creation, running, stopping, destruction and the suspensions between. About a thing that exists, where Work is about a job that completes.
Drawn on byProcesses, Services, Tasks
03
11 · 14
A unit of work moving through its stages: submitted, scheduled, started, progressing, finished one way or another.
Drawn on byChanges, Services, Tasks, Transactions
04
5 · 6
Bracketing as such: the universal Operations vocabulary and the domain signs that exist purely to open or stage an episode. Small by design; most bracketing is read from domain signs by their structure.
Drawn on byChanges, Operations, Transactions
05
19 · 30
Results: what an operation decided, observed or produced. Rich in domain synonyms for success and failure, deliberately, because a vocabulary reads better when its verdict is named in its own terms.
Drawn on byAgents, Atomics, Caches, Changes, Evals, Flows, Messages, Outcomes, Probes, Services, Timers, Transactions
06
11 · 14
Letting something through, or not. A decision made about incoming work by a gatekeeper, where a verdict is made about completed work by whoever did it.
Drawn on byChanges, Guards, Pipelines, Routers, Services, Valves
07
6 · 13
Capacity limits reached. Its signature is a symmetric pair, OVERFLOW and UNDERFLOW, wherever a container has two ends it can run out of.
Drawn on byAtomics, Counters, Gauges, Messages, Pipelines, Queues, Stacks, Systems
08
3 · 5
Capacity changing size. EXPAND and CONTRACT are the pair; DRAIN is the emptying case.
Drawn on byPools, Valves
09
6 · 6
Competing for progress: what a subject does while it cannot proceed. Directly observed actions and results, not an inferred judgment that it was slow.
Drawn on byAtomics, Locks, Transactions
10
17 · 19
Moving something from one place to another. Network transport and in-process container movement share a family because the observable shape is the same.
Drawn on byExchanges, Messages, Pipelines, Probes, Queues, Routers, Services, Stacks
11
6 · 7
Keeping something and finding it again. The characteristic sequence is a LOOKUP followed by a HIT or a MISS.
Drawn on byCaches, Messages, Pipelines
12
11 · 12
Returning to normal after something went wrong. The breaker’s TRIP, OPEN, HALF_OPEN, PROBE, CLOSE cycle is its most complete expression.
Drawn on byBreakers, Latches, Messages, Services, Transactions
13
4 · 4
Damage and disorder in what was moved or stored, and the bookkeeping kept against them.
Drawn on byPipelines, Routers
14
3 · 5
Numeric movement without a subject to speak of. The narrowest family, and the one closest to conventional metrics.
Drawn on byCounters, Gauges
15
22 · 25
Readings rather than events: a conclusion about how things are. Home of the universal ascent targets, and derived in its entirety, because inference is what produces its signs.
Drawn on byLogs, Sensors, Situations, Statuses, Systems, Trends
16
19 · 20
Communicative moves between parties: asking, disagreeing, promising, offering, accepting, retracting. The utterance is the event.
Drawn on byActors, Agents, Exchanges
17
3 · 3
Working on data already in hand. Transport moves it, Storage keeps it, Admission decides whether it passes, and Processing changes it.
Drawn on byPipelines, Probes
18
7 · 7
Belonging to a group and holding a role in it: joining and leaving, suspicion and its refutation or eviction, election and resignation. The group’s view of its members.
Drawn on byMembers
Counts are lexemes · slots. Families are an organising lens over the registry, not a structure the specification defines: they give vocabulary reuse something concrete to reuse from.
Cross-family lexemes
A sign has no meaning outside its set, so a consumer resolves every sign against the vocabulary that produced it. The registry renames nothing; it lists the cases so nobody builds a cross-vocabulary lexeme table by accident.
ATTEMPT
Acquisitiontry to take a held thing (Atomics, Locks, Resources)
Admissionpresent a credential or request at a gate (Guards)
CONTRACT
Elasticityshrink capacity (Pools, Valves)
Speech actcommit to terms (Exchanges)
DELIVER
Speech actpresent completed work (Actors)
Transporthand a message to a receiver (Messages)
DENY
Acquisitionrefuse a request for a held thing (Leases, Locks, Resources)
Admissionrefuse entry at a gate (Guards, Valves)
Speech actdisagree with a proposition (Actors)
EVICT
Storageremove an entry for capacity or policy (Caches)
Membershipremove a member declared failed (Members)
EXPIRE
Acquisitiona lease’s term ran out (Leases)
Workthe work outlived its deadline (Services, Transactions)
Storagea held item outlived its time to live (Caches, Messages)
FAIL
Verdictthe result was failure (Atomics, Changes, Evals, Flows, Outcomes, Probes, Services)
Lifecyclethe process died (Processes)
Workthe job did not complete (Tasks)
GRANT
Acquisitionhand over a held thing (Leases, Locks, Resources)
Admissionlet a caller through a gate (Guards)
PASS
Admissionallowed through (Valves)
Verdictsatisfied the criterion (Evals)
PROBE
Acquisitioncheck a lease is still valid (Leases)
Recoverya trial request testing whether recovery is safe (Breakers)
REJECT
Admissionrefused at submission (Changes, Services)
Workthe job was not accepted (Tasks)
RESET
Countingreturn a counter to zero (Counters, Gauges)
Recoveryreturn a mechanism to its initial state (Breakers, Latches)
SKIP
Admissionan element was passed over (Pipelines)
Verdictthe criterion was deliberately not evaluated (Evals)
START
Lifecyclethe subject began running (Processes, Services)
Workthe job began executing (Tasks)
Episodean episode opened (Changes, Transactions)
TIMEOUT
Acquisitionthe wait for a held thing expired (Latches, Locks, Resources)
Workthe job exceeded its budget (Tasks)
FAIL in Atomics is a compare-and-swap that will be retried. FAIL in Processes is terminal. Same word, different structure behind it.
Dimension families
A dimension is warranted only when the same sign genuinely means something different under each member. A queue enqueues, and there is no second viewpoint on that.
Perspective category
Which party to an interaction is reporting. The same event seen from both ends yields two signals that differ only in dimension, which is exactly what reveals a disagreement between the parties.
| Vocabulary | The ends |
|---|---|
| Services | CALLER · CALLEE |
| Agents | PROMISER · PROMISEE |
| Transactions | COORDINATOR · PARTICIPANT |
| Leases | LESSOR · LESSEE |
| Exchanges | PROVIDER · RECEIVER |
| Probes | OUTBOUND · INBOUND |
| Messages | PRODUCER · BROKER · CONSUMER |
| Members | SELF · PEER |
| Family | Vocabulary | Members |
|---|---|---|
| Stage | Flows | INGRESS · TRANSIT · EGRESS |
| Constraint kind | Systems | SPACE · FLOW · LINK · TIME |
| Reference point | Timers | DEADLINE · THRESHOLD |
| Sensors | BASELINE · THRESHOLD · TARGET | |
| Criterion | Evals | CORRECTNESS · COMPLETENESS · GROUNDEDNESS · HELPFULNESS · ADHERENCE · TOOLING · ROUTING · SAFETY |
| Guards | IDENTITY · PERMISSION | |
| Recurrence | Cycles | SINGLE · REPEAT · RETURN |
THRESHOLD in Timers and THRESHOLD in Sensors intend the same thing, and remain two distinct dimensions that must never be unified.
Three spectra: confidence, consensus and variability
Statuses · confidence
How strong the evidence for a reading is.
Surveys · consensus
How far independent observers agree.
Situations · variability
How much the condition itself fluctuates. A volatile condition can still be assessed with confidence.
Designing a vocabulary
Shapes that recur across vocabularies
Request, then outcome
Start, run, terminal
Symmetric pairs
Time against a limit