Explanation

Explanation pages describe why benchmatrix works the way it does. Use them for architecture, policy, security posture, and maintenance context rather than step-by-step instructions.

Available explanations

• Architecture, covering package boundaries and design constraints.
• Performance model, covering latency, throughput, and tail latency views.
• Threat model, covering supply-chain, benchmark input, and repository risks.
• Dependency policy, covering runtime and development dependency expectations.
• License policy, covering MIT-compatible project content and dependencies.
• Lifecycle, covering branch, version, and support expectations.
• Repository health, covering maintenance signals and cadence.
• Secrets, covering local checks and response steps.
• AI-agent guidance, covering operational expectations for automated contributors.
• Deprecations, covering public API migration expectations.
• GitHub Actions security, covering CI permissions and workflow controls.
• Deployment environments, covering package, documentation, and container outputs.
• Repository settings, covering external setup expectations.
• Publishing, covering release artifacts and publication checks.
• First release, covering readiness checks before the first public release.

Use how-to guides and runbooks when the next action needs to be concrete.