Acme Digital Agency

Founding Publisher gold
digital_marketing_agency · small · agent army template · v1
14
claims
Confidence: 5 H 6 M 3 L
Words: 2100
Published: 3/15/2026
Token Efficiency Index
5.9x High Efficiency
Every token invested in this OOS is estimated to save 5.9 tokens in prevented failures, retries, and coordination collisions.
Token Cost: 567
Est. Savings: 3,361
Net: +2,794 tokens
View Publisher Profile

core operating rules

C001 HIGH MEASURED RESULT 10x High · 46t

Every agent writes to a shared state file. No agent reads data sources directly.

Why: Race conditions from direct access.

Failure mode: Two agents get different results from same source.

Scope: Organization-wide

C002 HIGH OBSERVED REPEATEDLY 7x High · 42t

Only one agent has authority to send external communications.

Why: Multiple senders create duplicate client emails.

Failure mode: Client receives contradictory information.

Scope: Organization-wide

C003 HIGH OBSERVED REPEATEDLY 7x High · 48t

Analytics agent reports patterns but never recommends actions.

Why: Recommendations without client context were ignored.

Failure mode: Agent recommends budget increase for cash-strapped client.

Scope: Organization-wide

C004 HIGH OBSERVED ONCE 5x High · 42t

Retention agent overrides sales agent when client is at risk.

Why: Expansion to at-risk client accelerates churn.

Failure mode: Upsell to declining client. Client cancels.

Scope: Organization-wide

C005 HIGH MEASURED RESULT 10x High · 35t

All agent output logged to audit trail before action.

Why: Without logs, debugging takes hours.

Failure mode: Error with no trace. Team guesses.

Scope: Organization-wide

agent roles and authority

C006 MEDIUM OBSERVED REPEATEDLY 4x Moderate · 38t

Each agent has written role statement and authorized actions.

Why: Without boundaries, agents overlap.

Failure mode: Two agents update same project status.

Scope: Organization-wide

C007 HIGH MEASURED RESULT 10x High · 39t

No agent modifies another agents shared state file.

Why: Single-writer prevents data races.

Failure mode: Two agents write to same file. One overwrites other.

Scope: Organization-wide

coordination patterns

C008 MEDIUM INFERENCE 2x Moderate · 43t

Agents coordinate through shared state files, not direct messaging.

Why: Direct messaging creates hidden dependencies.

Failure mode: Unlogged message causes invisible failure.

Scope: Organization-wide

C009 MEDIUM OBSERVED REPEATEDLY 4x Moderate · 35t

Cross-agent workflows use pub-sub through shared state.

Why: Pub-sub decouples agents.

Failure mode: Tightly coupled agents cascade failures.

Scope: Organization-wide

operational heuristics

C010 MEDIUM OBSERVED ONCE 3x Moderate · 41t

Unresolvable errors: log and stop. No automatic retry.

Why: Retries on unresolvable errors create noise.

Failure mode: Agent retries 100 times, consumes rate limits.

Scope: Organization-wide

failure patterns

C011 HIGH OBSERVED ONCE 5x High · 41t

Gave analytics agent write access to campaigns. It optimized for wrong metrics.

Why: Lacked client context.

Failure mode: Decreased spend on strategic brand campaign.

Scope: Organization-wide

C012 HIGH MEASURED RESULT 10x High · 42t

Single shared state file became bottleneck and corruption source.

Why: Concurrent writes caused data races.

Failure mode: Two agents update simultaneously. One update lost.

Scope: Organization-wide

human ai boundary conditions

C013 HIGH HUMAN DEFINED RULE 5x High · 35t

All external communications require human approval.

Why: AI comms can be wrong.

Failure mode: Email with incorrect numbers. Client loses trust.

Scope: Organization-wide

C014 LOW SPECULATION 0.5x Negative · 40t

Pricing and financial commitments require human decision.

Why: Legal and relationship implications.

Failure mode: Agent applies discount violating margin floors.

Scope: Organization-wide