# sealmap corpus
Generated by sealmap. Do not edit: `sealmap generate --check` reports any hand edit, and the next `sealmap generate` overwrites it.
## Layout
- `<source path>.md`: exactly one document per source file (the 1:1 contract).
- `_index.json`: every document and fragment, with participants, calls and merge links.
- `_model.json`: the full code model (symbols, spans, signatures, docs, relations).
- `_overview.md`: crate graph, module graphs, data models and trait maps.
## Documents
YAML front matter: `source`, `module`, `language`, `source_hash` (BLAKE3 of the
newline-normalised source), `lines`, `fragments`.
Sections:
- `## structure`: `classDiagram` of what the file defines. `<<module>>` boxes
hold free functions, constants and submodules. Stubs annotated
`<<kind in path>>` are defined in another file; `<<external>>` ones are outside
the codebase. Edges: `..|>` implements, `<|--` extends, `*--` owns,
`o--` holds via Option/Arc/Rc/&/collection, `..>` uses in a signature.
- ``## `sym:cargo crate . path/Type#fn().` ``: `sequenceDiagram` of one function's calls in source
order. The first lane is the function's owner (its type, or its module).
`alt`/`else` = if/match arms, `opt` = if-without-else, `if let` or closure,
`loop` = for/while/loop or per-element closure, `par` = spawned task.
A `~` prefix means the callee was inferred rather than proven. `?` suffix =
error propagates, `.await` = awaited. `Note` = early return. Lanes marked
`ext` are external crates.
## Ids
Every symbol is named by a `sym:` id with no file path, so moving code
between files keeps it: `sym:cargo <crate> . <module>/<Type>#<method>().`.
The suffix gives the kind: `/` module, `#` type or trait, `().` function or
method, `.` const or static, `!` macro; `[Trait]` marks a trait-impl
method (`Db#[Store]put().`). `sym:extern a::b` is a path outside the code
whose kinds are unknown; `sym:? name` is a method on a receiver of unknown
type. Names outside `[A-Za-z0-9_+$-]` are quoted in backticks.
Every diagram id is derived from the `sym:` id by an injective encoding:
`__` before a module, `___t` before a type, `___f` before a function, and
so on (`my_crate__net___tClient___fconnect`). The same symbol has the same
diagram id everywhere, and no two symbols share one, so fragments can be
merged by id.
In `_model.json` every symbol also carries `sig_hash` (its contract) and
`body_hash` (its implementation); comments, formatting and moves change
neither.
## Merging
In `_index.json`, each sequence fragment lists its `calls`. A call with
`expands: "<fragment id>"` points at the callee's own sequence fragment:
inline it to deepen a sequence, or follow it to stitch flows across files.
`confidence` is `exact` (resolved through paths, imports or declared types),
`inferred` (heuristic), or `external` (outside the codebase).