Three workflows captured from Engram against a small public library-catalog repository. Every result below is a snapshot you can inspect and repeat.
Source revision c333c003e7b2 · index timestamp 14 July 2026 · captured 9 September 2026. This is a sample, not a production-scale benchmark.
Submit src/Services/BookRepository.cs for review context, then trace the borrowing entry point to inspect a relevant path.
The review result highlights FindById, Remove and Add as structural hubs in the changed file. It returns indexed callers and flags an incomplete test-reachability search.
The selected trace shows Borrow → AdjustAvailability → FindById. The links open the implementation so a reviewer can check the relationship.
Selected path from a captured Engram result, checked against public source. Static relationships; not a runtime trace.
See the queries and captured evidenceStart with the file’s retained history, then distinguish what the record says from what still needs investigation.
get_file_context returns one commit for BookRepository.cs: “Initial catalog API skeleton”. The retained history begins and ends with that commit.
There are no linked tickets, reviews or extracted source-rationale items in this sample result. Engram exposes that absence; it does not invent a decision trail.
Separately, the repository README identifies this as a deliberately small sample for indexing and code-navigation tools, with an in-memory repository. That supplies context, but it is not evidence of a missing design discussion.
In a connected estate, retained work-item and review links can sit alongside commits. A file-level association shows evidence worth reading; it does not prove why a particular line was written.
Retained evidence only. No historical source or graph reconstruction is implied.
The onboarding view combines the README, indexed outline, compiled modules and representative flows into one starting point.
src/Controllers, then follow services and models.The captured onboarding flow is deliberately short: GET /api/authors → AuthorsController.List. Continue into source for deeper behavior; a representative flow is not a complete execution map.
Compiled module counts are graph groupings, not an exhaustive count of every symbol in each directory.
Index the public sample at the recorded revision in your Engram installation. Invoke these MCP tools with the arguments below. Record your Engram release, index revision and configuration; newer resolvers or different budgets can change the output.
change_impact({
"repo": "engram-example-catalog",
"changed_files": "src/Services/BookRepository.cs",
"view": "review"
})
trace_flow({
"repo": "engram-example-catalog",
"symbol_id": "src/Services/LoanService.cs::LoanService.Borrow#method",
"max_depth": 2,
"max_response_chars": 16000,
"cross_repo": false
})
get_file_context({
"repo": "engram-example-catalog",
"file_path": "src/Services/BookRepository.cs"
})
brief_repo({
"repo": "engram-example-catalog",
"view": "onboarding"
})The download contains complete captured review and trace responses plus labelled file-context and onboarding excerpts. Optional ownership data and aggregated cross-repository contracts are excluded. The layout above is a readable presentation of those results, not a screenshot of Explore.
We’ll use a 30-minute scoping call to understand your repositories, tooling and evaluation goals.