RoboCoders

Selfware and project context

• Iron Trainer — Viktor’s personal training application: the recurring selfware exhibit.
• Iron Trainer architecture decisions — Project decisions and their rationale, kept alongside the implementation.
• ADR 0021: web UI information architecture — The architectural context behind the Today and Training Plan screens.
• Today-card implementation Bean — A work item connecting the UI decision to implementation and review.
• ADR 0020: backend replacement — The recorded decision to replace the FastAPI backend with Quarkus.
• Backend cutover Bean — Implementation work for the backend cutover and decommissioning.
• Documenting Architecture Decisions — Michael Nygard — The original lightweight ADR format: context, decision, status and consequences.
• Beans — A file-based issue tracker for people and coding agents, with work stored in the project.

Harnesses and agent coordination

• Herdr — A runtime for keeping coding-agent terminals and workspaces running.
• Paseo — An interface for running and coordinating coding agents from desktop and mobile.
• Paseo provider documentation — Provider integrations, including agents connected through ACP.
• Agent Client Protocol — The protocol connecting coding agents to clients.
• Claude Code agent teams — Separate sessions with shared tasks and direct teammate messaging.

Policy as software

• Baruch’s coding-policy — The shared engineering-policy plugin: rules, skills, scripts, hooks, review and team operation.
• Viktor’s coding-policy — Viktor’s adaptation of the engineering policy for his own workflow.
• Tessl — Tools for evaluating and distributing agent context.
• coding-policy in the Tessl registry — The distributed policy package and its published context artifacts.
• Agentic Context Registry — An experimental registry and packaging approach for versioned agent context.
• Context package manifest example — A concrete manifest grouping the parts of an agent context package.
• Context resolution and locking — How declared context dependencies resolve to concrete package evidence.
• Policy PR #376: release channels — The policy itself became a constraint; this change separated channel-specific publishing obligations.

Review loops

• Policy PR #380: persistent retrospectives — Preserving factory feedback before changing workers, with review discussion.
• Copilot’s review finding — The complementary reviewer’s finding in the retrospective change.
• Response with reproduction evidence — The author’s evidence-based response to the finding.
• Policy-aware Codex CI review — The workflow connecting the engineering policy to automated pull-request review.

Determinism and agent economics

• Script delegation rule — Encode known mechanics in scripts rather than re-inferring them for every run.
• Precheck gating — Skip agent invocation when deterministic checks establish that no work is needed.
• Worker allocation planner — Executable eligibility and allocation logic for the agent team.
• Shared-subscription-window test — Multiple worker names share one capacity pool; assignments account for that shared headroom.
• Headroom allocation test — A small fixture showing how projected remaining capacity affects assignment.
• Iron Trainer plan validator — A deterministic validator alongside model-generated training plans.
• Validator test example — Input, adjustment and assertion for an encoded plan rule.

Outer loops and factories building factories

• Port demo — The recorded Port demonstration used for the outer-loop example.
• Port — The agentic SDLC platform used for the shared organizational context and workflow examples.
• Port Context Lake — Modeled software and organizational context with explicit relationships.
• Port Workflows — Explicit workflow orchestration with agentic steps where reasoning is needed.
• Printf order API change — The code-change starting point for the fictional T-shirt company example.
• Printf documentation output — The merged documentation change produced in the demo scenario.
• Printf sizing guide — A public documentation artifact connected to the release.
• Printf factory-improvement issue — The recorded work item behind the workflow-building example.

Further reading

• The Goal — Eliyahu M. Goldratt and Jeff Cox — The Theory of Constraints novel behind the question: what limits useful results now?
• The art of loop engineering — LangChain — Further reading on nested execution, verification and orchestration loops.
• Software factories, light and dark — Addy Osmani — Further reading on software factories and ownership of the outer loop.

Optional public examples

• Calliope review example — A contributor’s keyboard-navigation fix, tests and review discussion.
• Calliope architecture reversal — A recorded architectural reversal with explicit tradeoffs.
• PopClip Summarize — Another personal utility, with on-device and API model paths.

Next talk

Spec-driven development continues in Anton Arhipov’s session at IntelliJ IDEA Conf 2026.