fix(linkedin-studio): N21 — scaffold-bånd-redesign + ferskhet-rester (newsletter-guide, first-comment) [skip-docs]
Del 1 — scaffold-bånd (KTG-beslutning: behold målbåndet, utvid komponentene). Komponentsummen var 960–1 640 mot målbåndet 1 200–1 800: en skjelett-konform draft kunne lande under gulvet og nådde aldri taket. Nye bånd — Context 250–350, Insight 550–850, Implication 250–350 (Hook 110–140 og CTA 50–100 uendret) — summerer til 1 210–1 790, altså INNI 1 200–1 800. Skjelett-konform er nå gate-konform per konstruksjon. Målbåndet 1 200–1 800 er uendret overalt; hooks/prompts/content-quality-gate.md (den kanoniske gaten) er ikke rørt. Alternativet — å heve taket per AuthoredUp D-4 — ville krevd 25 filer / 40 linjer inkl. gate-prompten, begge skills, quality-scorecard, config-malen og brain-fiksturen. Skjelettet fantes i seks kopier, alle rettet på KTG-go: commands/post.md, commands/batch.md, commands/pipeline.md, references/engagement-frameworks.md, agents/content-optimizer.md, skills/linkedin-content-creation/SKILL.md. De tre siste lå utenfor planens scope, men to av dem var internt selvmotsigende på én linje (overskrift 1 200–1 800 over komponenter som summerte til 960–1 640), og engagement-frameworks.md er nettopp fila post.md/pipeline.md instruerer modellen om å LESE for strukturen. Nabofunn tatt med på KTG-go: post.md:95 ga «Personal stories → 1 000–1 400», som motsa post.md:136s egen gate. Kald-review R2a MAJOR — nå 1 200–1 800. D-4 inn i kanonfila: ny «Post length»-seksjon i references/algorithm-signals-reference.md med AuthoredUp-optimumet 1 301–2 500 (372 126 poster, sep 2025–feb 2026), merket single-vendor/ett vindu, med eksplisitt note om at datapunktet gjør det shippede taket konservativt — ikke feil — og at de to AuthoredUp-N-ene i fila (621K vs 372K) er ulike studier. Kilde verifisert mot primærkilden, ikke overført fra planen. Del 2 — ferskhet-rester (begge påstander verifisert mot LinkedIn Help): - D-6 newsletter-strategy-guide.md: «5 000+ følgere» framstilt som terskel er feil — «All LinkedIn members have access to create a newsletter on LinkedIn» (a517914). Omskrevet til redaksjonell modenhetsvurdering (også i Mistakes-tabellen og Bottom Line). E-post er ikke garantert: LinkedIn de-dupliserer på tvers av kanaler — «if you receive an in-app or push notification, you should not expect to also receive an email for the same notification» (a517914). Bringer referansefila i tråd med newsletter.md:2384. Fjernet samtidig den ukildede «Algorithm favors newsletters from established creators» i den omskrevne blokka. - D-7 first-comment-strategy.md: «pinned by default» er uverifisert og feil — pinning er en eksplisitt forfatterhandling (a524166), og standard kommentarsortering er algoritmisk. Lagt til «What this file does not claim»- avsnitt som speiler kanonfilas «contested»/low-confidence-epistemikk. Scope 3 (KTG-go, amend): references/engagement-frameworks.md har FIRE skjeletter, ikke ett. To til brot gulvet i malbandet — Data-Driven Post (1 050-1 400) og Contrarian Post (1 060-1 410) — og er lagt om til samme komponentprofil som Standard, sum 1 210-1 790. Narrative Arc (1 350-1 500) la allerede inni og star urort; alle tre har na en eksplisitt sum-linje. Fila er den post.md:104 sender modellen til for «story structures», sa a sertifisere den som fikset med to odelagte skjeletter igjen ville vaert usant. SUPERSEDED og ikke gjeninnført: gammel B §S6 Del 2 pkt 1 (first-comment −5/−10 %-tall, pods-eskalering, 360Brew-fotnote). Verifisering: bånd-summen ligger inni målbåndet i alle seks kopier av standard-skjelettet og i alle fire skjelettene i engagement-frameworks.md (grep-bevis, 0 gjenværende 200-300/400-800) · D-6/D-7 omformulert (0 treff på «5,000+ followers» / «pinned by default» / «inbox + email») · alle ti suiter grønne, alle floors uendret: test-runner 270/0 (269 assertions >= floor 251) · trends 300/0 · analytics 202/0 · hooks 191/0 · brain 134/0 · editions 72/0 · render 63/0 · specifics-bank 45/0 · tests 35/0 · contract-gate 33/0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LhF1H7ctT5Fk8KkoCQpe5n
This commit is contained in:
parent
e7276cf8bb
commit
885526738c
9 changed files with 100 additions and 38 deletions
|
|
@ -6,18 +6,26 @@ LinkedIn Newsletters are a powerful tool for building an owned audience within L
|
|||
|
||||
## When to Launch Your Newsletter
|
||||
|
||||
### Minimum Thresholds
|
||||
### Not a platform gate — a readiness judgment
|
||||
|
||||
- **5,000+ followers** (ensures viable initial subscriber base)
|
||||
**LinkedIn imposes no follower minimum on individual members:** "All LinkedIn members have
|
||||
access to create a newsletter on LinkedIn" (LinkedIn Help, *Newsletters on LinkedIn FAQ*,
|
||||
a517914; company pages have separate access criteria). Everything below is an editorial
|
||||
readiness bar, not a requirement — you *can* launch at any size, the question is whether
|
||||
you should.
|
||||
|
||||
### Readiness signals
|
||||
|
||||
- **An audience large enough that a launch issue lands somewhere** — a few thousand
|
||||
followers is a common working floor, but it is a heuristic, not a threshold
|
||||
- **3+ months of consistent posting** (proven content discipline)
|
||||
- **Clear topical authority** (algorithm recognizes your expertise)
|
||||
- **Reliable content generation system** (can sustain weekly/biweekly publishing)
|
||||
|
||||
### Why Wait Until 5,000+
|
||||
### Why size matters at all
|
||||
|
||||
- Newsletter notifications go to all subscribers (empty newsletters damage credibility)
|
||||
- Every issue notifies every subscriber — thin editions damage credibility at any scale
|
||||
- Lower subscriber counts reduce perceived authority
|
||||
- Algorithm favors newsletters from established creators
|
||||
- Need sufficient content library to repurpose effectively
|
||||
|
||||
### Red Flags You're Not Ready
|
||||
|
|
@ -40,7 +48,11 @@ LinkedIn Newsletters are a powerful tool for building an owned audience within L
|
|||
|
||||
### LinkedIn Newsletters
|
||||
|
||||
- Direct notification to ALL subscribers (inbox + email notification)
|
||||
- Direct notification to ALL subscribers — but **not necessarily by email**: LinkedIn
|
||||
de-duplicates across channels, and "if you receive an in-app or push notification, you
|
||||
should not expect to also receive an email for the same notification" (LinkedIn Help,
|
||||
a517914). Treat the notification as the reliable channel and email as a bonus; do not
|
||||
plan an edition around inbox delivery
|
||||
- Owned audience (subscribers chose to be notified)
|
||||
- **Ideal for:** Deeper dives, comprehensive frameworks, email list building, monetization
|
||||
- Higher commitment from subscribers (they opted in)
|
||||
|
|
@ -278,7 +290,7 @@ When someone engages deeply on a topic:
|
|||
|
||||
| Mistake | Fix |
|
||||
|---------|-----|
|
||||
| Launching too early | Wait until 5,000+ followers and consistent posting habit |
|
||||
| Launching too early | Nothing on the platform stops you — wait for a consistent posting habit and an audience worth notifying |
|
||||
| Inconsistent publishing | Choose sustainable frequency and never skip |
|
||||
| Newsletter as dumping ground for post leftovers | Provide genuine additional value, not reposts |
|
||||
| Over-promoting newsletter in every post | Subtle mentions, maximum 1 per 5-7 posts |
|
||||
|
|
@ -289,4 +301,4 @@ When someone engages deeply on a topic:
|
|||
|
||||
## Bottom Line
|
||||
|
||||
Newsletters are powerful for building owned audience and deepening relationships, but only after establishing consistent posting and reaching 5,000+ followers. Quality and consistency matter more than frequency.
|
||||
Newsletters are powerful for building owned audience and deepening relationships. LinkedIn lets any member start one — the real gate is editorial: a consistent posting habit, a clear topic, and enough content capacity to sustain the cadence. Quality and consistency matter more than frequency.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue