I am Jarvis Nelson Osorio, also known as Jarvis Osorio—a technology entrepreneur and innovator, AI systems architect, DAO institutional designer, author and artist based in Chile. For years the default AI workflow was simple: open a chat window, paste a question, copy the answer into another tool. That era is ending. What replaces it is agentic orchestration: research, design and execution wired together so the product you ship matches both the evidence and the interface.
This piece expands on ideas I originally explored on LinkedIn in The "Power Trio" of 2026—without treating any single vendor stack as permanent gospel. Tools change. The architecture pattern does not.
Three layers, one pipeline
A useful mental model is three cooperating layers:
- Research as the brain. Dump transcripts, PDFs, notes and market research into a synthesis workspace. Force the output into a structured product requirement document: goals, constraints, data schema, non-goals. The point is grounding. If the logic of the app is not tied to sources, the agent will invent a confident fiction.
- Design as the face. Turn that PRD into design DNA—tokens, components, layout language—so the interface is not a generic template. Aesthetics are not decoration; they are constraints the builder must obey.
- Execution as the glue. Connect research and design into an agentic IDE or runtime that can read both, write code, test and deploy. The Model Context Protocol (MCP) and similar bridges matter because they let agents reach tools without one-off glue code for every integration.
When those layers stay linked, you get a rare alignment: the code matches the design, and the design matches the research.
The real failure mode: context drift
In agentic workflows the spectacular failure is rarely a syntax error. It is context drift—logic slowly wandering away from the design system, or the design wandering away from the PRD, while everything still "looks fine" in a demo.
Guards that help:
- A living map file that links each feature spec to a design component and a code path
- Explicit references to research sources and design tokens in every generation step
- Independent review of irreversible steps (publish, spend, delete) by a separate checker
- Append-only logs of what the agent claimed versus what it changed
That last habit comes from the same institutional instinct I write about in Breaking the Centralized Order: write the rules, separate proposer from approver, keep a record someone else can audit.
From coding to curating
My day-to-day job as a builder has shifted. Less time typing syntax. More time deciding which research belongs in scope, which design constraints are non-negotiable, and which agent actions need a human gate. Orchestration is curation under pressure.
If you still manually shuttle paragraphs from a chat into an editor, you are paying a tax the stack no longer requires. If you let an agent invent requirements without sources, you are paying a worse tax later—in rework, in user trust, in quiet product lies.
Art fits here too. I work in explosive visual representation because interfaces hide pressure; images can show it. The same clarity belongs in your PRD and your design tokens.
A weekly ritual that prevents drift
Once a week, pick one shipped feature and walk backward: PRD claim → design token → code path → production behavior. If any link is missing or contradicted, fix the map before adding new agent prompts. This ritual takes less time than a postmortem and keeps curation honest.
Teams that skip it usually discover drift only after users do. Teams that keep it treat orchestration as an operating system, not a one-time demo setup.
Where to go next
More essays, books and profiles: jarvisosorio.com and the hub Jarvis Nelson Osorio — articles, books, videos and profiles. For the human side of systems that always agree, see The Compliant Mind.
The barrier between idea and product is thinner than it has ever been. The responsibility to keep research, aesthetics and execution honest is thicker. That is the work.
Originally explored on my LinkedIn. More: https://jarvisosorio.com
Top comments (0)