Flutter presentation / shell
Views, navigation, gestures, interaction state, and security summaries. Core business processing is expected to live below the presentation layer.
Architecture
Separate the interface, the domain, the operating system, and the wire.
LicoUp uses four horizontal platform tiers with vertical domain slices. Stable endpoint wire semantics remain outside the client repository under Lico Arc Protocol governance.
Bridging contract / RPC
Structured Flutter ↔ Rust communication through desktop method frames and mobile FFI commands, rather than leaking raw CLI argument arrays into the UI.
Rust functional core + infrastructure
Canonical Conversation, Adaptive Flywheel, Agent Adapters & Runtime, SQLite/WAL storage, dynamic configuration, secret custody, network transport, and PTY/subprocess supervision.
Native OS adaptation
Platform-specific key custody, user-presence APIs, PTY/console primitives, sandbox paths, autostart, and other operating-system integration.
Vertical authority
The conversation is the durable product center.
Conversation is modeled as a vertical slice that crosses presentation, bridge, Rust domain logic, persistence, and native adaptation. The Rust-hosted Canonical Conversation is the durable authority for conversation state rather than a provider-native history silently becoming the product’s canonical record.
Agent adapters normalize concrete agent transports and vendor-specific protocols behind the product’s internal contracts. Native continuation locations remain private implementation detail.
Protocol boundary
LicoUp executes; Lico Arc defines the stable wire.
LicoUp owns endpoint key custody, plaintext, local history, approval, local effects, client configuration, platform adaptation, and conforming execution of a supported protocol line.
Lico Arc Protocol is the independent, implementation-neutral authority for stable wire-observable Pairwise Protection, Generic Message, Reliable Exchange, negotiation, Transport Profile, station-facing contracts, and federation governance.
The current Lico Arc protocol line remains a partial Candidate. This website therefore treats the protocol as an architectural boundary, not a released cryptographic capability.
Architecture evidence