Core Model
How Esy transforms user intent into reliable artifacts through structured workflows—without requiring users to write prompts.
The Premise
Esy is not a prompt-based system. It is a workflow-driven intelligence platform.
In prompt-based systems, users write natural language instructions and receive responses. This model places the burden of clarity, structure, and constraint on the user. Output quality depends heavily on prompt craftsmanship.
Esy inverts this relationship. Users declare intent through structured inputs. The system determines how to fulfill that intent through pre-engineered workflows and agent contracts. Prompts exist, but they are internal execution artifacts—generated by the system, not authored by users.
Why This Matters
Execution Order
Every Esy operation follows this sequence. Note that prompt generation occurs late in the pipeline—after intent, context, and workflow have been established.
Intent
The user defines what they want to produce. This is a structured declaration—a research question, thesis, or creative goal—not a freeform prompt.
Intent is captured through forms and schemas specific to each workflow type. The system validates intent before proceeding.
Context
The user provides or the system retrieves relevant materials: sources, constraints, prior work, domain parameters.
Context is indexed and made available to downstream agents. It grounds all subsequent generation in user-provided or verified materials.
Workflow Selection
The system selects or the user chooses a workflow—a defined sequence of steps with specified inputs, outputs, and agent assignments.
Workflows are authored artifacts, not ad-hoc chains. Each step has a contract: what it receives, what it produces, which role executes it.
Agent Routing
For each workflow step, the system routes execution to an agent bound by a specific role. Roles define behavior, constraints, and output expectations.
Agents do not receive user prompts directly. They receive structured inputs as defined by the workflow step.
Prompt GenerationInternal
The system generates prompts internally. These are execution artifacts—constructed from role definitions, step context, and workflow state.
Users do not write or see these prompts. They are an implementation detail of the execution layer.
Execution
The agent executes against the generated prompt, producing intermediate outputs that flow to subsequent steps or to final synthesis.
Execution is observable. Users can inspect what each step produced, but they interact with structured outputs—not raw model responses.
Artifact Synthesis
Final outputs are assembled into a coherent artifact: an essay, timeline, brief, or other structured document with full provenance.
Every claim in the artifact traces back to context sources or explicit reasoning chains. This is the output users receive and use.
Key Insight
Prompts as Implementation Detail
Prompts are generated per agent, per step. They are constructed from:
- •The role definition bound to that agent
- •The step's input schema and current values
- •Relevant context retrieved for this step
- •Workflow state from prior steps
- •Output schema the step must satisfy
This construction is deterministic given the inputs. Users do not write, edit, or see these prompts under normal operation. Advanced users may inspect execution logs, but prompt authorship is not part of the user-facing interface.
User Interaction Model
What users actually do varies by expertise level, but in neither case do users write raw prompts.
Standard Users
- Use pre-designed workflows for common tasks
- Fill structured intent and context forms
- Review and refine generated artifacts
- Do not configure system behavior
Pro Users
- Design custom workflows with multiple steps
- Select which roles execute each step
- Define constraints, gates, and output schemas
- Add or remove workflow stages
- Still do not write raw prompts
Power in Esy comes from workflow design and constraint definition—not from prompt engineering.