The part that is supposed to be uncomfortable

The refusal log

Pages this system declined to write, each with the material it was missing and what would unblock it. Publishing these is not humility. It is the only claim about grounding that a system which publishes everything cannot make.

Why a refusal is a feature

Every competitor in this category sells volume. The constraint is the product.

The rule

Below a material-sufficiency threshold, generation is refused and the reason is stated. A three-page brochure site gets a gap report and an honest "there is nothing here to transmute yet."

The threshold is computed from the count and type-mix of claims available to ground the target page — not from a model's opinion about whether it could write something plausible. It almost always could. That is the problem.

alkeyword.com/docs/spec/README.md §3.2

The failure mode this guards

Relaxing the refusal rule under revenue pressure is the single change that turns this into the segment it differentiates from — the one that sells "30+ articles a month" straight into a scaled-content-abuse penalty.

Which is why the log is a public page and not an internal metric. A quietly-lowered threshold is invisible. A refusal log that stops getting entries is not.

The log

Ordered by how close each is to being mintable.

Form · comparison

box-and-box vs. policy engines

REFUSED — material insufficient

The site names alternatives in passing but states almost nothing measurable about them. Writing this page would mean inventing the other side of every row.

shared attribute claims3/6
quantity claims4/2
entities compared2/2

To unblock: three more attribute claims about a named alternative. Publish them anywhere on the site and this becomes mintable.

Form · how-it-works

How a SkillBundle is verified

REFUSED — no ordered process claims

The six gates are documented individually and the schema is public, but nowhere does the corpus state the verification sequence as ordered steps. The page would have to infer an order — which is exactly the kind of plausible invention the provenance validator exists to catch.

ordered process steps0/3
process claims0/1

To unblock: one document stating the gate order as steps. This is a documentation gap the refusal just located — the cheapest kind of finding.

Form · FAQ

Frequently asked: the [&] protocol stack

REFUSED — no question claims anywhere in the corpus

Zero of twenty surfaces contain a single FAQ. There are no questions on record to answer, so any FAQ would be questions we imagined being asked — the least grounded page type it is possible to generate.

question claims0/5

To unblock: real questions. Support threads, a B1 debrief, anything someone actually asked. This is why B1 is scheduled before content generation, not after.

Form · statistics

The stack in numbers

HELD — mintable, awaiting a contradiction fix

Material is sufficient. Generation is held because the corpus states its own law count two different ways — 103 in four prominent places, 116 once and buried. Minting a statistics page on top of an unresolved contradiction would propagate it with better formatting.

quantity claims with units32/5
unresolved contradictions1

To unblock: resolve 103 vs 116 at the source. Zero generation cost — the fix is a sentence, and it is worth more than the page.

Standing count

If this stops moving, the rule stopped being enforced.

Refused this cycle
3
Held for a source fix
1
Published this cycle
0
Cap per cycle
6 pieces

The cap is a product constraint, not a pricing tier to be upsold away. Six pieces that close six measured gaps — never thirty articles a month. Three of the four entries above are documentation gaps in our own corpus, which is the refusal rule doing its second job: it finds what the writing would have papered over.