The first system that doesn't just store context for Claude — it enforces it. Built from real trading sessions. Zero installation. Works in claude.ai chat.
Every Claude memory solution stores your rules as passive text. Claude reads them — sometimes. Under pressure, during fast analysis, when things get complex — it skips steps. That's how a R1,046 account nearly got wiped on one trade.
Claude's built-in memory stores rules as suggestions. Process steps get skipped when Claude is under pressure to respond quickly.
claude-mem, claude-memory, supermemory — all require npm, Python, terminals, and background processes. Not for regular users.
Remembering a rule and being blocked from breaking it are completely different things. No existing system enforces — they only remind.
Every new chat, Claude starts from zero. Months of learned behaviour, rules, and lessons — gone. You re-explain everything.
| Feature | Other Solutions | Claude ECS |
|---|---|---|
| Works in claude.ai chat | ✗ Claude Code only | ✓ Any interface |
| Zero installation | ✗ npm / Python required | ✓ Nothing to install |
| Rule enforcement | ✗ Passive memory only | ✓ Enforcer blocks violations |
| Human readable | ✗ SQLite / vector DBs | ✓ Plain markdown file |
| User can edit directly | ✗ Technical skill required | ✓ Edit on GitHub in browser |
| Verification protocol | ✗ Not available | ✓ Confirmation phrase |
| Pre-action checklists | ✗ Not available | ✓ Built-in enforcer |
| Portable across accounts | ✗ Tied to local machine | ✓ Any Claude, anywhere |
| Setup time | ✗ Hours to days | ✓ Under 10 minutes |
Enterprise implementations available — contact for pricing. Community tier is and will always remain free.
Claude ECS wasn't designed in theory. It was built through real live trading sessions on a R1,046 demo account — with real mistakes, real losses, and real lessons committed to GitHub after every session.
After a near-miss where Claude placed a Gold trade risking R1,042 on a R1,046 account due to wrong lot sizing, the question became: how do we build a system that Claude actually follows — not just reads?
The answer became the External Context System. Week 1 results: +R2,297 profit. Rules violated after system setup: zero.
Evan also builds ClockPay — a biometric time-attendance and payroll system for South African SMEs — and is the founder of the Claude ECS open source community.