SynapCores Community Edition v2.5.1-ce
Community Edition · free · seamless upgrade from v2.5.0-ce
v2.5.1-ce is a correctness-and-polish release. The headline is drop-in parity for the
POST /v1/systemone decision endpoint: a noul (yes/no) question may now carry a criteria
field and still return a clean answer, so a request body written for a stock llama-server
decision call runs unchanged against SynapCores. It also ships two installer fixes that were
costing fresh installs. Additive and drop-in — no data migration, no config changes.
One request body, both runtimes
The /v1/systemone endpoint returns a typed decision — a routing choice with per-option
probabilities, a yes/no probability, or an urgency score — in a single forward pass with
zero generated tokens (see the v2.5.0 launch).
In v2.5.0, a noul question had to omit criteria — the field is meaningful for choice and
score questions but mathematically irrelevant to a yes/no pass, so the engine rejected it with
a 400. That was stricter than the reference llama-server, which simply ignores the field. The
result: a decision payload that worked against Ollama / llama-server returned an error against
SynapCores, breaking true drop-in parity.
v2.5.1-ce accepts and ignores criteria on noul questions. The same request body now
works against either runtime, and the yes/no probability is identical to what you'd compute by
hand. The fix lives in the one shared validator behind both the REST endpoint and the SQL
DECIDE family, so DECIDE_YESNO behaves the same way.