Work Loop runs locally, shows exactly what it read and skipped, and gives you source-linked project context you can verify.
It remembers — and it can prove it.
Turn a working project into an inspectable briefing: what changed, what the documents say now, what remains unresolved, and the exact source behind each supported answer.
Real product runAntelier
July 22, 2026 · freshness not checked
Walked
305
Imported
228
Skipped
77
Symbols
224
Answer citations
3
01 / Evidence, not a demo script
The receipt comes before the answer.
These are unedited screens from Work Loop reading the Antelier project. The gaps are part of the product: a skipped path stays skipped, an unsupported language stays unsupported, and an answer stops where its evidence stops.
Import accounting
Every walked path lands in one bucket.
Imported, skipped, failed, or not indexed yet. Work Loop exposes the arithmetic and the concrete exclusions before it makes a project claim.
228 + 77 + 0 + 0 equals the 305 paths walked
77 exclusions remain inspectable by path and reason
Freshness is reported separately from completeness
Actual Antelier import receipt. No fixture data.
Project picture
Browse the shape that was actually observed.
The current pilot extracts JavaScript, JSX, TypeScript, and TSX structure. Files distinguish “parsed with no exports,” “language not supported yet,” and “parse failed” instead of collapsing each case into zero.
189 code files in the real Antelier run
224 extracted symbols across the observed project
Static structure is not predicted runtime behavior
Current published generation, with exact source navigation.
02 / Ask with receipts
A useful answer can still say what it could not prove.
Asked what watermark.ts does and where it is used, Work Loop led with the supported documentation, pinned three sources, and named the unsupported half of the question.
Supported lead, explicit gap, three exact citations.Line range, byte span, source identity, and currentness at the point of trust.
03 / The honest boundary
Early means early.
Ask is early. Verify cited source lines, freshness, and decision conflicts before you or an agent acts.
In the pilot
What works now
Local, bounded project import with exact exclusions
Document reconciliation and current working positions
JavaScript and TypeScript source structure
Cited answers that can abstain or name a gap
Designed server-offline state with reconnect
Known limits
What needs your judgment
Static code structure is not runtime observability
Language coverage is deliberately incomplete
A complete scan can still be stale later
Typed relationships may be sparse or absent
No answer is permission to act without review
Direction
Where the loop goes
Agents start from a source-linked brief
Work reports back what actually changed
Decisions and conflicts remain governed
Each run improves the next handoff
Team, hosted, and action lanes reopen when evidence warrants them
Private pilot
Bring a real project.
We are looking for early users willing to test an actual install and tell us where the proof breaks down. If the fit is real, we will contact you with a pilot slot.
