Public evidence policy
Publication gatedClaims must never outrun evidence
Technical resource withheld pending evidence review, named responsibility, and publication permission. No site or customer outcome is established.
Review publication statusGridNinja methodology
Methods for claims that operators can defend
These methods define how GridNinja scopes public claims, comparisons, corrections, and Capacity Audit outputs. The governing principle is proof before autonomy and proof before promotion: exact wording stays tied to an environment, maturity, evidence object, caveat, approved surface, owner, and review date, while no-proof remains a valid published outcome.
Four distinct evidence stages
- 01Specified
- 02Implemented and tested in a stated environment
- 03Evaluated with authorized site data
- 04Accepted for a stated customer decision
A stage applies only to its stated environment, evidence, and decision. Synthetic software examples do not establish authorized site evaluation or customer acceptance. Public claims also require exact wording, scope, evidence, owner, permission, approved surfaces, review date, and expiry.
Publication boundary
Evidence earns visibility
The methodology index describes intended controls. Individual candidate text and artifacts are withheld until evidence, accountable ownership, and publication permission are established. The current assessment scope and its boundaries are described on the assessment page.
Resource index
Stable questions, scoped answers, explicit limits
Comparison governance
Publication gatedA scoped, source-backed comparison policy
Technical resource withheld pending evidence review, named responsibility, and publication permission. No site or customer outcome is established.
Review publication statusTrust policy
Publication gatedCorrections remain visible and attributable
Technical resource withheld pending evidence review, named responsibility, and publication permission. No site or customer outcome is established.
Review publication statusCapacity Audit method
Publication gatedHow a Capacity Audit turns constraints into a defensible decision
Technical resource withheld pending evidence review, named responsibility, and publication permission. No site or customer outcome is established.
Review publication statusRelated operator resources
Continue the proof path
- Evidence informs a decision. Authority stays explicit.See how Shadow Mode, replay, allow / repair / reject decisions, audit logs, and proof packs establish evidence before bounded autonomy.
- Evidence for safe, usable, auditable capacityPublication-gated methods, synthetic traces, ledgers, specifications, and proof artifacts for evaluating virtual capacity claims.
- Scope your next capacity decision.Scope a paid, bounded capacity decision assessment using authorized historical inputs, explicit conditions, model comparisons, and a reviewable brief.
Capacity Audit
Bring the operator question before the capacity claim
A bounded assessment reviews one capacity question, its evidence, constraints, and unresolved commercial decisions.