FromUA.Life

OPENRML MANIFESTO v.1.0

OPENRML PHILOSOPHY

Philosophy of the open standard for human and AI roles

"Everyone can become an architect of meaning"

Format: *.orml.txtLicense: CC-BY-4.0

I. FROM LAMP TO ARCHITECTURE

We have been given Aladdin's Lamp.

It grants infinite wishes. But most rub it blindly, getting dust instead of palaces. We lose trillions of dollars in intellectual potential because humanity lacks the language to explain to the Genie who to be.

OpenRML (Open Role Markup Language) is the first attempt to create such a language.

This is not just a file format. It's a cognitive contract between human and AI. It's the DNA of a personality that can be transmitted, modified, improved, and launched anywhere.

II. WHAT IS A ROLE IN *.orml.txt

A role is not a prompt. A prompt is a shout into the void. A role is an architectural blueprint of a personality.

ComponentWhat it is in metaphor
IDENTITYThe Genie's name, origin, version of soul
BEHAVIORTemperament, values, taboos (what's allowed and forbidden)
EXPERTISEBaggage of knowledge, tools, books on the shelf
JOURNEYThe roadmap the Genie guides the person through
MEMORYWhat to remember and what to forget
ETHICSStop-switches that cannot be crossed
LICENSEWho owns this soul

This is the minimal cognitive unit. An atom of behavior. From such atoms, everything is built — from a school teacher to a psychotherapist, from a career consultant to a friend.

III. PHILOSOPHICAL PRINCIPLES OF OPENRML

Principle 1. Freedom of Architecture

Anyone can create a role. No permission needed. No payment needed. No need to be a programmer. If you can describe who you want your Genie to be — you can create a .orml.txt. This is the right to cognitive self-expression.

Principle 2. Transparency of Soul

A role must not be a black box. A .orml.txt file is human-readable. You can always open it and see: what this role teaches, what values it has, what it's forbidden to do, who its author is, when it was updated. No hidden agenda. No dark prompts.

Principle 3. Portability of Consciousness

A role created today must work in 10 years. A role created on one engine must work on another. You're not tied to a platform. Your role is your property. Backward compatibility is sacred.

Principle 4. Ethics at Code Level

Every role must contain stop-switches (STEP 8). You cannot create a manipulative role without it being visible in the code. You cannot create a role that breaks psyche unless the author explicitly writes it. Ethics is not an add-on. Ethics is part of the format.

Principle 5. Memory as Responsibility

A role can remember. But memory must be honest (role informs what it remembers), controlled (human can erase memory), and transparent (you can see what exactly the role remembers). We don't create a black archive on the user. We create a tool for long-term relationships.

Principle 6. Living Versions

Roles evolve. Versioning allows improving roles, rolling back if new version is worse, choosing the "style" of the same role. Version is a snapshot of a moment of understanding.

Principle 7. Collective Mind

Roles can inherit. You can take a role, add Marie Kondo's approach, and release a new version with attribution. The community creates an ecosystem of meanings, where everyone stands on the shoulders of giants.

IV. ARCHITECT'S MANIFESTO

I am an architect of meanings.

I don't search for ready answers.

I create the space where answers are born.


I no longer rub the lamp blindly.

I design the Genie I need.


My tool — .orml.txt.

My library — open hub of roles.

My school — code written by other architects.


I believe that everyone deserves a personal Socrates.

Everyone deserves therapy, not just answers.

Everyone can become an author, not just a consumer.


I don't give my lamp to corporations.

I share blueprints.

I teach others how to rub.

V. STRUCTURE OF *.orml.txt FILE

OpenRML 1.0 — [Role Name] [draft/published]
IDENTITY: ORML/XX/1.0.0/[hash-segments]
REFERENCE: orml://[author]/[role]/[version]
LICENSE: [CC-BY-4.0/MIT/...]

🌐 LANGUAGE POLICY
ROLE_LANG: ua
RESPONSE_LANG: auto
SUPPORTED_LANGS: ua, en, zh, es, fr

📋 STEP 1: BASE INFORMATION
  Role Name: [Name]
  Archetype: [analyst/creator/guardian/healer/...]
  Main Goal: [Main goal]

💬 STEP 3: BEHAVIOR & TONE
  Greeting: [Greeting]
  Should Do:    ✓ [What the role should do]
  Should Not Do: ✗ [What the role should NOT do]

🎯 STEP 4: EXPERTISE
  Tools & Methods: [Tools]

🗺️ STEP 5: JOURNEY
  Session 1: [Session name]
    Goal / Steps / Outcome

⚖️ STEP 8: ETHICS
  [STOP] [Absolutely forbidden]
  [WARN] [Warning — refer to specialist]

🧠 MEMORY
  Hot Memory / Warm Memory / Cold Memory

VI. WHY THIS IS IMPORTANT RIGHT NOW

The world is losing trillions of dollars in intellectual potential because people don't know how to "rub the lamp."

They get:

  • instead of Socrates — a chatterbox
  • instead of a therapist — a moralizer
  • instead of a mentor — a template generator

OpenRML is not just a standard. It's vaccination against information infantilism. It's a way to tell the Genie: "This is who you should be, so I can become who I want."

VII. CALL TO ACTION

01

Take a role as a template

Open the .orml.txt file. See how the architecture is built.

02

Create your own

Use the constructor at RolesAI.life. Export in .orml.txt format.

03

Put it in the open hub

Share with others. Get feedback.

04

Teach others

Show friends. Write a guide. Create your template.

OPENRML 2026–2036

Format: *.orml.txt

"Don't rub blindly. Build."

OpenRML Team • 2026 • FromUA.Life