GoodMemory v1 closes Phase 17 as a retrieval-first rollout surface. rules-only remains the supported baseline. New retrieval behavior should move through observe, assist, and promote in order, and every step should be justified by persisted eval artifacts.
observe: run the candidate in isolated shadow only. Use this when you want evidence without changing the executed path. Checkshadow-executed-path-comparisons.jsonand make sure observe cases stay contamination-safe.assist: let the candidate strategy execute in eval or controlled provider-backed runs. Use this to measure real uplift and real regressions before any default change.promote: only use this afterstrategy-promotion-gate.jsonreportsaccepted/passed,regression-dashboard.jsonshows no blocking cases for the promoted path, and an explicit internalstrategy-promotion-authorization.jsonhas been issued from a clean gate run.
Rollback to rules-only when any of the following is true:
strategy-promotion-gate.jsonisrejectedordelayedstrategy-promotion-authorization.jsonis missing, expired, mismatched, or no longer trustedregression-dashboard.jsonreports blocking cases or new execution failures- shadow artifacts stop proving contamination-safe behavior
- provider-backed dependencies required by the candidate strategy are unavailable
Stay rules-only by default when:
- you do not have embeddings or other provider-backed recall support
- your latest eval run is incomplete or has execution failures
- you are in a regulated, low-trust, or incident-recovery environment
- the public surface decision still classifies rollout controls as internal
Before any non-default promotion, review:
report.jsonshadow-executed-path-comparisons.jsonstrategy-promotion-gate.jsonstrategy-promotion-authorization.jsonregression-dashboard.jsonpublic-surface-decision.json
bun run eval:phase-17: deterministic fallback gate for retrieval observe-mode artifacts and shadow safetybun run eval:phase-17-live-memory: provider-backed gate that runs bothobserveandassist, then writes the trusted promotion authorization artifact only when observe is clean/known-safe and the assist run is clean