Coding and Documentation Style

Sharp Runtime naming, component boundaries, portability and evidence conventions.

Principles

• Use human-facing “Sharp Runtime”; reserve sharp-runtime for repository/path/command identities.
• Match the existing System namespace/type spelling where implementing a compatibility API.
• Keep C++ ownership and const/copy/move behavior explicit.
• Place APIs under the narrow physical owner and declare real edge visibility.
• Compile with the project’s warnings-as-errors policy.
• Document reductions and platform limits next to the behavior.

Documentation evidence

Do not copy a mutable count or platform claim from an older summary. Prefer implementation, CMake registration, generated current metadata, tests and measured gate output.