Architecture

v5.1

Output is evidence. Growth is the purpose. Flourishing is the destination.

Output is evidence. Growth is the purpose. Flourishing is the destination.

Sorinverse의 계층 구조를 공개합니다. 이 페이지는 구조만 다룹니다 — 제품 계획과 상태는 모두 개발 로드맵에 있습니다.

계층 전체 구조

Layer spine G0 to L5The seven layers of the architecture, from the goal layer G0 down to infrastructure L5, each with the question it answers. Click a layer to jump to its section.G0Human FlourishingWhat is the ultimate human purpose?L0Core PathwayWhich pathway gets us there?L1Human Intelligence SystemsWhat capabilities does the pathway require?L2Platform LayerWhat implements those capabilities?L3Scene SolutionsIn which scenes are they used?L4Products & AppsHow do scenes become products?L5InfrastructureHow does technology support it all?
G0

Human Flourishing

What is the ultimate human purpose?

Everything exists for human flourishing.

10 Growth Dimensions

IQ

Cognitive

EQ

Emotional

BQ

Body

CQ

Creative

SQ

Social

FQ

Financial

AQ

Adversity

MQ

Meaning

FrQ

Frontier

WQ

Wellbeing

L0

Core Pathway

Which pathway gets us there?

Sorinverse — Human Intelligence Liberation System

Intelligence is the master lever — liberate it, and all dimensions of flourishing compound.

MissionLiberating Human Intelligence.

So ordinary people can learn, understand, create, and realize their life's value — more easily, faster, and with more joy.

i

Learn Faster

ii

Understand Better

iii

Express Clearly

iv

Create More

v

Live Freer

vi

Greater Impact

L1

Human Intelligence Systems

9 capabilities

What capabilities does the pathway require?

Observation

01 · OBSERVE

Sensory input · Attention focus · Signal recognition · Experiential presence

perception

Learning

02 · LEARN

Rapid learning · Information filtering · Knowledge absorption · Language acquisition

perceptionstructure

Understanding

03 · UNDERSTAND

Structured understanding · Systems thinking · Semantic compression · Essence abstraction

structuresystemevidence

Recall

04 · RECALL

Number memory · Word memory · Image memory · Knowledge retrieval

evidencestructure

Reasoning

05 · REASON

Logical reasoning · Critical thinking · Decision judgment · Handling uncertainty

systemfatevalue

Communication

06 · COMMUNICATE

Voice & pronunciation · Logic of expression · Writing & speaking · Influencing others

expressionrelationship

Creation

07 · CREATE

★ OUTPUT-CORE

Written output · Video & imagery · Teaching products · Commercial productization

expressionmanagementphysic

Execution

08 · EXECUTE

Time management · Discipline & habits · Financial management · Household operations

managementresourceprotection

Adaptation

09 · ADAPT

AI collaboration · Meta-learning · Cross-domain integration · Future adaptation

fatephysic+ all

개발 로드맵 제품 카드의 능력 태그(記憶 / 理解 / 実行 등)는 바로 이 9가지 능력입니다.

개발 로드맵 보기 →
L2

Platform Layer

12 engines · 5 groups

What implements those capabilities?

Output-Centric Architecture — everything flows toward expression.

L2 engine flowIN, COGNIZE, DECIDE and OUTPUT stages flow top to bottom into expression; the BASE substrate sits at the bottom. Engines are nodes inside each stage.01 · IN — PERCEIVESense02 · COGNIZE — MODEL THE WORLDUnderstand / Model03 · DECIDE — EVALUATE OPTIONSEvaluate / Choose04 · OUTPUT — EXPRESS / CREATEExpress / ExecutePerception & experienceperception-engineStructure & understandingstructure-engineSystems & simulationsystem-engineRelationships & propagationrelationship-engineEvidence & credibilityevidence-engineBranching & predictionfate-engineValues & prioritiesvalue-engineResources & constraintsresource-engineProtection & riskprotection-engineExpression & externalizationexpression-engineManagement & executionmanagement-engine00 · BASESubstratePhysical interaction & creationphysic-engine

Engines do not map one-to-one to L1 capabilities. A capability is the user's view — what you do. An engine is the system's view — how it is done. One capability is an orchestra of several engines.

Output-Centric is not one of the engines — it is the objective function of all of them. Perceiving, modeling, and deciding exist for the sake of some externalized output.

