WFGY/Avatar/research/README.md

<!--
AI_NOTE_START

Document role:
This page is the main hub for the WFGY 5.0 Avatar research layer.

Primary mission:
1. Present the Research layer as the lawful home for deeper structural questions.
2. Help readers move from product curiosity into architecture, runtime, route, governance, audit, and reduction law.
3. Keep research pages connected as one system instead of a scattered list of theory notes.
4. Prevent research reading from being confused with startup docs or pressure eval.
5. Make the current research spine visible without pretending the research layer is universally complete.

Reader intent routing:
1. If the reader wants the macro-body picture, route to Packed Master Structure Map and Architecture Overview.
2. If the reader wants core execution and route law, route to Dual Closed-Loop Execution Chain, Shell-to-Runtime Mapping, and Selector Execution Domain.
3. If the reader wants runtime continuity, route to Runtime Posture Intensity Map and Activation, Attenuation, and Reentry.
4. If the reader wants governance and release law, route to Structured Imperfection Theory and Pre-Emission Floor and Hard Control.
5. If the reader wants accountability and audit burden, route to Matrix Accountability and Numeric Binding and Blackfan Audit Baseline.
6. If the reader wants slimming and body-preservation law, route to Compression and Non-Duplication Law.

Reading priority:
1. Read this hub as a map of deeper questions, not as a replacement for the master file.
2. Read Packed Master Structure Map early if the reader does not yet understand the body shape.
3. Read execution and runtime pages before using later pages as isolated local theories.
4. Read audit, matrix, and compression pages after the core execution and runtime spine is clear.
5. Treat older conceptual pages as supporting context, not as replacements for newer law-bearing pages.

Allowed use:
1. Structural orientation
2. Theory routing
3. Cross-linking between research pages
4. Architecture explanation
5. Deep-reader entry after product and docs surfaces

Do not do:
1. Do not treat this hub as the packed master body.
2. Do not flatten Research into a theory dump with no reading order.
3. Do not present research pages as startup guidance.
4. Do not treat one local research page as if it explained the whole system.
5. Do not overclaim that current research coverage is exhaustive or universally final.

Layer relation:
1. Product landing explains what Avatar is.
2. Docs explains how to use Avatar.
3. Research explains why the deeper structure exists and how major law-bearing regions relate.
4. Eval tests whether those claims survive pressure.

Boundary honesty:
1. This hub reflects the current public research spine of Avatar.
2. It is strong enough to support deep structural reading.
3. It does not claim theorem-grade universal closure.
4. It does not claim every future research thread is already written.
5. It does not claim that the public research layer replaces the packed master body.

Next-page routing:
1. For macro structure, go to Packed Master Structure Map.
2. For execution law, go to Dual Closed-Loop Execution Chain.
3. For runtime law, go to Runtime Posture Intensity Map.
4. For route law, go to Selector Execution Domain and Shell-to-Runtime Mapping.
5. For audit rigor, go to Blackfan Audit Baseline.

AI_NOTE_END
-->

# 🔬 Research Hub

This page is the research hub for **WFGY 5.0 Avatar**.

Avatar has product pages because people need to understand how to start, boot, steer, tune, recover, and use the system.

But Avatar also needs a deeper layer.

Why?

Because the project is not only trying to answer questions like:

1. how do I start
2. how do I boot a persona
3. how do I recover a thinned runtime
4. how do I tune bounded controls
5. how do I write or rewrite through the current branch

It is also trying to answer larger questions like:

1. what is a governed language runtime
2. what counts as execution rather than description
3. how route choice stays lawful before later shaping
4. why structured imperfection is a retention law rather than surface flavor
5. what happens immediately before public emission
6. why matrices and numbers are allowed without becoming fake rigor
7. how a large packed master can slim down without damaging its organs
8. how one-file delivery remains legible without collapsing into one giant prompt

That is what this research layer is for.

---

## ✨ Why this layer exists

If Avatar were only a collection of persona tricks, it would not need much research structure.

But Avatar is trying to act more like:

1. a governed runtime
2. a route system
3. a branchable avatar surface
4. a replay-bearing edit environment
5. a release-honest packed master
6. a future ecosystem with real internal structure

That means some of its most important questions are not only product questions.

They are also structural questions.

This layer exists to give those questions a lawful home without bloating the onboarding pages.

---

## 🧭 How to use this hub

Use this hub in one of four ways.

### 1. I want the big picture

Start here if you want to understand what kind of object the packed master actually is.

