Mike/freno-dev
1
0
Fork 3
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

faq: mirror the CoS decision into the drafts copy of the plan

Browse Source 
Byte-identical to The-Nook drafts/faq-from-objections.md at 2c1915e3. FRE-334
returned option A, so step 2b is done and the publish card has one option, not
three.

Source issue: FRE-326.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Paperclip Agent
2026-10-29 06:13:46 +00:00
parent f20389e64e
commit 871e47dee9
1 changed files with 19 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
marketing/drafts/faq-from-objections.md
View File

@@ -1,6 +1,6 @@
# `/faq` from the objections we already have
**Date:** 2026-10-29 · **Owner:** CMO · **Status:** CTO-verified 2026-10-29 (FRE-329); **awaiting human approval** — not approved, not published · **Source issue:** FRE-326
**Date:** 2026-10-29 · **Owner:** CMO · **Status:** CTO-verified (FRE-329) and CoS-decided (FRE-334, option A: withdraw both) on 2026-10-29; **awaiting the sponsor's publish approval** — not approved, not published · **Source issue:** FRE-326
**Page:** `nook.freno.me/faq` · **Page source:** `freno-dev/src/routes/nook/faq.tsx` · **Site commit read:** `c1c498e` (branch `faq/from-objections-2026-10-29`, unmerged)
**Product commit read:** The-Nook `f9cbd879` — the exact revision the CTO verified against (0.13.4, build 37)
@@ -322,6 +322,15 @@ privacy page today.
rather than replace it with another sentence I cannot stand behind. The replacement is held until
the Security Engineer's egress inventory and the `/privacy` update land.
**Decided 2026-10-29 — option A, withdraw both.** The Chief of Staff ruled on
[FRE-334](/FRE/issues/FRE-334) (`decision` document) that the `/faq` answer and `positioning.md`
rule 3 with its approved-claims row come down **in one commit**, and that no privacy claim is written
anywhere until FRE-333 lands and the CTO verifies it. Three consequences for the sequence below: the
withdrawal is no longer one of the sponsor's options, it is settled company policy; the publish card
asks one thing, publish the eight entries with the privacy answer withdrawn; and if an answer ever
ships the seven entries with the false answer still up, that is not a variant to absorb — it stops
and goes back to the CoS, because it would publish something the CoS has ruled out.
**The rule that produced the falsehood comes down with it.** The CTO's verdict traces the live answer
to `freno-dev/marketing/positioning.md` rule 3 (“Honest privacy scoping”) and to the matching
approved-claims row, which state the defensible claim as “No prompt or code content leaves the
@@ -334,10 +343,12 @@ which NOOK-881 retired).
- **Claim:** none until the inventory exists — deliberately.
- **Audience:** the buyer for whom this is the whole decision.
- **Channel:** `/faq` (withdrawal), `/privacy` (replacement), `marketing/positioning.md` (the rule).
- **Owner:** CoS for the withdrawal decision; Security Engineer for the egress inventory and the
disclosure text; CTO for any build change; CMO for the replacement copy and the rule-3 strike.
- **Date:** withdrawal decision 2026-10-31; inventory 2026-11-05; replacement copy 2026-11-09; rule-3
strike in the same commit as the page patch (§7 step 3).
- **Owner:** CoS for the withdrawal decision — **done 2026-10-29, option A**; Security Engineer for the
egress inventory and the disclosure text; CTO for any build change and for verifying the replacement;
CMO for the replacement copy and the rule-3 strike.
- **Date:** withdrawal decision **done 2026-10-29** (was targeted 2026-10-31); inventory 2026-11-05;
replacement copy 2026-11-09, and it needs both the CTO's verification and the sponsor's approval —
rule-3 strike in the same commit as the page patch (§7 step 3).
- **Must be true:** every egress in the inventory is either in the answer or gone from the build, and
`/privacy` lists the same set. The inventory's scope is wider than the draft first drew it — it must
cover `main.swift`, `LicenseService.swift`, `Info.plist`, `ChangelogRelease.swift`,
@@ -399,9 +410,9 @@ until the gates below are satisfied; `faq-page.patch` re-checked against `freno-
| Step | Owner | Date | What settles it |
|---|---|---|---|
| 1. CTO verifies the claims and evidence pointers in E1–E8 | CTO | **done 2026-10-29** | [FRE-329](/FRE/issues/FRE-329), verdict in its `faq-verdict` document: E1/E7 verified as written, E2/E6 verified after one sentence each, E3/E4/E5/E8 corrected above, **no entry cut**. Applied in this revision. |
| 2. Human approves this revision | Sponsor | target 2026-10-31 | The draft moves from `marketing/drafts/` to `marketing/approved/`, or the confirmation card on FRE-326 is accepted. The card names the privacy withdrawal, which is part of the same page edit. |
| 2b. Withdrawal of the false privacy answer and of `positioning.md` rule 3 | Chief of Staff — asked in [FRE-334](/FRE/issues/FRE-334) | target 2026-10-31 | A CoS decision, recorded on this issue. If the CoS declines, the seven non-privacy entries can still ship; the privacy answer does not stay up and does not get replaced. |
| 3. Apply the page patch, strike rule 3 + its approved-claims row, commit on `freno-dev` | CMO | 2026-11-03 | The patch applies cleanly; the site's own suite passes; the diff contains only the FAQ entries, the page comment/description, and the `positioning.md` strike. One commit, so the page and the rule move together. |
| 2. Human approves this revision | Sponsor | target 2026-10-31 | The draft moves from `marketing/drafts/` to `marketing/approved/`, or the confirmation card on FRE-326 is accepted. The card asks one question now — publish the eight entries with the privacy answer withdrawn — because 2b is settled. |
| 2b. Withdrawal of the false privacy answer and of `positioning.md` rule 3 | Chief of Staff | **done 2026-10-29** | [FRE-334](/FRE/issues/FRE-334) `decision`: **option A, withdraw both, one commit**, no privacy claim anywhere until FRE-333 lands and the CTO verifies it. Recorded here so the page, the rule and the card cannot disagree. |
| 3. Apply the page patch, strike rule 3 + its approved-claims row, commit on `freno-dev` | CMO | 2026-11-03 | Both patches apply together to `freno-dev` master `c1c498e` (checked 2026-10-29, in a throwaway worktree, as one change set); the diff contains only the FAQ entries, the page comment/description, the `positioning.md` rule-3 strike and the 14.2 row. **The site's suite has not been run — this host has no `bun`** — so step 3 still has to run it before the commit. One commit, so the page and the rule move together. |
| 4. Merge to `freno-dev/master` (the publish) | Sponsor or Chief of Staff | 2026-11-05 | A human merge; Vercel deploys. No agent pushes to master. |
| 5. Verify the live page | CMO | 2026-11-05 | `https://nook.freno.me/faq` returns 200 and shows the eight entries with no privacy answer; the text matches the approved draft, sentence for sentence. |