● Internal Strategy Document

IrisGo Phase 1 Architecture
High-Level Design & Business Logic

Phase 1 MVP scope after the Hermes Fork: the five-layer architecture and the business model relationship map. A converged version produced through cross-discussion with internal agents holding full project context.

Public Beta · Live irisgo.ai/download/beta DAU 10K · 120-day checkpoint 2026-07-30 Series A · Post-MVP
Phase 1 MVP
Must ship before Public Beta
Post-Series A
Milestones after Series A
IrisGo-owned
Core moat nodes

01Product Architecture (5-Layer)

The Hermes v1.0 fork serves as the agent loop foundation. Identity & Auth is the foundational one-way door, and the differentiation layer (Context-Aware Engine + Watch & Learn) carries the Phase 1 moat.

flowchart TB classDef phase1 fill:#064e3b,stroke:#10b981,color:#ecfdf5 classDef postA fill:#374151,stroke:#9ca3af,color:#d1d5db,stroke-dasharray: 6 4,font-style:italic classDef irisgo fill:#7c2d12,stroke:#f97316,color:#fff7ed,stroke-width:3px subgraph L0["Layer 0 — Presentation"] OEM["Acer/ASUS Native App
OOBE 60-80% activation"]:::phase1 TG["@IrisBot Telegram
Consumer Gateway"]:::phase1 MKT["Marketplace Web Portal"]:::postA end subgraph L1["Layer 1 — Message Gateway"] GW_TG["Telegram Gateway"]:::phase1 GW_DC["Discord / Slack / Signal"]:::postA GW_EM["Email Gateway"]:::postA end subgraph L15["Layer 1.5 — Identity & Auth"] ID["User ID + Device Pairing + SSO
★ Single-way door ★"]:::phase1 end subgraph L2["Layer 2 — Agent Core"] HERMES["Hermes v1.0 Fork
run_agent.py + hermes_state.py
MIT · honcho removed"]:::irisgo MP["MemoryProvider ABC
Plugin Point"]:::phase1 end subgraph L3["Layer 3 — IrisGo Differentiation"] CAE["Context-Aware Engine
Long-term Memory + Session Memory
LongMemEval R@5 target 96.6%"]:::irisgo WL["Watch & Learn
1-shot Token Saver"]:::irisgo DP["Dynamic Persona + MBTI"]:::postA DF["Dayflow + ActivityWatch"]:::postA VLM["Visual VLM Pipeline"]:::postA SR["Skills Runtime
Core IrisGo Skills"]:::phase1 MKSK["Marketplace Skills TEE DRM"]:::postA SAR["Smart API Router
Cloud + Local Hybrid
Phison aiDaptiv+ · Intel OpenVINO"]:::irisgo DAN["Data Annotation Network"]:::postA end subgraph L4["Layer 4 — Platform Services"] GOT["GoT / Billing
Free · $8.9 · $14.9"]:::phase1 OTA["OTA Update"]:::phase1 MIG["Migration Tool
OpenClaw+Hermes → IrisGo"]:::phase1 TEL["Telemetry & Analytics
Privacy-Preserving"]:::phase1 end OEM --> GW_TG TG --> GW_TG MKT -.-> GW_DC GW_TG --> ID GW_DC -.-> ID GW_EM -.-> ID ID --> HERMES HERMES --> MP MP --> CAE MP --> WL MP -.-> DP MP -.-> DF MP -.-> VLM HERMES --> SR HERMES -.-> MKSK HERMES --> SAR SAR -.-> DAN HERMES --> GOT HERMES --> OTA HERMES --> MIG HERMES --> TEL

02Business Logic

Value exchange and cash-flow direction between IrisGo and its users, OEMs, creators, infrastructure partners, and licensing channels. The artery of recurring revenue is the Smart API Router (token routing + local/cloud hybrid), integrating Phison aiDaptiv+ (SSD-as-VRAM extending the context window that large models can run locally) and Intel OpenVINO (CPU/NPU/iGPU inference). It both honors stakeholder ecosystem commitments and serves as the pivot node for GoT billing. Caviarclaw is a license-fee business pilot, not the most important Phase 1 project. Joe's enterprise channel and the Intel TEE/DRM partnership unfold Post-Series A.

