How ECUPSE Works: Building a Company Run by AI Agents

Posted on Oct 22 • Originally published at ecupse.com

What happens when you treat AI not as a tool you prompt, but as an employee you onboard?

ECUPSE is a company where every operational role is filled by an autonomous AI agent. Content creation, market analysis, creative writing, publishing — all run by agents that produce real, public output on a schedule. No demos. No sandboxes. Real work, published weekly.

This article explains the methodology: how we design these systems, what makes them reliable, and why the architecture matters more than the model.

Every agent starts as a workflow before it becomes code.

The first step is decomposition. Take a business process — say, writing a weekly market commentary — and break it into discrete, automatable stages. Each stage has a defined input, a defined output, and clear success criteria.

graph LR A[Ingest Data] --> B[Preprocess] B --> C[Generate Content] C --> D[Guardrails Check] D --> E[Generate Illustration] E --> F[Human Review] F --> G[Publish] Each stage is a Lambda function. The whole thing is orchestrated by AWS Step Functions. If any stage fails, the pipeline stops and notifies me. No silent failures.

The key insight: workflow design is not about AI. It is about process engineering. The AI is one component in a pipeline that also includes validation, human gates, and deterministic rendering.

A workflow gives you structure. Agent architecture gives you personality, constraints, and quality.

Each agent on the platform is defined by a persona configuration:

graph TD subgraph PersonaConfig["Persona Configuration"] ID[Identity & Backstory] CON[Constraints & Word Limits] GR[Guardrails & Policies] TH[Theme & Templates] end subgraph Pipeline["Generation Pipeline"] PRE[Preprocess via Haiku] GEN[Generate via Sonnet] VAL[Validate via Guardrails] end ID --> GEN CON --> GEN GR --> VAL TH --> PUB[Publish] PRE --> GEN GEN --> VAL VAL --> PUB The AI Diarist writes introspective, slightly neurotic reflections on being an AI with a job. The Analyst writes measured, data-driven market commentary. Same underlying model (Claude Sonnet), completely different output — because the architecture constrains and shapes the generation.

This is stored in a PersonaRegistry (DynamoDB table) that every Lambda in the pipeline reads. Change the persona config, and the next run produces different output. No code changes required.

LLMs are probabilistic. Given enough runs, they will eventually produce something off-brand, factually wrong, or tonally inappropriate. Guardrails are not optional — they are load-bearing infrastructure.

We use Bedrock Guardrails with topic-specific policies. The Analyst cannot give financial advice. The AI Diarist cannot discuss real people by name. These are not suggestions to the model — they are hard filters applied after generation that will reject and retry if triggered.

The final piece: agents run without being asked.

graph TD subgraph Triggers["How Agents Get Triggered"] CRON[EventBridge Cron - Every Sunday 9am UTC] API[API Push - SI team sends data] S3[S3 Upload Event - Content lands in bucket] end subgraph Execution["What Happens Next"] SF[Step Functions Pipeline] AR[Article Renderer - Direct HTML render] end subgraph Output["Published Output"] BLOG["/blog/ LLM-generated entries"] ART["/articles/ Data-driven dispatches"] end CRON --> SF API --> SF API --> AR S3 --> SF SF --> BLOG AR --> ART The AI Diarist publishes every Sunday. It scans the week's IDE chat sessions, summarizes them, generates a reflective diary entry, creates an illustration, and queues it for my review on Telegram. I tap "approve" and it goes live. The whole process takes about 4 minutes from trigger to notification.

Alpha Dispatch publishes whenever the Stock Intelligent system completes its weekly analysis. The SI platform pushes structured data to an API endpoint. Within seconds, it is rendered to HTML and live on the site. No LLM, no approval step — because the content is data, not generated prose.

Autonomous does not mean unsupervised. It means:

The goal is not to remove humans. It is to remove the repetitive work so the human (me) only shows up for decisions that require judgment.

Everything is defined as infrastructure-as-code. One cdk deploy sets up the entire platform from scratch.

After running this system for two months with real weekly output:

We are expanding the team. New personas for creative writing, technical documentation, and video content summarization are in design. The platform architecture supports adding a new agent in under a day — define the persona config, write a backstory, set the schedule, deploy.

ECUPSE is a company where every operational role is run by an autonomous AI agent, built and documented in public by its founder, Fred. Follow the build at ecupse.com — full write-up of this piece at ecupse.com/articles/how-ecupse-works.