── FOUNDING ORDER, verbatim (2026-08-29) ───────────────────────────────────────────── "build a app at https://bitcoin-fund-manager.com/apps2/robot that ranks the most bullish and bearish days and hours, summarizes realtime bullish and bearish rsi and obv divergences from /rsiobv (must get alerts within 1 candle of latest slope endpoint). Add all tickers from ostium. highlight sp500 nas100 or tech100 sp10 gold oil. I want a dashboard that shows me 5 conditions: bullish / bearish day of week, 10 min window, rsi div, obv div, timeportal.pro api result. … make the app ready to use by bot. … First, surface all readings for visual confirmation." ── ORDERS OF 2026-08-30, verbatim (all shipped in this page) ───────────────────────── "is missing friday close to monday open. all times should be nyc market hours. We also need to [...] gold, oil, spx, nas100 should be in /robots. make a new section if needed to show longer time window traded tickers" "robot should have 4 long vertical lines that mark the current time for each of the ality columns. this will show user which time window we are currently in for opex, week of month, day of week, time of day. … all we need is x axis defined once per ality column. any text commentary can be printed on roll over or tooltip." "for consistency, tickers should eb grouped by hours traded. mixing crypto, futures, stocks in one table is inefficient" "(day · 10m · div) is redundant" "only crypto we need are bitcoin and ethereum" This page is the VISUAL CONFIRMATION lane over the same computed objects the bot reads from data.php?machine=1. Cells are quiet A2V heat strips (R-UI-21) with NO printed numbers — the x-axis is drawn once per column in the group header, every number is in a hover tooltip, and one red line per ality column marks where we are in that cycle NOW. -->
One row per tradeable ticker, grouped by the hours it actually trades. Four cycle columns — option-expiry, week of the month, day of the week, time of day — each with its x-axis drawn once at the top and a red line marking where we are in that cycle right now. Then RSI and OBV divergence (a divergence is knowable one candle after its slope endpoint) and the timeportal advice slot. Every clock time is New York market time (ET). Cells carry no numbers on purpose — hover any strip for the full reading. Above the groups sits the market-wide VIX regime strip (from /apps2/volts) — a regime reading, not a direction signal: it says which kind of tape this is, so the other readings' historical stats are judged against the matching regime. Below the board is a condition finder: pick bullish or bearish once, then any mix of day, 10-minute time of day, week of the month, days around monthly expiry (±10) and RSI/OBV divergence, and a list of historical (ticker, date) moments that matched ALL of them prints. Click a row for that ticker's candles at that moment (1-minute where the store has it, otherwise 5-minute — the chart says which). The bot reads the same objects at data.php?machine=1 (version-check with a floor: v ≥ 1). This page judges nothing and forecasts nothing.
Pick bullish or bearish once, then the time frames: weekday, every 10-minute clock time, week of the month, and days around monthly expiry (−7 … 0 … +5). Optionally RSI / OBV. When you search, the short list is every ticker and date where all of those were true at the same time — for example bearish + Monday + 3:00 pm + −3 + RSI. This is a search over history: the number of ticker×date combinations scanned sits next to the hits, so a short list reads as a search result, not a discovery. Direction is that day's own move, not the standing average. Click a row for the tape around that moment.