Deny-biased resolver port: verdicts, reasons, carried effects, ordering, failures #21
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#21
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
Port the resolver before application rules (handoff §Migration proof 2). The Mnestic evaluator preserves everything §Datalog unification requires; denial and evaluation failure win; only decisive claims carry effects; ordering is deterministic.
Tasks
Requirement scenario
GIVEN conflicting claims, WHEN the resolver runs, THEN the deny-biased outcome, carried effects, and output order are a deterministic function of (facts, rule digest).
Deny-biased resolver port: verdicts, reasons, carried effects, ordering, failures
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.