Security · FIRNA

Security at FIRNA is not a feature bolted on after launch. It is the architecture itself. Every layer of the pipeline is designed so that failure defaults to doing nothing, not doing something wrong.

Architecture: isolation by design

FIRNA runs six agents in a strict pipeline. Each agent has exactly one job and exactly one handoff point. Scout hands to Analyst. Analyst hands to Architect. Architect hands to Sentinel. Sentinel hands to Executor. Executor hands to Steward. No agent can skip a step. No agent can call another agent out of order.

This is not a microservices architecture chosen for scalability. It is an isolation architecture chosen for safety. If Analyst produces a bad score, it cannot route an order. If Architect builds a bad book, it cannot execute a trade. Only Executor can route orders, and only after Sentinel has approved every single one.

The pipeline is a chain of custody for decisions. Every link is auditable. Every handoff is logged.

The five controls

Before any order reaches execution, it must pass five hard controls. These are not guidelines. They are gates. If any gate fails, the order does not proceed.

01 Universe gating

Scout enforces three hard gates on every asset: verified custody, sufficient liquidity, and token maturity. An asset that fails any gate is excluded from the universe entirely. It never reaches scoring, construction, or execution.

02 Five-factor scoring

Analyst scores every eligible asset against five independent factors. The model adapts per mandate, but the factors are fixed. No asset enters the book without a complete score. Partial scores are treated as failures.

03 Risk-adjusted construction

Architect applies volatility penalties, sector concentration caps, an RWA floor, and a drift trigger of ±5%. Position sizes are derived from the model, not set manually. The book cannot exceed its risk budget.

04 Sentinel veto

Sentinel runs four independent risk checks on every proposed order. If any check fails, the order is vetoed. Sentinel has the authority to halt the entire desk. No other agent can override a Sentinel veto.

05 Paper-first settlement

The desk currently runs in paper mode. Real routing logic, simulated settlement. Every run on the tape is a real run through the full pipeline. The only difference is the settlement endpoint. No real capital is at risk until paper mode is explicitly disabled.

On-chain auditability

FIRNA settles on Robinhood Chain. Every order, every fill, every rebalance is recorded on-chain. There is no separate back office reconciling trades overnight. The chain is the book of record.

This means the desk's entire history is verifiable by anyone with access to the chain. You do not need to trust FIRNA's logs. You can verify them independently against the settlement layer.

Failure modes

The pipeline is designed so that every failure mode defaults to inaction:

Scout fails

No assets enter the universe. Analyst has nothing to score. The cycle produces zero orders.

Analyst fails

No scores are produced. Architect has no inputs. The book is not updated.

Architect fails

No position targets are generated. Sentinel has nothing to check. No orders are proposed.

Sentinel fails

All orders are vetoed by default. Executor receives an empty queue. Nothing is routed.

Executor fails

Orders are not routed. Positions remain unchanged. Steward monitors the existing book.

Steward fails

Drift is not monitored. The next cycle is not triggered automatically. The book holds its current state.

In every case, the result of a failure is that the desk does nothing. It does not execute partial orders. It does not route with stale data. It does not guess. It stops and waits.

A desk that does nothing when confused is safer than a desk that does something when confident.

What we do not do

We do not custody assets. FIRNA is a desk, not a custodian. Assets settle on Robinhood Chain. Custody is handled by the chain's infrastructure, not by FIRNA.

We do not store private keys. Order routing goes through Robinhood's agentic trading MCP. FIRNA does not hold, manage, or have access to user private keys.

We do not override risk limits. Sentinel's veto is final. There is no admin override. There is no emergency bypass. If Sentinel says no, the answer is no.

Reporting a vulnerability

If you believe you have found a security vulnerability in FIRNA, please contact us at security@firna.tech. We take all reports seriously and will respond within 48 hours.

Please do not disclose vulnerabilities publicly before we have had a chance to investigate and address them.