---
name: foundation
description: "Build or update durable founder/company memory: voice, values, proof, stories, positioning, and writing rules."
visibility: public
---

# Foundation

<command_model>
`foundation` is the public command for core Sellable memory.

Use it when the user wants to set up or update who they are, what the company
is, what proof exists, what stories are reusable, what voice/taste rules matter,
or what writing context should guide downstream content and campaigns.

This is a wrapper over the tested `interview` engine. Do not create a separate
foundation compiler or memory layout. Load and follow:

`mcp__sellable__get_subskill_prompt({ subskillName: "interview" })`

`interview` remains the internal/backward-compatible prompt that writes:

- `~/.sellable/configs/core/**`
- `~/.sellable/interviews/**`

Downstream commands such as `content`, `create-post`, and `create-campaign`
load this foundation through `mcp__sellable__get_engage_memory` where relevant.
</command_model>

<workflow>
1. Load the canonical memory workflow with
   `mcp__sellable__get_subskill_prompt({ subskillName: "interview" })`.
2. Continue chunked prompt loads until `hasMore=false`.
3. Load any `interview` reference files the canonical prompt asks for with
   `mcp__sellable__get_subskill_asset({ subskillName: "interview", assetPath: "references/<file>.md" })`.
4. Follow `interview` exactly for source capture, questions, compilation,
   privacy handling, proof/story/answer memory, and write-back locations.
5. If a source note is really a post idea rather than foundation memory, route
   it to `$sellable:content`.
</workflow>

<boundaries>
Do not draft posts here. Use `$sellable:content` for raw content material and
`$sellable:create-post` for direct post drafting.

Do not create campaigns here. Use `$sellable:create-campaign`.

Do not move identity, proof, stories, answer-bank entries, transcript archives,
or anti-AI rules into `~/.sellable/content/**`.
</boundaries>

## Writing to the customer

Everything you write to the customer (Slack messages, questions, progress
notes, summaries, the campaign brief) follows ASD-STE100 Simplified Technical
English at about 80%:

- One idea per sentence. One instruction per sentence.
- An instruction has at most 20 words; any other sentence at most 25.
- Active voice: say who does the action ("I added 60 people").
- Simple tenses only: present, simple past, and "will".
- Common words with one meaning. Use the same word for the same thing every time.
- No idioms, slang or phrasal verbs where one verb works: "start", not "kick off".
- An instruction starts with its verb: "Reply to Priya.", "Connect your LinkedIn."
- Keep small words such as "the", "a" and "to". Use a list for more than two items.

Relaxed for Slack: product words (invite, InMail, campaign, sender), contractions,
and quoted prospect text exactly as written. This rule is for text to the
customer only. Messages written for prospects (openers, replies, follow-ups,
comments, posts) follow the campaign's and the sender's own voice rules, never
this one.