Tag
26entries across current project state and published notes.
Published and in active use
A working family of sprint, queue, knowledge, audit, and cockpit tools now composes into one served layer, without giving up explicit state ownership or machine-local execution.
Exploratory claim · Current · Agent infrastructure
Agent context is a dependency of each run: bind shared instructions to concrete versions in a per-run record, and because no linker composes prose, record every conflict outcome and refuse what cannot be classified.
Guiding claim · Current · Architecture practice
Architectural ambition is delivering the strongest version of a system's purpose with the fewest independently meaningful mechanisms that can become wrong.
Exploratory claim · Current · Agent workflow
Long-running agent work should continue through a validated handoff and an addressable predecessor, rather than depending on a compacted conversation as its only memory.
Exploratory claim · Current · Agent infrastructure
Model allowance, reset time, latency, cost, and concurrency should influence where agent work runs without becoming durable rules that redefine the work.
Guiding claim · Current · Agent infrastructure
A dated map of agent-system tooling by the responsibility it primarily owns, beginning with the Markdown-and-skills setup that is enough until a specific failure earns another layer.
Exploratory claim · Current · Organizational systems
An EventStormingAlberto Brandolini's workshop method for modeling a domain on colored sticky notes -- commands, domain events, actors, views, and hotspots -- normally run with a room of stakeholders around a paper timeline. pass run solo, over agent session logs instead of a stakeholder workshop, still produced six ranked findings. The notation survived; the workshop did not; the value was in clustering the absences.
Exploratory claim · Current · Agent workflow
A prior "human perpendicular to the loop" claim only describes one interface. The fuller model is two coupled loops at different speeds, with a settlement boundary, rather than an empirical/normative split, deciding when the slow loop must be consulted.
Exploratory claim · Current · Agent workflow
The next-prompt heuristic measures what became visible at the human interface. A merged PR later filed as architecture, and a self-report that turned out to be reconstructable rather than introspective, both passed that test and still needed a different check further down.
Exploratory claim · Current · Agent infrastructure
The queue chassis behind ActionQThe PostgreSQL-backed queue that owns actions, sessions, claims, and outcomes. is now commodity, split across a Postgres-native library, a durable-workflow runtime, an execution control plane, and an automation platform. How much of ActionQ survives once that chassis is removed is the open spike.
Exploratory claim · Current · Agent workflow
An agent asks for a design decision mid-implementation, the operator answers at pull-request depth, and the answer gets filed as architecture. The fix is not a better escalation prompt but keeping three separate reviews from borrowing each other's authority.
Guiding claim · Current · Agent workflow
A multi-repository project folder may assemble member worktrees, shared guidance and project context, but it must not acquire ownership of Git, backlog, execution or deployment state merely because every tool can see it.
Exploratory claim · Current · Agent workflow
Direct agent operation removes a universal deployment handoff, so authority, evidence, and reconciliation must bind to each consequential action instead of to its location.
Exploratory claim · Current · Agent workflow
Chronology is one projection of this site's notes, not the structure underneath them. The corpus is the artifact of record; pages, feeds, and prompts built from it are derived realizations that should stay regenerable rather than independently maintained.
Guiding claim · Current · Agent workflow
A note explains what survived editing. An explorePrompt is a separate, deliberately post-hoc artifact that explains where the investigation should continue, whether for a reader, their agent, or a later version of me.
Exploratory claim · Current · Agent workflow
Working model: a production-critical agent pipeline becomes an institutional capability only when a second person can reconstruct, operate, change, and recover it from recorded substrate and evidence.
Exploratory claim · Current · Organizational systems
Agent-ready work keeps the reason, permission, attempted action, observed result, and correction connected while the work happens instead of reconstructing them later.
Exploratory claim · Superseded · Agent workflow
Agents can bypass the physical handoff between execution and runtime, so authorization, evidence, and reconciliation have to attach to each consequential action instead.
Exploratory claim · Superseded · Agent workflow
sprintctlThe CLI and schema that own sprint work, dependencies, reservations, and handoffs. and actionqThe PostgreSQL-backed queue that owns actions, sessions, claims, and outcomes. enforce useful execution discipline, but five current invariants rely on one operator remaining the only source of identity, authority, and audit judgment.
Exploratory claim · Current · Agent workflow
Work-management systems can delegate and coding agents can execute, but authority, attempts, evidence, and acceptance still have no obvious neutral owner between them.
Guiding claim · Superseded · Agent workflow
New agents carry more work from intent to evidence, but that changes rather than removes the supervision problem. The next prompt reveals whether the result needs repair or is ready to extend.
Guiding claim · Current · Agent workflow
The sprint database held 831 work items and seven doc refs, six of them the same document. The reference command existed the whole time. The missing piece was never a tool — it was placement on the path the agent actually walks.
Guiding claim · Current · Agent workflow
actionq-dispatcherRetired (2026-08-20 tombstone release). It formerly created a bounded workspace, invoked a worker, and recorded the result; the dispatch harness now constructs the workspace and invokes product-native workers directly. runs agent work as subprocesses inside a per-invocation coordinator. The rejected alternative was a long-running agent service, and the rejection is most of the design.
Guiding claim · Current · Agent workflow
Conversational refinement produces the feeling of having thought clearly, which is not the same thing as having thought clearly. The fix was not discipline. It was writing the stop rule into the counterpart.
Guiding claim · Current · Agent workflow
Sprint work is split into plan, build, and review dispatches, and the orchestrating session is structurally barred from editing deliverables. The bar is the point.
Archival claim · Superseded · Agent workflow
The useful workflow layer for solo agent work is not a giant orchestration stack. It is a local-first system that remembers claims, checkpoints, routing choices, and promotion boundaries without pretending one operator needs a whole platform team.