The graph as the primary surface
Engines, missions, workflows, integrations, and data sources are nodes. Selecting a node opens the Inspector, which is how you navigate the system rather than a side panel you occasionally consult.
React Flow
BLKPVNTHR.OS Live
(opens os.blkpvnthr.com in a new tab)
BLKPVNTHR.OS
“The graph is the application — every node is clickable, opens the Inspector.” That is the product’s own in-app tagline, and it is the literal design of the system.
BLKPVNTHR.OS is an AI-native operating system for financial intelligence, quantitative research, knowledge management, and operational automation. The platform represents applications, workflows, integrations, research experiments, financial resources, and system capabilities as connected resources inside an interactive knowledge graph.
Live at os.blkpvnthr.com — opens in guest mode, no sign-up.
at a glance
The system in one screen
- Role
- Sole designer, engineer, and operator.
- Status
- Live and public. Opens in guest mode.
- Interface
- React 19, TypeScript, Vite, Tailwind v4, React Flow, Zustand, React Router 7.
- Services
- Supabase (auth + 6 Edge Functions), FastAPI research engine (Python).
- Integrations
- Plaid (read-only bank links), Alpaca (paper), Supabase.
- Infrastructure
- nginx on an Oracle Cloud VM; research engine on 127.0.0.1:8010 behind
/research-api. - Quality
- Vitest, oxlint.
the problem
Context is lost at every boundary
Financial tools, research systems, automation, knowledge, and operational workflows are typically fragmented across disconnected applications. The accounts live in one place, the research in another, the notes in a third, and the automation nowhere at all.
Each boundary between those applications is a place where context disappears. A hypothesis loses its link to the data that produced it. A balance loses its link to the goal it was supposed to serve. A workflow loses its link to the engine it was meant to trigger. The work of holding the whole picture together falls back on the person, every single time.
BLKPVNTHR.OS is a personal answer to that fragmentation, built and operated by one engineer. It is not investment advice, and it is paper-first.
the approach
A connected operating-system model
Rather than another dashboard, BLKPVNTHR.OS models everything it knows about as a resource, and every relationship between those resources as an edge. The graph is not a visualization bolted onto the app. The graph is the app.
Specialized engines
Finance, research, knowledge, trading, and automation are separate engines with their own routes and their own boundaries, so a change in one does not silently reach into another.
/engines/*
Terminal-style interaction
The landing surface is a terminal at root@blkpvnthr-os:~$. Typing start
opens the AI Brain. Commands are a first-class way into the system, not a hidden power-user mode.
Command interface
Source-backed intelligence
Analysis is tied back to the resources it came from. Evidence and provenance are modelled explicitly so a conclusion can be traced to the data and the experiment that produced it.
evidence_fusion
Modular workflows
Workflows, missions, and an event bus compose engines into repeatable operations, so automation is assembled from parts that already exist rather than written from scratch each time.
/workflows
Personal and organizational modes
The same operating model serves an individual tracking their own finances and goals, and a research operation running laboratories, schedules, and a strategy pipeline.
Guest mode available
capabilities
What the system actually does
BLKPVNTHR.OS is an AI-assisted wealth-building platform: an autonomous quantitative research pipeline with investment account integration, a Personal Accounting Agent with live bank account integrations, a career goal tracker, an emailing assistant, and a day-to-day personal assistant — designed to help everyday people learn how to build their wealth, keep track of their finances, and work toward their financial goals.
Financial intelligence
Net worth
The Finance engine presents itself as an accounting department that closes the books each month and tracks long-term net worth across linked accounts.
Personal Accounting Agent
An agent sits over the connected accounts and keeps the picture current, so goals and progress are read off the account data rather than maintained by hand.
Account aggregation
Bank accounts are connected through Plaid, and brokerage data through the Alpaca proxy.
Reporting and read-only workflows
Financial reporting is built on read-only data workflows. Balances only: no transfers, no trading.
/engines/finance
Quantitative research
The Research Division runs 18 laboratories against an explicit research lifecycle. A candidate has to survive the whole chain before anything downstream will look at it:
-
Observe and detect
Observation → phenomenon detection → hypothesis generation → counter-hypothesis.
-
Design and validate
Experimental design → statistical validation → economic validation.
-
Stress and replicate
Historical robustness → paper trading validation → replication.
-
Publish
Publication → market law → deployable strategy. The division states plainly: paper / research only.
Hypothesis and experiment tracking
Hypotheses, counter-hypotheses, and experiments are tracked as resources, not as scattered notebooks.
Strategy validation
Walk-forward analysis and regime-aware research sit inside the validation stages of the lifecycle.
Evidence and provenance
Results carry their sources, so a claim can be traced back to the run and the data behind it.
Python research engine
research_engine (FastAPI, stdlib-first), pattern_engine, alpha_discovery, evidence_fusion, strategy_lab.
/research-division
Trading infrastructure
Trading is paper-first: a strategy runs as paper-trading research, and live orders stay disabled until it clears the platform’s paper-trading threshold. Execution is kept separate from analysis — the research side proposes, and nothing it produces reaches a live venue on its own.
Paper-first execution
The trading page states the bar directly: live orders are disabled until a strategy consistently averages $100/day net in paper.
Risk gates
A trading discipline layer applies risk limits to a strategy before it is allowed to progress.
Trade journaling and monitoring
A trading discipline module and strategy monitoring keep a record of what was done and why.
Portfolio and allocation research
Portfolio construction and allocation are studied as research questions, separately from execution.
/engines/trading
Knowledge and operations
Interactive knowledge graph
The AI Brain at /os. Every node is clickable and opens the Inspector.
Memory and context
A memory module and a knowledge base hold context across sessions and across engines.
Workflow orchestration
Workflows, missions, an event bus, a Meta-Agent, and a research scheduler coordinate the engines.
Command interface and navigation
Terminal, Graphify, Vault, Email, Career, and Automation are all reachable as part of one system.
/graphify · /vault · /memory
architecture
Four layers
The interface talks to orchestration, orchestration composes the engines, and the engines are the only things that talk to providers. Nothing in the browser holds a provider secret.
The following diagram describes four layers. Each layer is built on the layer below it: the interface layer is built on the orchestration layer, the orchestration layer is built on the engines layer, and the engines layer is built on the providers and persistence layer.
-
Interface
- Terminal root@blkpvnthr-os:~$
- AI Brain (graph) React Flow
- Application views & Inspector React 19 · Zustand
-
Orchestration
- Workflows /workflows
- Event Bus
- Meta-Agent
- Missions /missions
- Memory /memory
-
Engines
- Finance /engines/finance
- Research /research-division
- Knowledge Knowledge Base
- Trading /engines/trading · paper
- Automation
-
Providers & persistence
- Supabase auth + 6 edge functions
- Plaid read-only bank links
- Alpaca paper trading
- FastAPI research engine 127.0.0.1:8010 → /research-api
- Local persistence
The six Supabase Edge Functions are alpaca-proxy, plaid-link, brokerage-connect, email-classify, email-sync, and email-provider-token. nginx on an Oracle Cloud VM fronts the whole system and reverse-proxies the research engine, which binds to loopback and is never exposed directly.
stack
Technical stack
Interface
- React 19
- TypeScript
- Vite
- Tailwind v4
- React Flow (@xyflow/react)
- Zustand
- React Router 7
- Framer Motion
- Recharts
- Radix UI
- react-plaid-link
Services
- Supabase auth
- Supabase Edge Functions × 6
- FastAPI research engine
- Python (stdlib-first)
- research_engine
- pattern_engine
- alpha_discovery
- evidence_fusion
- strategy_lab
Data & integrations
- Plaid (read-only bank links)
- Alpaca (paper-api)
- Supabase
Infrastructure
- nginx
- Oracle Cloud VM
- 127.0.0.1:8010
- /research-api reverse proxy
Quality
- Vitest
- oxlint
boundaries
Trust and safety boundaries
Read-only financial data by default
You sign in with your bank inside Plaid’s secure widget. The app never sees your bank credentials, and the Plaid secret stays server-side. Balances only: no transfers.
Paper-first trading
Trading is paper-first. Live orders stay disabled until a strategy clears the paper-trading threshold, and the Alpaca proxy targets the paper API.
Analysis is separate from execution
Analysis and execution permissions are kept separate, so a research module cannot reach the execution path on its own.
Source-backed analysis
The system does not invent financial values. Figures are traced to the account data or the research run they came from.
Human review for consequential decisions
Anything with a real consequence is surfaced for review rather than acted on silently.
User-controlled credentials
Connections are established, inspected, and removed by the user. Nothing is linked in guest mode.
These are product design boundaries, not a formal compliance certification. Nothing in BLKPVNTHR.OS is investment advice.
the system
Inside BLKPVNTHR.OS
Eight screens from inside the OS. Scroll, swipe, or use the arrows.
-
AI Brain. Every engine, mission, workflow and data source is a node; selecting one opens the Inspector. -
AI CFO Department. An auditable accounting engine that closes the books each month and tracks long-term net worth. Figures shown are the product’s clearly-labeled demo data, not real finances. -
Quantitative Research Division. 18 laboratories and a research lifecycle that runs from observation through statistical validation to a deployable strategy. Paper and research only. -
Trading engine. Paper-first: live orders stay disabled until a strategy clears the paper-trading threshold. Any figures shown are the product’s own demo state — not real finances, and not a track record. -
Memory System. Seven memory types — user, project, research, conversation, semantic, working and RAG — that the agents create, tag, link and search across runs. -
Loop Engineering. Every run feeds the next — scheduled routines log their execution, compound lessons, and close the loop. Simulated runtime; the persistence and UI are real. -
Workflows. An automation framework — trigger, conditions, actions, a memory update and a notification — composed in a visual builder. -
Repository Explorer. Every folder is a first-class OS subsystem, with its role, linked engines and children modeled as nodes on the Brain graph.
start assembles the AI Brain.
Any values visible are the product’s own demo state, not real finances.
maturity
Where it stands today
BLKPVNTHR.OS is an actively developed software platform and working product environment. Some capabilities are production-oriented, while others remain experimental research modules.
The fastest way to judge it is to open it. It runs in guest mode with no sign-up.
disclosure
BLKPVNTHR.OS is a separate service
BLKPVNTHR.OS is a separate software service operated as a distinct product. It may be governed by its own product-specific terms and privacy disclosures, which are separate from the Terms of Use and Privacy Policy that apply to asmaa.dev. Review those before using it.
Nothing in the product is investment advice. Trading is paper-first and live orders are disabled. Bank connections are read-only through Plaid — balances only, no transfers. See the full Financial Disclaimer for details.
Explore the live system
Launch BLKPVNTHR.OS to explore the interface, architecture, and connected operating model.