We do not hand you a plan and wish you luck. We write the content.
Production is a full content operation, not a recommendations deck. We draft, edit, source, and ship complete units against the approved build sheet in two-week sprints down the priority stack: long-form pages, definitional blocks, comparative verdicts, explainer posts, third-party placements, review programs, and structured product feeds. Every unit is written in your voice, engineered to survive extraction, and routed to the surface where that theme's citations demonstrably live.
Produce is the fourth phase of the Citabld method. Citabld writes the content on the approved build sheet: pages, definitional blocks, and comparisons. Each piece is drafted answer-first, checked against the client's Voice Card, passed through a fourteen-point quality review, and published on the surface where AI engines already cite sources for that topic.
What do you actually produce?
Finished, publishable units at full depth. A priority theme does not become a bullet in a spreadsheet; it becomes a page, and the page is written by us end to end, with the research, the sourcing, and the structure done before anything is styled.
- /Long-form pillar pages covering a theme cluster at full depth, structured block by block for extraction.
- /Definitional blocks of 40 to 60 words, entity-named and standalone, that engines can lift without context.
- /Comparative pages with honest verdicts, including where a competitor is the better fit.
- /Explainer and research posts carrying original information rather than restated consensus.
- /Third-party placements and review programs for themes whose citations do not live on your domain.
- /Structured product feed records and trust fields for shopping fan-outs, where prose does not answer the query at all.
How do you keep it in our voice?
We build a Voice Card from 8 to 12 samples of your actual writing: sentence rhythm, vocabulary, the claims you are willing to make, and the ones you are not. Every unit passes a voice check against that card. Our voice never appears in client content, which is the whole point of collecting the samples before the first sprint.
We do not hand you a plan and wish you luck. We write the content.
Every unit passes a fourteen-point quality gate and your voice standard before it ships, and lands on the surface where the citations for that query actually live.
What is the quality gate?
A gated chain every unit moves through before it can ship. Nothing is published on the strength of a draft looking finished.
| gate | requirement |
|---|---|
| brief | a written information-gain declaration: what this unit carries that no competing passage carries |
| extractable core | the correct, sourced answer drafted before any styling or narrative |
| voice pass | checked against the client's Voice Card, not ours |
| quality rubric | fourteen points, hard ship gate, failures return to draft |
| placement routing | published to the surface where this theme's citations actually live |
How is the content engineered for extraction?
The unit of retrieval is the passage, so we build passages. Fact-bearing blocks run roughly 40 to 60 words inside the measured optimal retrieval band, the answer sits in the first sentence, the entity is named inside the block, one topic per block, and claims carry dates. Measured tactics are applied at drafting level rather than as a retrofit pass, because bolted-on optimization underperforms substantive writing.
What lifts extraction
Statistics with linked sources, attributable quotations, and named entities inside the block all measurably raise the odds a passage is chosen.
What lowers it
Keyword stuffing measurably hurts, and hidden content behind tabs and accordions extracts poorly, so definitional blocks are never collapsed.
What is the Citabld Composition Calculus?
The Citabld Composition Calculus (CCC) is the content-side twin of the Decomposition Calculus. Where the CDC derives what an engine will ask, the CCC derives the passage that wins when it asks. The insight it is built on: content is not written for the fragment, it is written for the selection event. When an engine retrieves, it holds several candidate passages at once and synthesis chooses among them, so every unit is composed to win that choice: answer first, entity named in-block, evidence installed, scope stated, and one selection axis it dominates outright against the incumbents already being cited.
Conjugate to the library
Every fragment in the library records how it was derived, and each derivation move has a mirror composition move that answers it. The library row is the writing instruction, which is why production is mechanical rather than a matter of taste.
Retrieved but not cited has a fix
The most common failure state is a passage that gets retrieved and passed over. That is a composition failure with defined causes, and the CCC names them: no dominance axis, diluted blocks, missing evidence, unbounded claims.
How do we know it worked?
The library doubles as the tracked-prompt inventory, so every shipped unit reports back with one of three outcomes, and each has a defined fix. Decision-stage themes can move in weeks. Awareness-stage influence works on the models' trained picture and moves on quarterly timescales, and we tell you which is which before you spend.
| outcome | fix |
|---|---|
| retrieved and cited | reinforce the theme and expand adjacent fragments |
| retrieved but passed over | the passage lost on substance; raise information gain and extractability |
| never retrieved | wrong surface or wrong fragment; reroute placement or regenerate the theme |
See this phase run on one of your own head queries, free.
Six questions, one modeled fan-out across seven engines, and one finished piece of content for the subquery you pick.