Commit graph

3 commits

Author SHA1 Message Date
35ed480e5a refactor(linkedin-studio): S31a multiplier-scrub (reference-docs) — unsourced "Nx" reach/format multipliers -> SSOT
Hardening, multiplier class (S31, batch a). Surgical SSOT-reconciliation of
unsourced "Nx" reach/format/growth multipliers asserted as fact in 7 reference
docs. Same discipline as S27/S28/S30: read-and-show -> grep-confirm -> re-grep
final; 8-step interactive gate; operator-approved catalog before edit.

26 edits / 7 files (+32/-32):
- collaborations-guide (10): 10x reach (:3,:476), 2-3x normal (:32), and the six
  per-format "Reach multiplier: Nx" fields (:165/:187/:210/:235/:252/:277) +
  the label-only :292 (no number) folded in for consistency -> "Reach:" with
  directional, no-reliable-multiplier wording.
- linkedin-growth-playbook (10): 3x faster growth (:57/:132), 1.6x reach (:175),
  1.4x engagement (:205), 1.64x poll (:234), the format-multiplier list
  (:246-251 -> SSOT format ranking, numbers dropped), 3.6x respond (:386),
  3x engagements (:422), 5.6x follower growth (:493), 40x search (:636).
- poll-strategy-guide:7 (1.64x), articles-strategy-guide:28-29 (2-3x/10x),
  video-strategy-guide:308 (2-3x distribution), ab-testing-framework:49
  (1.17x-1.6x format multipliers), trajectory:40 (2-3x saves) + :85 (3x).

Vocabulary 1:1 with S30: "tend to / more reach (multiplier unverified)",
"no reliable multiplier", format ranking kept + number dropped -> cite SSOT.

KEPT INTACT: SSOT-backed engagement-order multipliers (save ~= 5x a like,
quality comment ~= 2x a like, ~= 1x baseline). OUT of scope (untouched):
frequency counts (5x5x5, Nx/week), pixel dims, pricing/size-ratio multipliers.

SURFACED -> S31c (descriptive-% subpass, not edited here): growth:58 (130%
follow), growth:177/178 (Buffer 178%/247%), trajectory:39 (30-40%). Flagged
as absolute-figure class outside S31: growth:421/423. Sourcing overclaim to
revisit: growth:492 "Official LinkedIn data".

VERIFY: re-grep residual targets in 7 files -> 0; routed siblings + KEEP intact;
gate scripts/test-runner.sh = 81/0/0 exit 0, counts 29/19/26 + v0.5.0 unchanged.

Push held: origin = open/ (public namespace), STATE.md must not go there;
parked arrow is all-or-nothing pending STATE-placement fix.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qgzo6rxthw7KuxHjn5vyE
2026-06-20 09:29:25 +02:00
ff52ec8577 fix(linkedin-studio): S22 harden outreach — add missing Bash grant, drop orphan WebFetch+Write, re-source fabricated pod/DM stats to SSOT
Outreach is the first command in the hardening queue that both delegates to an
agent (network-builder) and mutates real state (recordOutreachContact), so the
weight fell on axis-d. Five fixes across two files (operator-approved scope
extension to the SSOT-diverging guide source):

- allowed-tools: ADD Bash (Step 8c runs `node state-updater.mjs --record-outreach`
  and needs it — firsthour precedent grants Bash for the same pattern; the command
  promised a mutation it couldn't execute), DROP orphan WebFetch + Write grants
  (zero body use; :410/:1040 "Write a post" is prose). Now
  Read·Glob·WebSearch·AskUserQuestion·Task·Bash.
- Step 7 pod-warning (axis-b'): replaced fabricated magnitudes ("30-55% reach
  reduction", "shadow suppression", "credibility score", "penalizes",
  "Post-March 2025", "low dwell") with the SSOT statement
  (algorithm-signals-reference.md:98 — demote out of "Most Relevant" / scope to
  own network / restrict repeat offenders) + cite.
- :652 DM-amplification "2-3x first-hour" (axis-b'): re-attributed 2-3x to collab
  reach (where SSOT places it), kept the first-hour effect qualitative.
- collaborations-guide.md:349-370 (axis-b', scope extension): same SSOT rewrite of
  the "March 2025 Crackdown" section so the Step 7 fix can't be re-rendered from a
  stale reference (dropped "shadow banning ALL future content / 90+ days / 6+
  months / permanent penalty" + speculative detection methods).

Verify: re-grep both files clean (orphans/fabricated stats NONE, Bash :21, SSOT
text in place); recordOutreachContact throwaway-fixture 10/10 PASS (additive,
$-safe, newest-first, untouched undeclared fields); test-runner 81/0/0 exit 0;
counts 29/19 unchanged (.md-only).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qgzo6rxthw7KuxHjn5vyE
2026-06-19 20:33:30 +02:00
Kjell Tore Guttormsen
40986575b6 feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command
Add /ultraresearch-local for structured research combining local codebase
analysis with external knowledge via parallel agent swarms. Produces research
briefs with triangulation, confidence ratings, and source quality assessment.

New command: /ultraresearch-local with modes --quick, --local, --external, --fg.
New agents: research-orchestrator (opus), docs-researcher, community-researcher,
security-researcher, contrarian-researcher, gemini-bridge (all sonnet).
New template: research-brief-template.md.

Integration: --research flag in /ultraplan-local accepts pre-built research
briefs (up to 3), enriches the interview and exploration phases. Planning
orchestrator cross-references brief findings during synthesis.

Design principle: Context Engineering — right information to right agent at
right time. Research briefs are structured artifacts in the pipeline:
ultraresearch → brief → ultraplan --research → plan → ultraexecute.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-08 08:58:35 +02:00