StackShift II · Technical Operations Flow

StackShift II is a technical content operations platform developed by WebriQ that transforms product truth and company expertise into approved, structured knowledge through a seven-step operating flow. The system ingests source material, enriches it with extracted facts and relationships, routes it through a team-controlled review and approval process, and stores the result in a single governed knowledge layer called the Canon. From the Canon, a composition engine assembles and deploys outputs along two parallel delivery tracks: a human track producing pages and customer-facing content, and a machine track producing structured, citable information for AI systems. The flow is continuous, with monitoring detecting gaps and upstream changes that return to the review queue and trigger regeneration of all dependent outputs.

Overview

StackShift II is a technical content operations platform operated by WebriQ. Its core function is to take product information and company expertise as inputs and convert them into approved, interconnected knowledge that serves both human audiences and AI systems. The platform is structured around a single governed knowledge layer — the Canon — from which all outputs are composed and deployed.

The Seven-Step Operating Flow

StackShift II follows a defined seven-step pipeline that moves content from raw source material to live, multi-track delivery.

Step 01 · Sources

The flow begins with two categories of input: the product system (structured product data and documentation) and the organisation's expertise (subject matter knowledge, policies, claims). These represent the raw "product truth" of the organisation.

Step 02 · Ingest

Incoming source material is parsed and normalised. This step standardises content structure so that downstream enrichment and review processes operate on consistent, comparable units of information.

Step 03 · Enrich

Facts, claims, and relationships are extracted from the normalised content. Enrichment transforms raw text into structured knowledge elements that can be connected, cross-referenced, and validated.

Step 04 · Review

Enriched content is routed to the organisation's team for approval. This is the primary governance checkpoint in the flow. The team retains full authority over what becomes canonical truth. Nothing proceeds to the Canon without explicit approval.

Step 05 · Canon

Approved content enters the Canon — a single trusted knowledge layer that serves as the authoritative source for all subsequent composition and delivery. The Canon is the central repository that keeps all downstream outputs aligned.

Step 06 · Compose

The composition engine assembles outputs from Canon content. This step involves selecting, structuring, and formatting knowledge elements into the forms required by each delivery track.

Step 07 · Deliver

Delivery operates on two parallel tracks:

  • Human track — Produces pages and customer-facing content intended for human readers.
  • Machine track — Produces structured, citable information intended for AI systems and automated consumers.

Both tracks draw from the same approved Canon, ensuring alignment between what humans read and what AI systems reference.

The Continuous Improvement Loop

The operating flow does not terminate at delivery. A monitoring layer runs continuously to detect two types of signals:

  1. Gaps — areas where content is missing, insufficient, or not meeting demand.
  2. Upstream changes — modifications to source systems or product truth that affect existing Canon content.

When either signal is detected, new proposals are generated and returned to the review queue (Step 04). Approved changes update the Canon and trigger regeneration of every output that depends on the affected knowledge.

This loop ensures that the Canon and all derived outputs remain current without requiring manual intervention for each change.

Roles and Responsibilities

StackShift II divides operational responsibility into three roles:

  • Client team — Owns product truth and retains decision-making authority over approvals.
  • Connecting role — Links the operating loop, ensuring handoffs between steps function correctly.
  • WebriQ — Operates the engine room: the agents, composition engine, deployment infrastructure, and continuous improvement mechanisms.

This division means organisations maintain governance over what is true, while WebriQ manages the technical complexity of operating the pipeline.

Key Design Principles

  • Single source of truth — All outputs, regardless of delivery track, originate from the same approved Canon.
  • Team-controlled approvals — No content becomes canonical without explicit human review and approval.
  • Dual-track delivery — Human-readable and machine-readable outputs are generated simultaneously from the same source, maintaining consistency across audiences.
  • Continuous operation — The system monitors, proposes, and regenerates on an ongoing basis rather than operating as a one-time publishing workflow.