Skip to main content

Read These First

Expectations

  • Keep current-state behavior in the architecture docs and future changes in the design docs.
  • Treat the Primitive Test as the gate before adding new SDK surface area.
  • Run make check before you open a PR.
  • Run make check-docs when changing navigation, cross-links, or docs structure.

When to Update Docs

  • Update architecture docs when code behavior changes.
  • Update design-doc status when a proposal is accepted, implemented, or superseded.
  • Move exploratory notes, audits, and roadmaps into the archive instead of presenting them as current onboarding material.
Last modified on March 20, 2026