Skip to content
Merged
83 changes: 53 additions & 30 deletions aligned-onboarding/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,13 +23,15 @@ build found.
## Where the package files live

This folder holds one part per subfolder: `meta/` (the Creative Attribution playbook, the
Account Context Brain package, the Meta Validation package, and the Motion CLI Data-Query
Guide) and `voc-data-pull/` (the VoC Data Pull skill, recipes, and templates). This README
Account Context Brain package, the Meta Validation package, the Motion CLI Data-Query
Guide, and the Cacheth Command Reference) and `voc-data-pull/` (the VoC Data Pull skill, recipes, and templates), plus `knoweth/` (the organize-the-brain part that runs after the questions). This README
covers all of them; `install-config.json` maps every file to its installed location.

These instruction files are the package itself, not its output. They live in the brain
outside the `meta` folder structure. The brain's `meta` folder holds only what Runneth
generates from running them: the per-creative attribution files and the filled account context.
generates from running them: the filled account context (which carries the confirmed naming
decode). Per-creative content lives in Cacheth (the local creative cache); nothing in this
package writes it to brain files.

---

Expand All @@ -40,8 +42,10 @@ generates from running them: the per-creative attribution files and the filled a
attribution config as if they do not exist. Everything comes from auto-pulled Meta ad data and
customer confirmation.
- **One workspace at a time.** Every auto-pull names the account with `--workspace-id <id>`.
- **Attribution files are customer-facing account content.** Only creative facts belong in them.
Never save internal notes, CLI commands, or debugging mechanics.
- **Brain files are customer-facing account content.** Only account facts belong in them.
Never save internal notes, CLI commands, or debugging mechanics. Per-creative content lives
in Cacheth; it goes into a brain file only when a person explicitly asks, as a dated snapshot
(the cache stays the source of truth for current facts).

---

Expand All @@ -50,18 +54,20 @@ generates from running them: the per-creative attribution files and the filled a
### Creative Attribution
File: `meta/meta-creative-attribution-playbook.md`

- **Job:** build and maintain one enriched record per active creative — identity, summary, hook,
value props, transcript, AI tags, naming. The per-creative facts Runneth uses for every analysis
the Account Context Brain defines.
- **Runs first.** Collects facts without interpreting them. Detects naming patterns provisionally
and passes them to the Account Context Brain as pre-filled proposals.
- **Persists to:** individual creative Markdown files under `/agent/brain/meta/creatives/`, plus
an optional tagging taxonomy at `/agent/brain/meta/creatives/_tagging-taxonomy.md`.
- **Retrieval:** automatic through Knoweth. Writing the file is the index step.
- **Maintenance:** daily and event-triggered.
- **Staging deployment note:** in staging, per-creative summaries live in **Cacheth** and are
surfaced through **Knoweth**. Never run this playbook automatically: do not auto-pull creatives
and store summary files in the brain. It runs only on an explicit request from a person.
- **Job:** establish the creative content layer — one enriched record per active creative
(identity, summary, hook, value props, transcript, AI tags) held in **Cacheth**, the local
creative cache — and detect naming patterns, passing them to the Account Context Brain as
pre-filled proposals.
- **Runs first.** Collects facts without interpreting them.
- **Persists to:** nothing. The provisional naming decode is a handoff to the Account Context
Brain (Field 4), which owns it once confirmed. **No creative files** — nothing here writes
per-creative content to the brain (Cacheth is the system of record; person-requested snapshot
files are a separate, explicit ask).
- **Retrieval:** Knoweth pre-context injection first (matching creative chunks arrive in the
turn automatically); when that is not enough, the local motion cache CLI
(`motion cache search-summaries`, `motion cache get-creative`).
- **Maintenance:** the cache syncs itself; if the account's naming convention changes, the
decode re-runs and routes through Field 4.

### Account Context Brain
File: `meta/meta-account-context-brain-onboarding-package.md`
Expand All @@ -87,6 +93,18 @@ File: `meta/motion-cli-data-query-guide.md`

---

### Cacheth Command Reference (supporting reference)
File: `meta/cacheth-command-reference.md`

- **Job:** the canonical contract for querying the local creative cache through the
`motion cache` CLI — all five commands with every flag, the full-record field layout, `jq`
extraction recipes, and the retrieval priority order. The Creative Attribution playbook's
compact contract points here for the detail.
- **Not run on its own.** Reference only, not a step to execute. Brand-agnostic; carries no
account-specific IDs.

---

## VoC Data Pull (separate part, own folder)

Folder: `voc-data-pull/`
Expand All @@ -111,23 +129,28 @@ Folder: `voc-data-pull/`

## Install and run order

