The canonical Ring A chain
Components expose nodes; nodes connect into workflows. Each node carries a typed input and output and an execution envelope — never a shared table.
Upload PRD → Export
Guided Mode configures this chain from a handful of questions. The advanced node canvas is deliberately deferred until the contracts are stable.
- Idle01
Upload PRD
Source Ingestionno model callsNormalises each uploaded document into a SALC Source Artifact. Original bytes are retained; extraction never overwrites the source.
in 4 documentsout 4 source artifacts - Idle02
Extract Product Knowledge
Product KnowledgeBuilds an immutable, versioned snapshot of requirements, business rules, risks, dependencies and contradictions, each carrying a citation back to its source.
in 4 source artifactsout 1 knowledge snapshot7 gateway calls · 33.2K tokens - Idle03
Generate Test Strategy
Test IntelligenceDerives risk-weighted testing priorities and scenario coverage targets from the snapshot.
in 1 knowledge snapshotout 82 scenarios4 gateway calls · 14.8K tokens - Idle04
Generate Test Cases
Test IntelligenceExpands each scenario into the SALC Test Specification Model: preconditions, steps, expected results, test data and automation suitability.
in 82 scenariosout 147 test cases7 gateway calls · 36.0K tokens - Idle05
Validate Quality Principles
Quality Principles Engineno model callsDeterministic validation. This node does not call the AI gateway — if it needed a model to decide, it would be more generation, not a quality principle.
in 147 test casesout 5 rule results - Idle06
Human Approval
Human Tasks & Approvalsno model callsFreezes the referenced snapshot, test specification and quality rule versions. Later edits cannot alter what was approved.
in 5 rule resultsout 1 frozen approval - Idle07
Export
Test Management Publishingno model callsPublishes the approved test specification to the configured destination. Every adapter consumes the vendor-neutral test model, never raw AI output.
in 1 frozen approvalout 147 published items
Activity
- 13:41:44Source Ingestion
Processed Claims-Intake-PRD.pdf · 48 pages · original retained
- 13:41:58Product Knowledge
C-014 surfaced — conflicting daily transaction limit
- 13:42:12Product Knowledge
Snapshot #KN-0842 sealed · 214 citations recorded
What travels between nodes
Components never read each other's tables. Everything moves as typed payloads, artifact references and job handles.
{
"workflowRunId": "run-1284",
"nodeRunId": "node-run-456",
"organisationId": "org-demo-001",
"projectId": "project-demo-001",
"schemaVersion": "1.0",
"executionLocation": "cloud",
"artifactReferences": ["KN-0842", "TS-0142"],
"idempotencyKey": "wf-ringA-1284",
"traceContext": { "sampled": true }
}SALC is n8n-like underneath, but lifecycle-specific on the surface. Users receive ready-to-use workflows and intelligence — not an empty canvas to assemble themselves.
See where the model calls go →