Module 3 of 4 · Stages 04–05
Verify & Publish
Objective
Close one gap: turn cleaned context into a page whose every claim traces to a source, and ship it where agents can read it.
Deliberate, on demand after approval · Produces a published Verified Source and its receipt · Usually marketing
In the loop
Verification is the gate: every claim traces back to a document you own, or it does not ship. Publishing is what makes the result reachable by an agent rather than only by you.
| Do this | Call | Why |
|---|---|---|
| Draft first, publish second | POST /org/content-engine/draft | Saves without shipping anything outward. |
| Read what is waiting for review | GET /org/content/verification | The queue a person works. Nothing leaves it on a score alone. |
| Publish once a person has signed off | POST /org/content-engine/publish | Needs a tracked question id, which module 2 produces. A brand-new org has none. |
| Approve anything going outward | A human decision, not a score. An agent can gather evidence and recommend; it cannot sign off. |
Stage 04 — Verify
- 1Pick one gap to close.A question where you are absent, out-cited or out of date. Not "write us a blog post".
- 2Choose the smallest repair that fixes it.Usually a passage or a section, not a new page.
- 3Generate the draft from your context.It can only say what your sources support.
- 4Run the gate.Each claim is checked against a human-verified source. Only failures and close calls come back to you.
- 5Resolve what the gate flagged.Unsupported claims stay visible as gaps. They are not hidden or dropped.Requires a human
Every claim ends as supported, corrected, unresolved or not applicable. None disappear.
Stage 05 — Publish
- 1Choose the destination.Your own site, a Senso agent-readable destination, or both.
- 2Approve the publish.Explicitly, every time. Not inferred from the draft being approved.Requires a human
- 3Keep the receipt.It is how you prove later what was checked and who signed off.
On a brand-new organization
Publishing requires the id of a tracked question. A fresh organization has none, so add at least one in module 2 before this call can succeed.
Which repair to choose
Refresh a page
Right in shape, wrong in detail.
Replace a section
One part has gone stale.
Add a passage
The page is nearly complete.
Update from the catalog
The catalog moved and the page did not.
Republish
The source of record changed.
Write a new page
Nothing suitable exists to repair.
Refreshing a passage beats writing a page nobody asked for.
What you are making
Verified Source
A page whose claims were each checked against a source of record, signed off by an accountable owner, and published so any answer built from it can be traced back. Anything that has not been through the gate is content, not a Verified Source.
Full definition →Receipt
Portable proof the check happened. It records what was examined, what the evidence was, who approved it, and where it went.
Full definition →A receipt records:
- Receipt id, organization, and what it is about
- Content version, and every claim that was checked
- The evidence behind each claim, and its result
- Who reviewed it, and when it was verified and published
- Destination, published URL, and whether provenance is complete
Status
The automated claim gate, receipts and provenance are not in the published API yet. Drafting, review listing and publishing work today.
How to reach it
/org/generate/sampleOpen in API reference →Draft one piece from your context, shaped by a content type./org/content-engine/draftOpen in API reference →Save the draft for review instead of publishing it./org/content-engine/publishOpen in API reference →Publish verified content to your configured destinations./org/destinationsOpen in API reference →List where you can publish, with live counts per destination.The CLI wraps these as senso engine draft and senso engine publish.
Rules for this module
- Drafting is not publishing. An agent prepares up to the gate and stops.
- Publication is always human-authorized. Nothing ships on model output alone.
- A price, policy, eligibility or compliance claim that cannot be supported blocks the ship.
- When blocked, name the missing evidence and ask for a source or a person. Do not soften the claim to get past the gate.
- Never put credentials or customer data in a draft, a log, or a receipt.
Done when
- The work started from a named gap
- Every claim has a verdict, and the unresolved ones are visible
- There is a live URL, approved by a person who is recorded as having approved it
- The receipt is retrievable