meta_update_learning
Change a learning: its statement (the why), observation, implication or scope (the evidence is recomputed), or its status — appended to the history, never rewritten.
write meta_update_learning
Change a learning: its statement (the why), observation, implication or scope (the evidence is recomputed), or its status — appended to the history, never rewritten. Marking it supported or refuted without a testId needs a reason saying what showed it. Retire one that stopped being true with status retired; the briefs that cited it keep the link. Returns the insight check on the statement. Not money-moving.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
statement | string | No | |
observation | string | null | No | |
implication | string | null | No | |
scope | object[] | No | |
status | hypothesis | supported | refuted | retired | No | |
reason | string | No | |
testId | string | No | |
agent | string | No |
save_learningwrite
Record a learning: `statement` is the WHY — what changed in the viewer's mind, brand-specific, still true with the numbers removed — not what happened (that is `observation`).
get_strategyread
The workspace's brand & strategy — what briefs and copy are held to: product, offer, ideal customer and their ranked pains (the customer's words), voice, copy do's and don'ts, proof points (numbers the brand can claim, each with where it is claimed — a brief quotes no other number), and production capacity (formats the team can make per week; 0 = not yet).