Skip to content

Compatibility Posture

Reference for the Nimi public docs' compatibility and migration posture.

Posture Summary

PropertyValue
Posture nameno_legacy_hard_cut
Pre-launchyes
Soft compatibility shimsforbidden
Time-phased layeringforbidden (layering is ontological: core / extended / custom)
Strict-only protocol versioningyes
Fail-close on contract violationyes
Retry rescues contract failureno

Practical Implications For Readers

SituationExpected behavior
A page is removedPreferred over a stale page
A typed contract failsSurfaces a typed error, not a silent fallback
A retry happensOnly for transport / auth refresh, never to rescue a contract
An older route existsEither kept as admitted public truth or hard-removed; not preserved as hidden compatibility
A new feature shipsLands with full contract design, not as an MVP subset to be filled in later

Forbidden Compatibility Shapes

The methodology's forbidden_shortcuts catalog enumerates the patterns public docs and implementation refuse:

KeyRefused pattern
legacy_aliasKeeping obsolete semantics alive via soft alias
compat_shimHiding owner-cut gaps behind temporary compatibility code
dual_readTwo parallel truth read paths without explicit admission
dual_writeTwo parallel truth write paths without explicit admission
mvp_subset_contractCutting canonical contract truth into a temporary minimum subset
time_phased_layeringReplacing semantic layering with time-sliced (v1/v2/v3) layering
placeholder_successFaking success or closure when required truth is missing
happy_path_only_closureClaiming closure when only the happy path is closed
app_local_shadow_truthApp-local convenience state becoming hidden canonical truth
silent_owner_cut_reopenReopening owner-domain truth inside a downstream execution wave

Public Claim Constraints

Claim typePosture
Install commands (curl / npm / pnpm / brew / apt / yarn)Withheld until admitted distribution evidence under the matching release contract
Download linksWithheld until admitted distribution evidence under the matching release contract
Release status / launch promisesWithheld until admitted release evidence
Concrete provider name / model nameWithheld until admitted catalog evidence under the runtime model-catalog contract
Provider availability matrixWithheld until admitted catalog evidence under the runtime model-catalog contract
"Available now" / "GA" / "Stable" claims for defined-but-not-shipped surfacesForbidden

The complete list of forbidden public docs claims with detection patterns is in Forbidden Claims.

Contract Evolution Path

How a defined-but-not-shipped surface graduates to a public surface:

  1. Kernel contract is admitted under the appropriate authority domain (P-PROTO-* / K-* / S-* / D-* / R-*).
  2. Implementation lands under the owner domain.
  3. Catalog evidence (for providers / models) is admitted.
  4. Distribution / release evidence is admitted (for install / download).
  5. Public docs page is updated to reflect availability.

A docs page cannot pre-announce a stage that the contract evolution has not reached.

Source Basis

Nimi AI open world platform documentation.