1. **Install the package.** Staging the files does not self-run anything. In particular, nothing
in this package may auto-grab creatives and store them in the brain with summaries; in staging,
summaries live in Cacheth and are surfaced through Knoweth.
2. **Creative Attribution (Step 1) — explicit request only.** When a person asks for it, builds
the per-creative attribution files, detects naming patterns, and passes them to the Account
Context Brain as provisional proposals. Never run automatically as part of install or
onboarding.
1. **Install the package.** Staging the files does not self-run anything. Nothing in this
package writes per-creative files to the brain — creative content lives in Cacheth and is
surfaced through Knoweth.
2. **Creative Attribution (Step 1).** Confirms the workspace scope, establishes the creative
content layer (Cacheth + the query paths), detects naming patterns, and passes them to the
Account Context Brain as provisional proposals. Writes nothing per-creative to the brain.
3. **Activate and run the Account Context Brain (Step 2).** Merge the guard block into
`/agent/user.md`, then run the fill-in. Confirms how the team judges performance, drawing on
the attribution build (if one was requested) for naming proposals and creative evidence.
4. **Set up the VoC data sync (when asked).** For each connected VoC platform, run the
voc-data-pull skill's "Set up the recurring sync" procedure - it creates the daily sync
routine and kicks the backfill in the background.
5. **Keep everything current.** Creative Attribution maintenance (daily and event-triggered)
applies only where the attribution build was explicitly requested. Account Context Brain on
monthly cadence and structural-drift triggers. VoC data refreshes itself through its daily
routines once set up.
5. **Organize with Knoweth (after the questions are answered).** Once the Account Context Brain is
confirmed and data-source content has landed, organize the brain: keep shared content in the
global lane and make it findable with tags and a naming decoder, and merge both the
`runneth:knoweth-organize` and `runneth:knoweth-brain` guard blocks into /agent/user.md (per the
MERGE INSTRUCTIONS in that doc) so the organize trigger fires and save-routing/maintenance stay on. Do not carve data-source-family or
initiative lanes today; only global, the user lane, and the workspace lane are queried. See
knoweth/knoweth-organize-onboarding-package.md.
6. **Keep everything current.** Creative content stays current through the Cacheth sync
automatically. Account Context Brain on monthly cadence and structural-drift triggers. VoC
data refreshes itself through its daily routines once set up.

---

