Jason Shen / Trading infrastructure · AI workflows · memory systems
Inspectable systems for trading, AI workflows, and memory under pressure.
I build systems where internal state is not allowed to pretend it is truth.
Trading infrastructure taught me one hard rule: intent, memory, risk, and provider-confirmed state must remain separate enough to be reviewed. This site is where I make those boundaries visible across trading systems, AI workflows, and memory infrastructure.
Three System Lanes
Boundaries that stay inspectable.
Trading Infrastructure
Execution, risk boundaries, reconciliation, monitoring, and provider-confirmed truth.
Status
Trading State Replay is inspectable now.
Open case file →
AgentOS
Durable memory, ephemeral context, human review gates, and filesystem-backed continuity.
Status
Exploration shell; memory model note pending.
Open case file →
AI Workflow Runtime
Intent → plan → tools → verification → artifact handoff.
Status
Case-file shell; workflow trace under construction.
Open case file →
System Map
Source, core, validation.
Writing Entry
Notes, essays, and build logs.
Eigenstate keeps its internal shelf names, but the entry paths stay plain: notes for field fragments, essays for durable arguments, and lab for traces.
Collaboration Entry
Start with context.
Best fit:
- trading, execution, or risk systems with unclear state boundaries
- AI workflows that need memory, review, and tool discipline
- technical partner conversations around infra-heavy products