Stabilize and release the public Stack Encrypt Rust API with explicit ownership/context semantics, interoperable ciphertext and query behavior, and executable conformance guarantees.
This milestone tracks both API refactoring and cross-language conformance. Release gates and supported versions (#1490) owns the final release checklist, version/capability matrix, and explicit required-versus-deferred decisions. Python/TypeScript delivery and proposed packaging changes are tracked here for visibility; their inclusion alone does not decide whether they block Rust stability. No release version or deadline is set.
Suggested sequence: finish the current PR stack; implement context-composition conformance; resume owned collection and record migration while expanding EQL/JSON evidence; remove transitional APIs after their consumers migrate. Broader runners, artifact exchange and test consolidation proceed alongside the refactor.
Conformance:
- Context composition (#1475) — next implementation slice.
- EQL and JSON/SQL profiles (#1476).
- Value, refusal and raw-frame gaps (#1477); reuse query-refusal baseline (#1317).
- Fresh artifact exchange and released-version pairs (#1478).
- Python runner/parity (#1393) and TypeScript runner and SDK mappings (#1479).
- Lifecycle, cleanup and key I/O (#1480).
- Consolidate duplicate expectations after coverage parity (#1481).
Refactoring:
- Owned collection conversions (#1482).
- Record derives, plans and owned declarations (#1483).
- Explicit whole-value blobs (#1484).
- Typed encoded ciphertext targets and tag access (#1485).
- Configured definitions and query APIs (#1486); reuse typed Rust JSON queries (#1459).
- Ciphertext binding versus search scope (#1487).
- Remove legacy traits and redundant execution APIs (#1488).
- Crate ownership and naming decision/migration (#1489); reconcile index-crate extraction (#1063).
- Reuse secure Buffer adoption (#1468) and key storage/copy removal (#1458) for cleanup implementation.
Compatibility policy: EQL and persisted-data guarantees (#1314). Preserve released SDK/storage/search contracts as implementation moves; do not introduce prototype-only compatibility scaffolding.
Existing stack: #1470 (PR #1404, scalar API), #1471 (PR #1460, scalar/declaration conformance), #1472 (PR #1461, runtime), #1473 (PR #1462, reads), #1474 (PR #1469, value/query fixture enrollment).
Plans: API redesign #1365 and conformance roadmap.
Issues
- Unread#1491 opened
Nov 1, 2026 · UpdatedNov 1, 2026 - Unread#1492 opened
Nov 1, 2026 · UpdatedNov 2, 2026