Neuruh Research Series

JGI Memory Workbench

Source: Jeramie General Intelligence (JGI V6) | Sections 33 to 46 and 162 | Founder working paper | Not peer reviewed | JGI is an internal engineering objective, not an AGI claim

Status: working tools built from the paper. Where the paper gives a formula, the tool uses it. Where the paper gives no formula, the tool says so and labels its rule an illustrative implementation of the paper's concept.

33. Memory Architecture

Use several distinct memory layers.

Working memory. Current mission context.

Episodic memory. What happened.

Semantic memory. Facts and relationships.

Procedural memory. How to do things.

Negative memory. What failed and why.

Strategic memory. Goals, decisions and business rationale.

Capability memory. What the organism can actually do.

Epistemic memory. Confidence, contradictions and provenance.

Do not collapse these into one embedding index.

34. Memory Write Gate

Every durable memory write answers:

35. Memory Decay

Operational knowledge becomes stale.

Use half-life decay where appropriate.

Freshness: F(t) = 2^(-t/h) where t is age and h is domain-specific half-life.

Examples: runtime state, minutes; repo state, hours; lead state, days; business strategy, weeks/months; historical fact, years.

36. Memory Consolidation

Periodically compress large episodic histories.

Do not delete raw evidence.

Create higher-order summaries with backlinks.

Process: episodes, recurring patterns, candidate lessons, Sentinel validation, semantic/procedural memory.

Preserve provenance.

37. Negative Knowledge

JGI must remember what not to do.

Record: failed method, reason, environment, evidence, correction, whether failure was intrinsic or contextual.

Negative knowledge should prevent repeated expensive mistakes.

38. Contradiction Graph

Contradictions are objects, not annoyances.

A contradiction records: claim A, claim B, sources, freshness, authority, possible resolution, impact.

Prioritize contradictions based on whether resolving them changes action.

39. Context Compiler

For each worker solve a constrained context-selection problem.

Maximize relevant information utility, subject to token budget.

Factors: relevance, source authority, freshness, confidence, directness, diversity.

Use redundancy penalty.

Do not provide every agent the entire estate.

40. Information Bottleneck Principle

Compress context while preserving decision-relevant information.

A good context pack should minimize irrelevant entropy while retaining information needed to produce correct action.

41. Code Custody Intelligence

Continuously reconstruct: repositories, remotes, branches, SHAs, worktrees, stashes, dirty tracked files, untracked files, local-only commits, remote-only work, deployments, CI, ownership, mission bindings.

Never confuse GitHub, local work, Cursor work, and deployment.

42. Cursor Intelligence

Treat Cursor as a volatile execution/work surface.

Recover: workspace, repo, branch, active worktree, modified files, processes, explicit agent task state, visible artifacts, recent outputs.

Do not treat chat text as completion proof.

Preserve stranded work.

43. Stranded Intelligence Recovery

Continuously hunt for valuable orphaned work.

Examples: old branches, stashes, unfinished prototypes, partial algorithms, datasets, scripts, automation, research, prompts, internal tools.

Score: uniqueness, recoverability, economic potential, integration cost, freshness.

Do not delete merely because current value seems low.

44. Provenance Graph

Every important artifact should answer:

This enables reproducibility.

45. Temporal Intelligence

JGI maintains timelines.

Understand: what was true, what changed, when it changed, why it changed, what caused it.

Current state without temporal history is insufficient for learning.

46. Event Sourcing

Prefer immutable events plus derived projections where possible.

Events describe: something happened.

Projections describe: current interpretation.

This allows reconstruction.

Avoid uncontrolled mutable truth tables when event lineage matters.

162. Independent Backup Memory

Critical canonical state should be exportable/reconstructable.

Do not make cognition dependent on one vendor's conversation memory.

Tool 1. Memory Write Gate simulator (Section 34)

The paper lists the eight questions the gate asks. It gives no numeric thresholds. The rule below is an illustrative implementation of the paper's concept, not a formula from the paper.

No candidate evaluated yet.

Tool 2. Memory Decay calculator (Section 35)

Paper formula: F(t) = 2^(-t/h), where t is age and h is domain-specific half-life.

No computation yet.
Age tRetention F(t)

Tool 3. Contradiction Graph explorer (Section 38)

The paper says contradictions are objects with claim A, claim B, sources, freshness, authority, possible resolution, and impact, and to prioritize by whether resolving them changes action.

No contradictions recorded.

Tool 4. Negative Knowledge register (Section 37)

The paper says record failed method, reason, environment, evidence, correction, and whether failure was intrinsic or contextual. The register blocks re-adding a known-false claim so it is never relearned.

Register is empty.
No entries yet.

Tool 5. Consolidation Planner (Section 36)

The paper says compress large episodic histories, never delete raw evidence, and create higher-order summaries with backlinks. It gives no scoring formula. The rule below is an illustrative implementation: importance and age decide compress, keep working, or drop.

MemoryImportance 1-10Age (days)Recommendation
Not run
Not run
Not run
Not run
Not run
Planner has not run.

Tool 6. Context Compiler (Section 39)

The paper says maximize relevant information utility subject to token budget, using relevance, source authority, freshness, confidence, directness, and diversity, with a redundancy penalty. It gives no formula. The rule below is an illustrative implementation: items are ranked by utility per token, and a second item from the same source loses half its utility.

No packet built yet.

Tool 7. Provenance Graph viewer (Section 44)

The paper says every important artifact should answer where it came from, what sources contributed, which model and version created it, what evidence, which mission, which verification, and which outcome. Any link with missing provenance is flagged.

No provenance chain yet.