Skip to content
neutron AI
Documentation Changelog

Changelog

Track public Neutron AI changes that affect memory, knowledge graphs, context, decisions, outcomes, SDKs, CLI workflows, MCP tools, API behaviour, migration steps, pricing, and product availability.

What Appears Here

  • new API endpoints
  • graph, context, decision, outcome, learning, and simulation contracts
  • SDK and CLI releases
  • MCP tool changes
  • provider integration helpers
  • migration notes
  • public benchmark reports
  • pricing and plan updates
  • deprecations and removal dates

Operational details, private system changes, and private runbooks are intentionally excluded from the public changelog.

v0.3.0 - 2026-10-13

Added

  • scopeId on GET /v1/entities/:entityId, GET /v1/relationships/:relationshipId, POST /v1/entities/tombstone, and POST /v1/relationships/tombstone. With it, a record in another Scope is not found.
  • scopeIds (or scopeId) on POST /v1/contradictions/resolve, naming the Scopes the caller acts for.
  • Context packs list each contradiction's competing claims (value, source, confidence) in contradictions[].claims and in promptContext. Once resolved, they show the claim kept and the resolution summary.

Changed

  • Contradictions are kept per Scope set: disagreeing claims within one Scope, or between two. A contradiction is listed, and included in context, only for a caller acting for every Scope it spans. A claim in one Scope no longer reopens, hides, or changes another Scope's own contradiction.
  • Resolving a contradiction that spans more than one Scope requires scopeIds covering each of them. A caller acting for fewer receives 404.

Fixed

  • An entity or relationship ID can no longer move between Scopes: upserting an existing ID for another Scope returns 409 instead of creating a version owned by that Scope.

Migration

  • Pass scopeId on reads and tombstones made for one Scope, and scopeIds when resolving a contradiction that spans Scopes.
  • Use a new ID for an entity or relationship that belongs in a different Scope.
  • Contradictions recorded before this release keep their IDs and history. New disagreements between Scopes receive new contradiction IDs.

Compatibility

  • REST API: compatible for single-Scope use; the changes above apply to requests that cross Scopes
  • TypeScript SDK: compatible (new optional fields)
  • CLI: compatible
  • MCP tools: compatible

Amazon Bedrock

Roadmap