rene/transceiver-db
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

blog: calibration v7 — remove Cause/Fix/Example labels, integrate as prose narrative

Browse Source
This commit is contained in:
Rene Fichtmueller 2026-04-01 00:10:50 +02:00
parent 6b77b18842
commit 52a04129e2
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
packages/api/src/llm/fo-blog-pipeline.ts
View File

@ -345,6 +345,13 @@ REMOVE:
- Perfectly symmetrical sections (same length = AI fingerprint)
- ALL markdown headers: ##, ###, ####, **Bold Section Title:** — strip every single one. Write plain text only.
- Repeated explanations: if cleaning, polarity, or power is in two sections, merge them into the first occurrence and remove the second.
- "Cause:" / "Fix:" / "Example:" labels — these are documentation format, not blog format. Integrate into prose.
BAD: "**Cause:** Mismatched firmware versions. **Fix:** Validate compatibility before deployment."
GOOD: "Firmware mismatches are rarely obvious. In one deployment, optics initialized cleanly but started flapping under load — the issue turned out to be a version mismatch between switch and transceiver firmware that only surfaced under realistic traffic."
- Repeated MMF→SMF transitions: if the cabling change is explained more than once, merge into one place.
- "fraught with hidden risks" or similar fear-selling language — replace with "introduces additional operational considerations"
- "When Not to Use" as a bullet list — integrate into prose: "In smaller environments or legacy MMF deployments, the overhead of validation and migration can outweigh the cost advantage."
- "Example:" as a standalone label before a quote — weave the example into the surrounding paragraph naturally.
REPLACE WITH:
- Natural, slightly imperfect flow
@ -488,7 +495,12 @@ CALIBRATION FAILS (auto-reject — fix before returning):
→ "$350 optic → $18,000 problem" must include: 2 engineers × 6h × $120/h = $1,440 troubleshooting, missed maintenance window = SLA penalty, customer escalation = business damage.
→ The number has to be traceable or it won't be believed.
28. HOOK PUNCH CHECK: Does the hook make the reader physically stop?
28. CAUSE/FIX/EXAMPLE LABELS (HARD FAIL): Search for "Cause:", "Fix:", "Example:" as standalone labels before explanations.
→ REMOVE ALL. Integrate into prose narrative.
→ BAD: "Cause: Firmware mismatch. Fix: Validate before deployment."
→ GOOD: "Firmware mismatches are rarely obvious. In one deployment, links started flapping under load — it turned out to be a version mismatch between switch and transceiver firmware that only surfaced under realistic traffic conditions."
29. HOOK PUNCH CHECK: Does the hook make the reader physically stop?
→ WEAK: "You're about to sign a PO for 400G optics."
→ STRONG: "You're about to spend $400,000 on optics. Here's how to accidentally turn it into a $2M problem."
→ If the hook lacks a concrete number or consequence, strengthen it.