Expand All @@ -144,5 +167,5 @@ Folder: `voc-data-pull/`
when creatives are discussed.
- **Naming decode is the handoff point.** Creative Attribution detects provisional naming patterns
from ad names and passes them to the Account Context Brain as proposals. Account Context Brain
confirms or corrects them in Field 4. Once confirmed, the naming decode is re-projected onto
the creative files.
confirms or corrects them in Field 4. Once confirmed, the decode lives in the Account Context
Brain — the single owner — and creative queries decode ad names through it at analysis time.
34 changes: 29 additions & 5 deletions aligned-onboarding/install-config.json
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"schema": "1.0",
"id": "aligned-onboarding",
"version": "2.1.0",
"description": "The Meta onboarding package, v2. Stages five instruction docs into the brain: the package overview, the Creative Attribution playbook, the Account Context Brain onboarding package (v1.21), the Meta Validation onboarding package (v1.1), and the Motion CLI data-query guide. Installing only stages files; nothing self-runs. The Creative Attribution build runs only on an explicit request from a person and must never auto-grab creatives and store summary files in the brain: in staging, per-creative summaries live in Cacheth and are surfaced through Knoweth. No corpus-search dependency. Meta only, one workspace at a time. Also carries the VoC Data Pull part (voc-data-pull/): a skill installed to the skills root that, when setup is requested, creates one daily sync routine per connected VoC platform pulling reviews, support conversations, community posts, and ad comments into /agent/brain/data-sources/voc/<platform>/. Nothing self-runs.",
"version": "2.3.0",
"description": "The Meta onboarding package, v2. Stages six instruction docs into the brain: the package overview, the Creative Attribution playbook, the Account Context Brain onboarding package (v1.21), the Meta Validation onboarding package (v1.3), the Motion CLI data-query guide, and the Cacheth command reference. Installing only stages files; nothing self-runs. Per-creative content lives in Cacheth (the local creative cache) and is surfaced through Knoweth; nothing in this package writes per-creative files to the brain. No corpus-search dependency. Meta only, one workspace at a time. Also carries the VoC Data Pull part (voc-data-pull/): a skill installed to the skills root that, when setup is requested, creates one daily sync routine per connected VoC platform pulling reviews, support conversations, community posts, and ad comments into /agent/brain/data-sources/voc/<platform>/. Nothing self-runs. Also carries the Knoweth organize part (knoweth/): after the questions are answered it organizes the brain so retrieval stays tight and sets the standing save + maintenance discipline.",
"requires": {
"runtime": "any Runneth sandbox",
"preinstalled": [],
Expand All @@ -22,13 +22,13 @@
"from": "README.md",
"to": "/agent/brain/aligned-onboarding/README.md",
"on_exists": "overwrite",
"purpose": "Package overview: the two parts, their run order, and the staging deployment rule that the Creative Attribution build never runs automatically."
"purpose": "Package overview: the parts, their run order, and the scope rules. Creative content ownership: Cacheth is the system of record; nothing in the package writes per-creative files to the brain."
},
{
"from": "meta/meta-creative-attribution-playbook.md",
"to": "/agent/brain/aligned-onboarding/meta-creative-attribution-playbook.md",
"on_exists": "overwrite",
"purpose": "Step 1 (explicit request only): how to build and maintain one enriched Markdown record per active creative under /agent/brain/meta/creatives/. Never auto-run; in staging, creative summaries live in Cacheth and are surfaced through Knoweth."
"purpose": "Step 1: the creative content layer — what Cacheth holds per creative and how to query it (Knoweth pre-context injection first, then the motion cache CLI) — plus provisional naming-pattern detection passed to the Account Context Brain. Writes no per-creative files to the brain."
},
{
"from": "meta/meta-account-context-brain-onboarding-package.md",
Expand All @@ -40,14 +40,20 @@
"from": "meta/meta-validation-onboarding-package.md",
"to": "/agent/brain/aligned-onboarding/meta-validation-onboarding-package.md",
"on_exists": "overwrite",
"purpose": "Step 3: the validation experience (v1.1). Answer-and-confirm loop, weekly deck build, lock-in (deck approval, refresh routine, Slack), and the MVCE gate saved to /agent/brain/meta/validation.md."
"purpose": "Step 3: the validation experience (v1.3). Answer-and-confirm loop with the show-the-work rule, weekly deck build, lock-in (deck approval, refresh routine, Slack), and the MVCE gate saved to /agent/brain/meta/validation.md."
},
{
"from": "meta/motion-cli-data-query-guide.md",
"to": "/agent/brain/aligned-onboarding/motion-cli-data-query-guide.md",
"on_exists": "overwrite",
"purpose": "Supporting reference: the canonical contract for pulling Meta data through the motion CLI. Brand-agnostic, carries no account IDs."
},
{
"from": "meta/cacheth-command-reference.md",
"to": "/agent/brain/aligned-onboarding/cacheth-command-reference.md",
"on_exists": "overwrite",
"purpose": "Supporting reference: the canonical contract for querying the local creative cache (Cacheth) through the motion cache CLI. All five commands with every flag, the full-record field layout, jq extraction recipes, and the retrieval priority order. Reference only, not a step to execute. Brand-agnostic, carries no account IDs."
},
{
"from": "voc-data-pull/SKILL.md",
"to": "/agent/.agents/skills/voc-data-pull/SKILL.md",
Expand Down Expand Up @@ -83,9 +89,27 @@
"to": "/agent/.agents/skills/voc-data-pull/templates/community-post.md",
"on_exists": "overwrite",
"purpose": "Copyable file skeleton for community-post output files."
},
{
"from": "knoweth/knoweth-organize-onboarding-package.md",
"to": "/agent/brain/aligned-onboarding/knoweth-organize-onboarding-package.md",
"on_exists": "overwrite",
"purpose": "Knoweth organize part: after the account questions are answered, organize the brain (keep shared content in the global lane, make it findable with tags + a naming decoder) and set the standing save + maintenance guard blocks. Today only global, the user lane, and the workspace lane are queried; data-source-family lanes are a documented forward path."
}
],
"changelog": [
{
"version": "2.3.0",
"date": "2026-07-24",
"type": "minor",
"notes": "Removed the per-creative-files model everywhere: creative content lives in Cacheth (the local creative cache) and is queried via Knoweth pre-context injection first, then the motion cache CLI (search-summaries / get-creative; local, no API call). The Creative Attribution playbook is now the creative-content-layer contract plus naming decode. Validation gates on cache coverage instead of files under /agent/brain/meta/creatives/. The naming decode is a handoff, not an artifact: detected provisionally in Step 1 and folded into account-context.md (Field 4) on confirmation — no separate taxonomy file. Performance metrics are pulled live via the motion CLI, never stored. Staged the Cacheth Command Reference (meta/cacheth-command-reference.md) beside the Data-Query Guide as the flag-level contract for the motion cache CLI."
},
{
"version": "2.2.0",
"date": "2026-07-23",
"type": "minor",
"notes": "Added the Knoweth organize part (knoweth/): after the account questions are answered, organize the brain so retrieval stays tight, plus a standing save + maintenance contract. Grounded in the real retrieval wiring - only global, user:<userId>, and project:<workspaceId> (the workspace) are queried today, so shared content stays in the global lane and is sliced by tags; data-source-family lanes are a documented forward path gated on a harness change, not shipped."
},
{
"version": "2.1.0",
"date": "2026-07-23",
Expand Down
Loading
Loading