Create avatar-submission-format.md

Avatar/community/avatar-submission-format.md

@@ -0,0 +1,485 @@
+<!--
+AI_NOTE_START
+
+Document role:
+This page defines the intended submission format for future avatar entries related to WFGY 5.0 Avatar.
+
+What this page is for:
+1. Show what a future avatar submission should include.
+2. Help contributors present avatars as legible character branches rather than random files.
+3. Make avatar submissions easier to review, compare, and curate later.
+4. Connect naming, personality description, tuning direction, sample writing, and visual identity into one readable structure.
+5. Keep the page practical and structured while remaining honest that some details may still evolve.
+
+What this page is not:
+1. Not the final PR template page.
+2. Not the full review policy.
+3. Not the final curation criteria for every future community repository.
+4. Not a guarantee that every correctly formatted submission will be accepted.
+5. Not a claim that this format can never evolve later.
+
+How to use this page:
+1. Prepare your avatar as a real branch first.
+2. Use this page to organize the submission clearly.
+3. Include enough information for another person to understand the avatar quickly.
+4. Include sample writing that demonstrates the route honestly.
+5. Follow the later PR guide when the submission path is opened more fully.
+
+Important boundary:
+This format exists to make avatar submissions readable and comparable.
+A formatted submission is not automatically a strong avatar.
+The route still needs to feel real, usable, and worth sharing.
+
+AI_NOTE_END
+-->
+
+# 🧾 Avatar Submission Format
+
+This page defines the intended structure for a future avatar submission related to **WFGY 5.0 Avatar**.
+
+The goal is simple:
+
+**an avatar submission should be easy to read**
+  
+**easy to compare**
+  
+**easy to understand**
+  
+**and easy to review later**
+
+This means a submission should not be only:
+
+- a file
+- a cool name
+- a vague personality claim
+- a random screenshot
+- a pile of unexplained edits
+
+A stronger submission should feel like a real avatar entry.
+
+---
+
+## ✨ What a Good Submission Should Do
+
+A good submission should help a reader quickly understand:
+
+- who this avatar is
+- what kind of route it represents
+- what kind of presence it has
+- what it was tuned toward
+- what kind of writing or interaction it is good at
+- how it is different from other avatars
+
+This is why format matters.
+
+A clean format does not make the avatar better by itself.
+
+But it makes a good avatar much easier to recognize.
+
+---
+
+## 🧱 Core Submission Structure
+
+A future avatar submission should usually include the following sections.
+
+### 1. Avatar Name
+The avatar's public name.
+
+This should be clear and readable.
+
+Good examples:
+
+- `Avery`
+- `Lina`
+- `North`
+- `Glassbird`
+- `Atlas Ember`
+
+Weak examples:
+
+- `final_v2_real_fixed`
+- `best-avatar-maybe`
+- `new prompt 7`
+
+The name should make the avatar feel like a real branch, not a temporary accident.
+
+---
+
+### 2. Base Route
+The starting route this avatar grew from.
+
+Examples:
+
+- `hello psbigbig`
+- `hello minips`
+- `hello YOUR_AVATAR_NAME`
+
+This matters because lineage helps people understand the branch.
+
+It also makes later comparison much easier.
+
+---
+
+### 3. Intended Personality
+A short natural-language description of the avatar's personality.
+
+This should be concise and human-readable.
+
+Examples:
+
+- calm, grounded, lightly witty, public-writing friendly
+- warm, companion-forward, present, soft but not sugary
+- slightly awkward, curious, gentle, low-pressure, beginner-like
+- clear, analytical, emotionally restrained, easy to trust
+
+This section is not supposed to be a novel.
+
+It should help another reader quickly imagine the route.
+
+---
+
+### 4. Intended Use Cases
+A short list of what this avatar is good for.
+
+Examples:
+
+- public writing
+- reflective conversation
+- customer-facing communication
+- multilingual support-style interaction
+- grounded analysis
+- companion response
+- creative but controlled writing
+
+This section helps keep the entry practical.
+
+---
+
+### 5. What Was Tuned
+A short description of what was adjusted or emphasized.
+
+This should be written in simple natural language.
+
+Examples:
+
+- reduced polish and increased grounding
+- preserved warmth but reduced emotional sugar
+- increased public-writing force
+- lowered abstraction drift
+- made the route easier to reuse across tasks
+- adjusted the companion feel to sound less soft
+- tuned the rhythm to feel more direct
+
+This is important because people should be able to see what kind of shaping happened.
+
+---
+
+### 6. WFGY_BRAIN Direction Notes
+A short note about the tuning direction, not necessarily every tiny internal change.
+
+Examples:
+
+- less polished, more grounded, stronger first-paragraph clarity
+- warm but not clingy, supportive without over-comforting
+- sharper reasoning without sterile distance
+- softer entry, stronger emotional continuity, controlled emoji use
+
+This section is not meant to expose every internal line.
+
+It is meant to make the branch legible.
+
+---
+
+### 7. Sample Writing
+One or more short example outputs that demonstrate the avatar.
+
+This may later be one of the most important parts of the submission.
+
+The sample should help readers feel:
+
+- the tone
+- the opening
+- the rhythm
+- the personality pressure
+- the route identity
+
+A good sample is better than a long self-description.
+
+This is where the avatar starts proving that it is real.
+
+---
+
+### 8. Avatar Image or Profile Picture
+A visual identity for the avatar.
+
+This can be:
+
+- an avatar portrait
+- a profile-style image
+- a stylized symbolic identity
+- another simple visual that helps the avatar feel more present
+
+If an image is missing, the author or maintainer may help create one later.
+
+That part is still evolving.
+
+But the general direction is clear:
+
+**a future avatar entry should feel more like a character card than a raw config file**
+
+---
+
+### 9. Optional Multilingual Notes
+If the avatar has multilingual intent, include a short note.
+
+Examples:
+
+- tested in English and Traditional Chinese
+- intended to preserve warmth across English and Japanese
+- still drifts too much in French
+- currently stronger in Chinese-facing public writing than in English chat
+
+This helps readers understand the multilingual maturity honestly.
+
+---
+
+### 10. Known Limits
+A short section describing what the avatar still does poorly.
+
+This is important for trust.
+
+Examples:
+
+- still too soft in long emotional exchanges
+- public writing is stronger than casual chat
+- multilingual branch still unstable in Japanese
+- can become too polished under certain tasks
+- not good for highly technical explanation yet
+
+Known limits make the submission more believable and more useful.
+
+---
+
+## 🧩 Suggested Submission Template
+
+Below is a simple suggested format.
+
+```md
+# AVATAR ENTRY
+
+## Avatar Name
+<name>
+
+## Base Route
+<hello psbigbig / hello minips / hello YOUR_AVATAR_NAME / other future route>
+
+## Intended Personality
+<short natural-language personality description>
+
+## Intended Use Cases
+- <use case 1>
+- <use case 2>
+- <use case 3>
+
+## What Was Tuned
+- <tuning direction 1>
+- <tuning direction 2>
+- <tuning direction 3>
+
+## WFGY_BRAIN Direction Notes
+<short note about the overall behavior shaping direction>
+
+## Sample Writing
+<one or more short sample passages>
+
+## Avatar Image
+<image link, file reference, or note>
+
+## Optional Multilingual Notes
+<optional>
+
+## Known Limits
+- <limit 1>
+- <limit 2>
+````
+
+This template is intentionally simple.
+
+It is strong enough to make entries readable without making submissions feel bureaucratic.
+
+---
+
+## 🖼️ About the Avatar Image
+
+The image is not only decoration.
+
+It helps the avatar become socially legible.
+
+That matters because a future avatar entry is meant to feel like a real branch with a visible presence.
+
+Recommended direction:
+
+* one clear image
+* one readable profile identity
+* one face, symbol, or persona visual
+* something that matches the route
+
+If the submitter does not provide one, a later community path may allow author-side help.
+
+That part is still:
+
+**WORK IN PROGRESS**
+
+But the intended spirit is already clear.
+
+---
+
+## 🗣️ About the Sample Writing
+
+Sample writing should be short enough to read quickly, but strong enough to reveal the route.
+
+Good sample qualities:
+
+* it sounds distinct
+* it shows the tone clearly
+* it feels reusable
+* it is honest
+* it does not rely only on hype
+* it helps another person imagine using the avatar
+
+Weak sample qualities:
+
+* too vague
+* too generic
+* too dramatic without substance
+* too short to show anything
+* only self-description with no actual route feeling
+
+A sample is not an ornament.
+
+It is evidence of behavior.
+
+---
+
+## 🎭 Recommended Community Style
+
+The ideal long-term vibe of the community layer is not only technical.
+
+It should also be alive.
+
+An avatar entry should feel like:
+
+* a route
+* a character
+* a voice
+* a branch with intention
+* something another person can understand and try
+
+That is why this format includes both:
+
+* structural information
+* expressive identity
+
+The system should remain legible without becoming dead.
+
+That balance matters.
+
+---
+
+## 🛠️ What Can Still Evolve Later
+
+This format is meant to be strong enough to start from.
+
+It is not pretending to be permanently frozen forever.
+
+Some things may evolve later, such as:
+
+* exact field names
+* image requirements
+* multilingual reporting detail
+* accepted sample length
+* PR structure
+* repository-level organization
+
+That is normal.
+
+The important thing right now is to define a readable direction.
+
+This page already does that.
+
+---
+
+## ⚠️ What This Page Does Not Guarantee
+
+This page helps future submitters prepare better.
+
+It does **not** guarantee:
+
+* that every formatted submission will be accepted
+* that every avatar with a nice image is strong
+* that every personality description is honest enough
+* that sample writing alone proves long-term reuse
+* that the final review standards are already fully frozen
+
+Format helps.
+But format is not quality by itself.
+
+That distinction matters.
+
+---
+
+## 🚀 Why This Format Matters
+
+Without format, community growth often becomes noise.
+
+With some format, a stronger thing becomes possible:
+
+* people can browse entries more easily
+* people can compare routes more clearly
+* people can see what changed
+* people can understand what an avatar is trying to be
+* stronger submissions become more visible
+* future curation becomes much healthier
+
+That is why this page matters.
+
+It is not just paperwork.
+
+It is part of how the ecosystem stays readable.
+
+---
+
+## 🧭 Where To Go Next
+
+### If you want the community direction first
+
+Go to [⭐ Awesome Avatar List](./awesome-avatar-list.md)
+
+### If you want the submission overview
+
+Go to [🌟 Submit Your Avatar](./submit-your-avatar.md)
+
+### If you want the avatar multiplication idea
+
+Go to [🌱 One Runtime, Many Avatars](../highlights/one-runtime-many-avatars.md)
+
+### If you want the workflow path first
+
+Go to [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)
+
+### If you want the highlights map
+
+Go to [✨ Highlights Index](../highlights/README.md)
+
+---
+
+## 🔗 Quick Links
+
+* [🏠 Avatar Home](../README.md)
+* [⭐ Awesome Avatar List](./awesome-avatar-list.md)
+* [🌟 Submit Your Avatar](./submit-your-avatar.md)
+* [🌱 One Runtime, Many Avatars](../highlights/one-runtime-many-avatars.md)
+* [🧭 Avatar Tuning Workflow](../docs/avatar-tuning-workflow.md)
+* [✨ Highlights Index](../highlights/README.md)
+* [⬆️ Back to WFGY Root](../../README.md)
+