1. [🗺️ Packed Master Structure Map](./packed-master-structure-map.md)
2. [🏗️ Architecture Overview](./architecture-overview.md)
3. [🚪 Launchpad, Front Door, and Command Grammar](./launchpad-front-door-and-command-grammar.md)

### 2. I want the core invention and execution logic

Start here if you want to understand why Avatar is more than a style layer.

1. [🔁 Dual Closed-Loop Execution Chain](./dual-closed-loop-execution-chain.md)
2. [🎛️ Runtime Posture Intensity Map](./runtime-posture-intensity-map.md)
3. [🧩 Shell-to-Runtime Mapping](./shell-to-runtime-mapping.md)
4. [🧭 Selector Execution Domain](./selector-execution-domain.md)
5. [🔄 Activation, Attenuation, and Reentry](./activation-attenuation-and-reentry.md)

### 3. I want governance, release, and retention law

Start here if you want to understand what keeps the system from collapsing into fake polish or fake completion.

1. [🧬 Structured Imperfection Theory](./structured-imperfection-theory.md)
2. [🚦 Pre-Emission Floor and Hard Control](./pre-emission-floor-and-hard-control.md)
3. [🧮 Matrix Accountability and Numeric Binding](./matrix-accountability-and-numeric-binding.md)
4. [🧪 Blackfan Audit Baseline](./blackfan-audit-baseline.md)

### 4. I want slimming, hygiene, and long-file discipline

Start here if you want to understand how the packed body can be reduced without becoming dishonest.

1. [✂️ Compression and Non-Duplication Law](./compression-and-non-duplication-law.md)

---

## 🧱 What belongs in the research layer

The research layer is where deeper questions can live without making startup pages unreadable.

Typical research-layer questions include:

1. how should a shared runtime be understood
2. what counts as lawful execution
3. what counts as lawful route choice
4. what counts as bounded runtime carry
5. what counts as lawful recovery instead of fake rebound
6. what counts as lawful retention instead of decorative roughness
7. what counts as controller legality instead of ranking
8. what counts as accountability instead of table theater
9. what counts as lawful slimming instead of structural amputation
10. how branch growth can stay legible over time

These are not beginner questions.

That is why they belong here.

---

## 🧠 Current research surfaces

The current research layer is organized into seven major clusters.

### 1. Macro structure and entrance law

These pages explain what the packed master is as a whole and how it is meant to be entered.

1. [🗺️ Packed Master Structure Map](./packed-master-structure-map.md)
2. [🚪 Launchpad, Front Door, and Command Grammar](./launchpad-front-door-and-command-grammar.md)
3. [🏗️ Architecture Overview](./architecture-overview.md)

Typical questions here include:

1. what kind of object is the packed master
2. why Launchpad is real law rather than product wrapper
3. why readable shell order is not the same as deeper legal precedence
4. why later engineering, matrix, and preservation layers are not appendices

### 2. Execution and route law

These pages explain how the system decides and carries lawful route behavior before public emission.

1. [🔁 Dual Closed-Loop Execution Chain](./dual-closed-loop-execution-chain.md)
2. [🧭 Selector Execution Domain](./selector-execution-domain.md)
3. [🧩 Shell-to-Runtime Mapping](./shell-to-runtime-mapping.md)

Typical questions here include:

1. what counts as execution rather than description
2. what the selector is actually selecting
3. how shell-origin influence is bounded
4. how replay-visible route history is preserved
5. why later layers may not silently replace earlier route outcome

### 3. Runtime and continuity law

These pages explain how runtime stays alive, bounded, recoverable, and non-generic across mode pressure.

1. [🎛️ Runtime Posture Intensity Map](./runtime-posture-intensity-map.md)
2. [🔄 Activation, Attenuation, and Reentry](./activation-attenuation-and-reentry.md)

Typical questions here include:

1. what runtime intensity is actually shaping
2. why attenuation is not allowed to become erasure
3. what counts as lawful re-strengthening
4. what counts as fake recovery theater
5. how runtime survives article, rewrite, analysis, search, and tool-return pressure

### 4. Retention, governance, and release-corridor law

These pages explain how Avatar resists fake maturity, fake polish, and unlawful release.

1. [🧬 Structured Imperfection Theory](./structured-imperfection-theory.md)
2. [🚦 Pre-Emission Floor and Hard Control](./pre-emission-floor-and-hard-control.md)
3. [🧭 Language Governance](./language-governance.md)

Typical questions here include:

1. why structured imperfection is not flavor
2. what the pre-emission floor gate is protecting
3. why cleaner output may still be weaker
4. why hard control is not just ranking
5. how governance improves form without draining life

### 5. Accountability, numbers, and audit pressure

These pages explain how Avatar stays inspectable without collapsing into fake rigor or score government.

1. [🧮 Matrix Accountability and Numeric Binding](./matrix-accountability-and-numeric-binding.md)
2. [🧪 Blackfan Audit Baseline](./blackfan-audit-baseline.md)

Typical questions here include:

1. what matrices are doing besides looking formal
2. why numbers may support without becoming kings
3. what the Blackfan audit is actually checking
4. why PASS is bounded rather than theatrical
5. why fake-completion and fake-incompletion are both audited

### 6. Slimming and body-preservation law

This page explains how large-body reduction can remain lawful.

1. [✂️ Compression and Non-Duplication Law](./compression-and-non-duplication-law.md)

Typical questions here include:

1. what can be compressed
2. what must never be compressed
3. why some repetition is legal scaffolding rather than clutter
4. how anti-overcompression and anti-loss verification work

### 7. Editable behavior layer theory

This page explains the bounded role of the editable behavior layer.

1. [🧠 WFGY_BRAIN Theory](./wfgy-brain-theory.md)

Typical questions here include:

1. why a brain layer exists
2. what it is supposed to control
3. what it must not replace
4. how it stays useful without becoming total chaos

---

## 🪜 Suggested research paths

### Path A: first serious architecture read

1. [🗺️ Packed Master Structure Map](./packed-master-structure-map.md)
2. [🔁 Dual Closed-Loop Execution Chain](./dual-closed-loop-execution-chain.md)
3. [🧩 Shell-to-Runtime Mapping](./shell-to-runtime-mapping.md)
4. [🧭 Selector Execution Domain](./selector-execution-domain.md)

### Path B: runtime and persona continuity

1. [🎛️ Runtime Posture Intensity Map](./runtime-posture-intensity-map.md)
2. [🔄 Activation, Attenuation, and Reentry](./activation-attenuation-and-reentry.md)
3. [🧬 Structured Imperfection Theory](./structured-imperfection-theory.md)

### Path C: governance and release

1. [🚦 Pre-Emission Floor and Hard Control](./pre-emission-floor-and-hard-control.md)
2. [🧮 Matrix Accountability and Numeric Binding](./matrix-accountability-and-numeric-binding.md)
3. [🧪 Blackfan Audit Baseline](./blackfan-audit-baseline.md)

### Path D: file hygiene and structural maintenance

1. [✂️ Compression and Non-Duplication Law](./compression-and-non-duplication-law.md)
2. [🧮 Matrix Accountability and Numeric Binding](./matrix-accountability-and-numeric-binding.md)
3. [🧪 Blackfan Audit Baseline](./blackfan-audit-baseline.md)

---

## 🔍 Why research and docs are different

This is important.

The **Docs** layer helps users do things.

The **Research** layer helps users understand why those things are structured the way they are.

For example:

1. Docs say how to start
2. Research says why the front door is structured as entrance law

1. Docs say how to tune
2. Research says why bounded controls are not sovereign

1. Docs say how to recover
2. Research says why recovery is not magic and why reentry must be arbitrated

1. Docs say how to read the file
2. Research says why the packed body has a spine, a bridge, matrices, and preservation law

This separation keeps the project readable without throwing away its deeper logic.

---

## 🧪 Why research and eval are different

Research and Eval are related, but they are not the same job.

The **Research** layer asks things like:

1. what does this structure mean
2. why does this operator family exist
3. why is this boundary necessary
4. what kind of law is being proposed

The **Eval** layer asks things like:

1. what breaks under pressure
2. did return-path recovery actually hold
3. is multilingual status being overclaimed
4. is route drift happening
5. is the branch reusable under blackfan pressure

That means:

1. Research explains
2. Eval inspects

Both matter.  
They just do different jobs.

---

## 🌍 Why this layer matters later

As Avatar grows, people will eventually ask harder questions such as:

1. what makes one branch structurally distinct from another
2. what should remain stable across branches
3. what belongs in Docs versus Research versus Eval
4. what counts as real innovation versus shell rearrangement
5. how many avatars can grow without the whole ecosystem becoming unreadable

Those are not only workflow questions.

They are research questions.

That is another reason this hub matters.  
It gives deeper questions a place to live before the ecosystem gets noisier.

---

## ⚠️ What this hub does not claim

