Skip to content

docs: flow/cog convergence for ONA and two Rubicon lineages - #1543

Merged
AdaWorldAPI merged 2 commits into
mainfrom
docs/flow-cog-rubicon-ona-convergence-20261013
Oct 13, 2026
Merged

AdaWorldAPI merged 2 commits into
mainfrom
docs/flow-cog-rubicon-ona-convergence-20261013

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

Follow-up to merged #1536 (and #1539 corrections)

Fresh branch from current main (350d30aa9f06ea3e700fd11e5d6e9c4a0a51b2ea), not a rebase of the already merged docs branch.

Research-backed design decision

An integrated cognitive method substrate around existing LanceGraph, OGAR, rs-graph-llm/graph-flow and z8run, reconciling:

  • Supabase-shaped callcenter + ractor supervisor, with honest admission/dispatch/restart gaps.
  • Existing graph-flow-lance ↔ z8run-lance handle bridge. No duplicate session runner/registry, no rows in workflow messages.
  • Optional Rig completion/tool interface, with text never implicitly promoted to evidence.
  • ONA NAL truth/revision/inference → global lance-graph-r2il FoldDialect → mask-risc/ndarray.
  • Two Rubicon traditions: Heckhausen/Gollwitzer deliberation/commitment/implementation intentions; O'Reilly/Axon benefit-cost/goal maintenance/outcome credit assignment. Separate NAL confidence, expected utility and authorization.
  • OpenCog/Hyperon-style expression composition and OpenPsi motivation as candidate pure methods, not a second AtomSpace or execution engine.

The four names lance-graph-flow, lance-graph-rig, lance-graph-z8, lance-graph-cog are conditional integration surfaces, not a mandate to create four duplicative crates.

Files

  1. D-FLOW-COG architecture: exact ownership, dependency direction, method and goal contracts, flow sequence, anti-duplication tests, staged F0–F6 milestones.
  2. Work implementation handoff: fresh-main/rebase safety, source audit, minimal executable W3 falsifier, two-lineage Rubicon extension, tests and separate coding PR requirements.

Validation

  • Branch is 2 commits ahead and 0 behind main; only two new Markdown files, no Cargo or runtime changes.
  • 19 internal relative Markdown links checked, none broken; fences balanced.
  • No compilation or tests run: documentation/prompt-only PR.

Guardrails

Prior Codex review corrections in #1539 are preserved: ONA oracle at dc4efd0..., supervisor restart backoff is NOT applied, dispatched non-Health work is not wired, declared mailbox bound is unenforced, and realtime drain is unbounded. The implementation follow-up must neither declare these production-safe nor bypass the canonical action gate.

Draft for architectural review; do not merge automatically. The Work handoff should create a separate smallest actual code PR after checking the current live source.

@coderabbitai

coderabbitai Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 9dcb9047-0b2f-4f0b-85ed-1b9fb8399642
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@AdaWorldAPI
AdaWorldAPI marked this pull request as ready for review October 13, 2026 19:46
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-13T19:48:41.138163Z 9a9413c Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@AdaWorldAPI
AdaWorldAPI merged commit fd974f4 into main Oct 13, 2026
1 check passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9a9413c86e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".


Given an observed service degradation and two possible remediation options:
1. Ingest two observed premises with distinct evidence roots and valid/knowledge epochs.
2. NAL W3 revision updates support for hypothesis H (first run must not claim W3 is built).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the plan to recognize the shipped W3 revision

When this handoff is followed, the staged work is directed to implement W3 and even instructed not to claim it exists, but the stated base 350d30a already contains merged PR #1538: nal::Revision, its R2IL/mask-risc lowering, evidence-overlap checks, and the independent oracle tests are present in crates/lance-graph-nal/tests/w3.rs. This stale status can cause a follow-up to duplicate or replace shipped work instead of selecting W4 or another genuinely absent method; update the inventory, example, and F1 milestone to consume the existing W3 implementation.

Useful? React with 👍 / 👎.

### What already exists (verified on current repositories)

- [`lance-graph-callcenter`](../../crates/lance-graph-callcenter/src/lib.rs) implements the external `ExternalMembrane` shaped by a partial Supabase transcode; `LanceMembrane` separates `ingest/project/subscribe`. The current server remains feature-gated and partly scaffolded.
- [`lance-graph-supervisor`](../../crates/lance-graph-supervisor/src/supervisor.rs) has ractor actor skeleton and lifecycle API; **non-Health `DispatchToG` returns `DispatchNotImplemented`**. `DEFAULT_MAILBOX_CAPACITY = 1024` is declared but not applied to the `Actor::spawn_linked` path. **Actual crash-restart backoff is not correctly applied; delayed respawns reschedule themselves** per #1539. Realtime drain in [`callcenter/drain.rs`](../../crates/lance-graph-callcenter/src/drain.rs) still uses unbounded mpsc. No production admission/backpressure claim.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Stop classifying the repaired supervisor backoff as broken

On the documented base, merged PR #1540 already repaired and tested this behavior: handle_supervisor_evt schedules exactly one delayed RespawnG, while the RespawnG handler spawns immediately and never reschedules itself (crates/lance-graph-supervisor/src/supervisor.rs). Treating backoff as a current defect can send the implementation handoff toward reworking fixed code and, together with the later instruction to disable respawn tests, weaken existing regression coverage; retain the dispatch/mailbox/drain caveats but mark restart backoff as shipped.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant