Step 3 of 4 · Stage 04
Generate & Verify
Not the same as Remediate
Remediate fixes what's wrong in your own sources — this is internal, knowledge-base work. It's separate from Verify in Step 3, which is the external, human sign-off before anything goes public.
Pick a gap from step 2 and draft the page that closes it. Generation reads only your context layer, so the draft can assert nothing your sources do not support, and every claim in it is traced back to a document id before a person signs it off.
- Pick a gap to closestep 2 produced the list
- Generate a draftwritten only from your own sources
- Save it for reviewnothing goes out at this stage
- See what needs reviewdrafts wait here until a person approves
Produces a verified draft.
How to run it
| Step | API call | Why it matters |
|---|---|---|
| Pick a gap to close | Judgement, not a call | Step 2 produced the list of gaps; work from it. A draft with no gap behind it is a page nobody asked for, and nothing in step 4 can tell you whether it did anything. |
| Generate a draft | POST/org | Drafts one piece from your context layer, shaped by a content type. Generation reads only your own sources, so the draft can assert nothing they do not support — an unsupported claim is a missing source, not a writing problem. |
| Save it for review | POST/org | Stores the draft for review without publishing anything outward. Shipping happens in step 4 and needs a person to sign off first. |
| See what needs review | GET/org | Lists every draft waiting on a reviewer. This is a queue a person works: nothing leaves it on a score alone, however confident the claim gate is. |
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.
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 →This step gets you the first two: checked, and signed off. It becomes a Verified Source when step 4 publishes it, and that is also where the receipt is written.
Status
The automated claim gate, receipts and provenance are not in the published API yet. Drafting and review listing work today.
How to reach it
/org/content-generation/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.The CLI wraps these as senso engine draft.
Rules for this step
- Drafting is not publishing. An agent prepares up to the gate and stops there.
- Every draft starts from a gap step 2 named. No gap, no draft.
- 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 or a log.
Done when
- The work started from a named gap
- The draft says only what your sources support
- Every claim has a verdict, and the unresolved ones are visible
- A person has signed it off, and is recorded as having done so