Bind output to evidence
Explore verified assertions and proof lineage instead of relying only on free-form memory summaries.
↳ Documented product behavior← Selected work
AI systems · Experimental research / 2026
Cortex Brain / RMVM
An experimental memory layer that combines a local proxy, encrypted storage and a bounded execution model with traceable assertions.
My role
System & interaction design / development
The scope
Rust · Python · TypeScript
Project status
Experimental research
The project, at a glance
- The challenge
- AI memory is difficult to inspect when the evidence behind an answer and changes to stored facts are hidden.
- My contribution
- I worked across memory architecture, evidence and verification contracts, local integration and developer-facing controls.
- What came out of it
- An experimental implementation and beta release with an evidence-oriented dashboard and evaluation work.
Experimental AI infrastructure / CortexMemory with
Memory with
a visible evidence trail.
01Connect02Structure the evidence03Inspect the trace
Original dashboard · Simulated status
Cortex Brain / RMVMOriginal dashboard UI · simulated status
01 / The question behind the work
Explore AI memory that can explain where an answer came from.
The problem
Free-form chat memory makes it difficult to understand which evidence influenced an answer, reconcile changing facts or clearly explain what forgetting means.
My contribution
Memory-system architecture, evidence and verification contracts, local integration workflow, provider setup and developer-facing controls.
What the work delivers
Rust memory kernel and proxy, Python and TypeScript SDKs, Encrypted store implementation, Browser connector, Local setup and status dashboard, Conformance fixtures and evaluation documentation.
02 / Design decisionsThe thinking
The thinking
in the details.
Specific choices, connected to the work you can see.
Keep execution bounded
Use a restricted plan model with cost and operation limits, allowing the kernel to reject unsupported execution shapes.
↳ Documented product behaviorExplain forgetting precisely
The documented forget action suppresses matching memory from future use; it does not promise permanent deletion of audit history.
↳ Documented product behaviorMake integration inspectable
A local dashboard exposes the selected brain, provider, model, endpoints and service health.
↳ Documented product behavior03 / Connecting the experience
How the pieces connect.
Select a stage to explore its purpose.
The moment
Configure a local brain and planner provider.
The design intention
Make the integration choices visible.
New portfolio explanation based on the documented implementation and original project material.
04 / Inside the experienceThe details.
The details.
With a purpose.
Selected views, framed to explain the work. Complete original artifacts are available in the source collection below.
Make the running configuration inspectable
The original dashboard surfaces proxy endpoints, provider, model and runtime health. This local capture uses simulated status and a clearly marked demo key.
CORTEX / MEMORY KERNELExperimental architecture
01A request, with context.Local proxy / SDK integration
↓
02 / STRUCTURE
A bounded plan.
Constrained execution
Traceable assertions
03 / RETAIN
Evidence, connected.
Encrypted storage
Source relationships
↓
04A response you can inspect.Trace metadata / evidence path
Suppression changes future use. Audit history remains distinct.
Explain how a request becomes traceable
This new diagram explains the documented architecture behind the dashboard. It describes an experimental system and does not establish production performance.
Original presentation boards1 source artifacts +
The complete originals behind this case study. Open a board to inspect the source presentation.
05 / What this work brings togetherCortex Brain / RMVM
Cortex Brain / RMVM
in perspective.
The result
A public experimental implementation and beta release. It demonstrates systems thinking and evaluation work, not established production security or elimination of hallucinations.
Sources & presentation notes +
Dashboard health is mock presentation data, not a live-system verification. No actual key or private memory appears in the capture. Keep experimental status visible. Do not use the earlier PCM 11× self-reported benchmark as a general Cortex product outcome.
The journey diagrams and editorial explanations were prepared for this portfolio from the available project evidence. They are not additional historical research or measured outcomes.
Keep exploring / Next project
From a remembered moment to a life story, with the author in control.