← Back to reports library

Editorial depth standards for Zeph Tech briefs

Zeph Tech briefs must provide enough depth that operators can brief executives and execution teams without chasing additional sources. Editors should verify every new entry in zephtech-site/content/feed/ against the depth controls below before submitting a…

Editorial Standards · Coverage focus 2025 · Updated November 14, 2025

Zeph Tech briefs must provide enough depth that operators can brief executives and execution teams without chasing additional sources. Editors should verify every new entry in zephtech-site/content/feed/ against the depth controls below before submitting a pull request.

Depth thresholds

Requirement Minimum Notes
Word count (word_count) 240 words Count after templating; automatic checks read the stored word_count field.
Structured sections (<h3> headings) At least three Organise the narrative across execution priorities (e.g., compliance checkpoints, operational moves, enablement).
Source citations (sources) Two or more Link to official regulations, vendor notices, or authoritative research—no press summaries or secondary commentary.

Failing any requirement blocks CI. Use the headings to distribute detail evenly; avoid dumping long paragraphs under a single section.

Validation workflow

Run the validator locally whenever you update or add feed content:

python scripts/check_brief_depth.py --baseline scripts/tests/fixtures/feed_depth_baseline.json
        

The command prints any failing slugs and exits with a non-zero status when a brief breaks the thresholds. The baseline file tracks historical briefs that still need rewriting; do not add new slugs to the baseline. Instead, expand the brief until it meets the standard and remove the slug from the baseline once the content passes. CI will also fail if a slug remains in the baseline but now satisfies the checks—this nudge keeps the backlog up to date.

Source expectations

  • Citations must point to first-party or regulatory material that fully supports the claims in the brief.
  • Summaries should include specific regulatory deadlines, enforcement expectations, or engineering tasks readers can action immediately.
  • When referencing enforcement policies, confirm the effective dates and scope in the primary source before publishing.

Aligning with these thresholds keeps nightly briefings “longer, more in-depth, and unique” so leadership can act on them without additional research.