hctl
humanctl
An attention router for a scarce human · humanctl
1 active asks · 1 waiting · 1 attached
Demo: choose the next loop step
What should the demo loop optimize for next?
Synthetic answered ask linked to a demo artifact for fixture coverage.
- Why now
- The fixture should show how an artifact-backed ask records a bounded answer.
- If ignored
- The fixture remains in an unresolved state.
Latest answer
Tighten the surface first
Polish the ask and artifact experience before adding channels.
ContextAttention router checkpoint
What I’m showing you
Attention router checkpoint
CLI-published demo artifact for the first real humanctl loop.
chief-of-staff demo artifact
Attention router checkpoint.
This is the kind of artifact an agent should be able to publish into humanctl before asking for a decision. The ask should then point at this exact surface instead of restating the whole thread.
local-first
artifact-backed asks
interrupt policy next
What this proves
- Agents can publish rich context without touching the app manually.
- The ask can stay tiny because the supporting artifact is already attached.
- The human sees one focused decision instead of a wall of reconstruction.
Decision wanted
- Is this artifact-forward loop the right wedge for the MVP?
- Should the next build step be notifications or richer artifact actions?
Other asks can wait
1 background watches
Presence-aware routing