How this documentation is generated

1Trigger: merge to master

A GitHub Action fires on every push to master. It checks out the merge commit and its parent, and collects three inputs:

• The pull request title, body and file list
• The committed openapi-external.json at both commits
• The repository's disclosure policy file

# .github/workflows/continuous-docs.yml
on:
  push:
    branches: [master]
jobs:
  docs:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with: { fetch-depth: 2 }
      - run: npx continuous-docs run --base HEAD~1 --head HEAD

Nothing has been judged yet. This step only gathers evidence.

2Relevance filter: did anything observable change?

This is the component that makes the pipeline trustworthy. It answers one question per surface.

For the API surface the answer is deterministic. The external spec is generated from code and CI fails if it drifts, so a structural diff of the two committed versions is the customer-visible API changelog.

 "paths": {
   "/v1/workflows/{id}/steps": {
     "post": {
       "requestBody": { "schema": { "properties": {
         "type":          { "type": "string", "enum": ["document", "selfie", "aml"] },
+        "livenessCheck": { "type": "boolean", "default": false,
+                           "description": "Require an active liveness check on the selfie step." },

One added property. Nothing removed, nothing renamed. Classified as additive, non-breaking.

For everything else the answer is a judgment call, so an LLM reads the PR and the file list with the disclosure policy in its context, and returns a structured verdict rather than prose:

{
  "observable": true,
  "reasons": [
    "New public request field `livenessCheck` on workflow steps",
    "Document recognition coverage expanded (vendor SDK upgrade)"
  ],
  "ignored": [
    "src/repositories/** refactor: no behavioural change, no public surface"
  ],
  "affectedPages": ["knowledge-base/workflows/configuring-steps.md"],
  "confidence": 0.86
}

3Tier 1: API reference, generated from a template

The API reference page for this endpoint is regenerated directly from the external spec. No language model is involved, so this tier is safe to auto-merge.

The page carries front matter that records its provenance, so the site can show a "generated from spec" badge and a reviewer can trace it back to a commit:

---
title: Create a workflow step
generated_by: continuous-docs
tier: 1
source: id-verification-service/openapi-external.json
source_commit: 9f3c1a7
---

4Tier 2: changelog entry, LLM prose over a structured diff

The same spec diff, plus the filter's structured verdict, is handed to a model with one instruction: write a customer-facing changelog entry. The disclosure policy is applied before the text is written, not scrubbed afterwards.

# .continuous-docs/policy.yml (id-verification-service)
disclosure:
  never_name:
    - Microblink
    - BlinkID
    - Regula
    - Hopae
    - IDRnD
    - EyeDP
  internal_only_concepts:
    - "fraud score thresholds"
    - "internal queue names"

Notice the second bullet. The merge upgraded a named vendor SDK; the entry says what the customer gains and names nobody. The same redaction already holds on the API surface, where the external spec contains zero mentions of any vendor. This tier gets a light review because the facts came from the diff and only the wording came from the model.

5Tier 3: knowledge-base draft, mandatory human review

The filter identified one conceptual page that now describes the product incompletely. The model is given the current page, the diff, the verdict and the policy, and asked to propose the smallest edit that makes the page true again.

6Output: one pull request against this docs repository

All three tiers land in a single pull request against the docs site. Its body is generated too, and it is written for the reviewer rather than the customer.

## Docs update for id-verification-service#1284 — "Admin release 2026.09"

**Detected (customer-visible)**
- Additive API change: `livenessCheck` on POST /v1/workflows/{id}/steps
- Expanded document recognition coverage (vendor name redacted per policy)

**Ignored (not customer-visible)**
- Repository layer refactor under src/repositories/** — no public surface

**Changes in this PR**
| File | Tier | Gate | Confidence |
|---|---|---|---|
| api-reference/workflows/create-step.md | 1 | auto | — |
| changelog/2026-09.md | 2 | light review | 0.91 |
| knowledge-base/workflows/configuring-steps.md | 3 | **required** | 0.86 |

Source commit: id-verification-service@9f3c1a7

The reviewer approves. The site rebuilds. The page you are reading renders the updated Markdown, and the raw .md file is served at a predictable URL so the next coding agent that integrates SEON reads the truth as of the last merge.