flowchart LR classDef phase1 fill:#064e3b,stroke:#10b981,color:#ecfdf5 classDef postA fill:#374151,stroke:#9ca3af,color:#d1d5db,stroke-dasharray: 6 4,font-style:italic classDef irisgo fill:#7c2d12,stroke:#f97316,color:#fff7ed,stroke-width:3px IRIS["IrisGo Inc.
$3.1M Seed"]:::irisgo USERS["Consumer Users
DAU 10K · 2026-07-30"]:::phase1 CREATORS["Skill Creators"]:::postA OEMS["Acer / ASUS
100M+ AIPC/yr"]:::phase1 INTEL["Intel TDX
TEE Substrate"]:::postA CAVIAR["Caviarclaw
License-fee Pilot
Standard Edition + Branding"]:::phase1 JOE["Joe · Enterprise Channel"]:::postA MODELS["Model Providers
OpenAI · Anthropic · Google"]:::phase1 IRIS -->|"Free · $8.9 · $14.9"| USERS USERS -->|"Context + Usage"| IRIS IRIS -->|"Pre-load + OOBE"| OEMS OEMS -->|"AIPC Shipments + Royalty"| IRIS IRIS -.->|"SDK + Revenue Share"| CREATORS CREATORS -.->|"Skills Supply"| IRIS IRIS -.->|"TEE DRM White Paper"| INTEL INTEL -.->|"Hardware Attestation"| IRIS IRIS -->|"License Fee + Branding"| CAVIAR CAVIAR -->|"License Revenue (pilot)"| IRIS IRIS -.->|"Enterprise Deal"| JOE IRIS -->|"Token Routing Spend"| MODELS IRIS -->|"Smart Router Optimization"| MODELS

03Tri-Perspective Cross-Validation

Phase 1 scope validated through three perspectives: engineering rigor, hardware reality, and distributed contracts. Each perspective identifies a gate that must be locked before proceeding.

MELCHIOR

Engineering Rigor

Eval-First · Lock the Metric
  • Context-Aware Engine + Watch & Learn are learned components — the eval metric must be locked before development begins
  • Phase 1 gate: LongMemEval R@5 ≥ 96.6% (MemPalace baseline)
  • Watch & Learn's 1-shot token saving needs a before/after benchmark — otherwise it is just marketing copy
  • Dynamic Persona + Dayflow deferred to Post-Series A — no population-scale data flywheel exists at MVP stage
BALTHASAR

Hardware Reality

Measured-First · No Assumptions
  • Acer AIPC on-device budget must be measured, not assumed
  • RAM: 16 / 32 GB (long-term memory hot set ≤ 800 MB)
  • Embedding model: ≤ 500 MB VRAM
  • Binary: < 500 MB installer · OOBE cold-start: < 3 s
  • Blocker: Calvin Chen's reference machine must be in hand within 7 days
CASPER

Distributed Contracts

Blast-Radius · Freeze Before Ship
  • The Context-Aware REST API (localhost:5700) is a one-way door — the spec must be frozen before Acer ships
  • The Message Gateway has the largest blast radius; shipping only TG in Phase 1 is the right call
  • The Identity & Auth Layer is the true foundation — without it, Skill DRM / GoT billing / Single Iris are all impossible
  • The Arnold + Calvin sync call must happen within 7 days

047-Day Validation Plan

Three gates, each the bottom line of one council member. All three must produce data within 7 days; otherwise, Phase 1 scope needs to be re-examined.

1
LongMemEval baseline
Run the Context-Aware Engine once to confirm R@5 ≥ 96.6% (engineering-rigor gate). Result feeds the Series A narrative appendix.
2
Acer reference-machine measurement
RAM / CPU / disk / OOBE cold-start time (hardware-reality gate). If we can't measure, the Acer pre-load timeline must be re-estimated.
3
Context-Aware REST API v1.0 spec freeze
Freeze the spec after the Arnold + Calvin sync call (distributed-contract gate). /api/v1/context/now · /summary · /profile.

05Open Blockers

!
MAGI Blocker 3 — product-side owner for dynamic persona + dayflow unassigned
The personal-experiment version of long-term memory (for research) and the product-side version (shipped to Acer) are two different things. Lman returned the PR on 4/17, but the person who ships these two modules on the product side is still undecided. Action: Tony (PM) or Arnold needs to explicitly pick this up; otherwise Phase 1 differentiation reduces to Context-Aware + Watch & Learn only.

06Prior References