[coderdan]

Summary

This adds a plan for using encrypted JSON documents from Go. json_tree is the EQL v4 type family (EQL is the SQL library installed into a customer's PostgreSQL database) for an encrypted JSON document. It supports containment, equality and ordering at a path, -> extraction and subtree walks. Rust can use it today; Go cannot.

The plan's main finding is that most of the work is in Rust. The Go SDK reaches the engine only through a data plan, and the engine refuses the JSON index there. The family is also missing from the EQL catalog, so no Go types are generated for it.

Changes

• docs/plans/2026-10-24-go-json-tree.md:
  • the constraints that come from the SDK design principles;
  • the proposed Go surface (struct tags, generated query methods, the SQL each feeds);
  • five PR-sized steps;
  • five decisions, each with a recommendation;
  • open questions.

Verification

Documentation only. The claims about the code were read from this branch (#1336) and from next (#1229), with file references in the plan. Nothing was run.

Related

• Tracking issue: Tracking: encrypted JSON documents (json_tree) in the Go SDK #1347
• Steps: json_tree is missing from the EQL catalog, so no Go types are generated for it #1348 (catalog), Stack Encrypt refuses the JSON index in a data plan, so the Go SDK cannot seal a json_tree document #1349 (data-plan form), json_tree operators (@>, <@, equality and ordering at a path, ->) have no data-plan form #1350 (query by operator), Go SDK: declare, store and query json_tree fields with stashgen #1351 (Go SDK), Go SDK: decrypt json_tree extracted entries and subtree walks #1352 (extraction and walks)
• Builds on feat(stack-encrypt, eql): the JSON index and the json_tree EQL v4 domain family #1288, perf(eql, stack-encrypt): store the json_tree projection, walk by parent map, budget the subtree #1325, feat(eql, stack-encrypt): chain json_tree tokens by ordinal and probe the walk to the first miss #1329, test(eql): hold the planner to the json_tree indexes on every supported PostgreSQL, and document what the tree reveals #1336 and test: hold json_tree containment to jsonb with proptest, and restructure the JSON index tests #1345.

Review notes

The section to review first is Decisions needed. Step 4 (#1351) waits on those answers, while steps 1-3 can start without them. This is stacked on #1336 so that it can cite the json_tree code. It changes no code.

https://claude.ai/code/session_01XQN1QpaWVDGjHEg39KEJF3

[changeset-bot]

⚠️ No Changeset found

Latest commit: 65ece53

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}