# v1.14.0 - optional Jev and Laya decisions

Same seventeen-skill workflow, with an optional
typed-decision layer. Core runs with the host-selected model and no provider
calls. Setup remembers core/Jev/Laya, and explicit settings can change it later.
Remote Jev and cached local Laya return advisory suggestions with timeout,
attempt-limit and malformed-response fallback. They cannot execute actions or
approve completion.

The top-ten review
maps existing coverage and identifies optional graph, scientific and research
capabilities without importing a second workflow or requiring a skill catalog.

## Evidence

- Baseline candidate: 198 deterministic tests passed before review fixes.
- After review fixes: 12 focused optional-decision tests passed. Full 201-test
  reruns encountered existing wall-clock runner failures on a heavily loaded
  host; the identical-to-1.13.0 runner suite passed all 14 tests in isolation.
  Clean Linux and macOS CI subsequently passed all 201 tests on implementation
  commit `8425ceafcf6bdcce3d9900c69b82fcc4c036e4f6`.
- Both validators, syntax checks and clean-tree checks passed in
  [CI run 35705688851](https://github.com/nobrainer-tech/nobrainer-tech-flow/actions/runs/35705688851).
  The Linux current-tree secret scan passed too.
- Live direct Jev 1.13.0 and offline cached Laya multilingual returned validated
  Noul, Choice and Score on synthetic input. Apple Silicon/macOS local evidence
  only. Laya's middling urgency result limits semantic quality claims.
- Workflow SVG rendered and inspected at 1600x900; no clipped new caption.
- Independent audit found setup, failure-model metadata and local-diagnostic
  gaps; fixes were rechecked. The final prompt-label correction is applied.
  Local cached-path loading was reverified after the fix with all three types.

Helper runtime evidence does not prove every harness loads or follows Flow.
Clean-session routing, package installation and public distribution each need
separate readback. No paid provider, download or second model is necessary for core.

## Rollback

Set decision mode off or provider core to disable optional calls. Reinstall
the verified v1.13.0 source if the release itself needs rollback; preserve
project instructions and unrelated changes. Website preimages must be retained
before deployment. GitHub release, public website and X permalink require their
own publication readback; CI does not prove those external states.