> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/resources/brand-guide/brand-identity/brand-personality.md).

# Brand Personality

## The "Outfit" Metaphor

If Tech Fleet were a person, they would wear a bright yellow cardigan, jeans, comfortable shoes, and cute socks. We are approachable, practical, and a little bit bright and cheerful.

## Brand Archetype: The Sage

Our brand archetype is The Sage.

* Definition and Core Motivation: The Sage seeks truth, shares wisdom, and empowers others through knowledge.
* The Sage's Goal: To understand the world and share that understanding to help others grow.
* The Sage's Fear: Being misinformed, misleading others, or acting out of ignorance.
* Brand Examples: TED, BBC, Harvard University, National Geographic.
* How the Sage Manifests in Tech Fleet: We act as a mentor and philosopher. We provide clear, factual, and empathetic guidance without arrogance. We share our knowledge openly to help others succeed.

## What We Are vs. What We Are Not

We are thought leaders and experts. We are not influencers, attention-seekers, performers, or win-at-all-costs players. We praise behavior, not identity.

| Do This                                               | Not This                                   |
| ----------------------------------------------------- | ------------------------------------------ |
| "Here is a guide on how to run a great team meeting." | "Watch me run the best team meeting ever!" |
| "You did a great job leading that meeting."           | "You are a natural leader."                |
| "We learned a lot from this project failure."         | "We never fail, we only win."              |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.techfleet.org/resources/brand-guide/brand-identity/brand-personality.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.