L1 × L2 — 능력은 엔진들의 협주다

L1 capabilitiesObservationLearningUnderstandingRecallReasoningCommunicationCreationExecutionAdaptation
L1 × L2 invocation matrixNine capabilities against twelve engines. A filled dot marks a primary invocation; a small hollow dot marks a secondary one. Capabilities and engines relate many-to-many.physicperceptionstructuresystemrelationshipevidencefatevalueresourceprotectionexpressionmanagement

● = 주요 호출 · ○ = 보조 호출 (적응은 모든 엔진에 연결)

L3

Scene Solutions

6 scenes

In which scenes are they used?

Sorinverse

Study

Master new knowledge and skills, faster

→ ENGINES

perceptionstructureevidenceexpression
Sorinverse

Work

Raise working efficiency and outcomes

→ ENGINES

systemvaluemanagementresource
Sorinverse

Creator

From idea to work and influence

→ ENGINES

expressionrelationshipphysicfate
Sorinverse

Life

A more ordered life with less mental load

→ ENGINES

managementresourceprotectionvalue
Sorinverse

Health

Manage health, prevent risk, extend lifespan

→ ENGINES

perceptionevidenceprotectionmanagement
Sorinverse

Kids

Scientific parenting, whole-person growth

→ ENGINES

structureexpressionrelationshipphysic
L4

Products & Apps

How do scenes become products?

Individual products live at this layer. What is being built, and where each product stands, is published on the development roadmap.

개발 로드맵 보기 →
E

Perfect Me

the Growth OS Entry

Perfect Me is not another learning app. It is the single entry point of the whole Sorinverse ecosystem — you answer "who do you want to become", and the system decomposes that goal into capabilities, then orchestrates scenes and products. It is a product, and at the same time a distribution protocol.

User Flow

  1. 01Enter Perfect Me and choose who you want to become → G0 dimensions (IQ · BQ · CQ · FQ · MQ …)
  2. 02The goal decomposes into trainable capabilities → L1 (Observe · Learn · Understand · Create …)
  3. 03Capabilities combine into scene solutions → L3 (Study · Health · Creator …)
  4. 04Scenes orchestrate concrete products into a training path → L4 products (Memory Trainer · Health Manager …)
  5. 05Use produces the six output types → growth evidence flows back and refreshes the G0 assessment

Without the single entry point, the products are just a pile of apps. With it, Sorinverse becomes an operating system — the user faces "who do I want to become", not "which app do I pick".

L5

Infrastructure

10 layers

How does technology support it all?

Cloud / edge computing

Cloud / Edge

Large-model capability

AI / LLM

Data lake

Data Lake

Vector database

Vector DB

Knowledge graph

Knowledge Graph

Security & privacy

Security

Interfaces & dev tools

API / SDK

Continuous delivery

DevOps

Data analytics

Analytics

Backup & disaster recovery

Backup / DR

The Output Filter

v4

Output is evidence. Growth is the goal.

Every Sorinverse product must produce at least one observable output in one of these six domains.

01 · COGNITIVE

Cognitive Output

Ideas, articles, teaching materials, research results.

→ IQ · FrQ

02 · SKILL

Skill Output

Certificates, language ability, technical mastery.

→ IQ · CQ

03 · PHYSICAL

Physical Output

Health metrics, fitness, sleep curves.

→ BQ · WQ

04 · FINANCIAL

Financial Output

Income, assets, business results.

→ FQ

05 · SOCIAL

Social Output

Relationship quality, influence, collaborative results.

→ SQ · MQ

06 · GROWTH

Personal Growth

Habits, emotional regulation, sense of meaning, quality of life.

→ EQ · AQ · MQ · WQ

✕ None of the six? Not Sorinverse — no matter how technically beautiful.

"Output is not the destination — it is the evidence of becoming."

Core Principles

01

Flourishing-Bound

Flourishing-Bound

02

Growth Purpose · Output Proof

Growth Purpose · Output Proof

03

Systemic Thinking

Systemic Thinking

04

Composable & Scalable

Composable & Scalable

05

Verifiable & Measurable

Verifiable & Measurable

06

Safe, Private & Aligned

Safe, Private & Aligned

07

Many-to-Many Hierarchy

Many-to-Many Hierarchy

08

Vertical First

Vertical First