/VISUAL INTENT OS
Inapse Inflow is a visual operating system for intent pipelines and QRC20 execution flows. Map, simulate, verify, and deploy — from natural language to executable payload.
"Deep infrastructure disguised as simplicity."
/CORE CONCEPT
Inflow is four systems in one: a visual compiler for intent, a design and simulation environment for QRC20 pipelines, a trust and security inspection layer, and a flow-based execution engine UI.
Visual Compiler
Transform natural language into structured, executable pipelines
Simulation Engine
Preview every step before deployment — costs, latency, failure paths
Trust Inspector
See exactly where data flows and what is exposed at every boundary
Execution UI
Deploy QRC20 payloads directly from the canvas with one action
"It transforms: natural language intent → structured pipeline → executable QRC20 payload."
/FLOW COMPOSER
The Flow Composer is a node-based pipeline builder with a large central canvas. Drag-and-drop nodes, connect them with lines, zoom and pan to see the full picture. Five node categories cover every stage of intent execution.
"Each node is clean, modular, and understandable — complexity through composition, not clutter."
/DEEP INSPECTION
When you click a node, a side panel reveals its full context — plain English explanation, technical breakdown, permissions, security classification, estimated cost, latency, dependencies, and risk indicators. It feels like Figma inspect meets Web3 wallet preview.
Node Inspector
/EXECUTION PREVIEW
Toggle execution preview to see a step-by-step timeline with animated flow of assets and data, confirmation points, cost estimation, and failure paths. It feels like a simulation engine — every outcome visible before a single transaction is signed.
Timeline
Step-by-step execution sequence
Animated Flow
Watch assets and data move
Confirmations
Tap, biometric, or auto-approve
Cost Preview
Gas, fees, and splits calculated
Failure Paths
See what happens if a step fails
Latency Map
Estimated time per operation
"Always show what happens next — before it happens."
/TRUST BOUNDARIES
The Trust Boundary Map is a visual layer showing exactly where data lives and what is exposed. Color-coded zones distinguish local secure processing, encrypted transport, QRC20 payloads, and blockchain settlement — with red flags for any step requiring approval.
Local Secure
Device enclave
Encrypted
Transport layer
QRC20
Execution payload
Settlement
Blockchain final
"Security transparency is not optional — it is the interface."
/QRC20 EXPLORER
The QRC20 Payload Explorer shows the decoded structure, execution logic tree, fee split and referral tree, validity rules, and trust score — all in one view. Think Etherscan meets JSON viewer meets product UI.
QRC20 Payload — Example
type: content_unlock
creator: 0x7a3f...b2c1 ✓ verified
action: unlock → split_payment → notify
fee_split:
creator: 90%
platform: 5%
referral: 5%
validity: 2025-01-01 → 2026-12-31
trust_score: 94 / 100
/LIVE EXAMPLE
A complete example: scan a QRC20 code, verify the creator, unlock content, split payment (90/5/5), attach a referral, and notify the user. Six nodes. One flow. Fully executable.
Natural Language Summary
"On scan → verify creator → unlock content → append referral → split payment → notify user"
Graph View
Visual node-based representation of the full pipeline with connections and data flow
Simulation View
Step-by-step animated execution with timing, cost estimation, and confirmation points
QRC20 Output
The compiled payload — decoded structure, fee splits, validity rules, and trust score
/CAPABILITIES
Intent → Flow
Auto-generate pipelines from natural language
Drag & Drop
Visual editing with modular node system
Real-Time Sim
Preview execution before deployment
Security Map
Trust boundaries visible at every step
QRC20 Compile
Output executable payloads directly
Share Pipelines
Export and distribute reusable flows
Multi-Party
Approval logic with multi-sig support
Attribution
Referral and fee routing built in
Agent-Ready
Pipelines compatible with AI agents
"Complex systems should feel simple. Progressive disclosure — simple mode for users, builder mode for developers."
/ECOSYSTEM ROLE
Inflow is where pipelines are designed, tested, and deployed. It sits above the execution layer — connecting Inapse Input (intent capture), K2K (encryption), Inclave (wallet logic), and QRC20 (programmable payloads) into a single visual environment.
"Inflow is the interface where the entire Inapse stack becomes visible, composable, and deployable."
/THE NEW COMPUTING LAYER
Inapse Inflow makes intent pipelines visible, verifiable, and deployable. Not a tool — a new computing layer for the execution economy.