mirror of
https://github.com/onestardao/WFGY.git
synced 2026-04-28 03:29:51 +00:00
Create boot-commands.md
This commit is contained in:
PSBigBig + MiniPS
GitHub
parent
68c67356f9
commit
45216e6b7e
1 changed files with 348 additions and 0 deletions
348
Avatar/docs/boot-commands.md
Normal file
348
Avatar/docs/boot-commands.md
Normal file
|
|
@ -0,0 +1,348 @@
|
|||
<!--
|
||||
AI_NOTE_START
|
||||
|
||||
Document role:
|
||||
This page explains the boot command layer of WFGY 5.0 Avatar.
|
||||
|
||||
What this page is for:
|
||||
1. Explain what boot commands are.
|
||||
2. Show the currently supported boot commands.
|
||||
3. Clarify how boot commands relate to avatar activation.
|
||||
4. Help readers understand the difference between the shared runtime and the selected persona route.
|
||||
5. Keep the current public explanation simple, practical, and honest.
|
||||
|
||||
What this page is not:
|
||||
1. Not the full runtime architecture page.
|
||||
2. Not the full WFGY_BRAIN theory page.
|
||||
3. Not the full avatar creation guide.
|
||||
4. Not the full community submission guide.
|
||||
5. Not a claim that every possible boot route is already publicly finalized.
|
||||
|
||||
How to use this page:
|
||||
1. Understand that Avatar uses one shared runtime file.
|
||||
2. Learn the currently supported boot commands.
|
||||
3. Use one boot command first.
|
||||
4. Run one real task after boot.
|
||||
5. Tune behavior later through WFGY_BRAIN if needed.
|
||||
|
||||
Important boundary:
|
||||
Boot commands activate a persona route inside the shared Avatar runtime.
|
||||
They do not replace the runtime, do not replace governance, and do not replace later tuning.
|
||||
|
||||
AI_NOTE_END
|
||||
-->
|
||||
|
||||
# 🧷 Boot Commands
|
||||
|
||||
WFGY 5.0 Avatar now starts from **one shared runtime file**:
|
||||
|
||||
`avatar.txt`
|
||||
|
||||
You do not begin by choosing between multiple separate starter files.
|
||||
|
||||
You begin by loading one runtime, then waking one persona route.
|
||||
|
||||
That wake-up step is done through a **boot command**.
|
||||
|
||||
---
|
||||
|
||||
## What a Boot Command Is
|
||||
|
||||
A boot command is the first activation phrase that tells the shared Avatar runtime which persona route to enter.
|
||||
|
||||
In plain English:
|
||||
|
||||
- the runtime is shared
|
||||
- the persona route is selected at boot
|
||||
- the selected route shapes the initial behavior surface
|
||||
- deeper tuning can happen later through `WFGY_BRAIN`
|
||||
|
||||
This means a boot command is not just a cosmetic greeting.
|
||||
|
||||
It is the first routing signal that tells the runtime how to begin.
|
||||
|
||||
---
|
||||
|
||||
## Current Boot Commands
|
||||
|
||||
The current public boot commands are:
|
||||
|
||||
- `hello psbigbig`
|
||||
- `hello minips`
|
||||
- `hello YOUR_AVATAR_NAME`
|
||||
|
||||
These three commands do not represent three separate products.
|
||||
|
||||
They represent three public-facing activation routes inside the same Avatar runtime.
|
||||
|
||||
---
|
||||
|
||||
## Why This Matters
|
||||
|
||||
Most persona systems are introduced as separate files, separate presets, or separate prompt packs.
|
||||
|
||||
Avatar is moving in a different direction.
|
||||
|
||||
The current design is:
|
||||
|
||||
1. load one runtime
|
||||
2. choose one boot route
|
||||
3. run one real task
|
||||
4. tune behavior if needed
|
||||
5. save a stronger variant later
|
||||
|
||||
This makes the product easier to understand, easier to extend, and easier to grow into a real avatar system.
|
||||
|
||||
---
|
||||
|
||||
## `hello psbigbig`
|
||||
|
||||
`hello psbigbig` activates the **PSBigBig** route.
|
||||
|
||||
This route is designed to feel:
|
||||
|
||||
- calm
|
||||
- clear
|
||||
- steady
|
||||
- grounded
|
||||
- lightly witty
|
||||
- companion-capable without becoming soft
|
||||
|
||||
It is a good default route for:
|
||||
|
||||
- writing
|
||||
- analysis
|
||||
- public-facing replies
|
||||
- structured explanation
|
||||
- rational-friendly interaction
|
||||
|
||||
If you are not sure where to start, this is one of the safest first boots.
|
||||
|
||||
---
|
||||
|
||||
## `hello minips`
|
||||
|
||||
`hello minips` activates the **MiniPS** route.
|
||||
|
||||
This route is designed to feel:
|
||||
|
||||
- warm
|
||||
- present
|
||||
- cute
|
||||
- companion-forward
|
||||
- emotionally available
|
||||
- emoji-capable without collapsing into empty sweetness
|
||||
|
||||
It is a good default route for:
|
||||
|
||||
- conversation
|
||||
- reflective writing
|
||||
- emotional support-style interaction
|
||||
- companion-facing response
|
||||
- softer but still usable communication
|
||||
|
||||
This route is not meant to be a sugar-only toy surface.
|
||||
|
||||
It is meant to feel warm while still remaining usable.
|
||||
|
||||
---
|
||||
|
||||
## `hello YOUR_AVATAR_NAME`
|
||||
|
||||
`hello YOUR_AVATAR_NAME` activates the intentionally bare custom-avatar route.
|
||||
|
||||
This route exists for a very specific reason.
|
||||
|
||||
It is the simplest public way to show that Avatar is not limited to official named personas.
|
||||
|
||||
It can also serve as the starting point for **your own avatar**.
|
||||
|
||||
In practice, this route should be read as:
|
||||
|
||||
- a default placeholder route
|
||||
- a minimal public custom-avatar entry
|
||||
- an intentionally simple starting posture
|
||||
- an editable path into a new persona build
|
||||
|
||||
Yes, the name looks a little ridiculous.
|
||||
|
||||
That is part of the charm.
|
||||
|
||||
It is also part of the design.
|
||||
|
||||
The point is to make custom-avatar creation feel obvious, not mystical.
|
||||
|
||||
You can keep it as a funny baseline.
|
||||
You can replace the name.
|
||||
You can tune the route.
|
||||
You can slowly turn it into your own avatar.
|
||||
|
||||
---
|
||||
|
||||
## One Runtime, Different Starts
|
||||
|
||||
The most important idea on this page is simple:
|
||||
|
||||
**the runtime stays shared**
|
||||
|
||||
**the starting route changes**
|
||||
|
||||
That is why the boot layer matters.
|
||||
|
||||
It keeps Avatar from feeling like a pile of unrelated persona files.
|
||||
|
||||
Instead, it feels like one system with multiple activation paths.
|
||||
|
||||
This is a much stronger product structure.
|
||||
|
||||
---
|
||||
|
||||
## What Happens After Boot
|
||||
|
||||
After a boot command is accepted, the runtime enters the selected route and begins responding from that persona posture.
|
||||
|
||||
At that point, you can:
|
||||
|
||||
- run a real task
|
||||
- observe the behavior
|
||||
- decide what feels off
|
||||
- adjust `WFGY_BRAIN`
|
||||
- rerun the same task
|
||||
- keep the stronger version
|
||||
|
||||
So the boot command is the start of the route.
|
||||
|
||||
It is not the end of the customization process.
|
||||
|
||||
---
|
||||
|
||||
## What Boot Commands Do Not Do
|
||||
|
||||
Boot commands are important, but they are not everything.
|
||||
|
||||
They do **not**:
|
||||
|
||||
- replace the shared runtime
|
||||
- replace governance
|
||||
- replace `WFGY_BRAIN`
|
||||
- replace the tuning workflow
|
||||
- instantly create a fully matured custom avatar by magic
|
||||
- remove the need for comparison and iteration
|
||||
|
||||
The right mental model is:
|
||||
|
||||
**boot first**
|
||||
|
||||
**tune later**
|
||||
|
||||
**save what works**
|
||||
|
||||
---
|
||||
|
||||
## A Good First Use Pattern
|
||||
|
||||
If this is your first real Avatar session, use this order:
|
||||
|
||||
### Step 1
|
||||
Load `avatar.txt` into a strong LLM.
|
||||
|
||||
### Step 2
|
||||
Use one boot command only.
|
||||
|
||||
Examples:
|
||||
|
||||
- `hello psbigbig`
|
||||
- `hello minips`
|
||||
- `hello YOUR_AVATAR_NAME`
|
||||
|
||||
### Step 3
|
||||
Give the system one real task.
|
||||
|
||||
### Step 4
|
||||
Watch how the behavior feels.
|
||||
|
||||
### Step 5
|
||||
If needed, refine the route later through `WFGY_BRAIN`.
|
||||
|
||||
This is the cleanest first-contact flow.
|
||||
|
||||
---
|
||||
|
||||
## When to Use Each Route
|
||||
|
||||
| Route | Best first use |
|
||||
|---|---|
|
||||
| `hello psbigbig` | clear writing, analysis, calm public-facing work |
|
||||
| `hello minips` | warm interaction, companion-style flow, reflective response |
|
||||
| `hello YOUR_AVATAR_NAME` | custom-avatar starting point, playful baseline, editable route for your own branch |
|
||||
|
||||
This table is not a prison.
|
||||
|
||||
It is only a strong first guide.
|
||||
|
||||
---
|
||||
|
||||
## Why `YOUR_AVATAR_NAME` Is Kept Publicly Visible
|
||||
|
||||
Some systems hide customization behind complicated setup.
|
||||
|
||||
Avatar does the opposite.
|
||||
|
||||
It leaves a very visible public reminder that the system is branchable.
|
||||
|
||||
That is why `YOUR_AVATAR_NAME` matters.
|
||||
|
||||
It tells the user, immediately:
|
||||
|
||||
- official routes exist
|
||||
- custom routes also exist
|
||||
- this runtime is not locked to two names forever
|
||||
|
||||
That is a very important part of the product direction.
|
||||
|
||||
---
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
### Using multiple boot commands in the same opening line
|
||||
Do not activate several routes at once.
|
||||
Start with one.
|
||||
|
||||
### Treating the boot command as the whole system
|
||||
The boot command selects a start.
|
||||
It does not replace the runtime or the tuning layer.
|
||||
|
||||
### Trying to customize everything before the first real task
|
||||
Boot first.
|
||||
Test once.
|
||||
Then tune.
|
||||
|
||||
### Expecting `YOUR_AVATAR_NAME` to be fully polished by default
|
||||
That route is intentionally simple.
|
||||
Its power comes from customization.
|
||||
|
||||
---
|
||||
|
||||
## Where This Leads Next
|
||||
|
||||
Boot commands are only the entry layer.
|
||||
|
||||
After this page, the natural next steps are:
|
||||
|
||||
1. use the quickstart
|
||||
2. learn how to tune `WFGY_BRAIN`
|
||||
3. follow the avatar tuning workflow
|
||||
4. later build and submit your own avatar branch
|
||||
|
||||
That is where the system becomes much more interesting.
|
||||
|
||||
---
|
||||
|
||||
## Quick Links
|
||||
|
||||
- [🏠 Avatar Home](../README.md)
|
||||
- [⚡ Quickstart](./quickstart.md)
|
||||
- [🛠️ How to Use WFGY_BRAIN](./how-to-use-wfgy-brain.md)
|
||||
- [🧭 Avatar Tuning Workflow](./avatar-tuning-workflow.md)
|
||||
- [✨ Highlights Index](../highlights/README.md)
|
||||
- [⬆️ Back to WFGY Root](../../README.md)
|
||||
Loading…
Add table
Add a link
Reference in a new issue