Home / Articles / Omnichannel programming / Versions / v1.2.0
Omnichannel programming: what changed in v1.2.0
From v1.1.0 (2026-10-19, d303ce0f1) to v1.2.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 47 unchanged. About 0 words added and 84 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot oc-multi-omni.webp | images/ | Multichannel and omnichannel programming: onseparate the left, each channel keeps its own copycopies of the work and a person carrieson the contextleft, betweenone them;shared state on the right, every channel reads and writes one shared state, so work started in one continues in any other.right. | comparison
16 unchanged paragraphs, under In short {#in-short}, Where the word comes from {#word}, What it looks like {#looks}…
!shot oc-session.webp | images/ | One session, many channels: what this newsroom session used from 13 to 15 October 2026, counted from its transcript and the repository log: what came in, what went out, what it was checked against, what kept it safe, and how I read it back, all around one shared state. | architecture
8 unchanged paragraphs, under Reviewing is a channel too {#review}, Every stage, every altitude {#stages}
!shot oc-spectrum.webp | images/ | Omnichannel at every stage of a Wardley map: explorers, villagers and town planners each use all the channels,planners, at every altitude from voice and intent, through interfaces and code, down to evidence. What changes between stages is what the work needs, not the channel.altitude. | comparison
21 unchanged paragraphs, under The new generation already works like this {#generation}, What breaks {#breaks}, The wider claim {#computing}…