@ericrisco/rsc 0.1.34 → 0.1.35

package/skills/marketing/references/brand-grounding.md

@@ -91,9 +91,19 @@ If the user can't answer a question, that dimension stays incomplete — note th
 
 ### Brand wiki article template
 
-Each `02-DOCS/wiki/brand/*.md` article follows the harness wiki format:
+Each `02-DOCS/wiki/brand/*.md` article follows the harness wiki format. It is an OKF v0.1 article: open it with YAML frontmatter carrying a non-empty `type:` (`brand-study`), then the H1 and body:
 
 ```markdown
+---
+type: brand-study
+title: Brand — Value Proposition
+description: The core benefit and what makes this brand different from the named alternatives.
+tags: [brand, value-proposition]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: brand
+status: stable
+---
+
 # Brand — Value Proposition
 
 > Sources: {user interview, YYYY-MM-DD}
@@ -124,9 +134,19 @@ One paragraph: the core benefit and what makes it different.
 
 ### Voice article specifics
 
-`voice.md` must contain the do/don't word lists and link to every raw sample:
+`voice.md` must contain the do/don't word lists and link to every raw sample (same OKF frontmatter; `type: brand-study`):
 
 ```markdown
+---
+type: brand-study
+title: Brand — Tone & Voice
+description: Tone descriptors, do/don't word lists, and the voice fingerprint extracted from real samples.
+tags: [brand, voice, tone]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: brand
+status: stable
+---
+
 # Brand — Tone & Voice
 
 > Sources: {user interview, YYYY-MM-DD}

package/skills/medium-strategy/SKILL.md

@@ -133,6 +133,16 @@ On a monthly/quarterly review:
 Every session ends with a dated record under `02-DOCS/wiki/medium/decisions/`. Minimum fields — the bet-on metric is mandatory, because a decision with no metric is an opinion, not a checkable bet:
 
 ```markdown
+---
+type: medium-decision
+title: Solo vs publication for AI-tools series
+description: Stay solo + canonical-import the blog series; pitch one Boost-eligible AI pub with a native original.
+tags: [medium, publications, monetization, distribution]
+timestamp: 2026-06-02T00:00:00Z
+topic: medium
+status: stable
+---
+
 # 2026-06-02 — Solo vs publication for AI-tools series
 
 Decision: Stay solo profile + canonical-import the blog series; pitch one Boost-eligible AI pub with a native original.
@@ -140,6 +150,8 @@ Rationale: 400 followers, no editor nomination path; the blog has evergreen sear
 Bets on metric: member reading time from external/search referral; 1 Boost nomination this quarter.
 ```
 
+`type:` is the required OKF v0.1 field; `timestamp` is ISO 8601. The `Decision:` / `Bets on metric:` lines are domain signals `verify.sh` greps for — keep them.
+
 After a review, append a `what-worked.md` entry tied to specific stories/pubs/tags (e.g. "`AI Coding Tools` long-tail + Boost → 3.2h member reading time"). Full templates, layout, and the verify.sh contract: [`references/wiki-records.md`](references/wiki-records.md). Sanity-check the wiki with `scripts/verify.sh 02-DOCS/wiki/medium/`.
 
 ## Anti-patterns

package/skills/medium-strategy/references/wiki-records.md

@@ -2,6 +2,8 @@
 
 This is the persistence layer that makes medium-strategy compound. Read SKILL.md §1 and §9 first; this file is the exact format.
 
+Every `.md` file written under `02-DOCS/wiki/medium/` is part of the OKF v0.1 bundle: it carries YAML frontmatter with a non-empty `type:` (the only required OKF field), and any cross-references use **standard markdown links** (`[Text](./pubs.md)`), never wikilinks (`[[...]]`). The domain lines `verify.sh` greps for (the dated heading, `Decision:`, the metric/bet field) stay exactly as shown below.
+
 ## Layout under `02-DOCS/wiki/medium/`
 
 ```text
@@ -21,6 +23,16 @@ This is the persistence layer that makes medium-strategy compound. Read SKILL.md
 Every decision file MUST carry three signals: a **date**, a **Decision:** line, and a **named metric/bet**. The metric is mandatory — a decision with no metric is an opinion, not something you can check next quarter.
 
 ```markdown
