---
title: "StackShift II: the Canon-first model for consistent pages"
description: "StackShift II publishes from a store of verified claims, so every page, feed and AI-facing document regenerates from the same approved source."
canonical: https://stackshift-ii.vercel.app/ss2-acceptance-probe-2026-09-18
source_origin: "Service-as-Software-2026.pdf"
source_kind: upload
source_retrieved_at: 2026-08-13T19:59:48.640876+00:00
license: "owned by WebriQ"
design_system: webriq-v2
composition: 5781bce2-fb25-45ec-a0c1-4e3e8f96740e v2
compiled_by: stackshift-ii-compiler/2
published_at: 2026-09-18T11:20:10.902Z
first_published_at: 2026-09-18T11:20:10.902Z
claims: 21
---

# StackShift II keeps every published page consistent with approved knowledge

The claim is the durable unit, held once and bound to the entity it concerns. Every page, feed and machine-readable document is a composition assembled from approved claims, and regenerated when one of them changes.

**Highlights:** Durable unit: The individual verified claim [^1] · When a fact changes: Update the claim once; every bound composition regenerates automatically [^2] · Ownership boundaries: Enforced: product system owns product truth, Canon owns claim truth, engine reads both, writes neither [^3]

[Book a call](/contact)

## Three waves of publishing, one unit that never moved

Philippe Bodart traces three waves of web publishing — the traditional CMS, headless, and composable architecture. Each wave improved how content was delivered, and each left the organising unit exactly where it had been: the page, or a content entry shaped like one.

The Canon-first model moves the durable unit down a level, to the canonical claim. What a business governs is no longer a page but the individual verifiable claim, held exactly once, bound to the entity it concerns. The Canon holds every claim a business is willing to stand behind, spanning multiple subjects, and it is organised by the entities each claim concerns rather than by which page a claim happens to sit on.

Compositions are then assembled from approved claims: pages, feeds and documents written for machines as well as for people. The build engine that produces them is architecturally forbidden from having editorial authority — it only assembles and publishes. Ownership is enforced in the same spirit: the product system owns product truth, the Canon owns claim truth, and the engine reads both and writes neither.

Consistency follows from that arrangement. When a fact changes, the claim is updated once and every bound composition regenerates automatically. Because the durable asset is the claim rather than the page, migration and replatform cost is near-zero for that asset — the pages themselves are disposable and regenerable.

- organizes around: the page, or a content entry shaped like one [^4]
- stayed: the page, or a content entry structured like one [^5]
- durable governed unit: the individual verifiable claim — not the page [^6]
- durable_unit: individual verified claim [^7]
- moves durable unit down to: canonical claim [^8]
- Where a fact lives: Exactly once, bound to the entity it concerns [^9]
- scope: holds every claim a business is willing to stand behind, spanning multiple subjects [^10]
- organization_scheme: by the entities each claim concerns rather than by which page it happens to sit on [^11]
- Editorial authority: The build engine is architecturally forbidden from having editorial authority; it only assembles and publishes [^12]
- Ownership boundaries: Enforced: product system owns product truth, Canon owns claim truth, engine reads both, writes neither [^3]
- When a fact changes: Update the claim once; every bound composition regenerates automatically [^2]
- Migration / replatform cost: Near-zero for the durable asset — pages are disposable and regenerable [^13]

## What changes in practice

### Two generations, one decision

StackShift I is Managed Presence: WebriQ operates everything so the customer can focus on running their business. StackShift II is Compounding Authority: the customer directs, the AI executes, and WebriQ governs the platform.

### A weekly review queue

In StackShift II, customers direct progress through a weekly review queue while an AI visibility engine surfaces content gaps. Dual-track publishing serves humans and machines from one source, and a semantic knowledge graph powers a continuous, self-improving visibility loop. PipelineForge arrives as an integrated platform module. It suits teams with content ambitions and at least one person who can engage with a review queue weekly.

- target_audience: Teams with content ambitions and at least one person who can engage with a review queue weekly. [^14]
- publishing_cadence: Publishing is continuous, not episodic [^15]
- publishing_model: Dual-track publishing: human + machine from same source [^16]

### The durable unit is the claim

The durable unit shifts from pages to canonical claims — verifiable statements carrying their own source, confidence and validity. Product truth is copied from existing systems and never overwritten, while all other content is read and separated into individually sourced claims. New claims require human approval, and pages, FAQs, feeds and machine-readable documents are compositions assembled from approved claims.

