NEO5 — The Asymmetric Nexus Protocol
A multi-agent investment decision system built to identify asymmetric tech investments. What it was, what it produced, what the receipts show, and what it did not prove.
The mission, stated plainly
NEO5 was built to grow starting capital 100x over 15 years through asymmetric tech investments identified by an AI decision system.
The mission was written into the system’s founding documents. It was not a vague aspiration. It was the design brief.
What was built
The Asymmetric Nexus Protocol — NEO5. A multi-agent investment decision system.
The architecture:
- Multi-agent swarms. Early form: Fundamental Analyzer, Trend Analyzer, Risk Assessor, Valuation Model, Synthesis Engine. Later evolved into a named cast — Physicist, Scout, Surfer, Analyst, Skeptic, Futurist, Red Team, Bookie, Oracle — each with a distinct role in the reasoning chain.
- Data backbone. SimFin API for fundamentals, Stooq for technicals, an archive-driven signal pipeline.
- Capital Gate with permission ledger. A formal gate before any capital deployment — no position without a logged decision.
- Behavioral finance framework. Interrupts FOMO, action bias, sympathy chasing, and the disposition effect at the point of decision.
- Expectation gap engine. Ties market-implied price to what the business case actually supports — modeled on how Howard Marks thinks about price versus value.
157+ documented sprints, each with a proof note. Live at neo5.thessenchill.com.
What the system produced — the receipts
The manual-memo bake-off (April 2026)
Ticker: SMCI.
- Neo5 posture: Pass — explicit reason: fundamentals stale.
- Human analyst: “Track it — something here but need more data” (ambiguous).
- Scoring: Neo5 4/4 on calmness, 4/4 on structural falsifiability. Human analyst 2.5/4, 1/4.
Neo5 won the bake-off. A structured system produced a clearer, more falsifiable call than scattered reading.
The Delta-4 behavior proof (April 2026)
- Primary pick: AXON.
- Reason it wins: “60% software-grade margins.”
- Reason RKLB loses: “38% gross margin vs 60% for AXON.”
- Government demand grounded: “205 awards, $226.5M in 12 months.”
Neo5 was materially better than scattered tabs for choosing the next hour of research.
The Palantir timeline
The origin conviction — the call that predated the system.
- April 2024: First buy at $23. Pre-NEO5. Own thinking, no system.
- June–July 2024: Added at $25–$28.
- September 2024: 160 shares at $37.30. NEO5 era — system being built while the conviction was being acted on.
- October–December 2024: Continued adding through $44, $60, $66, $71.
- January 2025: Sold 76 shares at $77.50.
- PLTR hit $128 by May 2025. $198 by October 2025.
The system never flagged the sell. The system never intervened.
The consequence contract
A 30-day contract, written into the system. One rule:
Create one documented capital behavior change.
What counts: a blocked chase, a reduced size forced by valuation burden, an exit triggered by a broken thesis, a decision memo written before moving capital.
What does not count:
More documentation. More prompts. More architecture. More dashboards. More analysis that does not affect capital behavior.
Contract status: OPEN.
The Capital Behavior Proof Log has a table with 10 rows. All 10 rows are empty. That is the receipt.
What this proves — and what it does not
These are not contradictory findings. They are the same finding stated twice.
A system can be technically correct and still not change what the operator does. The system beat a human analyst in a controlled bake-off. The system correctly identified AXON over RKLB with explicit margin-based reasoning. The consequence contract — one real capital behavior change — was never closed.
The gap between “the system is right” and “the operator acted on it” is not a product problem. It is a behavior problem. And behavior problems are not solved by better dashboards, better signals, or better architecture.
The consequence contract made the gap visible. Most builders never write the contract. The gap stays invisible and gets misdiagnosed as a product problem forever.
What this does not prove
- The PLTR call at $23 predates NEO5. NEO5 did not find Palantir. It was built to replicate the judgment that found Palantir.
- The SMCI bake-off victory does not prove Neo5 would have produced a closed consequence entry. Winning a memo comparison is not the same as changing a capital act.
- A different operator with different habits and capital constraints might have closed the contract.
Tools and methods the project produced
NEO5 the investment system did not close its consequence contract. NEO5 the building process produced real, reusable infrastructure:
- The consequence contract — a diagnostic instrument. Write the contract before you build the system. If it cannot close, you are building for the satisfaction of building, not for the decision you said the system was for.
- The Capital Gate and permission ledger — a formal gate pattern now applied to other decision domains.
- The proof-versus-summary discipline — the distinction that became Relayfox’s file-truth architecture. Every agent produces a summary; proof is reviewable evidence that can be checked without trusting the chat.
- The behavioral finance interrupts — FOMO, action bias, sympathy chasing, disposition effect — named and routed, not just diagnosed.
The building was not wasted. The byproducts outlasted the original system’s open contract.
Current status
Repositioned as an evidence engine. The project has meaningful receipts and a clear behavioral thesis, but limited current product momentum. The public value is stronger as fieldwork, guides, and models than as product promotion.
The site stays live. The repo is frozen. The receipts stand.
Evidence map
Proof layers
- 01
Runs
provenThe system is live at neo5.thessenchill.com. 157+ documented sprints.
- 02
Inspectable
provenSprint docs, consequence log, bake-off result, and proof log are in the build repo.
- 03
Beats a benchmark
provenOutperformed a human analyst in a structured memo bake-off (4/4 vs 2.5/4).
- 04
Changes a decision
not yetOne real capital behavior change logged in the consequence contract.
- Status
- working
- Evidence
- verified local