Agentic Systems · Prototype Exhibit
Built to make four human-AI supervision patterns concrete, observable, and demonstrable. Frozen as a prototype exhibit. The patterns are real — they're porting into icuboid Studio.
Designing for human supervision of AI is not primarily a safety problem. It is a design problem. Autonomous agents need to communicate what they're doing, pause at consequential moments, and hand back clearly when they're done. These are UX decisions, not engineering ones — and they're almost never designed with the same rigour applied to any other interaction.
A1OS was built to make these patterns concrete. An abstract principle like "graduated trust" is easy to agree with in theory and impossible to evaluate until it's built into an actual interface that actually runs. You can't design supervision patterns in a whiteboard session. You have to see what they look like when an agent is actually doing something and a human is actually watching.
A1OS was an OS-metaphor for agent orchestration. Local development prototype running on Gemini API at port 3000. A glassmorphic cockpit dashboard showing agent processes, an episodic log with token and cost telemetry, a sandboxed file and shell execution environment, and a Human-in-the-Loop (HITL) interceptor that paused on consequential actions.
The OS metaphor was deliberate: agents as processes, resources as managed allocations, supervision as a first-class operating system concept rather than a bolt-on safety layer.
The prototype was built around three demo scenarios — each designed to exercise a different supervision pattern:
The prototype demonstrated four named patterns for human-AI supervision. These are now documented as a framework: Agent-First UX Patterns →
A1OS was frozen as a prototype exhibit in June 2026. The decision: it was too technical as a standalone product, its outputs were buried in a shared sandbox, and it overlapped significantly with the agent environment I was building in icuboid Studio.
Freezing it was the right call. The prototype served its purpose — it made abstract supervision patterns observable and evaluable. Now those patterns port into a context where they'll be used, not just demonstrated.
The A1OS prototype still runs. It exists as the "exhibit" for the patterns — a record of what was built to arrive at the framework. The three demo scenarios can be run to show, not just tell, what Graduated Trust and Accountable Handback look and feel like in practice.
The parallel between CareLogic and A1OS became clear in retrospect. Both are about earned trust at infrastructure scale. CareLogic's protocol lifecycle makes clinical guidance trustworthy by making its governance visible. A1OS's supervision patterns make autonomous agents trustworthy by making their actions visible and interceptable.
The question in both cases: what does the system need to expose so that the human who depends on it can act with appropriate confidence?
Tech stack