- Where a fact lives: Exactly once, bound to the entity it concerns [^9]
- When a fact changes: Update the claim once; every bound composition regenerates automatically [^2]

### Enforced ownership

Enforced: product system owns product truth, Canon owns claim truth, engine reads both, writes neither [^3]

- Editorial authority: The build engine is architecturally forbidden from having editorial authority; it only assembles and publishes [^12]
- risk_mitigation_ai_hallucination: Human-in-the-loop review built into CiteForge and PublishForge ensures AI-generated content is validated before publishing. [^17]
- governance_features: Versioning, roles, and one-click toggles keep every asset governed. [^18]

## Canon-first and StackShift II, claim by claim

### Canon-first (product)

| Claim | Value | Valid | Ref |
|---|---|---|---|
| Durable unit | The individual verified claim | — | [^1] |
| Editorial authority | The build engine is architecturally forbidden from having editorial authority; it only assembles and publishes | — | [^12] |
| Migration / replatform cost | Near-zero for the durable asset — pages are disposable and regenerable | — | [^13] |
| Ownership boundaries | Enforced: product system owns product truth, Canon owns claim truth, engine reads both, writes neither | — | [^3] |
| When a fact changes | Update the claim once; every bound composition regenerates automatically | — | [^2] |
| Where a fact lives | Exactly once, bound to the entity it concerns | — | [^9] |

### Canon-first model (other)

| Claim | Value | Valid | Ref |
|---|---|---|---|
| durable governed unit | the individual verifiable claim — not the page | — | [^6] |

### StackShift II (product)

| Claim | Value | Valid | Ref |
|---|---|---|---|
| description | Your expertise, continuously published. Found by buyers, and by AI. | — | [^20] |
| generation_status | StackShift II is the AI-native generation, built for a buyer who is ready to operate at a different level of engagement and ambition. | — | [^19] |
| positioning_label | Compounding Authority | — | [^21] |
| publishing_cadence | Publishing is continuous, not episodic | — | [^15] |
| publishing_model | Dual-track publishing: human + machine from same source | — | [^16] |
| target_audience | Teams with content ambitions and at least one person who can engage with a review queue weekly. | — | [^14] |

### The Canon (product)

| Claim | Value | Valid | Ref |
|---|---|---|---|
| organization_scheme | by the entities each claim concerns rather than by which page it happens to sit on | — | [^11] |
| scope | holds every claim a business is willing to stand behind, spanning multiple subjects | — | [^10] |

## Questions the model raises

### Where does a fact live in a Canon-first model?

Exactly once, bound to the entity it concerns

### What happens when a fact changes?

Update the claim once; every bound composition regenerates automatically

### Who holds editorial authority?

The build engine is architecturally forbidden from having editorial authority; it only assembles and publishes

### How is AI-generated content checked before it publishes?

Human-in-the-loop review built into CiteForge and PublishForge ensures AI-generated content is validated before publishing.

## Find out which generation fits your team

Start with the claims your business already stands behind, and the compositions that should follow from them.

[Book a call](/contact)

---

Provenance: 21 verified claims from "Service-as-Software-2026.pdf" (retrieved 2026-08-13).

## Claim register