+---
+type: medium-decision
+title: Solo vs publication for the AI-tools series
+description: Stay solo; canonical-import the evergreen blog posts; pitch one Boost-eligible AI pub.
+tags: [medium, publications, monetization, distribution]
+timestamp: 2026-06-02T00:00:00Z
+topic: medium
+status: stable
+---
+
 # 2026-06-02 — Solo vs publication for the AI-tools series
 
 Decision: Stay solo profile; canonical-import the 6 evergreen blog posts; pitch one Boost-eligible AI publication with a new native original.
@@ -29,11 +41,23 @@ Bets on metric: member reading time from external + search referral over 90 days
 Status: open
 ```
 
-When the bet resolves, append a short outcome to the same file (`Status: won — Boost nomination 2026-07; +2.1h member reading time`) rather than editing the original — append-only history.
+`type:` (required) + `timestamp:` (ISO 8601, last meaningful edit) are the OKF surface; the `Status:` line in the body is the domain bet-lifecycle marker — distinct from the frontmatter `status:` (the OKF article lifecycle: draft | stable | stale). When the bet resolves, append a short outcome to the body (`Status: won — Boost nomination 2026-07; +2.1h member reading time`) rather than editing the original — append-only history. A running `decisions.md` log at the root carries one frontmatter block at the top (`type: medium-decision`).
 
 ## what-worked.md entry template
 
+`what-worked.md` is one running file; new review blocks are prepended newest-first under a single frontmatter block at the top.
+
 ```markdown
+---
+type: medium-record
+title: What worked — Medium
+description: Running log of outcomes tied to specific Medium stories, publications, and tags.
+tags: [medium, what-worked, member-reading-time, boost]
+timestamp: 2026-09-01T00:00:00Z
+topic: medium
+status: stable
+---
+
 ## 2026-09-01 — Q3 review
 - `AI Coding Tools` (long-tail) + Boost → 3.2h member reading time on one story. Double down: keep the long-tail tag, pitch the same pub again.
 - Imported blog post w/ canonical + newsletter push → +5% external bonus visible, but low member conversion. Keep importing; stop expecting member reads from cold list.
