v0.3.0 Release Recap
v0.3.0 is a pre-1.0, non-breaking release focused on making contextdb easier to inspect, explain, and tune in live systems. Existing write behavior remains unchanged by default; the new deduplication path is opt-in.
What Changed
| Area | New in v0.3.0 | Why it matters |
|---|---|---|
| GraphQL inspection | /graphql with search, filters, edges, sources, narratives, gaps, and feedback mutations | Gives apps and debugging tools a graph-shaped product surface without custom REST stitching |
| Score breakdowns | REST, gRPC, GraphQL, and Go SDK expose weighted score contributions | Makes retrieval ranking explainable: similarity, confidence, recency, and utility are visible per result |
| Feedback APIs | Validate, refute, mark useful, and mark stale across SDK, REST, gRPC, and GraphQL | Closes the loop between real outcomes and source/node credibility |
| Narrative retrieval | Go SDK, REST, and GraphQL return structured claim explanations | Turns "why does the system believe this?" into a first-class API |
| Knowledge gaps | Go SDK, REST, and GraphQL report sparse semantic regions | Helps agents and operators decide what information to acquire next |
| Write deduplication | Content fingerprint dedup can be enabled per write or server-wide | Reduces repeated embedding and storage work without changing default behavior |
| Docs and deployment | Feature matrix, GraphQL docs, and Mini/Norn deployment notes | Makes the live system and new surfaces easier to discover |
Non-Breaking Behavior
Deduplication is off by default. A repeated Write still creates a distinct node unless one of these is enabled:
| Surface | Opt-in |
|---|---|
| Go SDK per write | WriteRequest.Dedup |
| Go SDK default | Options.DedupWrites |
| REST per write | dedup: true |
| Server default | CONTEXTDB_DEDUP_WRITES=true |
| Explicit bypass | WriteRequest.SkipDedup or REST skip_dedup: true |
All response additions are additive fields or new endpoints. Existing REST/gRPC/SDK callers should continue to work.
Feature Tags
These tags are used throughout the docs and feature matrix:
| Tag | Meaning |
|---|---|
v0.3 | Introduced or substantially expanded in v0.3.0 |
non-breaking | Does not require existing clients to change |
inspectability | Helps developers understand or debug system behavior |
feedback-loop | Feeds user/operator outcomes back into ranking or credibility |
epistemics | Helps explain belief, uncertainty, contradiction, or missing knowledge |