Skip to content

Commit e2fd551

Browse files
committed
Add AgentCode architecture overview graphic
1 parent 727184c commit e2fd551

2 files changed

Lines changed: 143 additions & 0 deletions

File tree

README.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,20 @@ After surveying today's high-star Agent repositories, four opportunities stood o
1919

2020
`AgentCode` is a place to build those missing layers as focused OSS projects.
2121

22+
## Architecture at a glance
23+
24+
<p align="center">
25+
<img src="docs/assets/agentcode-overview.svg" alt="AgentCode architecture overview" width="100%" />
26+
</p>
27+
28+
This is the intended product story for the monorepo:
29+
30+
- `AgentCI` turns real runs into replayable regression artifacts
31+
- `TracePack` packages those runs into reusable benchmark cases
32+
- `FailMap` turns repeated failures into triage-ready clusters
33+
- `PackSlice` creates stable train/eval/test slices from the same pack
34+
- the root CI workflow validates that the whole chain works end to end
35+
2236
## Projects
2337

2438
### 1. AgentCI
@@ -69,6 +83,26 @@ That makes it easier to build release checks, artifact pipelines, and automated
6983

7084
For a fuller walkthrough, see `docs/automation.md` and the companion script `scripts/run_automation_demo.sh`.
7185

86+
## What the monorepo demo produces
87+
88+
The root workflow now runs an end-to-end automation demo and uploads artifacts that mirror a real team handoff:
89+
90+
```text
91+
agentci-summary.json
92+
agentci-regression.json
93+
tracepack-pack/
94+
manifest.json
95+
cases/
96+
failmap-clusters.json
97+
packslice/
98+
summary.json
99+
train/
100+
eval/
101+
test/
102+
```
103+
104+
That makes the repo feel less like four isolated READMEs and more like one coherent toolchain.
105+
72106
## Monorepo structure
73107

74108
```text

docs/assets/agentcode-overview.svg

Lines changed: 109 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)