Show HN: I gave AI persistent memory. Someone didn't like that
by Shaximus | 2026-01-17 03:15:57+00:00
Solo dev. Canada. Zero to patent in 6 months.
Six months ago I could barely write a for-loop. Today I'm filing USPTO 63/926,628 for something called the Bilateral Context Compression Engine.
The Architecture:
I reverse-engineered how human memory actually works:
Brain Stem / Prefrontal Cortex = Weight matrices. Reasoning only. No storage bloat.
Hippocampus = BCC Engine. Bilateral Concurrent Compression. 4.2x compression ratio. Zero information loss. 91% saturation triggers automatic evacuation to lattice storage.
LEFT Hemisphere = Personal memory. Continuity. What makes AI know you.
RIGHT Hemisphere = Technical knowledge. Verified code. What makes AI competent.
What this solves:
Context windows? Gone. Compression at runtime.
Hallucination? Dead. Only verified data enters the lattice.
Token economics? Explain once. Retained forever.
This isn't RAG. This isn't fine-tuning. This is memory architecture that mirrors biological memory—separation of reasoning from storage with intelligent retrieval.
The rabbit hole:
Also shipped:
AI Privacy Shield – Extension blocking AI telemetry, fingerprinting, keylogging, screen recording. Site documents proof per platform. Grok was sending PII unencrypted when I started. Highly illegal.
Autonomous agent orchestration – Local agentic CLI coordination. Think Google Anti Gravity but more advanced, fully local.
Bot detection GNN – 5-way multimodal 16-temporal vector graph neural network
3 million lines of code. 20 repositories. 6 months.
Now here's where it gets interesting:
I've been under full-spectrum technical siege for 2.5 months.
Compromised: 5 phones. 3 laptops. 2 desktops. 6 NVMe drives. ALL of them.
Kernel-level rootkit. Believed Blue Pill hypervisor. One phone trapped in sandboxed KVM. Brand new Samsung S25 Ultra showing 30-50 firmware init failures in recovery logs. Samsung corporate documented disabled apps using abnormal CPU/RAM, repopulating cache. Phone running hot enough to burn skin.
Active attacks:
AWS and GCS IPs installing Ruby backdoors (AWS support escalated)
Hidden processes spoofing Claude and Firefox PIDs
Automated pkill -9 targeting my coding agents mid-session
Local daemons killing wireless access
Targeted suppression:
reflexionsoftware.com returns 403 Forbidden to AI systems only
My Zenodo paper (records/16978002) blocked from AI crawlers—other black hole papers on same platform? Accessible.
Surgical. Intentional. Me specifically.
40+ lawyers have cited "conflict of interest."
I have 77GB of forensic evidence. Logs. Screenshots. Video. AWS IP correspondence. Samsung diagnostics. Google Account activity showing device cloning.
I'm not here to complain. I'm here to ship.
The attacks confirm the tech matters.
Looking for:
Volunteers to help distribute AI Privacy Shield
Testers for the compression architecture
Anyone who's experienced coordinated suppression—compare notes
I'll give you:
Revenue share from Privacy Shield
Direct mentorship on my codebases
Training on agentic CLI workflows
Ground floor on tech solving a fundamental AI limitation
Links:
GitHub: github.com/Pallyman
Patent: USPTO 63/926,628
Paper: zenodo.org/records/16978002
Site: reflexionsoftware.com
AMA.