Docs

What is the minimal-touch design standard?

Every tool in the platform must be fully operable from the UI with no terminal, no manual setup, and no configuration steps. A single button starts the backend, connects the data stream, and begins monitoring. The same button tears it down. If using a tool requires opening a shell, the design is incomplete.

How does the platform report its own state?

Status indicators, log panels, and connection state are built into every tool surface. You see exactly what is running, what data is arriving, and what any errors mean without asking. Errors include actionable context, not just a code.

What happens when a backend is unavailable?

Tools show the last known state with a timestamp rather than a blank screen. The Market Motion Compass, for example, rehydrates from a local SQLite snapshot on startup so there is always a valid reading displayed, even outside market hours.

When do external docs update?

Docs update when a feature is viable and intentionally available to users. Stable features get full public reference coverage. Some experimental labs may appear here in a clearly labeled preview form when the privacy model, user intent, and constraints need to be made legible before production launch.

What is the Rooted Reality Platform?

A human-layer intelligence platform for decision workflows. It gives you structured signal tools, not trade recommendations, to help you observe market conditions, assess cognitive state, and act with more deliberate context.

What do I need to run the platform?

Public docs are viewable in any modern browser. Authenticated product surfaces may include a local backend for live data and are launched from the product UI with no terminal setup required.

Is this connected to my brokerage account?

No. The platform has no broker integration. It reads public market data for context only. It cannot place, modify, or cancel orders.

What is the Digital Presence Risk Lab?

An experimental MVP 1 dashboard for a local-first personal digital behavior tool. It is designed to help a user understand category time, repeated short-check loops, attention fragmentation, late-night drift, and self-defined goal posture without sending behavior data to external servers.

What does it capture in MVP 1?

The intended desktop product is metadata-first: active application, window state, normalized browser hostname, timestamps, usage sessions, and user-defined goals. Screenshot-assisted analysis is optional, disabled by default, and not required for the MVP 1 dashboard to be useful.

Does it inspect messages, page content, or full browsing history?

No. The design target is pattern analysis, not content inspection. The tool is intended to operate on timing, app focus, domain-level metadata, switching behavior, and self-defined rules. It should not store full URLs, message contents, keystrokes, or hidden session recordings.

What kinds of signals does the lab surface?

Five explainable signals: Explicit Exposure, Compulsive Use, Social Media Drift, Attention Fragmentation, and Goal Violations. These roll up into an overall digital presence risk view with plain-language explanations such as repeated returns to social media, late-night drift windows, and shortened focus blocks.

Is this a monitoring or surveillance product?

No. The product framing is self-awareness and consent-based use only. It is not intended for employers, covert partner monitoring, or hidden observation of another person. The privacy model requires visible capture state, explicit consent, and local delete/export controls.

What is live today?

MVP 3 is complete for the authenticated desktop product preview. Current capabilities include multi-profile support, first-launch onboarding, browser extension ingest, local rule enforcement, Guardian review flows, and macOS/Windows foreground capture architecture. The public docs describe these capabilities, but the interactive product surface is not publicly exposed.

How will the desktop app be distributed?

The target distribution model is a single installer file with no terminal and no manual extension load. The current prototype requires loading the extension manually from `apps/browser-extension/` via Chrome developer mode. The design target is a bundled `.exe` installer that handles both the Tauri app and the Chrome extension, with Store and managed deployment paths later.

What does the compass show?

Six vol-normalized macro signals computed from 1-minute price bars across eight assets: S&P Futures (ES), Nasdaq Futures (NQ), Crude Oil (CL), Gold (GC), 10Y Treasury Futures (ZN), Dollar Index (DXY), VIX proxy (VX), and Bitcoin (BTC). Signals update every 60 seconds when the backend is running.

What are the six signals?

Pressure (broad risk-on/off momentum), Velocity (rate of change across the core tape), Volatility (VIX level relative to a calm baseline of 20), Haven Bid (safety asset momentum: ZN + GC + DXY), Rotation (safety momentum minus risk momentum), and Contagion (directional agreement across core assets).

What do the five regime states mean?

Defensive Rotation: risk assets selling, safety assets being bid. Risk Expansion: risk assets bid, rotation negative. Macro Instability: high velocity and elevated volatility simultaneously. Systemic Risk: contagion above 1.25 with broad pressure. Mixed / Transitional: no dominant regime signal.

How do I start the live feed?

Click Go Live on the compass. It starts the data backend, waits for the warm-up fetch, then connects the live stream automatically. One click with no terminal commands.

Where does the market data come from?

Yahoo Finance (yfinance), fetched every 60 seconds as 1-minute bars over a 2-day rolling window. Data is free and public. It is bar data with a small delay, not tick data.

Does the compass work when the market is closed?

Yes. The backend persists the last snapshot to a local SQLite database. On restart it rehydrates the last known state so the compass shows the most recent valid reading rather than a blank screen.

What is a shock event?

A shock is flagged when velocity exceeds 0.75 and at least one of the following is also true: rotation above +/-0.008, volatility above 0.25, or contagion above 1.25. The compass center circle pulses red and a shock indicator appears.

Why vol-normalize the signals?

Raw returns from BTC and ES are incomparable because BTC often moves 3-4x more per minute. Vol normalization divides each asset's return by its typical daily move, so all eight assets contribute proportionally to cross-asset readings. BTC and CL are down-weighted further in the Pressure signal to reduce noise.

Why is VIX excluded from Velocity?

VIX measures implied volatility sentiment, not tape acceleration. Including it would make Velocity react to fear spikes rather than actual price momentum. Velocity is intended to capture the speed of the core macro tape (ES, NQ, CL, GC, ZN, DXY).

Why is BTC excluded from Contagion?

Contagion measures directional agreement across the core macro tape. BTC often moves on crypto-specific news that has no macro cause. Including it would generate false contagion readings during crypto-only events.

Are these signals validated for production trading?

No. The compass is an experimental lab. Signal definitions and thresholds are research-grade and have not been backtested or validated against live trading outcomes. Treat it as a structured observation tool, not a signal service.

Where can a customer or reviewer read the current trust docs?

Use `/trust` as the entry point. It links the public privacy, terms, and data-handling pages and explains the current launch boundary for the digital-presence product.

What is the current commercial scope?

The lean path is Individual subscriptions first. Team and enterprise motions stay blocked until the required disclosure update is complete. If team features later ship, the manager view remains aggregate-only with no individual raw-data surface.

What data boundary should reviewers understand first?

Behavioral posture data stays local to the device by default. Server-side systems are for account, billing, and license state only, plus any future aggregate sharing flow that a user explicitly opts into.

Does the platform collect my data?

No analytics or tracking are embedded in the platform. No session data, keystrokes, or user behavior is recorded or transmitted externally.

How would the Digital Presence Risk tool handle screenshots?

Only as an optional local-only mode. Screenshot sampling is designed to be disabled by default, limited to the active window, and processed locally. Raw image retention should stay off unless the user explicitly enables it. The MVP 1 dashboard does not require screenshots at all.

Is market data stored anywhere?

Snapshots are stored in a local SQLite file (app/market_motion.db) on your own machine. Nothing is sent to external servers. You can delete this file at any time.

Does the platform call any external APIs?

Only when the Market Motion Compass backend is running. It makes one batched request to Yahoo Finance every 60 seconds to fetch price bars. No other external calls are made.