docs(features): split the response inventory by topic #512

Merged

coilyco-ops merged 1 commit from eng/split-the-response-inventory into main

2026-08-13 14:52:43 +00:00

coilyco-ops commented

2026-08-13 14:49:43 +00:00

Member

Two cuts, both by subject

features-observability.md takes what the service reports about itself: OTel ingress and joined traces, trace-correlated metadata logs, the metric families, liveness and readiness, the gateway heartbeat, and the caller/service fault split.

features-admission.md takes who may reach it: invocation gates, summoning by edit, the access policy, and the admission tiers.

That leaves the response-service file as one subject — how a turn is run, checked and answered — at 3312 characters. Telemetry is where six entries arrived in the last day, so it is the growth that most needed somewhere to go.

One cut would have met the acceptance and left 293 characters, which at the current rate is about a day. Two leaves each file with real room.

A stale number, replaced with the property

The inventory said "23 bounded SigNoZ exception groups". The catalog now holds 29 distinct outcomes across 32 codes — six of which I added today, so I am the reason it drifted.

I did not write 29 in its place. An untested count in prose drifts again on the next code, and this one already had. It now names the property instead: a build-time closed catalog tagged by stage, outcome, and fault. That is what the number was standing in for, and unlike the number it stays true.

Restored

The reply-assembly entry that was reverted when the cap refused it, in its author's wording, now that #413 has landed at c71f1ff.

closes #471

The inventory was 42 characters from its 4000-character cap, so the next shipped capability could not be recorded and the cheapest response for each agent was to skip the inventory. A few rounds of that and it stops being an inventory while still reading like one. ## Two cuts, both by subject **`features-observability.md`** takes what the service reports about itself: OTel ingress and joined traces, trace-correlated metadata logs, the metric families, liveness and readiness, the gateway heartbeat, and the caller/service fault split. **`features-admission.md`** takes who may reach it: invocation gates, summoning by edit, the access policy, and the admission tiers. That leaves the response-service file as one subject — how a turn is run, checked and answered — at 3312 characters. Telemetry is where six entries arrived in the last day, so it is the growth that most needed somewhere to go. One cut would have met the acceptance and left 293 characters, which at the current rate is about a day. Two leaves each file with real room. ## A stale number, replaced with the property The inventory said "23 bounded SigNoZ exception groups". The catalog now holds **29 distinct outcomes across 32 codes** — six of which I added today, so I am the reason it drifted. I did not write 29 in its place. An untested count in prose drifts again on the next code, and this one already had. It now names the property instead: a build-time closed catalog tagged by stage, outcome, and fault. That is what the number was standing in for, and unlike the number it stays true. ## Restored The reply-assembly entry that was reverted when the cap refused it, in its author's wording, now that #413 has landed at `c71f1ff`. closes #471

coilyco-ops added 1 commit

2026-08-13 14:49:43 +00:00

docs(features): split the response inventory by topic

ci / image-build (pull_request) Successful in 29s

Details

ci / test (pull_request) Successful in 44s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

e042a09969

The response-service inventory was 42 characters from its 4000-character
cap, so the next shipped capability could not be recorded in it and the
cheapest response for each agent was to skip the inventory. A few rounds
of that and it stops being an inventory while still reading like one.

Two cuts, both by subject. What the service reports about itself moves to
features-observability.md, and who may reach it moves to
features-admission.md. Telemetry is where six entries arrived in the last
day, so it is the growth that needed somewhere to go.

Restores the reply-assembly entry reverted when the cap refused it.

The exception-group count was stale: the inventory said 23 and the
catalog holds 29 distinct outcomes across 32 codes. Replaced with the
property rather than a fresh number, since an untested count in prose
drifts again the next time a code is added.

closes #471

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-13 14:49:43 +00:00

coilyco-ops merged commit 791376c497 into main

2026-08-13 14:52:43 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 14:52:44 +00:00

Merge pull request 'docs(features): split the response inventory by topic' (#512) from eng/split-the-response-inventory into main