Separate agent state from work state
An available process is not the same as a completed task. Making that distinction visible improves the quality of oversight and the next decision.
Lead the work, not just the prompt.
A fleet operations product for people leading named agents across projects, teams and locations.
Visit project ↗The problem worth solving.
Once several agents work together, coordination becomes a product problem. Who owns the task? Which run is active? What is blocked? Where does a human decision belong? SkiaFleet turns that operational context into something people can see and manage.
My role
I build the product and the harnesses around it: defining the operating model, designing the coordination experience and developing the platform foundations. The work combines product decisions with execution safety, recovery and a practical review loop.
SkiaFleet
How the pieces fit.
Explore the responsibilities and the boundaries between them.
System relationshipsSelect a node to explore
Shared boundary
Claims · Generation fencing · Approval · Durable recovery
Responsibility
Ownership and decisions
Coordinate the work
Responsibility
Tasks, context, tools
Make execution visible
Responsibility
Results, review, next action
In focus
People lead
A fleet operations product for people leading named agents across projects, teams and locations.
Separate agent state from work state
An available process is not the same as a completed task. Making that distinction visible improves the quality of oversight and the next decision.
Conceptual architecture drawn from the project’s responsibilities and design decisions. Arrows show relationships, not an execution trace.
Decisions that shape the system.
Treat approval as a boundary
Approval needs the proposed action, relevant context and a consequence a person can understand. It cannot be just a decorative confirmation button.
Design the second attempt
Claims and generation fencing address competing or stale execution. Recovery and retained context help the system resume useful work after interruption.
Agent operations is an exercise in making authority, ownership and progress legible. The interface and the harness have to agree.