Skip to content

Add restart-safe proactive runtime with MetaHarness and WASM - #3

Open
ruvnet wants to merge 13 commits into
mainfrom
feat/proactive-metaharness
Open

ruvnet wants to merge 13 commits into
mainfrom
feat/proactive-metaharness

Conversation

@ruvnet

@ruvnet ruvnet commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

Adds @ruvbot/proactive alongside the existing chatbot, turning Build Your Own Duet guidance into three ADRs and executable contracts.

Attention: bounded polling, source-qualified deduplication, persistent cursors, severity floors, stale-event filtering and quiet-hour deferral. P0 and imminent deadlines still alert.

Work: immutable expiring approval packets; edits revoke prior approval; host permissions and outbound checks gate dispatch. Optional private single-writer snapshots persist executing receipts before dispatch. Interrupted actions recover as uncertain and cannot automatically retry. Storage faults halt mutation. Stale locks require explicit operator reconciliation.

MetaHarness: pinned npm kernel 0.1.3, truthful backend reporting, separate reproducible 86-byte WASM promotion predicate, proposal-only learning and labelled replay evaluation.

Validation: 23 tests pass locally and GitHub CI passes on Node 20, 22 and 24. CI verifies WASM rebuild parity, tests, synthetic benchmark, demo, doctor and npm packaging. Tests include actual process exit during dispatch, corrupt approval recovery rejection, storage failure and concurrent execution. Fresh tarball install exposes the new store and evaluation modules. The original production dependency audit reported zero vulnerabilities.

Synthetic 1000-scenario replay (100 critical, 900 routine) returned 100% encoded-rule recall/precision/accuracy in approximately 13 ms locally. This is regression evidence, not real-world quality evidence.

Production boundaries: no deployed scheduler, chatbot UI, live connectors, authenticated approval API, durable notification outbox or distributed execution. Snapshots contain plaintext action payloads and require protected host storage. MetaHarness's published WASM artifact is absent, so doctor reports JS; ruvbot's own WASM predicate executes in tests. No publication, production activation or merge performed.

@ruvnet ruvnet changed the title Add governed proactive runtime with MetaHarness npm and WASM gate Add restart-safe proactive runtime with MetaHarness and WASM Oct 24, 2026
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.

2 participants