PAGE 04AUTOMATION

Automation.

Processes that run without depending on anyone remembering to execute.

S
AGENT-01
Strategos
STRATEGY · DECISION
C
AGENT-02
Contento
CONTENT · LANGUAGE
M
AGENT-03
Métrikos
DATA · BI · ANALYSIS
N
AGENT-04
Nexo
AUTOMATIONS · FLOW
SECTION 5.0DESIGN PRINCIPLES

What governs
every decision.

01
P-01 · FUNDAÇÃO

Process before tool

Automating a bad process just produces a bad process faster. We map the current human flow and identify bottlenecks before writing a single line of workflow.

02
P-02 · CONTROLE

Supervision, not abdication

AI executes, the human decides what matters. Every automation has defined checkpoints where the system stops and waits for approval. No agent acts alone on high-risk decisions.

03
P-03 · VISIBILIDADE

Total observability

If you can't see what the system did, it isn't automation; it's hope. Structured logs, proactive alerts, health dashboards. No black box.

04
P-04 · EVOLUÇÃO

Continuous iteration

Version 1 is a starting point, not a final delivery. The system learns from errors and expands coverage over time. Automation is a living product, not a project with an end.

SECTION 2.0AGENT ARCHITECTURE

Four agents,
continuous operation.

Each agent has a defined scope, specific tools and a handoff protocol. None works in isolation.

AGENT-01 · STRATEGY
S
Strategos

Market analysis, campaign planning, project prioritization and allocation decisions. Reads data from Métrikos, guides Contento and Nexo.

INPUTS: BRIEF · DATA · CONTEXT
AGENT-02 · CONTENT
C
Contento

Content production at scale: articles, copy, scripts, emails, posts. Operates in the brand's tone, respects the editorial calendar, delivers ready to publish.

INPUTS: BRIEF · BRAND GUIDE · CALENDAR
AGENT-03 · DATA & BI
M
Métrikos

Collects, transforms and delivers data. Generates reports before Monday's meeting. Fires alerts when metrics leave the defined threshold.

INPUTS: PIPELINE · KPIs · THRESHOLDS
AGENT-04 · AUTOMATIONS
N
Nexo

Orchestrates the flows between systems: CRM, email, notifications, webhooks, scheduled posts. Glues the other three agents into a single workflow.

INPUTS: TRIGGER · WORKFLOW · TOOLS
HANDOFF · PROTOCOL
Handoff Protocol

Each agent passes structured context to the next: what was done, what's pending, what the priority is. No rework, no noise.

FORMAT: JSON · STRUCTURED · VERSIONED
OVERSIGHT · HUMAN
H
Human Supervision

High-risk decisions go through human approval. The system flags when something deviates from the pattern and waits before acting.

TRIGGER: ANOMALY · RISK · ESCALATION
SECTION 4.0WORKFLOW SCHEMATIC

From manual
to a living system.

Four implementation phases. Each phase with an input, an output, and a defined owner: auto (AI agent) or human.

STEP 5.01 HUMAN
01
Map

Identifying the current process: who does it, what they do, in which tool, how often. Without a map, automation stays fragile.

OUTPUT5–7 DAYS
STEP 5.02 HUMAN
02
Design

The automation architecture: which agents take part, which tools connect, where the human validates, where the system decides.

OUTPUT3–5 DAYS
STEP 5.03 AUTO + H
03
Build

Implementing the agents and workflows. Tested in parallel with the old manual process until reliability is proven.

OUTPUT2–8 WKS
STEP 5.04 AUTO
04
Iterate

A living system. Failure monitoring, prompt tuning, expanding the agents to cover unforeseen cases.

OUTPUTCONTINUOUS
HUMAN OPERATED
AUTO / AI + SUPERVISION
SHEET 4 OF 6
SISTEMA ATIVO FRAME 05 / 06
A process becomes a system.
A system becomes an advantage.
TH—AUT—TRANS WORKFLOW RUNNING ©2026
SECTION 3.0OPERATIONAL STACK

Infrastructure without friction.

A stack built in layers that talk to each other. Each tool has a specific function. None of that all-in-one that locks up when you need to leave.

LAYER 01 · INGESTION
Connectors & APIs
HubSpot · GA4 · Meta API
Salesforce · Custom Webhooks
LAYER 02 · ORCHESTRATION
Workflow Engine
n8n · Make · Zapier
Python Scripts · Cron Jobs
LAYER 03 · AGENTS
AI & Reasoning
Claude · GPT · Gemini
Custom Prompts · Tool Use
LAYER 04 · DATA
Storage & BI
BigQuery · Looker Studio
Notion · Airtable · dbt
LAYER 05 · DELIVERY
Output & Notification
Slack · E-mail · CMS
WhatsApp API · Relatórios PDF
TH—AUT—03 · BLUEPRINT SPEC · REV. 01 SHEET 3 OF 6
SECTION 7.0IMPLEMENTATION

Automation that scales
with you.

First workflow running in 3 weeks. No proprietary code that locks you in. An open-source stack you control. Agents that learn from use.

IMPLEMENTATION 3 wks
ACTIVE AGENTS 4 nodes
TARGET UPTIME 99%
STACK Open-source
IN OPERATION · NOW

One engine. Two opposite worlds.

The same agent operation produces content for an investment fund and for a rally team: from the sober compliance of one to the adrenaline of the other. And nothing, in either case, reaches the public without passing through two human eyes. The agents carry the weight. You and the client decide.

01 · Topic
Agents research and suggestYou reviewClient approves
02 · Copy
Agents produce copyYou reviewClient approves
03 · Art
Agents generate the artYou reviewClient approvesPublish
Real client · anonymized

An investment fund

Constant institutional presence, in the tone a regulated sector demands. The agents research market and thesis topics, produce the copy and the art in the fund's identity. And the double human gate isn't a caveat: it's what makes automation viable where nothing can go out without review.

InstitutionalRegulated toneDouble supervision
Real client · anonymized

A rally team

The opposite in everything (pace, tone, aesthetic) in the same system. Race hooks and behind-the-scenes become the agenda, the copy comes out in the fans' voice, the art in the team's identity. High volume, heavy production on the agents, decisions in the right hands.

High volumeFans' voiceOn-brand art

Two human gates per stage. Scale with control, not automation in the dark. Names and logos come in when the clients agree.

PROOF

Where it ran.

Documented projects, with the problem, the decision and what changed.

FREQUENTLY ASKED

Before you ask.

What people usually want to know before the first brief.

Which processes do you automate?
The ones that depend on someone remembering to run them: reporting routines, moving data between systems, follow-up, publishing, reconciliation. If it has fixed steps and repeats, it's a candidate.
Do I need a technical team to maintain it?
No. The operation is delivered running and supervised by the agents. You approve the process design, you don't write code.
What if the automation fails midway?
Every flow has a stop point and an alert. The rule is to fail visibly, not silently: a process that breaks without warning is worse than a manual one.
Can we start small?
That's the recommendation. One well-mapped process first, measuring the time it gives back, before expanding to the whole operation.
WHERE IT RAN