@@ -44,6 +68,20 @@ When the bet resolves, append a short outcome to the same file (`Status: won —
 
 Keep these lightweight. `pubs.md`: pub name | status (accepted/pitched/dropped) | niche fit | a one-line guideline note. `tags.md`: tag | popular-or-long-tail | did it pull member reading time?
 
+Both still carry OKF frontmatter (one block at the top of each file):
+
+```markdown
+---
+type: medium-record
+title: Publications tracker   # or: Tag sets tried
+description: Accepted / pitched / dropped Medium publications and their guideline notes.
+tags: [medium, publications]   # or [medium, tags, distribution] for tags.md
+timestamp: 2026-09-01T00:00:00Z
+topic: medium
+status: stable
+---
+```
+
 ## The verify.sh contract
 
 `scripts/verify.sh` is a **structural lint, not a craft judge.** Run it after a session:

package/skills/medium-writing/SKILL.md

@@ -117,6 +117,25 @@ If `02-DOCS/` exists, learn before you write:
 - Bias toward the title/subtitle patterns and topics that historically beat a 50% read ratio for *this* author; avoid angles that drew clicks but bounced.
 - After a notable result, append the learned pattern to `02-DOCS/wiki/medium/read-ratio-patterns.md` so the next draft inherits it.
 
+`read-ratio-patterns.md` lives in the `02-DOCS/wiki/` OKF v0.1 bundle, so it carries YAML frontmatter with a non-empty `type:` — one block at the top, with new pattern blocks prepended newest-first below it. Use `type: medium-record` (the same type the `medium-strategy` skill writes under `02-DOCS/wiki/medium/`, keeping the two skills' wiki content consistent). Create it with this header if it does not yet exist:
+
+```markdown
+---
+type: medium-record
+title: Read-ratio patterns — Medium
+description: Title/subtitle/topic patterns that historically beat a 50% read ratio for this author.
+tags: [medium, read-ratio, titles, hooks]
+timestamp: 2026-06-02T00:00:00Z
+topic: medium
+status: stable
+---
+
+## 2026-06-02 — <pattern learned>
+- <title/subtitle archetype + topic that beat the 50% read ratio, with the number observed>
+```
+
+Cross-references use standard markdown links (`[Text](./what-worked.md)`), never wikilinks (`[[...]]`).
+
 If `02-DOCS/` is absent, proceed from the craft defaults above and say so in one line, rather than inventing stats.
 
 ## Anti-patterns

package/skills/plan/references/plan-template.md

@@ -9,9 +9,20 @@ flows, levels — not framework syntax.
 ---
 
 ```markdown
+---
+type: plan
+title: Plan — <feature name>
+description: The structure-level implementation plan for <feature> — contracts, shapes, flows.
+tags: [sdd, plan]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: sdd
+slug: <slug>
+status: draft
+---
+
 # Plan — <feature name>
 
-> Spec: ../specs/<slug>.md · Constitution: ../constitution.md · Status: draft | approved
+> Spec: [../specs/<slug>.md](../specs/<slug>.md) · Constitution: [../constitution.md](../constitution.md) · Status: draft | approved
 > Last updated: YYYY-MM-DD
 
 ## 0. Global Constraints

package/skills/shortform-packaging/SKILL.md

@@ -63,8 +63,13 @@ stranger's voice that contradicts what already won.
 4. **No script or no settled angle? Route OUT** (see Handoffs). Never invent here.
 
 Persist the package under `02-DOCS/wiki/shortform/` and raw test results under
-`02-DOCS/raw/shortform/`. Pattern depth lives in
-[references/package-templates.md](references/package-templates.md).
+`02-DOCS/raw/shortform/`. The `shortform/` wiki tree is an **OKF v0.1 bundle** shared
+with the `tiktok-api` and `shortform-strategy` siblings: each persisted package `.md`
+leads with YAML frontmatter carrying a non-empty `type: shortform-package` (plus the
+recommended `title`/`tags`/`timestamp`), and any cross-references use standard markdown
+links, never `[[wikilinks]]`. The raw feedback log under `02-DOCS/raw/shortform/` is
+`raw/`, not `wiki/` — no frontmatter required. The full frontmatter + pattern depth
+lives in [references/package-templates.md](references/package-templates.md).
 
 ## The two-second decision
 

package/skills/shortform-packaging/references/package-templates.md

@@ -6,10 +6,21 @@ filled `02-DOCS` feedback-log schema.
 
 ## The package file format
 
-Emit one plain-text/markdown block per short. `scripts/verify.sh` lints exactly these
-labels (English or ES/CA, one per line, content following):
+Emit one markdown file per short under `02-DOCS/wiki/shortform/`. The `shortform/`
+wiki tree is an **OKF v0.1 bundle** shared with the `tiktok-api` and
+`shortform-strategy` siblings, so the file leads with YAML frontmatter (a non-empty
+`type` is the only OKF hard requirement; `title`/`tags`/`timestamp` are the recommended
+surface). The labeled body below is unchanged — `scripts/verify.sh` lints exactly these
+labels (English or ES/CA, one per line, content following) and ignores the frontmatter:
 
 ```text
+---
+type: shortform-package
+title: faceless productivity TikTok — package
+tags: [shortform, packaging, tiktok]
+timestamp: 2026-06-02T12:00:00Z
+platform: tiktok
+---
 Hook:
   - I deleted my to-do app. Here's why.
   - The app that runs my whole week (it's free)

package/skills/shortform-strategy/SKILL.md

@@ -113,9 +113,21 @@ Every decision must end up in the ledger so next month's call is grounded.
 
 ### Decision record format
 
-Append every call to `02-DOCS/wiki/shortform/decisions.md` as a dated block:
+`02-DOCS/wiki/shortform/decisions.md` is an OKF append-log: write the frontmatter
+header once (a non-empty `type` is the only OKF hard requirement; `title`/`tags`/`timestamp`
+are the recommended surface), then **prepend each new dated block newest-first** so the
+latest call is on top. Use ISO 8601 dates; never edit a past block. Bump the header
+`timestamp` on each append. Header + one block:
 
 ```markdown
+---
+type: shortform-decision-log
+title: Shortform strategy decisions
+tags: [shortform, strategy, decisions]
+timestamp: 2026-06-02T10:00:00Z
+---
+# Shortform strategy decisions
+
 ## 2026-06-02 — Drop daily posting to 4 Reels/week
 **Decision:** Cut from ~7 thin posts/week to 4 strong Reels/week, fixed Tue/Fri.
 **Rationale:** Reach fell as volume rose; consistency > velocity past the ceiling.
@@ -140,10 +152,22 @@ Append every call to `02-DOCS/wiki/shortform/decisions.md` as a dated block:
 
 ## Persist it
 
-Write the account's brain back so it compounds (mirrors the harness Karpathy-wiki convention):
+Write the account's brain back so it compounds (mirrors the harness Karpathy-wiki convention). The `shortform/` wiki tree is an **OKF v0.1 bundle** shared with the `tiktok-api` and `shortform-packaging` siblings: every `.md` written here carries YAML frontmatter with a non-empty `type`, cross-references are standard markdown links (never `[[wikilinks]]`), and `decisions.md` follows the OKF newest-first append-log rule.
+
+- `02-DOCS/wiki/shortform/strategy.md` — positioning, cadence/mix, KPI, length bands, current series. Lead with frontmatter; the body keeps the H1 + sections the linter checks:
+
+  ```markdown
+  ---
+  type: shortform-strategy
+  title: Shortform account strategy
+  tags: [shortform, strategy, positioning, cadence]
+  timestamp: 2026-06-02T10:00:00Z
+  ---
+  # Shortform account strategy
+  ...
+  ```
 
-- `02-DOCS/wiki/shortform/strategy.md` — positioning, cadence/mix, KPI, length bands, current series.
-- `02-DOCS/wiki/shortform/decisions.md` — the dated decision log (format above).
-- `02-DOCS/raw/shortform/metrics.csv` — the per-post ledger (schema in `references/learning-loop-template.md`).
+- `02-DOCS/wiki/shortform/decisions.md` — the dated decision log, OKF append-log (`type: shortform-decision-log`, newest block on top; format above).
+- `02-DOCS/raw/shortform/metrics.csv` — the per-post ledger (schema in `references/learning-loop-template.md`). This is `raw/`, not `wiki/` — a CSV, no frontmatter.
 
-Verify a produced strategy doc with `scripts/verify.sh 02-DOCS/wiki/shortform/strategy.md` — a read-only structural lint (positioning, cadence, completion KPI, ride-or-skip rule, ≥1 dated decision, sends/saves logged).
+Verify a produced strategy doc with `scripts/verify.sh 02-DOCS/wiki/shortform/strategy.md` — a read-only structural lint (positioning, cadence, completion KPI, ride-or-skip rule, ≥1 dated decision, sends/saves logged). The lint reads body content, so the added frontmatter does not affect it.

package/skills/shortform-strategy/references/learning-loop-template.md

@@ -38,9 +38,17 @@ Run once a month, reading `02-DOCS/raw/shortform/metrics.csv`:
 
 ## Decision-record template
 
-Append to `02-DOCS/wiki/shortform/decisions.md`. Every block is dated, rests on a named metric, and carries a revisit date so it is an experiment, not folklore.
+`02-DOCS/wiki/shortform/decisions.md` is an OKF v0.1 append-log: the frontmatter header (a non-empty `type` is the only OKF hard requirement; `title`/`tags`/`timestamp` are recommended) is written once, then each new block is **prepended newest-first** under the H1. Every block is dated (ISO 8601), rests on a named metric, and carries a revisit date so it is an experiment, not folklore. Past blocks are immutable; bump the header `timestamp` on each append.
 
 ```markdown
+---
+type: shortform-decision-log
+title: Shortform strategy decisions
+tags: [shortform, strategy, decisions]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+---
+# Shortform strategy decisions
+
 ## YYYY-MM-DD — <short decision title>
 **Decision:** <what changes, concretely — cadence/positioning/series/trend rule>
 **Rationale:** <the one-line why>

package/skills/specify/references/spec-template.md

@@ -6,10 +6,21 @@ endpoint, library, file path, or algorithm. If you can't phrase it without
 naming the tech, it's a *point to clarify*, not a requirement.
 
 ```markdown
+---
+type: spec
+title: Spec — <Feature name>
+description: WHAT and WHY for <feature> — problem, goals, behaviour, acceptance criteria.
+tags: [sdd, spec]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: sdd
+slug: <slug>
+status: draft
+---
+
 # Spec — <Feature name>
 
 > Slug: `<slug>` · Status: draft · Created: <YYYY-MM-DD>
-> Inherits: 02-DOCS/wiki/sdd/constitution.md
+> Inherits: [constitution](../constitution.md)
 
 ## Problem & why
 <The pain, who feels it, and the cost of leaving it unsolved. One short

package/skills/tiktok-api/SKILL.md

@@ -251,10 +251,14 @@ A pull that prints to stdout and vanishes is wasted. **Every pull appends a date
 
 Filenames carry the `tiktok-` prefix because the same `shortform/` wiki may also hold Instagram and YouTube pulls — namespacing keeps platforms from colliding.
 
-Per-pull entry template:
+Per-pull entry template. The frontmatter is **OKF v0.1 conformant** — a non-empty `type` is the only hard requirement; `title`/`tags`/`timestamp` are the recommended OKF surface; the domain `date`/`range`/`account`/`platform`/`source` keys the siblings parse are preserved additively (OKF tolerates extra keys). `date` is the reporting day; `timestamp` is the ISO 8601 write moment:
 
 ```markdown
 ---
+type: shortform-metrics
+title: TikTok account snapshot — 2026-06-02
+tags: [tiktok, metrics, snapshot]
+timestamp: 2026-06-02T09:00:00Z
 date: 2026-06-02
 range: 2026-05-26..2026-06-01
 account: <open_id>
@@ -274,7 +278,7 @@ For You 71% · Personal profile 14% · Search 7%
 completion +3.1pts after the tighter cold-open; FYP share up 5pts.
 ```
 
-Rule: **append, never overwrite.** The feedback log *is* the value — overwriting yesterday's snapshot destroys the trend the siblings need, and erases the 24–48h settling you only see across pulls. Exact file tree, naming, and how siblings read the log: `references/wiki-schema.md`.
+Rule: **append, never overwrite.** The feedback log *is* the value — overwriting yesterday's snapshot destroys the trend the siblings need, and erases the 24–48h settling you only see across pulls. The per-video log (`videos/tiktok-<id>.md`) is an OKF append-log: write its frontmatter header once, prepend each new dated block newest-first, never edit a past block. `index.md` is the OKF reserved file — no frontmatter, standard markdown links only. Exact file tree, frontmatter, naming, and how siblings read the log: `references/wiki-schema.md`.
 
 ## 6. Rate & failure math
 

package/skills/tiktok-api/references/wiki-schema.md

@@ -24,8 +24,19 @@ from colliding and lets a sibling grep `tiktok-*` for just this account.
 
 ## Account snapshot entry (one file per pull)
 
+Frontmatter is **OKF v0.1 conformant**: a non-empty `type` is the only hard
+requirement; `title`/`tags`/`timestamp` are the recommended OKF surface. The
+domain keys (`date`, `range`, `account`, `platform`, `source`, `provisional`) are
+preserved verbatim — siblings parse them, and OKF tolerates arbitrary extra keys.
+`date` is the snapshot's reporting day; `timestamp` is the ISO 8601 moment the file
+was written. Keep both.
+
 ```markdown
 ---
+type: shortform-metrics
+title: TikTok account snapshot — 2026-06-02
+tags: [tiktok, metrics, snapshot]
+timestamp: 2026-06-02T09:00:00Z
 date: 2026-06-02
 range: 2026-05-26..2026-06-01
 account: <open_id>
@@ -50,11 +61,23 @@ completion +3.1pts after the tighter cold-open; FYP share up 5pts.
 
 Newest entry on top, so a glance shows the latest. Each pull **prepends** a block —
 this is where the 24–48h settling becomes visible (the same video's
-`full_video_watched_rate` will drift between pulls).
+`full_video_watched_rate` will drift between pulls). This is an OKF append-log:
+the frontmatter header is written once and stays immutable; new dated blocks are
+prepended **above** older ones (newest-first), past blocks are never edited, and
+dates are ISO 8601.
 
 ```markdown
+---
+type: shortform-record
+title: tiktok-7399 — "cold open hook test"
+tags: [tiktok, video-log]
+timestamp: 2026-06-02T09:00:00Z
+video_id: "7399..."
+platform: tiktok
+posted: 2026-05-28
+duration: 21s
+---
 # tiktok-7399... — "cold open hook test"
-posted: 2026-05-28 | duration: 21s
 
 ## 2026-06-02 (final-ish)
 views 52,140 | completion 28.4% | avg_watched 6.1s | FYP 71%
@@ -63,13 +86,18 @@ views 52,140 | completion 28.4% | avg_watched 6.1s | FYP 71%
 views 18,900 | completion 24.1% | avg_watched 5.3s | FYP 64%
 ```
 
+On each prepend, bump the header `timestamp` to the new pull's ISO moment; never
+edit a past dated block.
+
 ## index.md
 
-A thin pointer, not a data dump:
+A thin pointer, not a data dump. As an OKF **reserved** file it carries **no
+frontmatter**, and its cross-references are standard markdown links (never
+wikilinks), so an OKF consumer can follow them straight to the snapshot files:
 
 ```markdown
 # shortform wiki — index
-- tiktok: latest snapshot → tiktok-account-2026-06-02.md
+- tiktok: latest snapshot → [tiktok-account-2026-06-02.md](./tiktok-account-2026-06-02.md)
 - open questions:
   - is the cold-open change holding completion above 27%? (watch next 2 pulls)
 ```
@@ -83,3 +111,9 @@ A thin pointer, not a data dump:
 - **Namespace by platform.** `tiktok-` prefix on every file so IG/YouTube pulls coexist.
 - **Numbers only, no interpretation.** "What changed" is a factual delta line, not a
   recommendation — what to *do* about it belongs to `shortform-strategy`.
+- **OKF v0.1 conformant.** Every snapshot and per-video file carries YAML frontmatter
+  with a non-empty `type` (`shortform-metrics` / `shortform-record`) plus the OKF
+  `title`/`tags`/`timestamp` surface; domain keys like `date` are kept additively. The
+  reserved `index.md` carries no frontmatter. All cross-references are standard markdown
+  links — never `[[wikilinks]]` — so the `shortform/` tree is a portable OKF bundle the
+  siblings (and any OKF consumer) read without translation.

package/skills/verify/SKILL.md

@@ -113,9 +113,19 @@ A criterion you "reviewed by reading the code" is not verified. Reading is `revi
 
 ### 4 — RECORD
 
-Write a dated verification record to `02-DOCS/wiki/sdd/verifications/<slug>-YYYY-MM-DD.md` so the project's living knowledge carries the proof, then index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer) under the `sdd/` topic. Keep it short and factual:
+Write a dated verification record to `02-DOCS/wiki/sdd/verifications/<slug>-YYYY-MM-DD.md` so the project's living knowledge carries the proof, then index it in `02-DOCS/wiki/index.md` (the Knowledge map; root `CLAUDE.md` keeps only a short pointer) under the `sdd/` topic. It is an OKF v0.1 wiki article: open it with YAML frontmatter carrying a non-empty `type:`. Keep it short and factual:
 
 ```markdown
+---
+type: verification
+title: Verification — <slug> — YYYY-MM-DD
+description: Evidence-backed verdict for <slug> — stack gate, task done-checks, acceptance criteria.
+tags: [sdd, verification]
+timestamp: YYYY-MM-DDTHH:MM:SSZ
+topic: sdd
+slug: <slug>
+---
+
 # Verification — <slug> — YYYY-MM-DD
 
 ## Stack gate

package/skills/youtube-api/SKILL.md

@@ -215,10 +215,15 @@ A pull that prints to stdout and vanishes is wasted. **Every pull appends a date
   videos/<VIDEO_ID>.md      # per-video running log, newest entry on top
 ```
 
-Per-pull entry template:
+Per-pull entry template (OKF v0.1: non-empty `type` + the domain keys siblings parse):
 
 ```markdown
 ---
+type: youtube-metrics
+title: Channel snapshot 2026-05-31
+description: Channel KPIs, traffic and retention for 2026-05-01..2026-05-31.
+tags: [youtube, channel-snapshot]
+timestamp: 2026-05-31T00:00:00Z
 date: 2026-05-31
 range: 2026-05-01..2026-05-31
 channel: MINE
@@ -237,7 +242,7 @@ Sharp drop 0.00→0.06 (intro), recovers, second dip ~0.55.
 avg_view_pct +2.1pts; SUGGESTED share up 6pts after the Ep.13 packaging change.
 ```
 
-Rule: **append, never overwrite.** The feedback log *is* the value — overwriting yesterday's snapshot destroys the trend the siblings need. Exact file tree, naming, and how siblings read the log: `references/wiki-schema.md`.
+Rule: **append, never overwrite.** The feedback log *is* the value — overwriting yesterday's snapshot destroys the trend the siblings need. `02-DOCS/wiki/` is an OKF v0.1 bundle: keep the domain keys (`date`, `range`, `channel`, `source`) the siblings parse, add `type`/`timestamp` alongside them, use standard markdown links (never `[[wikilinks]]`), and leave the reserved `index.md` frontmatter-free. Exact file tree, naming, per-video log shape, and how siblings read the log: `references/wiki-schema.md`.
 
 ## 7. Quota & failure math
 

package/skills/youtube-api/references/wiki-schema.md

@@ -2,6 +2,8 @@
 
 The point of this skill is not to print stats once; it is to grow a **feedback log** the strategy/packaging siblings can read. The log lives under `02-DOCS/wiki/youtube/` and every pull **appends** to it.
 
+`02-DOCS/wiki/` is an **OKF v0.1** bundle, so every non-reserved `.md` file written here carries YAML frontmatter with a non-empty `type`. This skill writes `type: youtube-metrics` on its snapshots/logs and keeps the domain keys (`date`, `range`, `channel`, `source`) that the strategy/packaging siblings parse literally — `type` and `timestamp` are added *alongside* them, never replacing them. OKF allows arbitrary extra keys, so the shared keys stay stable. Links between wiki files are standard markdown links (`[text](./file.md)`), never Obsidian wikilinks.
+
 ## File tree
 
 ```text
@@ -24,6 +26,11 @@ Naming:
 
 ```markdown
 ---
+type: youtube-metrics
+title: Channel snapshot 2026-05-31
+description: Channel KPIs and traffic for 2026-05-01..2026-05-31.
+tags: [youtube, channel-snapshot]
+timestamp: 2026-05-31T00:00:00Z
 date: 2026-05-31
 range: 2026-05-01..2026-05-31
 channel: MINE
@@ -40,9 +47,20 @@ BROWSE 44% · SUGGESTED 31% · YT_SEARCH 12%
 avg_view_pct +2.1pts; SUGGESTED share +6pts after the Ep.13 packaging change.
 ```
 
-## Per-video entry template (prepended to `videos/<id>.md`)
+## Per-video log file — `videos/<VIDEO_ID>.md`
+
+The file carries frontmatter once (at the top); each new dated block is **prepended directly under the frontmatter** (newest entry first — this is an append-log, past entries are immutable). On the first write, create the frontmatter; on every later pull, refresh `timestamp` and insert the new block above the previous newest one. Keep the domain key `channel` so siblings can parse it.
 
 ```markdown
+---
+type: youtube-metrics
+title: Video log — dQw4w9WgXcQ
+description: Per-pull KPI/traffic/retention log for video dQw4w9WgXcQ, newest entry first.
+tags: [youtube, video-log]
+timestamp: 2026-05-31T00:00:00Z
+channel: MINE
+source: youtube-analytics-api-v2
+---
 ## 2026-05-31  (range 2026-05-01..2026-05-31)
 views: 8,902 | avg_view_pct: 41.0% | ctr(studio): 6.2%
 traffic: SUGGESTED 52% · BROWSE 23% · YT_SEARCH 9%
@@ -52,10 +70,12 @@ note: held suggested-traffic share week over week.
 
 ## index.md
 
+OKF **reserved file**: a directory listing, so it carries **no frontmatter**. Point at the latest snapshot and tracked videos with standard markdown links (never wikilinks).
+
 ```markdown
 # YouTube channel feedback log
-latest snapshot: channel-2026-05-31.md
-videos tracked: dQw4w9WgXcQ, abc123XYZ
+latest snapshot: [channel-2026-05-31.md](./channel-2026-05-31.md)
+videos tracked: [dQw4w9WgXcQ](./videos/dQw4w9WgXcQ.md), [abc123XYZ](./videos/abc123XYZ.md)
 
 ## Open questions for strategy/packaging
 - Intro drop-off at 0.06 recurs across last 3 uploads — packaging or pacing?
@@ -67,4 +87,5 @@ videos tracked: dQw4w9WgXcQ, abc123XYZ
 1. **Append, never overwrite.** A snapshot is a point in time; deleting it erases the trend. The history is the deliverable.
 2. **One source of truth for derived numbers.** Store what the API returned. Mark Studio-sourced values explicitly (`ctr(studio)`) so a reader knows it was not API-derived.
 3. **No interpretation in the log beyond a one-line "what changed."** Deeper reading ("we should change the hook") is the strategy/packaging sibling's job — this skill records, it does not prescribe.
-4. **Siblings read this tree.** Keep frontmatter keys stable (`date`, `range`, `channel`, `source`) so a sibling can parse the latest snapshot without guessing.
+4. **Siblings read this tree.** Keep the domain frontmatter keys stable (`date`, `range`, `channel`, `source`) so a sibling can parse the latest snapshot without guessing. The OKF keys (`type`, `title`, `description`, `tags`, `timestamp`) are added alongside them, never instead of them — all four youtube skills share this same key set and the same markdown-link style.
+5. **OKF-conformant wiki content.** Every non-reserved `.md` here has a non-empty `type` (`youtube-metrics`). `index.md` is the lone reserved file (no frontmatter, a directory listing). Per-video logs are newest-first append-logs with ISO 8601 dates; past dated blocks are never edited. Cross-references use standard markdown links (`[text](./file.md)`), never `[[wikilinks]]`.

package/skills/youtube-packaging/SKILL.md

@@ -46,7 +46,13 @@ produce generic copy in someone else's voice.
   hook, the keyword, and the audience all at once.)
 
 Persist what you write under `02-DOCS/wiki/youtube/` (the package) and raw test
-results under `02-DOCS/raw/youtube/`.
+results under `02-DOCS/raw/youtube/`. `02-DOCS/wiki/` is an **OKF v0.1** bundle:
+every package or log file persisted there carries YAML frontmatter with a
+non-empty `type` (`youtube-package`) plus the OKF surface (`title`, `description`,
+`tags`, `timestamp`) shared with the strategy/thumbnail/api siblings, and all
+cross-references use standard markdown links — never `[[wikilinks]]`. The OKF
+frontmatter shape for the persisted package and log is in
+[references/description-and-chapters.md](references/description-and-chapters.md).
 
 ## The title
 
@@ -158,7 +164,9 @@ carry forward what won as priors: if numeric titles beat curiosity titles 3 test
 running on this channel, the new set leans numeric. If a hashtag set tanked, drop
 it.
 
-**Append after you test.** One row per test:
+**Append after you test.** One row per test, into `02-DOCS/wiki/youtube/packaging-log.md`
+(OKF v0.1: file-level `type: youtube-package` frontmatter at the top, the table
+below it, newest rows appended, past rows immutable):
 
 ```text
 | date | video | title set tried | winner | CTR | impressions | avg view duration | note |