MARLO TECHNOLOGY
INTELLIGENCE THAT ACTS.
Persistent intelligence that can remember, perceive, adapt, automate and act across the user’s digital environment.
ONE INTELLIGENCE. MULTIPLE SYSTEMS. REAL ACTION.
Execution
ACT
ACT is MARLO’s execution system. A turn can become a planned device or browser action. The path is intent → plan → action → observe → verify → adapt. On Android, ACT runs through the Marlo app Accessibility service after you approve. MARLO does not invent a successful tap — it reports what the device actually did.
- INTENT→
- PLAN→
- ACTION→
- OBSERVE→
- VERIFY→
- ADAPT
Specialized processes
DAEMON ARCHITECTURE
Phone control, SMS relay, wake, and cron intelligence are separate processes — not one prompt-response loop. Android runs ACT poll and SMS outbox services. The web app runs scheduled stewardship, reminders, WIRE, and evolve jobs. Each daemon has a bounded job.
- CHAT TURN→
- DAEMONS→
- DEVICE / CRON→
- RESULT
Adaptation
SELF-EVOLUTION
MARLO adapts from experience, interaction, preferences, trust, feedback, and outcomes. SELF-v2 and WIRE can enqueue bounded evolve work. This is adaptation of behavior and routing — not a claim of consciousness or AGI.
- EXPERIENCE→
- PREFERENCE→
- TRUST→
- OUTCOME
Governance
AEGIS
Aegis is the governor: allow, deny, require confirmation, or contain. Sensitive operations go through approvals. A kill switch can pause ACT execution. Humans stay in the loop for money, SMS, and device taps.
- PERMISSION→
- GOVERN→
- OVERRIDE
Ongoing responsibility
STEWARDSHIP
Stewardship keeps tasks, reminders, bills, subscriptions, and workflows alive across days. Items are captured from conversation, verified on a cron, and can spawn ACT work. A chat turn is not the whole relationship.
- CAPTURE→
- HOLD→
- VERIFY→
- ACT
Context
GROUND + WORLD
Ground is understanding of the current external environment — what is in front of MARLO now. World is the evolving internal state — drives, presence, and continuity. Both feed the next reply and the next action.
- GROUND→
- WORLD→
- MEMORY→
- MARLO
Continuity
PERSISTENT MEMORY
Conversation, preferences, identity threads, tasks, and episodes persist server-side for the session. Web, iPhone, and Android talk to the same MARLO backend. There is no second intelligence and no local personal-data warehouse on hosts.
- TURN→
- EPISODE→
- THREAD→
- RETURN
Authorization ledger
GDDL
GDDL is the Global Digital Dollar Ledger — transaction and authorization technology MARLO can prepare against. MARLO may request a payment. Only the user authorizes it. The path is understand → act → authorize → transact → verify. Biometric authorization is hardware-backed on Android (BIAS). There is no silent payment, and GDDL is not a bank, card network, or regulated financial institution.
- UNDERSTAND→
- ACT→
- AUTHORIZE→
- TRANSACT→
- VERIFY
CONNECTIVITY
WEB
marlosai.app — conversation, memory, voice, approvals, Guardian, stewardship.
ANDROID
Marlo app — SMS, Accessibility phone control, sensors, GDDL BIAS, BLE lab.
APPLE / iPHONE
Home Screen PWA and native iOS shell (nima-ios.zip on the landing page) on the same marlosai.app backend. Android-only controls stay off.
MARLO has been exercised over a vehicle Bluetooth audio path. That is connectivity and voice, not vehicle control, OBD, or CarPlay automation.
MODULAR TECHNOLOGY
An existing AI company does not have to replace its model to use MARLO technology. Components can be licensed, integrated, or acquired on their own.
- ACTDevice execution and approval runtime
- AegisAction governance and kill switch
- Daemon systemsBounded background workers
- Persistent intelligenceMemory, threads, episodes
- StewardshipOngoing task ownership
- Self-EvolutionPreference and outcome adaptation
- GDDLAuthorization and ledger prepare/execute
- SDK / integration@nima/sdk, @anima/core, qualia layers
Beyond MARLO’s consumer-facing experience is a broader collection of application frameworks and developer technologies that may be included in licensing or acquisition discussions.