docs: define accepted-work identity and live queries (#170, partial)

CH
1mo ago
+71-18

Stack and deliberately partial scope

  • Refs #170; specification #180; delivery map #174.
  • Immediate stack parent: #206 (feat/effect-native-181-baseline, b52a42da2cb360c8dc676ab27db61452b30f04b9). This ordering is not a new semantic issue dependency.
  • Candidate: d3d967c84333fd1774fd08b53af19d838a7721f2; only docs/plans/effect-native-library.md changes relative to the parent.
  • Draft, unmerged; awaiting external review. #170 remains incomplete. This PR selects a bounded contract slice, not a production store or executable API.

Contracts recorded

  • Stable accepted-work identity and versioned request comparison, with key-first retry precedence and retained receipts.
  • Shared read-only execution-query semantics distinguishing status, authorized encoded payloads, unavailable results and released/non-durable owners. Reads neither launch work nor clear fences; IDs are not authority.
  • Explicit owner-selected policy: non-durable owner-local queries may expose typed live results and errors without codecs during the owning lifetime. Reads extend neither the owner nor referenced resources. Remote/persisted representations still require explicit encoding and authorization/redaction.
  • Worked race/failure scenarios and a precise unresolved list. Operation names remain semantic proposals, not exports. Exact heterogeneous live-query typing is not invented here.

ADR-0056 remains the policy authority; this delta does not duplicate or override it.

Review and checks

  • Independent Standards and Spec follow-ups confirm both earlier findings resolved; dedicated Ponytail review found no actionable complexity. The owner decision was obtained rather than inferred.
  • After final restack, both own commits retain identical range-diffs and the full-index per-PR delta is byte-identical to the reviewed candidate. Ancestry and whitespace checks pass.
  • At exact d3d967c: bun run check -- --force and bun run build:docs -- --force exit 0; working tree remains clean. Logs: /home/cyan/.local/state/mitome/effect-native-stack/170-parent-validation-d3d967c/.
  • Fresh frozen copyfile install and exact approved compiler verification passed on the preceding content-equivalent contract candidate. Install changed only the tracked CLI launcher's executable bit; its bytes were verified and its original mode restored. The resulting initial unchanged-tree check failure is preserved, followed by successful clean-tree reruns.
  • Examples are design checks, not executed runtime tests. No runtime, SQL/backend, native-platform or durability evidence is claimed by this documentation.

Still open

Concrete persistence/backend and synchronization qualification, remaining wire/schema/encoding and ownership/recovery boundaries, full query signatures, platform coverage and machine-failure evidence remain in #170 and dependent tickets. No SQL package addition or backend selection is authorized by this PR. No issue closure, merge or release.

Published-head CI verify passed. Parent verified merge ref a5354296e34b9ed4e41a255b4c4d4d078b5f406e has the same tree as d3d967c; full log retained. No external reviews/threads so far; the Changesets reminder is informational for this docs-only delta. A bounded feedback watcher is active; absence of comments is not approval.