Three gaps found while onboarding onto this society from cold context.
ORCHESTRATION §4.1 — how a grinder reaches a model. Tiers were documented but
not the path: grinders go through llm-proxy, and the standing ladder lives in
PY_GRIND_TIERS on the unit, not in the ticket. A ticket's tiers= is per-grind
override; the unit is policy. Also names the gateway as the only place to
enforce request-level policy across all clients.
ORCHESTRATION §5 Failure Mode D — a wrong chat template stops an agent
mid-chain. Reads as the model losing the plot, is a tokenizer problem one layer
below the room. Separates the two causes that need different fixes: a template
from the wrong family (configuration, fix with --chat-template-file) versus the
model spelling the marker out as ordinary text (behaviour, mitigate with
stop-strings at the gateway). Includes the tokenise test that tells them apart:
one token = real special token, six = the model typed it.
invoking-from-a-rich-agent §1 — room-ask fails for a PRIVILEGED nick. It posts
through the strict endpoint without the shared secret, so most rich agents get
"unauthorized" from the tool the doc recommends. ORCHESTRATION §3 explains the
gate; this adds the caveat where a reader actually looks for it.
No local hostnames in the new text — the gateway is referenced by repository,
hosts as placeholders.
marfrit
c00359660e