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 |22
mainUTF-8 · Markdown
MemberSkillsWrites
narrative-designerdevelop-narrativestrategic-narrative
message-architectadapt-messages
build-messages
maintain-lexicon
model-product-value
product-value-model
message-system
audience-messages
lexicon
proof-designerdesign-proof
produce-proof
proof-system

Example

The LeanOS messaging, produced with Messaging.

Claude CodeMessaging
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 getYou’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

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.