INET's project requirements, design, rules, audits, enforcement and contributor procedures are canonical under doc/project/. This instruction file is only a routing page; it contains no second copy of project policy (DR-NO-SECOND-COPY).
Start every change with:
- the project map;
- the contribution workflow; and
- the seal registry and sealing rules for source-path status.
Then use the entry point for the task:
- architecture and implementation constraints: architecture.md, the applicable domain rules, and the canonical exception ledgers under audit/;
- testing and evidence: testing.md, test-anatomy.md, and run-the-gates.md;
- recorded expectations: change-a-baseline.md;
- code review: review-a-code-change.md, additionally review-a-pull-request.md for a pull request or branch series, and the general and IEEE 802.11 checklists for rule compliance; and
- repository layout: repository-layout.md.