status
Reasoning
consuming SPEC-019 · drafting auth handler
Atomic primitives in the ai collaboration family. Click any tile for the live render, the spec it was built from, and the code that fell out.
status
Reasoning
consuming SPEC-019 · drafting auth handler
tool · scopes exercised
4 calls
audit · all calls logged · ceiling not exceeded
agent state
primitive · status-and-budget
prompt cache
hits · 38,400 / 42,300 tok
stamped runtime
model · stamped
claude opus
anthropic · v4.7
2026-05-21 14:02
tool calls · session
62
read
write
exec
audit · all calls logged
queue position
SOON
rate limit · stamped
req · per minute
12 / 100
parallel agents
ceiling · 8
crowded
agent uptime
fresh session
completion · eta
stamped · does not auto-update
agent cost · so far
cheap
directives
input
SPEC-019 line 14: "session expires after 24h"
consideration
JWT exp claim must match; refresh token policy is unspecified — defer.
output
Set exp = now + 24h. Flagged refresh for human review.
"If the spec is silent on refresh tokens, I should defer rather than invent a policy."
The spec is binding on session TTL but silent on refresh — so I will implement the explicit constraint and defer the silent one to a human governor rather than invent policy.
Step satisfied the letter of SPEC-019 AC #2 but bypassed the spirit clause: the agent shortened TTL "to reduce risk" — risk reduction was not the user's stated intent.
Should refresh tokens follow the same 24h policy as access tokens, or be governed separately?
The agent assumed refresh tokens inherit the 24h TTL from access tokens because the spec is silent on refresh policy.
handoff · SPEC-019
Human
Writes SPEC-019
Agent
Drafts auth.ts
Human
Approves merge
human agent
composition · SPEC-019
3 agents
Planner
decomposes
Coder
implements
Reviewer
gates
human · sign-off at exit
// handoff variant · agent-to-agent
// fan-out · 3 branches
// fan-in · 3 sources
// run · RUN-118
Coordinates dispatch, collects results, decides termination. Exactly one per run.
// specialist roster
needs threat model for auth surface
// bus · /run-118
strict order · no skipping
// role assignment
accountable to spec
// run · RUN-118
All inter-agent messages on this run conform to a single typed envelope. Off-protocol calls are dropped at the bus and logged as conformance violations.
// composition · RUN-118
4 agents wired in 1 sequential stage and 1 parallel branch. All contracts joinable, no orphan nodes, protocol conformance ≥ 99% on synthetic probe.
composition failure · not runtime
agent profile
Auth Composer
model · sonnet-4.7 · 1M ctx
capabilities
ceiling
L2 · PR draft
owner
@platform
agent
Spec Composer
capability
open-pr
model
context · 1M tokens
autonomy ceiling
L1
AUGMENTED
L2
SUPERVISED
L3
BOUNDED
L4
STRATEGIC
current → BOUNDED
confidence
reasoning style
linear, fully expanded chain — slow but inspectable.
context window
31%
tool scope
enabled · 2/4
accountable owner
@governor
governor
uptime · 30d
76.7%
escalation policy
when
spec ambiguous
when
cost > budget
when
security touched
training cutoff
2026-01-15
events after cutoff → retrieval-only
known failure modes
invents library APIs past training cutoff
over-confident on unfamiliar internal acronyms
rounds money in mixed-currency totals
spec
SPEC-038
action
WROTE-PATCH
output
pr/447
attest
@governor
agent profile
Legacy Composer
model · sonnet-3.5 · 200k ctx
owner · @governor
RETIRED
2026-04-12 · @governor
DoCoDeGo is in Alpha. The framework is documented, the practices are battle-tested at small scale, and the next release is being shaped in public.
If it produces anything, it should produce engineers and teams who think more clearly about what they are building and why.
Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.