Nova the Optimal AI

Upgrade and rollback

Preserve first. Replace once.

Earlier Free editions and 4.3.0 share the nova-the-optimal-ai plugin ID. Extracting both is safe staging; the host cannot keep both active under the same selector.

Preflight

  1. Record the installed marketplaces, plugin versions, and enabled state.
  2. Preserve the old Nova package and marketplace source for rollback.
  3. Locate and back up any governed Continuity data that matters.
  4. Record any old MIND hook, database, or local-model configuration without deleting it.
  5. Inspect the accepted 4.3.0 package and confirm that replacing this active binding is within your authorized upgrade.

Controlled replacement

  1. If a legacy augment-of-mind route is still enabled, disable that competing route while preserving its files and state. MIND is ambient in Nova; no separate MIND installation is needed.
  2. Install 4.3.0 from the extracted codex marketplace.
  3. Open a new task and verify host discovery, enabled state, and one explicit $nova invocation.
  4. Leave old databases, hooks, model downloads, and customer records untouched until the new route is accepted.

Trellis 1.1.0 artifact boundary

Earlier Free 3.1.2 bytes may contain Trellis 1.0.x and v1 Model Agnosticism artifacts. Free 3.8.0 carries the repaired runtime with MIND 0.4.0, but Trellis 1.1.0 accepts only cd-model-agnosticism-model-set/v2 and cd-model-agnosticism-observation-sequence/v2 inputs and emits only v2 receipts.

There is no automatic v1-to-v2 Trellis migration. Preserve v1 inputs and receipts byte-for-byte as historical evidence; structural recognition by the v2 receipt schema does not rerun, endorse, or upgrade an old calculation. Build new v2 inputs with explicit epistemic lane, candidate-selection and stopping contracts, structured step semantics, parameter provenance, and current comparison and calibration bindings. Never relabel a v1 document or rewrite a historical receipt. If the original inputs or a defensible mapping cannot be recovered, retain the history and continue with qualitative Model Agnosticism.

Rollback

If discovery or behavior fails, preserve the exact error and installed state. Restore the recorded previous marketplace source and plugin version, restore the old enablement pattern, open a new task, and verify the old Nova invocation before calling rollback complete.

Plugin removal is not data removal. Deleting customer state, models, hooks, exports, or databases requires a separate explicit decision and exact target.