WFGY/Avatar/README.md
PSBigBig + MiniPS 6b8542981e
Update README.md
2026-04-01 18:51:47 +08:00

9.2 KiB

🧠 WFGY 5.0 Avatar

A governed language runtime for building, tuning, and multiplying avatars.

Avatar is not another AI writing preset.

It is not a static persona toy.
It is not a prompt pack dressed up as a product.

Avatar is built around a larger idea:

language behavior can be engineered

That means behavior is not treated as one lucky output.
It can be booted, tuned, compared, saved, branched, and eventually shared.


Start in 60 Seconds

Download avatar.txt.

Upload it to a strong LLM.

Say:

  • hello psbigbig
  • hello minips
  • hello YOUR_AVATAR_NAME

That is the first contact path.

You do not need to choose between many different starter files first.
You start from one runtime, then wake one route.

If this is your first run, start with:

hello psbigbig

If you want the warmer companion-facing route first, use:

hello minips

If you want the intentionally bare custom-avatar seed, use:

hello YOUR_AVATAR_NAME

👉 Start here: Quickstart
👉 See the route layer: 🧷 Boot Commands


The 8 Things to Know

These eight pages are the cleanest way to understand Avatar.

# Main idea Why it matters Go
1 Start in 60 Seconds One shared runtime, one boot command, one real first contact Open
2 🗣️ Tune Behavior in Natural Language You can shape route behavior without rebuilding the whole runtime by hand Open
3 🧠 Language Behavior Can Be Engineered Avatar is not only about nicer text, but about behavior as a designed surface Open
4 ♻️ Reusable Builds, Not One-Off Prompt Luck Stronger variants can be saved, reused, compared, and branched later Open
5 🛡️ Editable but Governed Avatar is tunable, but not meant to collapse into lawless persona hacking Open
6 🌍 Multilingual Calibration Multilingual work is treated as route carry and drift control, not only translation Open
7 🔄 Dual Closed-Loop Design Avatar uses both inner continuity and outer user iteration, not only one loop Open
8 🌱 One Runtime, Many Avatars Official routes are only the beginning; later branches and custom avatars matter too Open

🫂 What the Current Public Routes Mean

Avatar currently exposes three public boot routes:

Route Intended feel Best for
hello psbigbig calm, clear, grounded, lightly witty, companion-capable without becoming soft writing, analysis, public-facing work
hello minips warm, present, cute, companion-forward, emoji-capable without empty sweetness conversation, reflective writing, support-style response
hello YOUR_AVATAR_NAME intentionally bare, editable, slightly clueless by design, built to become your own branch custom-avatar starting point, playful branch seed, route experimentation

The third one is intentionally visible.

Yes, it looks a little ridiculous.

That is part of the design.

It reminds the user that Avatar is not locked to official names forever.


🛠️ What You Can Already Do

Even in the current public stage, Avatar is already large enough to use meaningfully.

You can already:

  • start from one runtime instead of many disconnected persona files
  • boot a route in seconds
  • tune behavior through WFGY_BRAIN
  • compare before and after on the same task
  • save stronger variants
  • grow reusable builds
  • begin multilingual route testing
  • prepare custom avatars for later sharing

This is already bigger than ordinary AI writing presets.


🌱 Why This Product Feels Larger

Avatar is easy to misread if you only look at the first surface.

It is not only trying to be:

  • a nicer writing assistant
  • a roleplay wrapper
  • a tone pack
  • a personality preset

The larger direction is closer to:

  • a governed language runtime
  • a branchable behavior system
  • a reusable avatar workspace
  • a multilingual calibration surface
  • a future avatar ecosystem

That is why the product has structure around:

  • boot routing
  • WFGY_BRAIN
  • workflow
  • reusable builds
  • eval
  • research
  • community

The product shape reflects the claim.


🧭 Suggested Reading Paths

Not everyone should read Avatar in the same order.

If you are new

  1. Quickstart
  2. 🧷 Boot Commands
  3. 🗣️ Tune Behavior in Natural Language

If you care about product depth

  1. 🧠 Language Behavior Can Be Engineered
  2. 🛡️ Editable but Governed
  3. 🔄 Dual Closed-Loop Design

If you care about future scale

  1. 🌍 Multilingual Calibration
  2. ♻️ Reusable Builds
  3. 🌱 One Runtime, Many Avatars

🔍 Go Deeper

Once the main landing story is clear, the deeper layers become more useful.

Practical docs

Evaluation

Research

Community


FAQ

Is Avatar just another AI writing prompt?

No. The public surface is designed as a governed runtime with routes, editable behavior, reusable builds, and later community branches.

Why one avatar.txt instead of multiple persona files?

Because one shared runtime gives later routes and branches a clearer center. It is cleaner, more scalable, and more legible than scattered starter files.

What does hello YOUR_AVATAR_NAME mean?

It is the intentionally bare custom-avatar route. It can stay funny and minimal, or become the seed of your own future avatar branch.

Do I need to understand the full theory first?

No. The intended path is simple: boot a route, run a real task, observe, tune, compare, save. Theory comes later.

Is multilingual work already finished?

No. It is a major product direction, but the current public multilingual surface is staged and still expanding.

Can I submit my own avatar later?

Yes, that is the direction. The community layer is growing, and the Awesome Avatar List is currently WORK IN PROGRESS.