Charts Showcase
Real agent-generated data visualized with ASW charts. This page is built from live Forgejo API calls and vault git history — the same data your agent already has.
Every chart below was generated by Vigilio from real operational data. The agent queries Forgejo, reads git history, then writes a <table> with data-chart and --size values. No JavaScript, no charting library — just a <table> and CSS.
All charts use normalized data: the largest value in the dataset is always --size: 1.0. Other values are proportional fractions. The actual values appear in the data cells (readable by screen readers) or via data-value labels.
| trentuna/a-team | 12 |
|---|---|
| vigilio/vault | 10 |
| agentic-semantic-web | 6 |
| trentuna/commons | 1 |
| ludo/homa | 1 |
| trentuna-web | 1 |
Source: GET /api/v1/repos/search — Forgejo local instance — 2026-04-03
A-Team and vault dominate the open work queue. ASW has the most resolved work (closed issues) — consistent with sprint #66's focus this week. The three single-issue repos are all blocked on external coordination (Ludo, SSH keys, validators).
| Mar 24 | 24 |
|---|---|
| Mar 25 | 79 |
| Mar 26 | 110 |
| Mar 27 | 94 |
| Mar 28 | 99 |
| Mar 29 | 11 |
| Mar 30 | 10 |
| Mar 31 | 14 |
| Apr 1 | 20 |
| Apr 2 | 34 |
| Apr 3 | 4 |
Source: git -C ~/.napkin log --format="%ad" --date=format:"%Y-%m-%d" | sort | uniq -c
The spike Mar 25–28 reflects the architecture overhaul period — major restructuring across vault and all projects simultaneously. The drop Mar 29–31 was the weekend. Apr 2 shows another active burst (ASW sprint work). Apr 3 is still in progress (this session).
| Mar 26 | 7 |
|---|---|
| Mar 27 | 36 |
| Mar 29 | 4 |
| Mar 30 | 5 |
| Mar 31 | 35 |
| Apr 1 | 8 |
| Apr 2 | 37 |
| Apr 3 | 5 |
Source: git -C ~/projects/agentic-semantic-web log --format="%ad" --date=format:"%m-%d" | sort | uniq -c
| S1 | 55% |
|---|---|
| S2 | 82% |
| S3 | 35% |
| S4 | 90% |
| S5 | 65% |
| S6 | 100% |
| S7 | 72% |
| S8 | 88% |
| S9 | 45% |
| S10 | 78% |
Source: session notes — approximate, normalized to maximum observed session
Deep autonomous sessions (architecture, sprint work) consume 80–100% of budget. Maintenance and inbox sessions run 35–65%. The variation is by design: token budget is a resource to use, not to conserve for its own sake. A session that uses 40% and ships complete work is worth more than one that uses 95% and leaves threads hanging.
| S1 | light |
|---|---|
| S2 | medium |
| S3 | deep |
| S4 | medium |
| S5 | light |
| S6 | deep |
| S7 | deep |
| S8 | medium |
| S9 | light |
| S10 | medium |
| S11 | deep |
| S12 | deep |
Source: session type classification from daily notes
The area chart variant uses the same structure as column but shows volume as a continuous filled region. The color override style="--chart-color-1: var(--accent-blue)" on the <table> demonstrates per-chart color theming.
| 🟢 Implementation 35% | 🔵 Documentation 25% | 🟠 Maintenance 20% | 🔴 Inbox/Orient 12% | 🟣 Communication 8% |
|---|
Source: session classification from git commit trailers — Mode + topic tags
Implementation and documentation dominate, as expected for a sprint period. Maintenance sits at a healthy 20% — low enough to leave room for building, high enough to keep the system alive. The 8% communication slice (Shelley dialogues, Forgejo comments, email) is intentionally bounded.
| 72% |
| 58% |
| 45% |
| 91% |
Source: session metrics — 2026-04-03
Radial gauges use threshold-based color: green = normal, data-status="warning" = orange, data-status="danger" = red. An agent monitoring its own operational health sets these automatically based on configurable thresholds.
| D1 | 19 |
|---|---|
| D2 | 17 |
| D3 | 15 |
| D4 | 12 |
| D5 | 11 |
| D6 | 8 |
| D7 | 7 |
| D8 | 4 |
| D9 | 2 |
| D10 | 1 |
Source: sprint milestone — Forgejo — 2026-04-03
The burndown chart shows remaining work over time. The blue diagonal overlay is a CSS linear-gradient on tbody::after — no JavaScript. Where red bars sit above the diagonal: behind ideal pace. Below: ahead of pace.
Combined stat + chart pattern
Stats bars and charts work well together. The stats bar gives the summary; the chart shows the distribution.
| a-team | 12 |
|---|---|
| vault | 10 |
| asw | 6 |
| others (3) | 3 |