ruvnet / ruvnet/RuVector

emergent-time: published state and follow-up work (crate v2.2.4, PR #561)

Open
#565 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
4.5k
Forks
603
Avg merge
23h 32m
Merged PRs (30d)
59

Description

Summary

emergent-time is published to crates.io (v2.2.4) and is on branch claude/emergent-time-quantum-db4z51 (PR #561). This issue tracks its current state and remaining work.

Current state

  • 72 tests pass; dependency-free; clippy clean.
  • Physics: Page–Wootters and thermal time faithful (independent recomputation); Wheeler–DeWitt and entropic time have discriminating tests added.
  • Performance: Page–Wootters evolution ~53× faster via cached eigenbasis, physics values unchanged.
  • Agentic Time: diagnostic layer (per-channel attribution, ATI, 7-state classifier) implemented and tested.

Measured benchmark result

On the two available real agent traces, with pre-registered thresholds and the agentic clock blinded to the predicted error signal:

Detector Agentic clock vs fair baseline
Fixed-window mean + 3σ 0 win / 1 tie / 1 loss
Adaptive Page–Hinkley 0 win / 0 tie / 2 loss

The agentic clock does not lead the fair baseline. The ADR baseline-dominance gate is marked unmet.

Follow-up work

  1. Larger real-trace corpus. The early-warning evaluation has n=2. A larger, pre-registered, instrumented corpus of real agent failures is the only path to establishing (or ruling out) an early-warning lead. The harness exists (examples/real_trace_eval.rs); the gap is data.

  2. Channel instrumentation. The current channel mappings are heuristic proxies extracted from session transcripts. A direct instrumentation of an agent runtime (emitting belief/memory/retrieval/goal/contradiction/plan deltas natively) would remove proxy noise.

  3. Provenance hash. The witness chain uses FNV-1a, which is an integrity/corruption check, not adversarial tamper-resistance. If the provenance is to resist a motivated tamperer, replace with a keyed cryptographic hash (e.g. BLAKE3 keyed mode, as in rvm-witness). The current docstring states this limitation; the README wording "tamper-evident" should be narrowed to "integrity/provenance."

  4. Wheeler–DeWitt non-trivial kernel. The discriminating test confirms a generic clock yields an empty kernel. A stronger demonstration would construct a kernel that arises from a genuine (non-energy-matched) resonance rather than by construction.

  5. Scale regime. Performance and recall numbers are at small n (≤32). The numerical core's behavior at larger n (eigensolver convergence, exponentiation cost) is untested.

Non-goals

  • The crate does not claim an early-warning lead over fair baselines; that is unproven on real data.
  • The physics modules are finite-dimensional toy realizations of the formalisms, not claims of new physics.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/adr/ADR-251-agentic-time.md and the existing examples/real_trace_eval.rs harness to understand the baseline and evaluation gap. The issue lists several independent follow-ups, from collecting real traces to changing provenance hashing and extending Wheeler–DeWitt tests, but does not define one bounded change or a single completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.