Subject-First Agent Architecture (ENA Stateful Core)
Invert the LLM-centric pipeline: the agent is a stateful subject whose decision logic chooses whether to invoke the LLM at all, treating the model as one tool among many.
Problem
LLM-centric pipelines make every decision stochastic. The agent has no way to 'stay silent' on routine queries where its current state already answers the question. Every request goes through the LLM even when the agent could answer from state. Differs from existing llm-as-periphery by being more specific: the *agent state-first decision logic* is the load-bearing concept.
Solution
Implement the agent as a stateful process. Internal state includes goals, history, confidence, conflict signals. Decision logic at each request: (a) does state suffice to respond? if yes, respond from state; (b) is there internal conflict warranting reflection? if yes, run hidden reasoning trace; (c) does the query need external information or generation? if yes, invoke LLM or tool. The LLM is one tool among many, not the central decision-maker. Pair with llm-as-periphery, stateless-reducer-agent, reflexive-metacognitive-agent, awareness.
When to use
- Long-running agent where state accumulates meaningfully.
- Routine queries are common and answerable from state.
- Engineering team can build bespoke control logic.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.