Find the implementation authority¶
Use this map to locate an existing mechanism before changing it. It is a source navigation, not another build graph or support database. Source links bind the site’s exact document revision; offline consumers can inspect the same paths in the matching checkout or Source SDK.
Task |
Maintained entry |
Contract and validation |
|---|---|---|
Authored assembly and fields |
Assembly reference; actual resolver rejection tests |
|
CPU facts and Runtime |
Arch contract; CPU runtime compiler/model matrix |
|
Request and deadlines |
Ownership; actual Core/epoch contracts |
|
Public face and dispatch |
Factory; public headers and generated fixture tests |
|
Chip/IRQ/DMA implementation |
Provider guide; production-register models and exact ARM ELF |
|
PCB data |
Reviewed Board JSON and exact physical unknowns |
|
Wait, task and kernel adapters |
OS contract; actual kernel and boundary tests |
|
Reusable algorithms |
Public narrow ports; component and owner behavior tests |
|
Consumer/export boundary |
SDK tutorial; independent relocated C/C++ consumers |
|
Build targets and presets |
Build contract; actual configure/build/resource gates |
|
New production behavior |
TDD workflow; retained actual RED/GREEN and full gate |
|
Qualification and hardware |
Qualification; distinct software and physical records |
|
Document content and delivery |
Maintenance; strict source/build/package/published-site checks |
Read the relevant contract and adjacent README before changing behavior. Select only maintained modes, keep private provider/vendor types out of consumers, and update declarations, diagrams, examples and translations together when their meaning changes. Preserve original evidence bytes and scope instead of renaming historical results to current HEAD.