Skip to content

Commit db2c999

Browse files
author
Builder Weekly
committed
Phase 12A: add foundations pillar README
1 parent 1d3bba2 commit db2c999

1 file changed

Lines changed: 26 additions & 0 deletions

File tree

pillars/foundations/README.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Foundations
2+
3+
What every production agent needs underneath it. Observability, budget enforcement, retry logic, error handling, the stack you would otherwise reinvent for every project.
4+
5+
## Entries
6+
7+
_No entries yet. The first foundations tutorial is in the queue._
8+
9+
## The pattern
10+
11+
Every foundations tutorial teaches one piece of infrastructure that cuts across all agent types. The before-state is always "the agent works until it doesn't and you have no idea why." The after-state is always "the agent works, and when it breaks, you know exactly what happened."
12+
13+
- **Before-state:** "The agent runs in production and you're flying blind."
14+
- **After-state:** "The agent runs in production and you see everything."
15+
16+
## Cluster tags in this pillar
17+
18+
- `logging` — structured event logging for agent pipelines
19+
- `tracing` — distributed tracing across agent steps
20+
- `metrics` — per-step latency and cost tracking
21+
- `budgets` — spend-based throttling and circuit breakers
22+
- `rate-limiting` — controlling agent API call velocity
23+
- `cost-control` — keeping agent operations within budget
24+
- `orchestration` — multi-step workflow management
25+
- `human-in-the-loop` — approval gates in automated pipelines
26+
- `state-machines` — explicit state transitions for complex flows

0 commit comments

Comments
 (0)