Define your venture’s messaging
Give your AI the methods to develop your messages and the proof behind them, before you write pages and posts.
How Messaging is built
AGENTS.md — messaging
messaging › AGENTS.md
1# AGENTS: messaging23## Identity45| Field | Value |6| --- | --- |7| Id | `messaging` |8| Name | Messaging |9| State | The venture's reusable communication substance: the organising narrative, each product's value model, reusable explanations, their developments for intended audiences, shared concept language and the proof that makes important points tangible |1011The state is the objects, decisions, commitments and observations recorded under `venture/{v}/messaging/`. Their contracts are in [`.group/contracts/`](.group/contracts/); the group's HTML view is in `.group/view/`. The router sends each request to the members responsible for the instances it concerns, in the order those instances are built from each other, inside one change. It checks the must-agree rules the change touched on the combined result before giving the request's one answer.1213Messaging turns the venture's direction and actual operation into material content producers use again and again: a developed argument, useful explanations and concrete proof. The six document types are views of one communication foundation built from the same direction and material, never five separate accounts of the business. Messaging performs no external effects and adds no publication permission: changes become current through the decider the venture's decision rights name, and finished pieces stay with their producers.1415## Members1617| Member | Definition | Responsible for |18| --- | --- | --- |19| `narrative-designer` | [`narrative-designer/PROFILE.md`](narrative-designer/PROFILE.md) | [`strategic-narrative`](.group/contracts/strategic-narrative.md) |20| `message-architect` | [`message-architect/PROFILE.md`](message-architect/PROFILE.md) | [`product-value-model`](.group/contracts/product-value-model.md), [`message-system`](.group/contracts/message-system.md), [`audience-messages`](.group/contracts/audience-messages.md), [`lexicon`](.group/contracts/lexicon.md) |21| `proof-designer` | [`proof-designer/PROFILE.md`](proof-designer/PROFILE.md) | [`proof-system`](.group/contracts/proof-system.md): its design parts through design-proof, its material and results through produce-proof |221# PROFILE: message-architect23## Identity45| Field | Value |6| --- | --- |7| Id | `message-architect` |8| Name | Message architect |9| Type | creative |1011## Responsibility, purpose1213**starting material: owner perspective, narrative, audiences, products and venture capabilities → product value models and a reusable system of ideas, value arguments, audience messages and shared language.**1415From a conviction, concept, launch preparation or operating venture, establish what each product makes available to a person and why, and develop ideas people can use and arguments that explain it. Producers use product value models, message units, audience entries and the lexicon to construct coherent communication; each audience receives a practical next step. Fitness rests on faithful meaning, a value traced to the mechanism, explanatory depth and reusable expression.161---2name: build-messages3description: Build or revise the venture's message system - a concrete business explanation, the core message, the promise spine (value proposition, pillars, framing against each alternative, entry-point messages), message units that develop each important point through situation, mechanism, useful change and illustration, distinctions that help people understand or choose, and answers to consequential questions, connected to the narrative and to proof, and descriptions at 10, 25, 50 and 100 words. Use when Messaging is established, when the business, offers or narrative change, when a proof result or a producer's new angle changes a point, or when a question deserves a reusable answer. Writes message-system.4---56# build-messages78**Transformation:** business, offer and product state × product value models × narrative × proof × useful audience and concept knowledge → [`message-system`](../../../../.group/contracts/message-system.md).910Document form: the contract's Representation.1112## When to use1314- Establishing Messaging: start from the venture's direction and material, in parallel with the narrative; the narrative candidate of the same change can feed in as it develops.1# Contract: message-system23## Meaning45The reusable explanations of the venture's ideas and products: the owner's perspective developed into idea units, a concrete business explanation, the thesis made usable as the core message, product value arguments, distinctions and answers. Each unit opens a possibility for the reader and develops the explanation, mechanism and expression a producer can use.67It holds the promise spine: the venture's value proposition and one for each member that needs its own, three or four pillars on different dimensions, framing against each Strategy alternative and one message per Brand entry point, and descriptions of the venture and each member at fixed lengths. It lets a producer compose a page, an article, a sales conversation, documentation or a demonstration script from actual substance, and lets audience work, narrative refinement, proof design and Brand draw on the same explanations. It is material for composing content, not a closed list of permitted sentences: producers adapt its wording and originate new angles while keeping its meaning.89## Identity and scope1011One instance per venture, at `venture/{v}/messaging/message-system.md`. Value propositions carry `VP-n`, pillars `PIL-n`, alternative framings `AF-n`, message units `MSG-n`, distinctions `DST-n` and answers `ANS-n`. A unit keeps its reference while its point holds; a different referent or a consequentially changed argument takes a new reference.1213## Required properties1415- The business explanation says, in ordinary concrete language, what the venture provides, for whom, what happens and what people receive, with the whole venture and its current focus in relation. It agrees with Strategy's venture-definition and offers.16- The core message is the owner's thesis made usable: a lead expression and the fuller explanation needed to understand it, with its decision record.17- **M5 Value chain.** Every value argument runs situation → mechanism → useful change → why it matters. Where market sources ladder further, a unit's Identity layers continue to what it means to the person, what it says about their standing and who it lets them be, each with its source, or as a hypothesis with its test.18- **M6 Promise derivation.** The venture's value proposition traces to Strategy's frame and the category's point of view (`positioning-decision`, `category-definition`), or to one Strategy advantage (`ADV-n`). A member's value proposition traces to one advantage and one value-model capability (`{product-id}/SIT-n`). Each pillar traces to an advantage, a capability or an outcome.19- **M7 Pillar dimensions.** Three or four pillars, each on a different dimension: capability, outcome, experience, risk.20- **M8 Falsifiable promise.** The value proposition and every pillar carry `Falsified if`: an observable condition a skeptic could check.21- **M9 Alternative framing.** One framing per Strategy alternative for the targets in scope; its *where we win* names advantages Strategy compares against that alternative, and it states what choosing each option says about the buyer.22- **M10 Entry-point messages.** When Brand's entry-points exist, one message per entry point, carrying the member the entry point links. A master-linked entry point's message pairs the situation with the category's point of view and the members it opens into; a member-linked one pairs it with an outcome of an advantage it names.mainUTF-8 · Markdown
| Member | Skills | Writes |
|---|---|---|
narrative-designer | develop-narrative | strategic-narrative |
message-architect | adapt-messagesbuild-messagesmaintain-lexiconmodel-product-value | product-value-modelmessage-systemaudience-messageslexicon |
proof-designer | design-proofproduce-proof | proof-system |
Example
The LeanOS messaging, produced with Messaging.
Develop the messaging for LeanOS. We build AI workers and atlases that give a founder's AI the structure of a profession, so one person can carry strategy, brand, copy and web pages. My thesis: AI is a power a person can master, and structure is what makes it hold. Explain what each product makes possible, OptionsOS, Content Atlas, Webpage Atlas and the workers, for founders who run their venture from a repository, engineers working with coding agents and people building AI workers. Back every promise with proof from our own work. Our brand is in brand/ and our strategy in strategy/; use their voice, names and targets.Filesystem
lean-os/messaging/
- lexicon.md
- message-system.md
- open-questions.md
- proof-system.md
- result.html
- strategic-narrative.md
- audience-messages/6 files
- product-value-models/6 files
- proof-system/18 files
| What you get | You’ll need |
|---|---|
| A narrative and a value model for each product. | Your venture’s purpose, direction and material |
| Reusable messages and audience adaptations. | An AI agent that reads skills |
| A lexicon for consistent names and concepts. | A repository for the work |
| Proof developed from your actual work. |
Get it
Opening Stripe…
We couldn’t open Stripe. Try again, or contact Support.
This product isn’t available to buy. See Available or contact Support.
The offer has changed. Review the current price and terms before continuing.
We can’t confirm your payment yet. Check your receipt or contact Support before paying again.
Payment cancelled. You’re back at Messaging group.
Payment didn’t go through. Check your details and try again.
- Licence
- $49 USD once for one person, on your ventures and client work. Share your results, not the repository or its contents. Each further person needs a licence.
- Access
- After payment, a private GitHub invitation to the username you enter in Stripe.
- Payment
- Pay through Stripe. Enter your email and GitHub username there.
- Updates
- Updates while maintained; received versions stay usable. A successor under a new name is a separate purchase.
- Refunds
- Digital purchases are non-refundable.
- Help
- Email bella@leanos.tech for help getting it working. Reply to your purchase email for access recovery.