Skip to content

[DESIGN] Overview diagram: Yonatan's layout in the archify style - #94

Merged
haimbj1 merged 15 commits into
docs/diagram-designfrom
docs/overview-diagram
Sep 14, 2026
Merged

[DESIGN] Overview diagram: Yonatan's layout in the archify style#94
haimbj1 merged 15 commits into
docs/diagram-designfrom
docs/overview-diagram

Conversation

@haimbj1

@haimbj1 haimbj1 commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

A dedicated commit so the overview can be judged on its own, separate from #93.

Takes Yonatan's board (Figma node 44:3559) and rebuilds it with the color scheme and export pipeline the other eleven diagrams use.

Kept from his board

  • The four zones and their grouping: Host chain, CoFHE, Compute pipeline nested inside it, Registry chain
  • The tile arrangement, which reads well
  • His wording, with the corrections we agreed: contract names lose the .sol suffix per STYLE.md, "Securely authorizes" loses the adjective, and the Client SDK no longer claims to decrypt

Changed

  • Colors follow the zone rule rather than component type, so this diagram matches the other eleven
  • The blueprint palette and ground, exported through the same export-svg.py
  • Nested boundaries: Compute pipeline sits inside CoFHE, as on his board

Known rough edges, worth a look before merging

Three components have no connections. Client SDK, Ciphertext store and ZK Verifier sit in their zones without edges. Adding them crossed other nodes, and the validator rejects that.

The pipeline does not read continuously. Slim listener and FheOS are on one row, FHE Engine and Blockchain poster on the next, and the FheOS to FHE Engine link is missing, so the four-stage order is not visible.

Sublabels are much shorter than his. Archify sublabels are a single line, and desktop readability caps the viewBox at about 1023px, which caps sublabel width. The full descriptions live in the page's component lists directly below the diagram.

The option worth considering

Dropping sublabels entirely would lift the width cap, allowing five or six columns and the pipeline in a single row, which fixes the reading order. The page already describes every component underneath, so little would be lost. Say the word and I will build that variant to compare.

@mintlify

mintlify Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
fhenix 🟢 Ready View Preview Sep 10, 2026, 7:16 AM

@haimbj1
haimbj1 marked this pull request as ready for review September 14, 2026 11:55
@haimbj1
haimbj1 merged commit 1ea988a into docs/diagram-design Sep 14, 2026
5 checks passed
@haimbj1
haimbj1 deleted the docs/overview-diagram branch September 14, 2026 11:57
haimbj1 added a commit that referenced this pull request Sep 14, 2026
* [DOCS] encryption flow: designed diagram, colour marks where each component runs

* [DOCS] encryption flow: SVG uses the blueprint palette, matching the explorable page

* [DOCS] style/diagrams: colour marks the zone a component runs in, across every diagram

* [DOCS] style/diagrams: colour table covers the eight columns, CT Server explained

* [DOCS] encryption flow: SVG ground follows the preset, embed drops its frame

* [DOCS] encryption flow: Runs in column decodes the diagram colour

* [DOCS] style/diagrams: the Runs in column is the colour legend

* [DOCS] deep-dive: designed diagrams and explorable pages for the five Tier 1 flows

* [DOCS] zk-verifier: split the zone tip into shorter sentences

* [DOCS] diagrams: keep the legend clear of the last segment band

* [DOCS] diagrams: arrows land on the lifeline, or on the activation bar

* [DOCS] intro pages: designed diagrams with the CoFHE column in the offchain colour

* [DOCS] tier 3: designed diagrams for key management, the pipeline and the version lifecycle

* [DOCS] diagrams: legends name zones and states, not renderer internals

* [DOCS] key-management: name the consumers and cofhe-keys, so the diagram and page agree

* [DOCS] use American spelling for color, matching the rest of the site

* [DOCS] diagrams: crop each SVG to its own content, top and bottom

* [DOCS] introduction/what-is-cofhe: component table matches the diagram vocabulary

* [DOCS] cofhe-components/key-management: align the mmd source and the tip with the designed diagram

* [DOCS] cofhe-components/teecryptor: the coprocessor stores the bytes, not the FHE Engine

* [DOCS] data-flows/encryption-request-flow: CT Server is not drawn in the designed diagram

* [DOCS] introduction/mental-model: canonical coprocessor spelling, sentence-case headings

* [DESIGN] Overview diagram: Yonatan's layout in the archify style (#94)

* [DOCS] overview: Yonatan's layout and wording in the archify style

* [DOCS] overview: open the layout up, pipeline in one row

* [DOCS] overview: 2x2 blocks, and crop every diagram to its content

* [DOCS] overview: three wide columns, every component keeps its description

* [DOCS] diagrams: description in its own band, frames colored by group

* [DOCS] diagrams: ground follows the crop, overview in a wider ratio

* [DOCS] diagrams: fill the frame instead of letterboxing inside it

* [DOCS] overview: partners release to both TEEs, drawn as a stack

* [DOCS] diagrams: new house palette, solid headline bands, registry to the right

* [DOCS] diagrams: crop the sides, space the frames, palette in the explorable pages

* [DOCS] diagrams: declare a width past the column so they fill the frame

* [DOCS] overview: ACL beside PlaintextsStorage, white names on the blue accent

* [DOCS] overview: left to right, host chain left, CoFHE middle, registry right

* [DOCS] overview: one packed grid, aligned frames, pipeline as one component
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant