Slice 6 — Datalog dialect migration #32
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
Depends on
#33 Slice 7 — selective semantic compilation
Ting/CurryComb
#42 Build: implementation Slices 2→7
Ting/CurryComb
#21 Deny-biased resolver port: verdicts, reasons, carried effects, ordering, failures
Ting/CurryComb
#23 Vedanta canary port (Migration proof 5)
Ting/CurryComb
#31 Slice 5 — targeted Rig extraction
Ting/CurryComb
Reference
Ting/CurryComb#32
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?
Change package: wiki OpenSpec-32-datalog-migration — authoritative engineering contract for this Session.
One decision schema and Datalog dialect across CurryComb, Jostoph, and Vedanta without a shared central database. The replacement MUST preserve typed values, guard semantics, recursion, deny-biased resolution, effect-to-claim joins, deterministic ordering, rule digests, and pure evaluation (
docs/handoff.md§Datalog unification).Tasks
Exit (handoff)
The estate uses one decision schema and Datalog dialect without a shared central database. Ascent retires only after the parity gate.
Slice 6 — Datalog dialect migration
State:
open· Labels: Kind/Enhancement, Meta/Session · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.
The Session must carry a conformant record: one-line outcome, an explicit child acceptance/exit scenario, and named gate edges. It must state that contract rather than delegating it to wiki or handoff pointers. Audit G42, grooming audit 2026-09-19/20.