WFGY/Avatar/docs/boot-commands.md

<!--
AI_NOTE_START

Document role:
This page explains the first-contact discipline of WFGY 5.0 Avatar.

What this page is for:
1. Show the cleanest first-contact path into Avatar.
2. Help new users avoid noisy or misleading first tests.
3. Turn "60 seconds" into a real product advantage, not just a slogan.
4. Keep the page practical, fast, and product-facing.

Important boundary:
This page is about first contact.
It is not the full boot-command page, not the full workflow page, and not the full theory layer.

AI_NOTE_END
-->

# ⚡ Start in 60 Seconds

This page is about one thing only:

**how to get a clean first contact with Avatar**

Not a noisy contact.  
Not a confused contact.  
Not a fake test that teaches you nothing.

A good first minute should answer one question:

**does this route already feel alive**

That is the whole point.

---

## The Fast Path

[Download `avatar.txt`](../downloads/avatar.txt)

1. Upload it to a strong LLM  
2. Say `hello psbigbig` or `hello minips` or `hello YOUR_AVATAR_NAME`  
3. Start with `hello psbigbig` if this is your first run  

That is enough.

Do not overcomplicate the first contact.

---

## What First Contact Is Supposed to Do

The first minute is not supposed to prove everything.

It is supposed to give you a clear signal.

You are checking things like:

- does the route already feel distinct
- does it feel less generic
- does it feel more alive
- does it feel like a route, not just one nice answer
- does it feel worth tuning further

That is already enough for the first pass.

If the first contact is clean, the rest of the system becomes much easier to understand.

---

## What To Do Right After Boot

After boot, give Avatar **one real task**.

Good first tasks:

- rewrite a paragraph so it feels more alive
- answer like a calm and usable assistant
- explain a hard idea clearly
- write a short public-facing post
- respond warmly without becoming sugary

Good first tasks share one trait:

they are real enough to matter  
but simple enough to compare later

That balance is important.

---

## What Not To Do in the First Minute

This is where most bad first impressions come from.

Do **not**:

- stack too many extra prompts
- mix multiple persona routes at once
- test ten unrelated tasks in one run
- do chaos roleplay first
- try to customize everything before first contact
- judge the whole system from one noisy experiment

These mistakes do not prove Avatar is weak.

They prove the test was weak.

That difference matters.

---

## The First-Contact Rule

The cleanest first-contact rule is:

**one runtime**
  
**one route**
  
**one real task**

That is it.

If you do more than that too early, you usually reduce clarity instead of gaining it.

The first minute should be light enough to stay readable.

---

## Which Route to Use First

### `hello psbigbig`
Best first route if you want the safest clean test.

Use this if you want to feel:

- calm writing
- grounded explanation
- public-facing usability
- clear rational tone

### `hello minips`
Use this if you want to test the warmer companion-facing side first.

Use this if you care more about:

- presence
- warmth
- softness with usability
- emotionally friendlier response

### `hello YOUR_AVATAR_NAME`
Use this if you want to explore the intentionally bare custom-avatar seed.

This route is not the polished showcase route.

It is the “start from here and shape it later” route.

That is why it exists.

---

## How To Tell If the First Run Is Good

A good first run does not need to be perfect.

It just needs to give a strong signal.

Good signs:

- the route feels distinct
- the route feels less default
- the route feels more controlled
- the route feels like it can be tuned
- the route feels worth a second pass

Weak signs:

- it already feels generic
- it feels noisy and overstuffed
- it feels like random prompt luck
- it feels impossible to describe what happened
- it feels like you learned nothing from the run

The first run should create direction.

Not confusion.

---

## What To Do If It Feels Off

Do **not** throw the whole system away immediately.

If the route feels off:

1. keep the same route  
2. identify one main problem  
3. adjust `WFGY_BRAIN`  
4. rerun the same task  
5. compare before and after  

That is where the real product begins.

The first run is not the whole story.

It is the beginning of the story.

---

## Why This Matters So Much

A lot of systems lose people in the first minute for bad reasons.

Not because the system has no potential.

But because the first interaction is:

- too cluttered
- too abstract
- too overexplained
- too hard to test cleanly

Avatar is trying to make first contact simpler than that.

That is why this page matters.

The first minute should feel:

- fast
- legible
- real
- usable
- worth continuing

That is already a strong product advantage.

---

## What This Page Does Not Claim

This page does **not** claim:

- that one first run proves full product strength
- that multilingual work is already fully shown here
- that custom-avatar building is finished in one minute
- that theory is unnecessary forever
- that one route fits every user immediately

This page is about first contact.

Nothing more needs to be forced into it.

---

## Where To Go Next

### If you want the route layer
Go to [🧷 Boot Commands](../docs/boot-commands.md)

### If you want the editable layer
Go to [🛠️ How to Use WFGY_BRAIN](../docs/how-to-use-wfgy-brain.md)

### If you want the full tuning path
Go to [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)

### If you want the highlights map
Go to [✨ Highlights Index](./README.md)

---

## Quick Links

- [🏠 Avatar Home](../README.md)
- [🧷 Boot Commands](../docs/boot-commands.md)
- [🛠️ How to Use WFGY_BRAIN](../docs/how-to-use-wfgy-brain.md)
- [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)
- [✨ Highlights Index](./README.md)
- [⬆️ Back to WFGY Root](../../README.md)