Shared value + relation schema crate: typed values replace Jostoph Atom #20
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#32 Slice 6 — Datalog dialect migration
Ting/CurryComb
Reference
Ting/CurryComb#20
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Proposal
One cross-runtime schema for
event/subject/field/nests/… values, replacing Jostoph's RustAtomand its JSON-text effect parameters — behind the byte-stable serialization gate that already exists (docs/spec/canonical-serialization.md; handoff §Minimal shared relation model).Specification-completion clause (OD-6 / #39)
The canonical home (repo/crate name for the shared schema and resolver) awaits OD-6. Content and interface are decided here; placement is the seam — file locally in CurryComb first; the ruling moves it with a re-export shim.
Tasks
Requirement scenario
GIVEN one logical value, WHEN Rust, and (fixture-driven) any second-language encoder serialize it, THEN bytes match the golden digests in §5 of the canonical serialization spec.
Shared value + relation schema crate: typed values replace Jostoph Atom
State:
open· Labels: Kind/Enhancement · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.