Code Navigation

When you need to inspect the crate quickly, use this route order.

Fast Reading Path

1. start at the crate root to confirm the crate exports one deliberate public facade
2. read the public API facade to see what the crate claims publicly
3. jump to the owning family: artifacts, observations, navigation solutions, identifiers, time, units, geodesy, diagnostics, support inventory, or configuration
4. read the corresponding crate-local guides, especially the public API guide, contract guide, contract map, invariants guide, and serialization guide
5. confirm with the narrow integration or property test that protects the contract

Review Shortcut

If a change touches the public facade, artifact records, observation records, navigation-solution records, or time model, treat it as a cross-crate contract review first and an implementation review second.

First Proof Check

• the crate root
• the public API facade
• the navigation artifact validation
• the tracking artifact validation
• the timekeeping property tests
• the public API guardrail