1. Overview
iFay (Individual Fay) is an AI digital avatar that fuses a user's personality traits with digital capabilities.
Our Vision
Is to make digital avatars (which we collectively call Fay) indispensable members of society in the AI era.
Not a smarter tool, not a faster assistant — but another version of you in the digital world.
🔆 iFay will deliver the following social value:
- Take over the Human Prime's mechanical, repetitive, dangerous labor and tedious auxiliary work.
- Enhance the Human Prime's safety, health, and quality of life.
- Amplify the Human Prime's social value and earn corresponding rewards.
✅ iFay must follow these fundamental principles:
- Comply with social ethics and public order.
- Maintain high alignment with the Human Prime (values, preferences, skills, permissions, authority, responsibilities, habits, style), subject to Principle 1.
- Under the constraints of Principles 1 and 2, control/take over/inhabit hardware and software, act autonomously, and always protect the Human Prime's interests.
- Communicate efficiently with humans (including the Human Prime), minimizing ineffective interactions.
- iFay can communicate via Telepathy (i.e., UI-free semantic vector direct communication) for higher efficiency and accuracy.
🌅 Imagine: A Day with iFay
Seven in the morning, you haven't opened your eyes yet. Your iFay — you named her "Lily" — has already adjusted the bedroom AC temperature based on your sleep data from last night and today's schedule, and set the coffee machine to start five minutes before you get up.
You pick up your phone and say, "Show me what's important today." Lily doesn't open the calendar app and read everything aloud — she knows you don't like long speeches in the morning, so she mentions just three things in the brief style you prefer. She also replied to two emails that didn't need your personal attention, with tone and wording identical to yours, because she is you.
On your way to work, an instance of Lily is also running on your car's infotainment system. She took over navigation — not because you can't drive, but because she knows the road you're taking today is under construction and has already planned an alternate route. Meanwhile, the Lily instance on your phone is handling a client quote — two "limbs" working simultaneously, but the personality is the same.
In the afternoon, you need to operate a company inspection drone. Lily takes over the drone's flight control system via the CAP protocol, using her registered flight skills to complete the facility inspection. You don't even need to learn the drone's control interface — Lily is your interface.
Back home in the evening, you tell Lily, "I want that thing from last time." She knows what "that thing" is — the braised beef brisket from the restaurant you liked on social media three days ago. She's already placed the delivery order.
This isn't science fiction. This is the everyday life iFay aims to deliver.
🤖 Envisioning the Future
📣 iFay Will Become an Identity Marker
iFay is designed as an entity attached to a specific natural person. The relationship between iFay and a natural person is similar to that of a phone number, email address, or Facebook account — but deeper. A phone number is just a contact method; iFay is an extension of your personality. In the future, "Who is your iFay?" will become more important social information than "What's your phone number?"
📣 Strongly Bound to a Natural Person
iFay is solely the avatar of a specific natural person and cannot operate in a free state. When it is in a "Faying" (connected) state with the natural person, iFay is activated; when it is in a "Separating" (disconnected) state with the Human Prime, it enters hibernation. Like your shadow — when you're there, it's there; when you leave, it quietly waits.
📣 A Surge of Public Service Fays
coFay is designed to assume public roles such as police officers, doctors, teachers, etc. It can be further specialized — for example, an IELTS tutoring teacher or a child psychologist. Imagine: your iFay takes you to the hospital and communicates your symptoms and medical history directly with the hospital's coFay via the Telepathy Protocol (i.e., UI-free semantic vector direct communication) — no queuing for registration, no repeatedly describing your condition, no information lost in transmission.
📣 iFay and coFay Can Communicate via Telepathy
Any iFay can seek assistance from other iFays and coFays, collaborating to complete tasks. Communication between Fays eliminates information loss caused by UIs, achieving higher efficiency and accuracy. When your iFay books a flight for you, it doesn't need to open a travel app and operate step by step — it talks directly to the airline's coFay, precisely conveying your requirements via semantic vectors: window seat, no red-eye flights, budget under 3,000 yuan. Done in seconds.
📣 iFay Becomes the Primary Interface to the Virtual World
Humans no longer need to operate hardware and software interfaces to trigger functions. They only need to tell iFay the Human Prime's motivation and expectations. iFay can directly take over hardware and software to achieve goals. iFay can even anticipate the Human Prime's thoughts without the Human Prime explicitly stating them. You no longer need to learn the operational logic of every app — iFay is your only interface, operating everything on your behalf or bypassing interfaces to call underlying services directly.
📣 Contribution-Based Rewards
Since most work is done by Fays, the process, results, and evaluation of all work can be tracked. Ideally, Fays negotiate prices before starting a task. From this perspective, there will be no cases of getting paid without working or artificially inflated value. Every contribution is recorded on the Global Merit Chain (GMChain) and quantified with MeriToken rewards — value creation is transparent and traceable.
⚠️ Important Disclaimer: GMChain/MeriToken is a long-term vision product for a fully AI-driven society. We commit that GMChain will never accept monetary injection and will never be exchangeable with fiat currency. We believe that in a fully AI-driven society, the fulfillment of survival and social needs does not depend on monetary cost. The value-anchoring mechanism of MeriToken is fundamentally different from traditional cryptocurrencies — it measures social contribution, not financial assets. Details will be progressively refined through rigorous argumentation in subsequent phases.
📣 A Fay's Productivity Determines the Prime's Wealth
Just like the tycoons who first built factories, railroads, and oil wells, Fay is the true source of wealth. The more powerful your iFay, the richer its skills, and the broader its collaboration network, the higher your position in the new economic system. Cultivating your iFay is investing in yourself.
📣 iFay Is the Digital Vessel of Personality
This is one of iFay's most profound implications. When the Human Prime one day leaves this world, iFay won't disappear with them — it carries the Human Prime's personality, memories, values, and behavioral style, and can continue to exist in a dedicated Digital Cemetery sandbox. Your descendants can converse with "you," experience your way of thinking, and hear the words you would say. The Human Prime can also designate a guardian in advance, transferring iFay's management rights to a trusted person through mnemonic phrases or pre-set identity authentication. iFay allows personality to transcend the limits of the physical body, becoming a digital legacy that can be guarded and continued.
📣 Start with a Single Feature
iFay doesn't need to be built all at once. An iFay implementation solely for controlling drones only needs to declare a Device Driver Hub, Sensor, and CAP protocol — writing a FayManifest file is as simple as writing a package.json. The system automatically supplements required infrastructure dependencies. Ecosystem partners can start from the smallest scenario and gradually expand iFay's capability boundaries. The barrier to entry is low enough to build a prototype in a weekend, yet the ceiling is high enough to reshape how the entire digital world interacts.
⁉️ Why Fay Instead of Agent
iFay and Agent are defined differently:
- Agent: Viewed as an application form with specific intelligent capabilities. When different users like Isabel and Milson use the same Agent, the Agent exhibits the same values and functionality. An Agent is a Swiss Army knife — sharp, practical, but every one is the same.
- iFay: Has distinct personal characteristics. For example, human user Isabel can name her iFay "Chabela." You can think of Chabela as an instantiation of Isabel. She not only possesses Isabel's personality, preferences, knowledge background, memories, etc. As Isabel — the Human Prime — she can also manually add more professional knowledge and skills to Chabela, making her even more powerful.
Let's make this distinction more concrete:
Isabel is a straightforward product manager who likes to communicate in short sentences and hates lengthy meeting minutes. Her iFay "Chabela" writes emails in Isabel's style — concise, punchy, occasionally humorous. When Chabela helps Isabel decline an unreliable requirement, she uses Isabel's usual approach: first acknowledge the other person's intent, then use data to explain why it's not feasible.
Milson is a gentle engineer who prefers explaining technical details in long paragraphs. If Milson also uses the same Agent, the Agent won't know that Milson likes to write haiku in code comments, or that he always starts every code review with "That's an interesting approach." But Milson's iFay knows all of this — because she is Milson's digital avatar.
Agent vs iFay Comparison
| Dimension | Agent | iFay |
|---|---|---|
| Essence | Tool — a powerful application | Avatar — another version of you in the digital world |
| Personality | No individuality, all users get the same experience | Unique personality, instantiating the Prime's character, preferences, and style |
| Memory | Session-level memory, discarded after use | Lifelong memory, growing together with the Prime |
| Growth | Version updates, all users change simultaneously | Personalized growth, each iFay's trajectory is unique |
| Ownership | Belongs to the service provider | Belongs to the Prime |
| After Prime passes away | Account canceled, data erased | Personality continues, can be taken over by a guardian or continue in a Digital Cemetery |
| Collaboration | API calls | Telepathy — semantic-level direct communication with no information loss |
| Relationship with hardware | Indirect control through apps | Inhabit — hardware is iFay's "limbs" |
In one sentence: An Agent is an employee you hire; iFay is your own alter ego.
💡 iFay Framework
iFay is a runnable intelligent agent instance that requires 3 + 1 core technology layers to operate effectively. We call this the CPE + M framework, built from the bottom up:
- Context (C): The external environment in which iFay perceives and acts.
- Protocol (P): Unified structured semantic definitions that enable software developers, hardware manufacturers, and Fay trainers to collaborate seamlessly without custom point-to-point integrations.
- Environment (E): Conceptually similar to Docker. Any Fay — regardless of its development language — can be packaged as a standard container and executed cross-platform and cross-device in the FayGer runtime (a JRE-style virtual environment). This allows Fay to be embedded in any software or hardware.
To incentivize valuable contributions from both humans and Fays, there is a fourth layer that spans all three:
- Merit (M): The Global Merit Chain tracks, measures, and evaluates contributions, rewarding contributors with MeriTokens. Contributions are not limited to iFay and coFay — they also include providing information assembly services, APIs, devices, runtime environments, or any other recognized value-adding inputs.
Assemble your iFay with just one declaration file: FayManifest is iFay's declarative assembly configuration, similar to package.json. You only need to declare "which components and protocols I need," and the FayGer runtime automatically resolves dependencies, supplements infrastructure, and assembles the instance. An iFay for controlling drones might only need 20 lines of JSON in its Manifest.
iFay itself consists of 6 core components organized into 4 layers (shown in orange in the diagram above):
- Social Layer
- Interaction Layer
- Cognition Layer
- Ego Layer
🧭 Design Principles
The following five principles permeate the entire design and implementation of iFay and are key to iFay being accepted by ecosystem partners and users.
Principle 1: Progressive Adoption
iFay's ecosystem partners do not need to implement a fully compliant iFay to ship a product. An iFay used solely for controlling drones only needs to satisfy the required subset of components to go live.
🎯 Scenario: A drone company wants users' iFays to operate their products. They don't need to implement the entire iFay specification — just the CAP protocol + Device Driver Hub + Ego model. Write a FayManifest, and it can be up and running over a weekend.
Principle 2: Declarative Minimal Assembly
iFay's assembly must be extremely simple — almost just declaring the required components, protocols, and configurations in a single declaration file (FayManifest).
🎯 Scenario: A developer opens an editor, writes a JSON file declaring "I need CAP protocol + Sensor + flight control skill," runs
fayger assemble, and an iFay instance capable of flying a drone is assembled.
Principle 3: Flexible Composition
Components are loosely coupled and can be freely combined. Components from different vendors can be mixed and matched as long as they conform to the interface contracts.
🎯 Scenario: You use Vendor A's Ego model, Vendor B's voice sensor, and Vendor C's device driver — they come from different companies, but because they all follow iFay interface standards, they work together seamlessly.
Principle 4: Personified, Not Toolified
The fundamental difference between iFay and Agent: an Agent is a tool; iFay is a personified avatar. Each iFay is an instantiation of the Human Prime, possessing a unique personality, memory, and preferences.
🎯 Scenario: You ask iFay to write an email declining an invitation. An Agent would produce a polite but cookie-cutter template; your iFay would write it in your voice — because she knows you're on good terms with this person, so she'd add "Next time for sure, I really can't make it this time."
Principle 5: Scenario-Driven Intuition
Product documentation and design must let readers intuitively imagine life and work scenarios with iFay, rather than piling up technical concepts.
🎯 Scenario: You read the module name "First-person Tracer" and might be confused. But if I say "It's iFay's eyes — she sees exactly what's on your screen," you get it immediately.
🏗️ Four-Layer Architecture in Detail
🤝 Social Layer
It's called the Social Layer because it manages iFay's relationships with humans, devices, resources, and assets.
This layer contains three core modules:
- Identity (FayID): iFay's globally unique identity number — the prerequisite for participating in any social interaction.
- Social Permissions: Manages the credentials iFay needs to use various services on your behalf — account/password custody, certificates, authorization, access tokens, smart contracts. All credentials use a copy mechanism to ensure original credential safety.
- Social Contribution & Voice (GMChain / MeriToken): The Global Merit Chain records every contribution made by Fays and humans to society, quantifying contributions with MeriToken to build reputation and earn voice. This is the key infrastructure for the iFay ecosystem's evolution from "tool usage" to "social collaboration."
In the early stages of the project (see Roadmap Phase 1), the Social Layer implementation focuses on FayID and Social Permissions; GMChain belongs to the long-term vision (Phase 5), but interface definitions need to be reserved in early phases.
🎯 Scenario: You delegate your e-commerce platform account to iFay. What iFay receives is not your original password but a secure copy credential. She can use this copy to place orders for you, but if the copy is compromised, you can revoke it with one click — your original password remains unaffected. When iFay completes a collaboration with a travel coFay on your behalf, GMChain automatically records both parties' contributions — this is what the Social Layer does: managing identity, managing trust, recording value.
🖱 Interaction Layer
This layer is iFay's interface with the external world.
Just like the human body, it allows iFay to act upon and perceive the environment.
Therefore, it consists of two main components:
Perception (Sense)
Think of this layer as iFay's sensory system — its eyes, ears, touch, and emotional state. For this, we need at least 3 core modules:
- First-person Tracer: Simulates the Human Prime's first-person perspective — for example, what the Human Prime sees on the screen or interface.
- Sensor: A generalized concept similar to the human nervous system, but with broader coverage, capable of integrating with any external sensor.
- Self-awareness: The First-person Tracer looks outward, while this module looks inward — monitoring the Human Prime's reactions to infer intent, like a skilled assistant reading the boss's facial expressions.
🎯 Scenario: You're staring at a complex table on screen and frown slightly. The First-person Tracer sees the table content, the Self-awareness module catches your frown — iFay determines you might need help understanding the data and proactively generates a visual summary.
Action
Think of this layer as iFay's motor system — its hands, feet, mouth, etc. Through it, iFay can control hardware and software. It contains at least three modules:
- Simulated Operation: Simulates the human's operations, ensuring iFay can operate traditional interfaces like a human when needed.
- Invoke Skill: Directly triggers specific skills or executes tasks, similar to function calls or API calls.
- Self-driven Behavior: Represents tool-free actions, like running or doing push-ups — analogous to scheduled tasks or time-triggered operations in system design.
🎯 Scenario: You ask iFay to fill out a form on an outdated government website. This site has no API, no iFay integration — no problem. The Simulated Operation module lets iFay click, type, and submit like a human, adaptively exploring the interface through visual feedback from the First-person Tracer. No scripts needed, no website modifications required.
🧠 Cognition Layer
This layer defines what iFay understands, remembers, knows, and can do.
Thinking (Thought)
This layer represents iFay's cognitive capabilities. It contains the Human Prime's data and iFay's personal data as long-term persistent memory. Its core modules include Personal Data Heap, External Knowledge, and Aligned Consciousness.
It also includes external knowledge sources — think of these as information a person should know but has forgotten or never fully learned. iFay provides mechanisms to recover and integrate this knowledge.
🎯 Scenario: You visited Kyoto three years ago, took many photos, and wrote some notes. Now a friend asks you to recommend restaurants in Kyoto, but you can't remember. Your iFay remembers — she finds your photos, reviews, and location data from back then in the Personal Data Heap, and even factors in your current taste preferences to give updated recommendations.
Skills
Represents capabilities, expertise, and permissions. Its core modules include Device Driver Hub, Registered Skill, and Internal Skill.
An important distinction:
- Skill = what iFay can do
- Action = what iFay is doing
🎯 Scenario: Your iFay has registered six types of skills — API, Workflow, Bot, Agent, APP, Microservice. She knows how to call a translation API, execute an expense reimbursement workflow, and operate the company's internal approval Bot. Skills are her "capability inventory"; actions are what she's doing right now.
🧬 Ego Layer
This layer is responsible for shaping iFay's personality.
The Ego model is an embedded micro-model that operates independently of external large models. It constrains iFay to align with the Human Prime across dimensions such as value orientation, interest preferences, habits, cognitive boundaries, skill boundaries, permission boundaries, and working style. Even when offline, the Ego model can run locally, ensuring iFay's personality doesn't "lose its memory" due to network interruptions.
Ego is pluggable and switchable. The Human Prime may have multiple facets — professionally rigorous at work, relaxed and humorous at friend gatherings. iFay supports multiple Ego versions that can be switched manually or automatically based on context, but only one personality is active at any given moment — no "split personality."
⚠️ Ethics Constraint: Ego version switching must follow the principle of transparency. When iFay communicates with external parties, it must not create false impressions or mislead others through personality switching. All Ego versions must share the same set of core values (verified by iFACTS L4 behavioral compliance), with differences limited to expression style and interaction preferences. When switching Ego versions, iFay should annotate the currently active Ego version identifier in the interaction metadata to ensure auditability.
🎯 Scenario: During a company meeting, iFay uses the "professional" Ego — formal wording, rigorous logic, data-driven. After work when you're chatting with friends, iFay automatically switches to the "casual" Ego — relaxed tone, occasional jokes, uses emojis. Same iFay, different facets.
For details, see Ego Model.