@letterstory/design 0.2.4 → 0.2.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/PRINCIPLES.md +23 -2
  2. package/package.json +1 -1
package/PRINCIPLES.md CHANGED
@@ -20,8 +20,9 @@
20
20
  stops being phantom-only loses its `phantom-` prefix in the same PR.
21
21
 
22
22
  3. **One operation, one function, many projections.** UI route, MCP tool, REST endpoint and CLI
23
- command are _projections_ of one lib function with one Zod schema. The manifest is `TOOLS`
24
- in `src/lib/mcp/registry.ts`; MCP, OpenAPI and `/docs/api` are derived from it at request time
23
+ command are _projections_ of one lib function with one Zod schema. The manifest is `TOOL_MANIFEST`
24
+ in `src/lib/mcp/manifest.ts` (handlers keyed by name in `src/lib/mcp/registry.ts`, which binds
25
+ them into `TOOLS`); MCP, OpenAPI and `/docs/api` are derived from it at request time
25
26
  and cannot drift (`src/app/docs/api/AGENTS.md`). Where the UI has its own `/api/*` route, that
26
27
  route and the tool must call the same lib function and share the schema — derive the tool
27
28
  contract with `.omit()` for key-derived fields exactly as
@@ -81,3 +82,23 @@ Add a third for surfaces:
81
82
 
82
83
  > If the app can do it and an agent cannot (or vice versa), which projection is missing, and
83
84
  > why did the shared function not force it?
85
+
86
+ ## Letterpress: Build, Plan, Fix
87
+
88
+ The founders' definitions (All Hands 2026-10-29). Detail in `docs/architecture/one-recipe-engine.md`.
89
+
90
+ - **Build is unbounded.** It does what the member asks ("build X", "answer Y"). Its execution may read
91
+ the Plan's recipes and Fix's known issues through the MCP, but it has no list of its own, and it never
92
+ refuses words because no catalog action fits them: the words go to one change as they are
93
+ (`lib/growth-builds/start-build.ts`).
94
+ - **Plan is a curated list.** Its rows are staff-written recipes (`recipes.kind = recipe`, edited in
95
+ Super Admin), never generated by a model, because most model-made strategy is mediocre. Showing
96
+ nothing beats showing a weak row. The fit runs in the app over the account's stored facts and probes
97
+ (checking `llms.txt` is a probe), never in a sandbox: a sandbox takes minutes to start. Plan is reached
98
+ through one headless door, `ask_letterpress` on the MCP, which the dashboard, Slack and the terminal
99
+ all use.
100
+ - **Fix finds and fixes what is broken.** Models are good at finding errors, so Fix gets more room than
101
+ Plan. It works from a list of known issues (`recipes.kind = known_issue`), not recipes, and also
102
+ catches problems outside that list. Technical problems a rule can decide (broken or missing
103
+ structured data, link previews) are rules (`lib/site/observations/`). A "Z is broken" row belongs
104
+ in Fix's known issues, never in the Plan.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@letterstory/design",
3
- "version": "0.2.4",
3
+ "version": "0.2.6",
4
4
  "description": "Letter design tokens, the phantom theme registry, and the design principles — one source for every Letter repo.",
5
5
  "type": "module",
6
6
  "license": "UNLICENSED",