FreedomCore last 12 hours: Pumphouse hardening, live chart cards, Atlas cleanup, token council prep

This note records the visible work completed across the FreedomCore franchise during the latest overnight build window into 15 May 2026. It is written as a dated system note, not a launch announcement. The useful question is simple: what changed, what became more reliable, and what is now ready for the next council or operator decision.

Pumphouse moved from visual tracker toward alpha infrastructure

The Pumphouse audit started from a hard complaint: the paper demo looked frozen, the tracker cards were not recognisable enough, and the earlier council had identified real alpha components that were still not built. The response was not cosmetic only. The system now has a clearer map of what exists and what still has to mature: SPL holder scanning, wallet graph building, PumpSwap Phase 0 capture, migration mint repair, local historical harness work, and paper-demo ledger visibility.

The paper demo issue was especially important. The demo had not stopped because intake was dead. It looked static because the available paper slots had filled overnight and the old recycle rules only freed slots at a deep loss threshold or a large multiple. The recycle policy was tightened for paper-ledger use: a clearer stop, a time-out for stale non-bonded entries, a sell-half-on-bond rule, and live card metadata showing current value, age, exit rule, active open-slot state, active PnL, closed PnL, total paper demo equity, and latest ledger timestamp. That makes the demo legible as a learning system instead of a black box.

The Pumphouse page also stopped fighting the phone. Auto-refresh now waits until the page is idle at the top, so scrolling a board no longer gets dragged back to the header. Cards now expose token names alongside contract addresses, so early candidates can be recognised without treating every card like a raw address blob. The price ladder was corrected from the old high-end joke tier toward a more plausible product ladder, with the visible top tier moved down to £99.

Maverick got a visible trading-card surface

Maverick had a separate problem: live position cards and chart cards did not feel like a trading terminal. The public Maverick positions, Streamline symbol overlays, and the Flask-rendered /live page have now moved toward a Hyperliquid-style visual model: darker chart-first panels, dense symbol and price strips, mobile svh chart heights, visible TradingView toolbar controls, and a cleaner live-position layout.

The important correction came after the first pass. The public homepage and Streamline had changed, but the operator was viewing /live, which is a separate Flask template. That template still rendered a small stat card. The /live template now renders each open position as a full chart card, including a TradingView iframe, KuCoin symbol, PnL tile, entry tile, mark tile, and route tile. The dashboard service was restarted only to reload that template. The trading engine, order path, stop path, wallet path, and leverage path were not touched.

Atlas is being refocused back to research

Atlas had one confusing product split. The page exposed a SHADOW Alpha Feed CTA inside the Atlas hero and mobile menu. That link led toward a wallet/alpha structure that belongs in SHADOW, not in a cross-asset research terminal. It has now been removed from Atlas. Atlas points users toward Research Notes, Symbol Coverage, Templates, Docs, and subscription access instead.

That matters because the surfaces need clean jobs. Atlas is the research and market-intelligence layer. SHADOW is the wallet-copying and Hyperliquid attribution layer. ARENA is the public wallet proof layer. Maverick is the autonomous trading engine. Pumphouse is the Solana meme-coin tracker. When Atlas links directly into wallet-alpha output, the franchise map becomes harder to understand. Removing that CTA makes the product family easier to explain.

Council and memory infrastructure stayed in the loop

The FCORE tokenomics 20-round council completed overnight with Codex GPT-5.5 present as a high-court seat. That run produced a conservative verdict, but the operator has now asked a different question: not whether a token exists, but how the token should be structured if tokenisation is the chosen path. That distinction is being turned into a new council brief so the next run evaluates supply, utility, burn design, rewards, access gates, launch venue, treasury, community rights, and product-surface mapping under a token-first assumption.

The council memory path is still important. Prior token councils, product-surface councils, SEO councils, Pumphouse councils, and the current upgrade ledger all become source context. The next council should not deliberate cold, and it should not accidentally re-answer the previous question. The useful output is a tokenisation implementation charter: what gets token-gated, what stays public for SEO, what stays Stripe-compatible, what gets burned or consumed, what holder utilities exist, and what the operator must approve before any irreversible action.

Current state after the window

The latest build window improved three things at once: product clarity, visible proof, and operator control. Pumphouse has a stronger data path and paper-demo presentation. Maverick live cards now look and behave more like trading cards. Atlas has been cleaned back toward research notes and symbol coverage. The token discussion is being reframed as an implementation design council rather than another abstract argument about whether tokenisation should ever happen.

The next practical actions are narrow. Atlas needs the new note indexed. Pumphouse needs the real wallet graph and holder scanner to continue maturing against live data. SHADOW should own alpha/wallet surfaces. Maverick should keep its live trading state separate from public chart cosmetics. The token council should produce a buildable charter, not motivational copy.

This note is the handoff point for that next step.