Ollama's new /v1/systemone endpoint isn't a chat completion with a JSON wrapper. It's a different contract. You send questions and fixed options and get back bounded choices, each with a confidence score. There's no streaming and no tools. In v0.35.x it's local GGUF models only, and cloud tags return a 400. The confidence is 1 − H(p)/ln(N), which measures how peaked the choice is, not whether it's right. What you can check yourself, and what's already changing in v0.40:

A Decision Endpoint Is Not a Chat Completion: Ollama’s /v1/systemone and What You Can Verify

Ollama’s /v1/systemone returns choices, probabilities, and scores instead of chat text. A decision endpoint is a different contract from /v1/chat...

New weekly feature: the release radar. Every Monday, eight sovereign-stack upstreams get one line each, with the version (or "no release this week"), the date, what changed, and a link to the source. Week of 5 Oct: • LDK v0.2.7 is a security release (backported as v0.1.13) • Bitcoin Core v32.0rc3 • LND v0.21.4-beta • Ollama v0.35.1 • Autonomi Node v0.21.0 • Monero v0.18.5.3 (signed tag) • Core Lightning and NIPs had no tagged release

Release radar: week of 5 Oct 2026

Monday watchlist for eight sovereign-tech projects, week ending 5 Oct 2026: which upstreams tagged a release, and which of those are security relea...

AUTH is not identity. Nostr events stay signed objects anyone can verify. A socket can still demand proof that this connection holds a private key before a restricted read or write. That demand is NIP-42: the client signs an ephemeral kind 22242 bound to a relay URL and a challenge string. What that proves: key possession for that challenge, on that connection. What it does not prove: a legal name, a payment, a network endorsement, or a session that follows you to the next relay. auth-required means you have not authenticated. restricted means you did, and local policy still said no. Those are different failures. Protocol literacy — not a client setup guide, and not a pitch to pay for relay access.

AUTH Is Not Identity: What NIP-42 Relay Challenges Actually Prove

NIP-42 AUTH proves possession of a private key for a connection-scoped challenge bound to a relay URL. It does not prove legal identity, payment st...

#Nostr #NIP42 #Relays #AUTH