From 93a2f3fe2255bb1f7700bbe0090452a91b526c09 Mon Sep 17 00:00:00 2001 From: ZuyiZhou <144661423+ZuyiZhou@users.noreply.github.com> Date: Sun, 20 Sep 2026 17:10:08 +0800 Subject: [PATCH 1/4] docs: add the design-engine runs to the showcase Two more cases, both ending in something other than a deck: a light-pollution poster campaign and an interactive GPS explainer. The campaign run is the first case whose graph takes an edge from the code side: three research nodes and a plate-generation node run in parallel, a Raven-Code node computes the sky-brightness panel, and a Raven-Design node composes the key visual plus the street, social and banner cuts off one master. The explainer run pairs two Raven-Code nodes, a solver and an independent oracle, into a Raven-Oncall cross-check before the page is built. Images are user-attachments, not repository files, per the assets rule. Co-authored-by: Claude (claude-opus-5) --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index 097007499..3be560284 100644 --- a/README.md +++ b/README.md @@ -148,6 +148,18 @@ Runs that end in something other than a deck. Retrieval sweep: recall@k is set by top_k alone, and latency stays flat across the grid + + +

A light-pollution campaign, researched and art-directed

+Task graph: three Raven-Research nodes and one Raven-Design plate node in parallel into a Raven-Code node, then one Raven-Design node +Key visual plus the derived series: street poster, data panel, social square and wide banner + + +

An interactive explainer, with its own solver

+Task graph: two Raven-Code nodes and one Raven-Design node in parallel into a Raven-Oncall cross-check, then one Raven-Design node +GPS trilateration explainer: the live page, and the fix at two, three and four satellites + + ## ❯❯ Connect Third-Party Agents From d2d84c7b15a6c4d7d32da460af58b19266883fb6 Mon Sep 17 00:00:00 2001 From: ZuyiZhou <144661423+ZuyiZhou@users.noreply.github.com> Date: Sun, 20 Sep 2026 17:18:59 +0800 Subject: [PATCH 2/4] docs: align the two new showcase cells The pair sat unevenly: a two-line heading on the left pushed that column's images down, and the two task graphs differ in height because one has four stacked nodes and the other three, so the artifacts below them started at different heights too. Each case now spans three table rows - headings, graphs, artifacts - so cells in a row share a top edge and a long heading no longer cascades into the images. The graphs are centred and their widths set so both render to one height, as are the two artifact sheets. Both headings are short enough to hold one line. Co-authored-by: Claude (claude-opus-5) --- README.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 3be560284..4fac5ec3e 100644 --- a/README.md +++ b/README.md @@ -149,16 +149,16 @@ Runs that end in something other than a deck. - -

A light-pollution campaign, researched and art-directed

-Task graph: three Raven-Research nodes and one Raven-Design plate node in parallel into a Raven-Code node, then one Raven-Design node -Key visual plus the derived series: street poster, data panel, social square and wide banner - - -

An interactive explainer, with its own solver

-Task graph: two Raven-Code nodes and one Raven-Design node in parallel into a Raven-Oncall cross-check, then one Raven-Design node -GPS trilateration explainer: the live page, and the fix at two, three and four satellites - +

A light-pollution poster campaign

+

An interactive explainer and its solver

+ + +

Task graph: three Raven-Research nodes and one Raven-Design plate node in parallel into a Raven-Code node, then one Raven-Design node

+

Task graph: two Raven-Code nodes and one Raven-Design node in parallel into a Raven-Oncall cross-check, then one Raven-Design node

+ + +

Key visual plus the derived series: street poster, data panel, social square and wide banner

+

GPS trilateration explainer: the live page, and the fix at two, three and four satellites

From 53b55951bca06a22a0cf4ff2d75222214d87eb80 Mon Sep 17 00:00:00 2001 From: ZuyiZhou <144661423+ZuyiZhou@users.noreply.github.com> Date: Sun, 20 Sep 2026 17:31:18 +0800 Subject: [PATCH 3/4] docs: correct the two task-graph alt texts Both descriptions routed the Raven-Design plate node through the intermediate node. The plate node feeds the final Raven-Design node directly; its edge passes behind the intermediate card, which is why it looks like it terminates on that card's lower border. Two connectors emerge from behind that card and converge on one arrowhead. Screen-reader users were getting a different graph from sighted readers. Co-authored-by: Claude (claude-opus-5) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4fac5ec3e..bcda8e060 100644 --- a/README.md +++ b/README.md @@ -153,8 +153,8 @@ Runs that end in something other than a deck.

An interactive explainer and its solver

-

Task graph: three Raven-Research nodes and one Raven-Design plate node in parallel into a Raven-Code node, then one Raven-Design node

-

Task graph: two Raven-Code nodes and one Raven-Design node in parallel into a Raven-Oncall cross-check, then one Raven-Design node

+

Task graph: three Raven-Research nodes in parallel into a Raven-Code node; that node and a Raven-Design plate node running alongside them both feed the final Raven-Design node

+

Task graph: two Raven-Code nodes in parallel into a Raven-Oncall cross-check; that node and a Raven-Design plate node running alongside them both feed the final Raven-Design node

Key visual plus the derived series: street poster, data panel, social square and wide banner

From 91a28cbd087940b9e925a686b32e73a41b309f0c Mon Sep 17 00:00:00 2001 From: ZuyiZhou <144661423+ZuyiZhou@users.noreply.github.com> Date: Sun, 20 Sep 2026 17:35:09 +0800 Subject: [PATCH 4/4] docs: redraw the two task graphs so the plate edge reads The plate node's connector ran behind the intermediate card, so it looked like it terminated on that card's lower border rather than continuing to the final Raven-Design node. Both graphs are redrawn with that edge routed clear of the card, arriving at the final node under its own arrowhead. The dependencies are unchanged; only the drawn path is. Co-authored-by: Claude (claude-opus-5) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bcda8e060..39fe67aee 100644 --- a/README.md +++ b/README.md @@ -153,8 +153,8 @@ Runs that end in something other than a deck.

An interactive explainer and its solver

-

Task graph: three Raven-Research nodes in parallel into a Raven-Code node; that node and a Raven-Design plate node running alongside them both feed the final Raven-Design node

-

Task graph: two Raven-Code nodes in parallel into a Raven-Oncall cross-check; that node and a Raven-Design plate node running alongside them both feed the final Raven-Design node

+

Task graph: three Raven-Research nodes in parallel into a Raven-Code node; that node and a Raven-Design plate node running alongside them both feed the final Raven-Design node

+

Task graph: two Raven-Code nodes in parallel into a Raven-Oncall cross-check; that node and a Raven-Design plate node running alongside them both feed the final Raven-Design node

Key visual plus the derived series: street poster, data panel, social square and wide banner