[^1]: `9ff84875-541c-4b06-9cd6-5690bbb48b61` — Canon-first · Durable unit = The individual verified claim — "| Durable unit | The page — content and presentation fused | The content entry — still shaped like a page | The individual verified claim |"
[^2]: `50a2b815-9c16-4458-93ed-b9df6fa23931` — Canon-first · When a fact changes = Update the claim once; every bound composition regenerates automatically — "| When a fact changes | Manual find-and-replace across every page that has it | Manual update per entry — nothing tells you which entries hold copies | Update the claim once; every bound composition regenerates automatically |"
[^3]: `73d06058-0709-464e-b18f-fb6bf19dbe48` — Canon-first · Ownership boundaries = Enforced: product system owns product truth, Canon owns claim truth, engine reads both, writes neither — "| Ownership boundaries | Blurred — dev, marketing, product often edit the same system | Cleaner content/front-end split, but product data is often re-entered or synced and can drift | Enforced: product system owns product truth, Canon owns claim truth, engine reads both, writes neither |"
[^4]: `a21a28e2-bdfd-4625-8bdf-6df5a6751e68` — Web publishing industry · organizes around = the page, or a content entry shaped like one — "the actual unit the industry organizes around: the page, or a content entry shaped like one"
[^5]: `98d5f74f-fbe8-4ca9-ac2c-90851a9045e0` — Organizing unit · stayed = the page, or a content entry structured like one — "the organizing unit stayed the page, or a content entry structured like one"
[^6]: `78f2d5ad-4c07-4948-8f62-2a21c86bebc1` — Canon-first model · durable governed unit = the individual verifiable claim — not the page — "where the durable, governed unit is the individual verifiable claim — not the page"
[^7]: `7f894896-a61f-4bbc-99c5-2d091085d098` — canon-first · durable_unit = individual verified claim — "That gap is what canon-first closes, by changing what the durable unit is: not the page, not the content entry, but the individual verified claim."
[^8]: `a87ebd69-c7af-4faf-9cac-b3ea5aa9eb38` — Canon-first model · moves durable unit down to = canonical claim — "A Canon-first model moves that durable unit down to the **canonical claim**"
[^9]: `61f45fb4-9a8b-493a-82cc-e82be633a8d5` — Canon-first · Where a fact lives = Exactly once, bound to the entity it concerns — "| Where a fact lives | Hand-typed into every page/template that mentions it | Structured, but usually duplicated across separate entries | Exactly once, bound to the entity it concerns |"
[^10]: `de3e19b7-c76b-4a4d-ad54-1f9c1a3d7dfa` — The Canon · scope = holds every claim a business is willing to stand behind, spanning multiple subjects — "The Canon isn’t limited to one subject — it holds every claim a business is willing to stand behind, organized by the entities each claim concerns rather than by which page it happens to sit on."
[^11]: `8169b448-fe08-465d-a27f-0a97b58633a1` — The Canon · organization_scheme = by the entities each claim concerns rather than by which page it happens to sit on — "organized by the entities each claim concerns rather than by which page it happens to sit on"
[^12]: `b3c40d28-0524-4a4c-b5e6-faa40cf392d9` — Canon-first · Editorial authority = The build engine is architecturally forbidden from having editorial authority; it only assembles and publishes — "| Editorial authority | Requires developer involvement to fix a fact baked into a template | Editors edit entries, but the CMS itself holds unaudited authority — a database with permissions | The build engine is architecturally forbidden from having editorial authority; it only assembles and publishes |"
[^13]: `c2bb6c4f-0743-42e6-bf39-7913b7da841a` — Canon-first · Migration / replatform cost = Near-zero for the durable asset — pages are disposable and regenerable — "| Migration / replatform cost | High — content re-authored to fit new templates | Lower — front end decouples, but the content model still mirrors the old site's structure | Near-zero for the durable asset — pages are disposable and regenerable |"
[^14]: `7b315381-8598-452f-8c55-33906a088d22` — StackShift II · target_audience = Teams with content ambitions and at least one person who can engage with a review queue weekly. — "Teams with content ambitions and at least one person who can engage with a review queue weekly."
[^15]: `4012654d-5c29-4820-a097-116f2708357c` — StackShift II · publishing_cadence = Publishing is continuous, not episodic — "Publishing is continuous, not episodic."
[^16]: `cc06f0b2-53ed-4d4f-bbb7-48206acd1f46` — StackShift II · publishing_model = Dual-track publishing: human + machine from same source — "Dual-track publishing: human + machine from same source"
[^17]: `2b34e7e5-a329-40d3-af62-4bf43dace536` — CiteForge and PublishForge · risk_mitigation_ai_hallucination = Human-in-the-loop review built into CiteForge and PublishForge ensures AI-generated content is validated before publishing. — "Human-in-the-loop review built into CiteForge and PublishForge ensures AI-generated content is validated before publishing."
[^18]: `061fbbcc-8a5d-47f0-a4ac-a9b71d475f9e` — PublishForge · governance_features = Versioning, roles, and one-click toggles keep every asset governed. — "Versioning, roles, and one-click toggles keep every asset governed."
[^19]: `6667a1f9-1aa7-4a5c-8ba0-e949bc9e82a6` — StackShift II · generation_status = StackShift II is the AI-native generation, built for a buyer who is ready to operate at a different level of engagement and ambition. — "StackShift II is the AI-native generation, built for a buyer who is ready to operate at a different level of engagement and ambition."
[^20]: `951fd3f0-50da-40c0-988a-20db1aae0e16` — StackShift II · description = Your expertise, continuously published. Found by buyers, and by AI. — "Your expertise, continuously published. Found by buyers, and by AI."
[^21]: `afe48536-ec4e-42b6-96c7-a6a87c0ba970` — StackShift II · positioning_label = Compounding Authority — "Compounding Authority"