Bitcoin
Base monetary context and native capital semantics. It anchors the field without becoming a custody, wallet, or settlement claim.
Public Reality Field
Capital exists, moves, leaves evidence, and forms structure.
ArCa begins as the public field for exploring that reality: observe environments, reveal evidence, follow flow, and discover structure before entering higher-resolution lenses that do not turn evidence into authority.
Capital Flowmovement context
Bitcoinmajor monetary environment
Multichainrepresentation and dependency
RWAclaim evidence
Liquidityaccessibility context
ArCapublic field for capital reality
Observe / Environment
Capital environments come before products.
The Public Reality Field begins with persistent environments. They are not logos, integrations, or equal feature cards. They are contexts where capital exists, is represented, constrained, claimed, accessed, and understood before a higher-resolution lens adds evidence context.
Multichain
Representation and movement context across networks.
Capital Flow
Source, sink, and movement context without advice or recommendation.
RWA
Claim and representation evidence where capital references off-chain rights.
Liquidity
Accessibility, depth, and dependency context without route-quality authority.
Reveal / Evidence
Evidence anchors appear before interpretation.
This layer uses illustrative traces only. It shows how evidence can be anchored conceptually without pretending to stream live data, calculate outcomes, expose internal dry-run outputs, or become authoritative truth.
not live data
Evidence anchors show observation, traceability, and visibility as public language. They are static examples, not fabricated intelligence or claims of truth.
Observed context
Capital evidence becomes visible inside an environment before it becomes a product insight.
Traceable reference
A trace can link movement, lifecycle, verification, or lineage without becoming final truth.
Bounded visibility
Visibility helps users understand capital reality while preserving authority separation.
Follow / Flow
Flow connects environments without selecting paths.
Flow is the guided movement layer: capital movement, dependency, routing context, and lifecycle transition. Flow traces help visitors follow relationships through continuity rails without implying optimization, recommendation, prediction, or execution.
movement
Environment to environment
Capital context moves across networks, claims, liquidity constraints, and source/sink relationships.
- representation
- dependency
- accessibility
future surface
Routing context
Routing can explain path availability, constraints, and prerequisites without choosing or authorizing a route.
- constraints
- provenance
- no selection
no execution authority
Lifecycle flow
Execution-adjacent evidence is represented as lifecycle state, not as a command, action, or promise.
- intent
- submitted
- filled
Discover / Structure
Evidence and flow settle into structure.
The Public Reality Field does not begin with a full architecture diagram. It lets repeated environment, evidence, and flow relationships form topology layers where structure can emerge without becoming prediction.
01
Recurring patterns
Repeated evidence and flow make relationships visible without claiming future knowledge.
02
Organized topology
Environments, ArCa, products, and intelligence layers become one readable system.
03
Verification paths
Execution, reconciliation, and lineage preserve evidence relationships without authority.
04
Bounded surfaces
Products become specialized lenses into capital reality, not the starting point.
Product lenses
Lenses inherit the Public Reality Field.
BaseAlpha and Routing now link to separate read-only ArCa lenses. BaseAlpha opens the Capital Reality overview and intelligence-stack connection state. Routing opens the top-level route operations lens for the completed read-only route proof. AgentForge, revenue, and YieldPilot remain boundary or future states unless a scoped surface is authorized.
Open Capital Reality overview
Open Routing read-only proof
AgentForge boundary: autonomous Routing execution not authorized
YieldPilot: future deployment lens
Intelligence lens
BaseAlpha
Structured Capital Reality lens for reading what is live, aggregate, static, dry-run, blocked, or not connected.
- capital states
- source status
- evidence
read-only route proof
ArCa Routing
Read-only route console for the completed Base / LI.FI / ETH to USDC proof. It shows settlement, reconciliation, and blocked revenue authority without route execution controls.
- settled proof
- reconciled
- read-only
no execution authority
AgentForge
Governed action visibility remains boundary-only here. Autonomous Routing execution is not authorized.
boundary only
no autonomous execution
- lifecycle
- governance
- visibility
future surface
YieldPilot
Future deployment lens. No current landing action is linked because a safe target route was not confirmed in this queue.
coming soon
not connected
- deployment context
- future
- bounded
Lens preview
The public field now points to measured operating intelligence.
BaseAlpha is the high-resolution lens. The public page can show which operating surfaces exist, but full indexes, chart readiness, blockers, and source-backed inspection stay inside the app.
Operating picture
Domain indexes are inside BaseAlpha.
Visible domains, index readiness, chart readiness, and blocker queues are shown in the higher-resolution lens.
Movement coverage
Movement is measured before it is interpreted.
Source-family roles, ETH/Base dominance boundaries, and aggregate context are inspectable without claiming Capital Movement Reality.
Routing proof
Routing remains read-only.
The completed live proof is visible through the Routing lens with settlement and reconciliation evidence, not execution controls.
Bounded field
No public prediction or authority.
The landing page previews structure only. It does not expose full lens value, route selection, recommendations, execution, fees, or revenue authority.
Operating cockpit first.
BaseAlpha opens with visible domains, index readiness, chart readiness, active output, aggregate context, and the next inspection target.
Domain indexes stay inside the lens.
Movement, Hyperliquid, Routing, Stablecoin, Bitcoin, Multichain, Liquidity, and RWA are sorted by source-backed readiness, not public claims.
Charts require numeric basis.
The preview points to chart-ready surfaces without exposing raw operational data or rendering fake live charts.
Evidence remains inspectable.
Rows, windows, proofs, and source context are available in the app. The public field keeps only the navigation shape.
Sources explain coverage.
Source coverage and aggregate context are lens diagnostics, not source-of-truth promotion.
Blockers become implementation targets.
Missing numeric fields, source gaps, and authority limits stay compact and actionable without becoming the main product.
Boundaries stay secondary.
No prediction, recommendation, route selection, execution, fee capture, revenue authority, or source-of-truth claim is introduced here.
Boundary system
Evidence stays useful by staying bounded.
Boundary labels stay close to sensitive concepts. They keep evidence non-authoritative and prevent flow, verification, lineage, and future deployment from being read as recommendation, prediction, execution, or source-of-truth authority.
01
Static informational.
The explorer explains the public reality field. It does not expose internal intelligence outputs, premium evidence, or live operational systems.
02
Navigation only.
Any app link remains navigation into a lens. It does not imply authorization, recommendation, prediction, execution, routing, or deployment change.
03
No authority transfer.
Evidence, flow, verification, and lineage remain descriptive, non-authoritative, and not source of truth in the public explorer.
Public reality path
Move through the model in order.
This is curated navigation through the Public Reality Field, not search or a command palette. It keeps discovery public-safe before a visitor enters a higher-resolution lens.
Public Reality Field, explored carefully