Skip to content

Dataflow: Persistent stratified negation #183

Closed as not planned
Closed as not planned

Description

@jsam

Problem

Negated results must reflect settled upstream revisions, without exposing transient false rows.

Evidence

Source: 5c1f313379a5cb2995a43a66ddba0b5cc9798b7f (inspected 2026-10-03). These are source findings; the acceptance scenarios below still need implementation and execution.

Acceptance criteria

Delivery

Plan item: D04. R4 - Persistent incremental dataflow.

Dependencies / related work: #182.

Contributes to #143; completing this slice alone does not close the broader issue.

Activity

  1. added
    backendBackend/server related
    P1Required next for reliable reactive delivery and operations
    on Oct 3, 2026
  2. jsam commented on Oct 4, 2026

    @jsam
    ContributorAuthor

    Moved to Later / deferred. Persistent incremental dataflow (R4) follows engine production readiness; every slice stays gated by the oracle and the perf gate.

    The neurosymbolic decision layer plan narrows the roadmap to two milestones: Engine production readiness (current focus), then Gateway neural integration (Jev, CLM, Laya) (#266). This issue stays open and can be pulled back in. Tracker: #199.

  3. jsam commented on Oct 5, 2026

    @jsam
    ContributorAuthor

    Superseded by #312 (V5) in the incremental-views plan, epic #305.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Required next for reliable reactive delivery and operationsbackendBackend/server related

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions