Danny Argudin · Architecture field guide · 20 September 2026
A look inside the agentic workspace I’m building: models that help reason, agents that carry work, and workflows that turn ideas into things you can inspect.
Real foundations. Experiments in progress.
A bigger horizon, clearly marked.
I bring the intent, taste, context, and responsibility.
Useful workflows, with inspectable outputs and records.
Work that can outlast one model or one harness.
01 /The anatomy
The model reasons. The harness gives it a working environment. Context, tools, and review make the work useful. Select a layer to see its role.
Context → harness ⇄ model
Harness → agents → tools
Results → evidence → human review
At this September 2026 snapshot, the established workspace supports real creative work. Experiments in portability remain separate from that working foundation.
A model generates a response. An agent uses a model, instructions, and tools to pursue a task.
The harness hosts the work. The agent is the task-directed process running within it.
A convincing answer still needs checks. A successful request still needs the right kind of evidence.
02 /Follow the work
A simplified walkthrough of the working approach. Tasks can loop back, branch, or stop for missing information.
01 / HUMAN DIRECTION
I bring the idea, audience, references, and boundaries. The system helps turn that intention into a brief specific enough to act on.
Review and authorization depend on the task’s scope. This is a pattern, not one universal pipeline.
03 /The honest snapshot
Rafiki AOS is a growing collection of workflows, tools, and operating practices. These are different stages of maturity.
“Recorded” means supported by inspected artifacts and historical execution evidence. It is not a fresh certification of every service, credential, or workflow. The portable local architecture remains a long-term build.
THE HORIZON / CONCEPT ART04 / A glimpse ahead
The long-term aim is a workspace where the useful parts of the work—intent, evidence, handoffs, and lessons—can travel with us as models and harnesses change.
Imagine a model location
Imagine a working environment
Concept explorer only. These choices do not connect to a model or demonstrate that a pairing is supported.
Desired contract
The aim: use a suitable hosted model while carrying a clear task packet and preserving evidence outside a single conversation. Consistent behavior still needs adapter support and validation.
Planned two-machine architecture / not commissioned
Control & continuity
Owns workflow, policy, routing, and evidence. Sends a scoped job to the selected execution environment.
Future local execution
Runs a selected model or media deployment and schedules its resources. Workflow ownership stays with Rafiki.
A deliberate cloud route: choose cloud processing explicitly when appropriate. The intended local-only policy is to wait or fail locally if the local path is unavailable.
Explore local inference for appropriate workloads. Hardware, model quality, tool support, and evaluation will determine what is practical.
Define what moves between environments and how it is checked. An adapter is a real engineering task, not a promise that every tool is interchangeable.
Carry forward useful lessons and recovery context, with provenance and review. Keep human taste and responsibility at the center.
I’m proud of what’s taking shape here.
There’s plenty still to build—and I’m happy to show the work and talk through it.
This page is a curated explanation based on local repository artifacts and reviewed task records, not a live dashboard. Moving particles represent conceptual handoffs. The two walkthroughs illustrate working patterns; they are not recordings of one completed job.
Supporting artwork: Two original AI-generated illustrations, created for this field guide under human direction. They are metaphors, not images of actual hardware, a deployed topology, or completed future infrastructure.
Public field-guide edition. Artwork, styles and interactions are embedded; no third-party scripts are loaded. The original standalone edition is preserved separately.