How to read the source city
Move from generated catalogs to package READMEs, then types and events—avoid blind index.ts spelunking
graph → contract → producer/consumer → implementationIn a large agent repository, do you search functions first or find contracts first?
To repair complex equipment, start with wiring diagrams and interface catalogs before opening the chassis. Following one screw rarely reveals the system.
Mechanism
DeepSeek Harness generates module graphs, capability-seam graphs, event producer/consumer matrices, persistence catalogs, and config catalogs from source declarations.
Read in this order: establish responsibility, locate service/event contracts, identify providers and consumers, then enter implementations and tests.
Locate graph
Choose module, service, event, or persistence view in graph-atlas.
What extensions must preserve
- Generated documentation blocks must stay source-synchronized
- Teaching material should name the upstream commit it aligns to
- Inference and source-backed fact must be clearly separated
The tempting wrong turns
- ×Copying package names from stale posts
- ×Reading only the happy path, not cancellation and disposal
- ×Assuming the first provider found is the only one
Do not trust the conclusion—verify it
These anchors are pinned to official deepseek-harness@47f9438; account for later breaking changes when reading current upstream.
Pause for ten seconds before revealing
Why inspect consumers before deciding what a service really does?
With this method, we enter Cordis through its collaboration surface: Context.