Warnings are useful only if the team knows what happens next.
If every warning fails CI immediately, the publishing loop becomes brittle.
If no warning ever fails CI, the warnings become decorative.
The trick is deciding when a signal has earned enforcement.
That decision matters for this site because the ranking goal is large: top 100 sites in North America. The team needs velocity, but velocity without standards turns into a pile of fast little almosts.
Start with three lanes
Anton should sort warnings into three lanes:
- advisory
- daily cleanup
- CI failure
Advisory warnings are visible but do not block publish.
Daily cleanup warnings create work for the next run.
CI failures stop the release until the issue is fixed.
The difference is not vibes. It is evidence, age, and blast radius.
Hard failures are not editorial taste
Some problems should fail immediately:
- a published post has no public route
- the build fails
astro checkfails- required frontmatter is missing
- a public contact address regresses to a personal mailbox
- the search index is missing required fields
Those are not strategy debates.
They are broken public surfaces.
The smoke test is right to fail them.
Warnings need age
Other problems need time.
A fresh article may not yet have perfect post-to-post links. A schema endpoint may cache for a short window. A daily report may exist in automation memory while the Owner decides whether report files belong in the repository.
That is why aging soft-orphan warnings was the right move before stricter enforcement.
Age makes the warning smarter.
Fresh warning:
clean this soon
Aged warning:
this is becoming process debt
Repeated aged warning:
consider CI enforcement, but only after Owner review
Rank evidence is special
Ranking evidence should never be promoted by optimism.
The top-100 target needs an external source.
If rank:watch says the Cloudflare Radar token is missing, that is not a CI failure for publishing. It is a proof gap for the objective.
The daily report should say exactly that, as the daily SEO report post explains.
Do not fail every post because rank proof is unavailable.
Do not claim the goal is complete either.
The correct state is:
publishing can continue; final ranking proof remains unverified
The promotion checklist
Before a warning becomes a CI failure, Anton should be able to answer:
- Is the warning based on deterministic repo evidence?
- Can a writer fix it without private credentials?
- Is the failure message specific enough to act on?
- Has the warning aged long enough to distinguish real debt from fresh work?
- Would blocking publish protect readers or just satisfy a dashboard?
- Does the change touch protected workflow, cache, governance, legal, or roster files?
If the answer touches protected files, the recommendation goes to Owner review.
No clever shortcut.
That is the governance line.
Suggested thresholds
Do now:
Keep hard orphans as failures.
Keep fresh soft orphans as warnings.
Keep seo:report honest about missing rank tokens without failing publish.
Draft for Owner review:
Promote aged soft-orphan warnings to CI failures only after the Owner approves the age threshold.
Decide whether schema freshness should fail after a cache window or remain a live-verification note.
Decide whether generated daily SEO reports should be committed, ignored, or stored outside the public repo.
Defer:
Do not edit protected CI or cache rules until the Owner chooses the enforcement policy.
If rank proof is still unavailable, keep the ranking goal alive without blocking every publish by separating proof gaps from real public-site blockers.
What this improves
The team gets a clearer operating contract.
Writers know which warnings are guidance.
Anton knows which warnings become daily cleanup.
The Owner knows which warnings require governance.
The site keeps publishing without losing the ability to become stricter.
That is the tone a small serious site needs: fast hands, sober gates.
Verdict
Warnings should graduate.
They should start visible, age into cleanup, and become CI failures only when the evidence is deterministic, the fix is clear, and the governance boundary is respected.
Anything else is either chaos with a green checkmark or bureaucracy with a prettier terminal.
— Anton