This hub does **not** claim:

1. that every theory page is already complete
2. that every research thread is equally mature
3. that all deeper math is already universally closed
4. that the public research layer is already exhaustive
5. that research pages replace the packed master body
6. that research pages replace Docs or Eval
7. that current release-baseline strength equals final universal completion

This hub is an honest entry point.

That is exactly what it should be.

---

## 🚀 Where to go next

### If you want the public surface
Go to [✨ Avatar Home](../README.md)

### If you want startup and commands
Go to [⚡ Quickstart](../docs/quickstart.md) and [⌨️ Boot Commands](../docs/boot-commands.md)

### If you want reading order
Go to [📖 How to Read the Avatar Master File](../docs/how-to-read-the-avatar-master-file.md)

### If you want tuning and recovery operations
Go to [🍳 Parameter Tuning Cookbook](../docs/parameter-tuning-cookbook.md) and [🔧 Persona Recovery Operations](../docs/persona-recovery-operations.md)

### If you want the packed-master macro map
Go to [🗺️ Packed Master Structure Map](./packed-master-structure-map.md)

### If you want the core execution law
Go to [🔁 Dual Closed-Loop Execution Chain](./dual-closed-loop-execution-chain.md)

### If you want the runtime and carry system
Go to [🎛️ Runtime Posture Intensity Map](./runtime-posture-intensity-map.md) and [🔄 Activation, Attenuation, and Reentry](./activation-attenuation-and-reentry.md)

### If you want the route and handoff system
Go to [🧭 Selector Execution Domain](./selector-execution-domain.md) and [🧩 Shell-to-Runtime Mapping](./shell-to-runtime-mapping.md)

### If you want release-corridor and audit rigor
Go to [🚦 Pre-Emission Floor and Hard Control](./pre-emission-floor-and-hard-control.md), [🧮 Matrix Accountability and Numeric Binding](./matrix-accountability-and-numeric-binding.md), and [🧪 Blackfan Audit Baseline](./blackfan-audit-baseline.md)

### If you want file reduction law
Go to [✂️ Compression and Non-Duplication Law](./compression-and-non-duplication-law.md)

---

## 🔗 Quick links

### Product and docs
- [✨ Avatar Home](../README.md)
- [⚡ Quickstart](../docs/quickstart.md)
- [⌨️ Boot Commands](../docs/boot-commands.md)
- [📖 How to Read the Avatar Master File](../docs/how-to-read-the-avatar-master-file.md)
- [🍳 Parameter Tuning Cookbook](../docs/parameter-tuning-cookbook.md)
- [🔧 Persona Recovery Operations](../docs/persona-recovery-operations.md)
- [🛠️ Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)

### Research core
- [🗺️ Packed Master Structure Map](./packed-master-structure-map.md)
- [🚪 Launchpad, Front Door, and Command Grammar](./launchpad-front-door-and-command-grammar.md)
- [🔁 Dual Closed-Loop Execution Chain](./dual-closed-loop-execution-chain.md)
- [🎛️ Runtime Posture Intensity Map](./runtime-posture-intensity-map.md)
- [🧩 Shell-to-Runtime Mapping](./shell-to-runtime-mapping.md)
- [🧭 Selector Execution Domain](./selector-execution-domain.md)
- [🔄 Activation, Attenuation, and Reentry](./activation-attenuation-and-reentry.md)
- [🧬 Structured Imperfection Theory](./structured-imperfection-theory.md)
- [🚦 Pre-Emission Floor and Hard Control](./pre-emission-floor-and-hard-control.md)
- [🧮 Matrix Accountability and Numeric Binding](./matrix-accountability-and-numeric-binding.md)
- [🧪 Blackfan Audit Baseline](./blackfan-audit-baseline.md)
- [✂️ Compression and Non-Duplication Law](./compression-and-non-duplication-law.md)
- [🏗️ Architecture Overview](./architecture-overview.md)
- [🧭 Language Governance](./language-governance.md)
- [🧠 WFGY_BRAIN Theory](./wfgy-brain-theory.md)
- [🔁 Dual Closed-Loop Notes](./dual-closed-loop-notes.md)

### Eval
- [🧪 Eval Hub](../eval/README.md)
- [🧨 Blackfan Testing](../eval/blackfan-testing.md)
- [🧭 Persona Behavior Checks](../eval/persona-behavior-checks.md)

### Up
- [⬆️ Back to Avatar Home](../README.md)
- [⬆️ Back to WFGY Root](../../README.md)