Framework

The TACT™ Framework

A four-part anatomy for every agentic AI workflow. Define these four letters and any AI platform can build the rest.

Platforms like Google Workspace Studio, Claude Cowork, and Microsoft Copilot Studio give you a powerful engine — but they don't give you the road map. You get agents, but not agentic workflows. TACT™ fills that gap. It gives you a repeatable structure so that any process — from a weekly report to a multi-step customer onboarding — can be translated into a file that an AI system reads, understands, and executes.

The Four Pillars

Trigger · Agent · Connector · Tool

T — Trigger
When does the workflow start?

Every agentic workflow needs a signal to begin. The Trigger defines when and how the agent activates — removing the need for a human to prompt it every time.

Trigger types
  • Time-based — "Every Monday at 9 AM"
  • Event-based — "When a new row is added to the spreadsheet"
  • Manual — "When I type 'run briefing'"
## Trigger
A new customer inquiry arrives via email or web form
A — Agent
Who does the thinking and acting?

The Agent is the brain — an LLM given a specific persona, role, and set of instructions. It's not just "chat with AI." It's a specialist assigned to a job.

Agent roles
  • Knowledge — reads, summarizes, answers from your data
  • Action — routes, triages, and executes tasks
  • Decision — evaluates, approves, or escalates
## Agent
Customer Inquiry Responder
Draft polite, accurate replies referencing official docs
C — Connector
Where does it get data?

A brain in a jar is useless. Connectors are the eyes and ears — they let the agent read live data from your business systems instead of hallucinating from stale training data.

Example connectors
  • Email inbox (Outlook, Gmail)
  • SharePoint / Google Drive folders
  • Calendars, CRMs, ERPs, databases
## Connectors
- Incoming inquiry email
- FAQ knowledge base
- Product documentation folder
T — Tool
What actions does it take?

Once the Agent has reasoned about the problem, it needs hands to act. Tools are the strictly-defined actions the agent is allowed to take — nothing more.

Example tools
  • Send email or Slack message
  • Create ticket, update CRM record
  • Generate document, save draft for review
## Tools
- Draft response email
- Save to drafts folder
- Notify team for review
In Practice

A Real Example: Daily Intelligence Briefing

Here's how the four parts come together in a real TACT™ blueprint.

The Blueprint
## Trigger
8:00 AM daily, Monday–Friday
## Agent
Senior Intelligence Analyst — scan, filter, summarize top stories
## Connectors
- Google News API
- Industry RSS feeds
- Company watchlist
## Tools
- Generate briefing doc
- Send via email
- Save to Drive
What Happens
01At 8 AM, the trigger fires automatically. No human needed.
02The agent reads news feeds and your watchlist via the connectors.
03It filters, ranks, and summarizes the top stories relevant to your industry.
04The tools generate a polished briefing document.
05Your team receives the briefing in their inbox before their first meeting.
From Framework to File

TACT™ + Manifest = Your Complete Blueprint

The TACT™ overview tells humans what the workflow does. The Agent Manifest tells the AI how to build it. Together, they form a single .md file that any supported platform can read and execute.

TACT™ Overview

For humans. Readable summary of the trigger, agent, connectors, and tools.

Agent Manifest

For machines. Full specification that AI systems read to build the workflow.

Browse Blueprints