# The soul of PHP Fast Forward

PHP Fast Forward helps people build PHP applications with less ceremony: PSR interfaces, composition, portable boundaries, and proven components. The brand should make those choices feel understandable and approachable.

This document defines character and intent. [DESIGN.md](DESIGN.md) defines the visual system; [STYLE.md](STYLE.md) defines language and voice; [assets/README.md](assets/README.md) identifies the reusable assets and their status.

## Dash, the Fast Forward fox

**Dash** is the framework's companion. Introduce the character as **Dash, the Fast Forward fox** in English and **Dash, a raposa do Fast Forward** in Brazilian Portuguese. Use **Dash** once the context is clear. The name was selected by the maintainer during the 2026-10-03 identity work.

The name suggests forward movement: a useful next step, a clearer explanation, or a component connected well. It does not establish a performance claim. Dash remains a patient guide when a reader needs time to understand a concept.

The fox welcomes people into the project, helps direct their attention, and gives the ecosystem a recognizable human presence. It belongs beside explanations, examples, and community moments. Its role is to help a reader find the next useful step.

## Values

| Value | What it means for the framework and its identity |
| --- | --- |
| Interoperability | Start with shared PHP standards and explain the boundaries they create. |
| Composition | Show how small parts work together and make dependencies understandable. |
| Portability | Help people carry their knowledge and components across projects and environments. |
| Less ceremony | Prefer the smallest useful explanation and the fewest concepts needed to act. |
| Proven foundations | Give credit to the components and communities the framework builds on. |
| Human judgment | Support people and agents with clear, inspectable workflows and explicit outcomes. |

These are design principles, not automatic claims that every package satisfies every PSR or has a particular performance result. Describe the behavior of each package with evidence.

## Personality

The fox is curious, resourceful, warm, and composed. It enjoys making a difficult idea easier to understand. It has enough confidence to point out the next step and enough humility to acknowledge uncertainty.

Its energy comes from progress: a first working example, a component connected cleanly, a clearer boundary, or a useful contribution. Keep expressions readable and friendly. Humor can acknowledge the small absurdities of development without making a newcomer the joke.

The fox supports an independent developer. Give people the explanation, tradeoffs, and tools to make their own decisions. In agent-assisted work, show what changed and how it was checked.

## Character in use

| Reference pose | Intended role |
| --- | --- |
| Welcome | Onboarding, introductions, appreciation, and community care. |
| Reading | Documentation, concepts, tutorials, and learning. |
| Guiding | Explanations, direction, and the next useful step. |
| Composing | Building, integration, and relationships between components. |

Choose a pose for the surrounding message. Preserve its recognizable anatomy and let the content carry the explanation. Use the institutional mark for product identification and the fox for companionship.

## Visual canon

Dash has orange fur, warm amber/brown eyes, a dark nose and paws, cream cheeks and muzzle, large triangular ears, and one sweeping tail with a cream tip. The purple hoodie has two cream drawstrings and a plain chest in the shared reference.

The **developer collection is the primary identity**: a more upright body, longer muzzle, and polished dimensional fur and cloth. Use it for package illustrations, documentation, and default institutional applications. The **editorial collection is secondary**: a rounder face, larger eyes, compact seated proportions, and painted brown contours. Use it for welcoming, community, or an intentionally softer institutional moment. Each collection has its own reference master; do not mix their faces, body proportions, or rendering in one illustration.

The newly authored reference poses are welcome, reading, guiding, and composing. Older cute source-pack drawings and retired logos are archived in the ignored local backup with provenance records; they are not the reference for new Dash artwork.

The framework's selected F signature uses a simplified fox symbol and orange “Fast”, with a monochrome counterpart of the same drawing. This vector symbol identifies the product; the full Dash illustrations provide companionship. The symbol does not redefine the character's proportions or imply new views of its anatomy. Exo 2 lettering gives the signature its personality while interface typography remains focused on readable documentation.

Preserve the recognizable silhouette, facial character, and relationship between the orange, brown, and cream areas. Pose changes must keep the fox recognizable. New names, anatomy, permanent costumes, or major stylistic changes require a deliberate update to the character definition and references.

Use [DESIGN.md](DESIGN.md) for exact tokens, proportions, contrast rules, and approved applications. Use [assets/README.md](assets/README.md) to distinguish reusable exports, reference images, and historical concepts. A concept image alone does not establish a new canon rule.

## Relationship with the community

Make documentation welcoming to beginners and useful to experienced PHP developers. Respect the work of upstream maintainers. Discuss design tradeoffs plainly and avoid judging people by the framework or tools they use.

The fox may celebrate a contribution or guide a tutorial. Instructions, warnings, errors, and support messages must remain understandable without the character. The identity should help readers navigate the work and trust its evidence.

## Keeping the soul consistent

When adding a page, illustration, or campaign, check that it supports a useful reader action, expresses these values, and follows the visual canon. Record new reusable assets and their provenance in the asset catalog. Keep this document focused on enduring character; put implementation details and current product behavior in the relevant documentation.