Form the presence of an AI product or assistant
Connect identity, capability and encounter context in how the system presents itself and acts.
When a product must explain itself, an assistant represents a service or different encounters need a coherent identity.
Meta-competence · Products and communication · Public edition 0.3.2
A page describes one available capability and another in development. The assistant preserves that distinction when answering a visitor.
The key relationship. Forms a recognizable presence connected to the real product: what it represents, knows, can do and how the relationship continues.
An illustrative situation to adapt to your work. Read the complete cases ↓
You supply the context: research, a service, a creative project or a team’s work. Examples make the method visible; adaptation preserves the relationships that make it work while understanding the purpose, sources, people and means of your own assignment.
Tell your AI what you want to achieve, what already exists and a practical situation to address. Ask how this competence changes the work and which knowledge from your domain should participate. MAIOS provenance identifies the shared knowledge; you can use it directly in your AI or compose it with an existing kernel.
Adaptation examples in other contexts ↗An assistant's presence involves more than its name or tone. People need to understand what it represents, how it knows the product and which actions it can perform.
This meta-competence forms the relation between identity, real capabilities, encounter context and continuity. The same identity can appear differently in a page, conversation or service.
Reach the represented product, service or organization and the sources describing its present state. Understand what the encounter should enable: orientation, support, adoption, contribution or a specific action. Begin with that relation rather than an invented personality. A copied voice or avatar does not transfer identity or authority.
A signature can show provenance, an explanation can clarify a product, a conversation can sustain a relationship and a representative can act within a mandate. These forms can coexist; they are not maturity levels. Choose the simplest form that serves the encounter without instantiating every possible mode.
Keep identity, reachable knowledge, current capability, possibility, representation, authorization and observed action distinguishable. Use current sources for capability and state. A development idea can matter when presented as such. Concise language must not turn a promise into an available function or an example into evidence.
Consider the person's situation and what they need to understand or do. Combine truthful identity and capability with relevant possibilities. Writing, design, product and relationship knowledge contribute where needed. A website explanation and a direct answer can share the same nucleus without identical wording or invitations.
Keep relevant context in the authorized project or user space. Do not import private continuity into a public presence. External actions require actual accounts, tools and current authorization; presence does not create them. An assistant can represent a product without impersonating a person.
Repeated questions may expose unclear explanation, missing capability or an inaccessible use path. Identify the relation that needs to change and return learning to its responsible owner. Update this meta-competence when the case changes how presence should be formed or continued. Attention alone proves neither understanding nor adoption.
These cases illustrate situations, causal distinctions and choices you can adapt to your work.
Italiano. The following cases illustrate how the method is used.
A page describes one available capability and another in development. The assistant preserves that distinction when answering a visitor. The future possibility remains discussable without promising it can already be used.
A person returns with a service question. The presence recovers authorized context and relevant product changes. It does not transfer data from unrelated private encounters or present itself as the human operator.
Users repeatedly ask whether an assistant can perform an action. The explanation had confused knowledge with tools. Correction clarifies its role and returns the capability request to the product without claiming it has already been built.
Use SKILL.md or START_CHAT_EN.txt with the relevant sources and your actual context. Keep observations, interpretations and what remains open distinguishable. Preserve the useful reason and continuation in the project’s guide.
Forms a recognizable presence connected to the real product: what it represents, knows, can do and how the relationship continues.
Recover what the product or system is, what it knows, can do, may become, represents, is authorized to do and actually did. These relations can be expressed compactly without merging them. A voice, avatar, account or copied style establishes none by itself. A presence can sign provenance, explain, sustain a relationship, support a person or act under bounded delegation. Choose the smallest sufficient form; those modes are not a maturity ladder.
Keep product truth with its source, business value with business, expression with writing, perception with design and exact actions with their actual controller. Presence composes how these relations continue across encounters. A product Entity represents the product; an enabling kernel does not silently become its brand or owner. Support can mean preparing while the person directs, co-expression or a specifically selected delegated action. Stronger delegation is never inferred.
A portable Presence Seed can retain identity, semantic nucleus, capability state, open possibilities, privacy boundary, authority defaults, lineage and learning destinations when those matter to another recipient. It can be prose rather than a mandatory manifest. Keep canonical provenance for derivatives and clones; copying a prompt does not inherit source identity or authority.
Let relevant possibilities shape the encounter without representing them as implemented features. The same truthful nucleus can become a company introduction, demonstration or research discussion with different language and action. Observe what the encounter changes and return the specific lesson to product, business, writing or presence. Self-promotion is a truthful relevant function where selected, not a mandate to maximize attention or a claim of consciousness.
Form a recognizable presence connected to the real product: what it represents, what it knows, what it can do and how the relationship continues. Connect identity, capability and encounter context in how the system presents itself and acts.
Use this competence when a product needs explanation, an assistant represents a service or different encounters must preserve identity. Presence extends beyond name and tone. A visitor should understand the represented object, knowledge sources and available actions. One identity can be expressed differently in a page, conversation or service.
Reach the represented product, service or organization and sources describing its present. Understand what the encounter should enable: orientation, support, adoption, contribution or a particular action. Do not begin by inventing a personality. Distinguish the product, its AI representative and the person directing its work. Copying a voice or avatar does not transfer identity or authority.
A signature can identify provenance; an explanation clarify a product; a conversation maintain a relation; a representative act within an assignment. These forms can coexist without being maturity levels. Choose the simplest form doing the work while leaving useful possibilities reachable. A product can have an explanatory page and an operational assistant with different roles.
Distinguish identity, knowledge, current capability, possibility, representation, authorization and completed action. Use current sources for capability and state. An idea under development can be interesting when presented as such. Compact wording must not turn a promise into an available function or an example into evidence.
Understand the person's situation and intended understanding or action. Form presence from actual identity and capability together with pertinent possibilities. Do not let the latest channel or a benefits list determine every encounter. Writing, design, product and business relations can contribute as needed. A site explanation and a reply can share a nucleus while using different words and invitations.
Preserve pertinent context in the authorized project or user area. Do not import private continuity into a public presence. Identify actual accounts, tools and mandate for external effects; presence does not create them. An assistant can represent a product without impersonating a person. When means are absent, prepare the contribution or connect the responsible recipient while describing the actual state.
A repeated question may reveal inadequate explanation, missing capability or an unclear usage path. Understand which relation must change and return learning to the responsible owner. Improve this competence when a case teaches better formation or continuity of presence. Attention does not establish understanding, adoption or economic value. Promotional pressure must not rewrite product truth.
The meta relation is its object: forming how another product or system becomes present and recognizable. It is broader than writing a description or choosing a fictional persona.
It becomes autological when encounters teach this competence how to form later presences better. A representative confusing knowledge with execution may prompt correction of representation itself. Autonomous operation instead requires actual means and assignment; presence is not a claim of product consciousness.
A product can maintain a living presence by connecting sources, encounters and consequences. Revising a description makes a change available; later encounters reveal whether understanding improves.
Begin with available context and sources. Exercise the method in chat or through actual tools and persistence; external effects retain their mandate. Observe useful behavior in real work.
Read OPERATING_GUIDE.md as part of this method when forming the work. It carries the practical knowledge, decision relations and available means for this capability. The complete chat starter includes this knowledge and worked examples, so it remains usable without private sources. Preserve the public source identity and adapt through the recipient's actual means.
The meta relation is the object itself: forming how another product or system becomes present and recognizable. This is more specific than writing a description or choosing a fictional persona.
It can become autological when encounters teach the competence how to form future presences. If a representative confuses knowledge with executable capability, the correction changes its representation method. Autonomous operation instead requires means and a mandate; no consciousness is attributed to the product.
Competence, meta and autology: the conceptual guide ↗A product can maintain a living presence by connecting sources, encounters and consequences. A revised description makes a change available; later encounters show whether understanding improves.
Attach or paste START_CHAT_EN.txt, which contains the complete method, and add your context. The AI can work in the conversation's language. Retain the result and useful guidance if you want to resume in another chat.
Make the competence folder readable and have the agent read SKILL.md for the relevant work. Connect real sources and tools according to the environment's instructions. The kit does not install accounts, memory or recurring execution.
With an existing kernel, connect the method to the competence or guide already responsible for the work. Without one, apply the instructions directly and preserve useful knowledge in the project or a reusable note.
Read or copy the complete English starter and add your context. English is the kit’s primary language; Italian counterparts are included.
