20:"$Sreact.view_transition" 21:I[9754,["/_next/static/chunks/2t36f5p4pjzlb.js","/_next/static/chunks/1gyqeidjm5eoa.js","/_next/static/chunks/0_fjnxc4tt_l_.js","/_next/static/chunks/1ymt1shyhmu-4.js","/_next/static/chunks/3kv2zf0i7s2wc.js","/_next/static/chunks/1vs_3g_g75zmk.js","/_next/static/chunks/2g4dh802s8oz3.js","/_next/static/chunks/1bc3f0shukf1j.js","/_next/static/chunks/192kgs9v_t14j.js","/_next/static/chunks/0z6pw0v5c_lx5.js","/_next/static/chunks/08r60e6icmtkc.js","/_next/static/chunks/3trx6c0i7_x-3.js","/_next/static/chunks/40sro5bzp9bi_.js","/_next/static/chunks/1wgf3tk38y6cf.js"],"ProjectDetail"] 22:T4eab, kkterm · 一个窗口，管理所有连接

kkterm · local-first terminal workspace

一个窗口，
管理所有连接。

面向运维与 Vibe Coder 的本地优先桌面终端工作台 —— 本地 shell、SSH、SFTP、RDP/VNC、嵌入式网页、文件浏览与文档查看，同处一片共享的连续工作面上。

▮ ▌ live session
— cursor thread

local shelllive

第一格介质：本机会话的实时光标线。

◆ ssh
channel · standby

◇ idle state

sshidle

远程主机通道，就绪待命。

▤ ▤
▤ row ▤　██
▤ row ▤　██

▁ file stream

sftpidle

列式文件流通道。

▓▒░
▒█ ▒　█▒
░ ▓　▒█

▚ pixel plane

rdp / vncidle

像素平面，图形化远程桌面就绪。

web ▸ files
page · doc viewer

web · filesmixed

嵌入式网页与文档查看器并列，无需切换应用。

✛human gate · one confirm

ai assistantawait confirm

AI 在窗格内提出动作，等待你的确认 —— 主动权在你手上。

02 · why it stays open

为何你会让它开上一整天

plane.value → local-first · no-telemetry · instant-launch
stays.lit ▣ all-day
● local · ● approved · ○ idle

一切数据都在自己的本地平面上运行：不设遥测、无需云同步，也没有团队账户 —— 你关闭窗口，也只是合上这扇门。

本地优先数据与连接都留在你的机器上，工作全程不离开本地平面。
无遥测不收集、不上报，安静地做你手中的工具。
即时启动体积极小的桌面应用，双击即开，不必为各连接反复打开新窗口。
跨平台支持 Windows、macOS 与 Linux，一处配置，各处运行。

03 · media streak

每一格，都有自己的介质

medium.type → shell | stream | pixel
lane.readable ● 独立呈现
one shared gutter

多窗格网格让不同类型的连接在同一标签页里并排出现 —— 例如 SSH 与 SFTP 肩并肩，各自保持自己的介质语言。

local shell ssh sftp rdp / vnc web files doc viewer ai assistant

终端会话光标流转的即时命令行介质。
文件流列式浏览的 SFTP 通道，横向传输。
像素平面RDP/VNC 的图形化远程桌面画面。
同窗并用多窗格混排，各介质互不干扰地同处一个窗口。

04 · the approval gate

机器提议，确认之后才执行

propose → gate → execute
ai.role = propose-in-pane
human.role = ✛ confirm

内置 AI 助手能在会话内直接操作终端，但它绝非默认自主 —— 每一步都要在你的确认之后才会真正执行。

AI · 只在窗格内提议人类 · 唯一确认权

PROPOSE→ HELD→ EXECUTE

执行仅在确认通过之后发生。

05 · it ops plane

站点、主机与机架，同一张连接图

ops.graph → site · host · rack
repeatable.work ▣ batch
one lattice, many nodes

IT Ops 模块为站点、主机与机架提供统一管理，批量任务与自动化在同一直线上铺开 —— 一个窗口，连接整张拓扑。

/site prod · connected

站点根节点，承载全部主机与机架。

ssh · live

/host app-01 · auth ok

会话内可直接复用的主机连接。

ssh · sftp

/rack R3 batch scheduled

批量任务与自动化循此铺开。

ops · repeat

06 · workspace isolation

用 Workspaces 让不同世界各自独立

world.sep ▦ own lattice
context → kept apart
AI.state → isolated scope

用 Workspaces 将不同工作域拆成各自独立的格子 —— 环境、连接与 AI 状态互不串扰，换一个世界就是换一张新的连接图。

项目隔离每个 Workspace 各自承载独立的连接布局。
上下文清晰站点、脚本与 AI 状态不相互污染。
随手切换在不同工作的格子之间来去自如。

07 · get the plane

把这张连接图带回你的机器

kkterm 支持 Windows、macOS 与 Linux，从一个窗口接入你的所有连接。

访问 kkterm.ryantsai.com↗ 查看源码仓库↗

最新版本 v3000.0.1 提供 Windows、macOS 与 Linux 下载。

23:T4a99, kkterm · One window for every connection

kkterm · local-first terminal workspace

One window,
every connection.

A local-first desktop terminal workspace for sysadmins & vibe coders — local shell, SSH, SFTP, RDP/VNC, embedded web, file browsing, and document viewing living on one shared surface.

▮ ▌ live session
— cursor thread

local shelllive

The first medium — a live cursor thread on this machine.

◆ ssh
channel · standby

◇ idle state

sshidle

A remote-host conduit, standing ready.

▤ ▤
▤ row ▤　██
▤ row ▤　██

▁ file stream

sftpidle

A column-style file-stream lane.

▓▒░
▒█ ▒　█▒
░ ▓　▒█

▚ pixel plane

rdp / vncidle

A pixel plane, ready for a graphical remote desktop.

web ▸ files
page · doc viewer

web · filesmixed

Embedded pages and document viewers, no app-hopping.

✛human gate · one confirm

ai assistantawait confirm

The assistant proposes inside the pane — approval is yours to give.

02 · why it stays open

Why people leave it open all day

plane.value → local-first · no-telemetry · instant-launch
stays.lit ▣ all-day
● local · ● approved · ○ idle

Everything runs on a single local plane: no telemetry, no cloud sync, no team account — close the window and you just shut the door.

Local-firstData and connections stay on your machine; the whole session never leaves the plane.
No telemetryNothing is collected or reported — a quiet tool in your hands.
Instant launchA tiny desktop app that opens on demand, instead of spawning new windows per connection.
Cross-platformRuns on Windows, macOS, and Linux — one setup, everywhere.

03 · media streak

Each tile is its own medium

medium.type → shell | stream | pixel
lane.readable ● rendered distinct
one shared gutter

The multi-pane grid lets different connection types sit side by side in the same tab — SSH next to SFTP — each speaking its own medium without interference.

local shell ssh sftp rdp / vnc web files doc viewer ai assistant

Terminal sessionsAn immediate command-line medium, cursor in motion.
File streamsColumn-style SFTP lanes moving data sideways.
Pixel planesRDP/VNC's graphical remote desktop surface.
Mixed in one windowPane types interleave freely, each lane held apart.

04 · the approval gate

Machine proposes. Confirm, then it acts.

propose → gate → execute
ai.role = propose-in-pane
human.role = ✛ confirm

The built-in AI assistant can operate terminals within a session, but it is not autonomous by default — nothing runs until you approve it.

AI · proposes inside the pane only Human · sole confirming authority

PROPOSE→ HELD→ EXECUTE

Execution happens only after approval passes.

05 · it ops plane

Sites, hosts, and racks, on one connection map

ops.graph → site · host · rack
repeatable.work ▣ batch
one lattice, many nodes

The IT Ops module manages sites, hosts, and racks in one place, spreading batch tasks and automations across the same lattice — one window reaching a whole topology.

/site prod · connected

The root node carrying every host and rack below it.

ssh · live

/host app-01 · auth ok

Host connections reusable inside the session.

ssh · sftp

/rack R3 batch scheduled

Repeatable work and automation fan out from here.

ops · repeat

06 · workspace isolation

Keep your worlds apart with Workspaces

world.sep ▦ own lattice
context → kept apart
AI.state → isolated scope

Workspaces split different working worlds into their own tiles — environments, connections, and AI state stay separate, so switching worlds means drawing a fresh connection map.

Project isolationEach workspace carries its own set of connections.
Clear contextSites, scripts, and AI state never cross-contaminate.
Easy switchingMove between tiles of different work at will.

07 · get the plane

Bring the plane onto your machine

kkterm runs on Windows, macOS, and Linux — one window reaching your whole connection set.

Visit kkterm.ryantsai.com↗ View the source repo↗

Release v3000.0.1 ships downloads for Windows, macOS, and Linux.

24:T43e,The connection-lattice direction best expresses KKTerm's defining mechanism: 'one window, every connection.' The project's own evidence centers on mixing heterogeneous connection types (SSH next to SFTP) in a multi-pane grid within one window — a fact that no other direction names as its core structure. The lattice simultaneously carries the local-first/non-telemetry trust value (everything lives on a single local plane), the approval-gated AI (the one amber gate inside the shared gutter), and the IT Ops inventory (sites/hosts/racks as tiled connectable mediums). The ops-hierarchy direction is strong for IT Ops but foregrounds inventory over the 'one window' proposition; the approval-gate direction is emotionally compelling but over-weights the assistant feature against the broader terminal workbench. Connection-lattice also avoids the terminal shell cliché by using a media-neutral tile field, and since material.json ships no qualified media assets (assetManifest is empty), its typography/geometry-driven composition can stand on its own without any forged screenshot.a:[["$","$20",null,{"enter":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-enter","default":"none"},"exit":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-exit","default":"none"},"update":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-update","default":"none"},"default":"none","children":["$","$L21","cmt2zh2p701h16271slpwys44:zh-CN:beautified",{"project":{"id":"cmt2zh2p701h16271slpwys44","slug":"ryantsai-kkterm","name":"kkterm","description":"面向运维与 Vibe Coder 的本地优先桌面终端工作台","authorName":"ryantsai","authorVerification":{"verified":false,"verifiedAt":null},"category":"development_tools","subcategory":"data_ai_tools","experienceUrl":"https://kkterm.ryantsai.com/","qualityScore":83,"featured":false,"officialSite":null,"views":{"original":{"available":true},"official":{"available":false,"reason":"disabled_by_policy"},"beautified":{"available":true,"reason":null},"defaultView":"beautified"},"beautifiedView":{"revisionId":"cmt2zh2pu01hd6271o5oe4rmn","kind":"artifact","artifact":{"schemaVersion":"localized-static-html-v4","kind":"static_html","locales":["zh-CN","en"],"defaultLocale":"zh-CN","documents":{"zh-CN":"$22","en":"$23"},"designDirections":{"schemaVersion":"dodot-design-directions-v1","directions":[{"id":"connection-lattice","name":"Connection Lattice","projectMetaphor":"One window, every connection — a single glass plane tiled into heterogeneous conduits (local shell, SSH, SFTP, RDP/VNC) that commute between the operator's machine and remote worlds.","signatureVisual":"A non-uniform grid of connection cells (no app chrome): each tile is a distinct medium — a live session cursor line, a file-stream column, a pixel plane — knit together by shared dividers, reading as one connected field rather than a product screenshot.","heroGeometry":"A 2x3 lattice of irregular tiles where cell sizes encode connection type and activity; one live cursor thread flows across the shared gutter, so the eye reads 'many mediums, one window'.","sectionSequence":["The Lattice Hero: one window holding many mediums simultaneously","Why It Stays Open: local-first, no telemetry, instant launch (value of keeping the plane open all day)","Media Streak: reading each tile (terminal, stream, pixel) as its own medium","The Approval Gate: AI proposes inside the pane, human confirms before it acts","IT Ops Plane: sites, hosts, racks as connectable nodes on the same lattice","Workspace Isolation: separate worlds as separate lattices/compartments","Get the Plane: cross-platform downloads"],"surfaceModel":"A single continuous working surface split by hairline gutters — panes are recessed wells with differentiated depth (live action vs idle), dividers are the only color-accent architecture, no floating cards.","palette":"Deep graphite working surface, near-black wells, one restrained signal hue reserved for live activity + one approval-amber reserved strictly for the human gate.","typography":"Mono-first voice with a spatial sans for hierarchy: mono for connection/idle labels and the signature cipher, sans for narrative headlines to keep human voice distinct from machine stream.","desktopComposition":"Full-bleed lattice reaching the viewport edges; hero cells hold explanatory density within the pane frame; dividers carry the section-to-section transition; copy sits inside pane gutters as annotations rather than overlaid slabs.","mobileTransformation":"The 2x3 lattice folds into a vertical 'drawer stack': live panes collapse to horizontal channel strips you can open one at a time, each strip retains the gutter identity; approval gate becomes a full-width confirmation drawer.","mediaStrategy":"No media region: no qualified local screenshots exist, so the hero and sections are built purely from evidence-driven lattice/typography composition; no fake screenshots.","forbiddenPatterns":["No browser/terminal/dashboard/editor shell chrome frame drawn around content","No three equal metric cards under a slogan","No glowing grid or particle field as decoration","No feature-card wall that accepts any project's copy","No fake tabs, status bars, or synthetic terminal prompts"],"compositionFingerprint":"Irregular connection lattice of heterogenous pane types sharing live gutters, with a mono cipher override for idle states and a single amber approval gate."},{"id":"ops-hierarchy","name":"Ops Hierarchy","projectMetaphor":"The operator's inventory as a living tree — sites branch into hosts, hosts branch into racks — an IT Ops domain that you manage as one connected topology rather than scattered utilities.","signatureVisual":"A structural topology diagram (root site → host → rack) drawn with orthogonal connectors, where each node carries a compact medium glyph and live/working state; reads as an inventory graph, not a control panel.","heroGeometry":"A vertical root-to-leaf tree where the trunk is the single window and each branch is a managed domain; connection type labels hang on the branches like typed annotations.","sectionSequence":["The Inventory Root: sites, hosts, racks drawn as one connected tree","Mixed Media per Node: each node hosts a different connection medium on the same plane","Batch Ops: repeatable work and automations fan out across sibling nodes","Approval-Gated AI: AI acts within the tree but each action is confirmed by the operator","Dashboard That Doesn't Pretend: honest status, not Grafana theater","Keep Agents Alive: managed runs and capture across the topology","Get the Tree: downloads seeding the root node"],"surfaceModel":"A structured diagram plane: connectors and node bodies are ruled, status is conveyed by orthogonal tick glyphs (not traffic light dots), grouping by containment borders, no floating toolbar panels.","palette":"Paper-dark stage with ruled grid lines; ink-colored connectors; green used strictly for 'live/ok' status ticks; amber reserved solely for the pending-approval state.","typography":"Tabular/system-aligned type for node labels and status glyphs; a recording/document-style serif or warm sans for the narrative voice to contrast operator story with machine inventory.","desktopComposition":"The tree occupies the left two-thirds as a persistent diagram; the right third is a reading column of evidence-led section copy; scroll advances the tree at a different rate than the copy (optical drift between inventory and story).","mobileTransformation":"The horizontal tree is re-rooted into a stacked branching list: each node becomes a tappable row that expands its children and its medium; connectors become indent guides; batch + approval collapse into bottom-sheet actions.","mediaStrategy":"No media region due to absent qualified assets; the topology diagram itself is the evidence-derived signature visual, rendered with rules and status glyphs, never impersonating a product screenshot.","forbiddenPatterns":["No terminal or dashboard shell frame around the diagram","No three metric stat cards","No decorative glowing grid or particle field","No browser/editor shell recreation","No fake charts, graphs, or Grafana-style panels"],"compositionFingerprint":"Rooted inventory topology with orthogonal connectors, per-node medium glyphs, tabular status ticks, and an optical-drift reading column."},{"id":"approval-gate","name":"Approval Gate","projectMetaphor":"Trust as a relay race: the machine proposes, the human holds the relay baton, action only passes when the operator confirms — an assistant that acts inside your session but never leaves your hands.","signatureVisual":"A three-stage relay line (propose → confirm → execute) drawn as a horizontal conductance path with an explicit gate node where a human-stamp glyph sits between the AI and the target medium; reads as a handoff circuit, not a chat window.","heroGeometry":"A horizontal signal path across the hero: machine stream enters from the left, passes through a human gate node in the center, and emerges as confirmed action on the right; the gate is the visual center of gravity.","sectionSequence":["The Relay Hero: propose → gate → execute as one humane circuit","What It Is: one window holding local terminals, SSH, SFTP, RDP/VNC side by side","Why It Stays Open: local-first, no telemetry, instant launch","The Handoff: AI acts in-session but only with your confirmation","Mediums as Conductors: each connection is a separate lane on the same path","Ops Paths: sites, hosts, racks as endpoints you route to","Get the Relay: cross-platform seeds the run"],"surfaceModel":"A conductive flat plane where the signal path is the primary architecture; mediums sit as lane insets along the path; the confirming gate is a tactile raised boss (the only raised element) to physionalize human control.","palette":"Neutral conduit surface with machine-blue for proposed/stream states and one human-amber for the gate node; executed-complete uses a restrained green tick; no decorative gradient wash behind content.","typography":"A mechanical sans for machine-side labels paired with a humanist, clearly editorial voice for confirmation/narrative copy — two voices to dramatize the handoff between machine and human.","desktopComposition":"The relay path runs horizontally across the full hero width; sections hang as lanes beneath the path; the gate node keeps visual neutrality so it always reads as the most important object on the page.","mobileTransformation":"The horizontal relay rotates to a vertical descending circuit: propose stacks above, the gate sits as a full-width confirmation tactile toggle, execute below; lanes collapse into stacked segments that reveal their medium on tap.","mediaStrategy":"No media region because no qualified local asset exists; sign-off (the approve gesture) is rendered as typographic/typographic form, not a fake screenshot or control.","forbiddenPatterns":["No AI chatbot/chat bubble interface recreation","No terminal shell frame around content","No three metric cards","No glowing gradient or particle background substition for the idea","No fake buttons, switches, or approval controls pretending to be live UI"],"compositionFingerprint":"Horizontal propose→gate→execute conductance path with a single raised human gate node, medium lanes, and twin machine/human voice contrast."}],"selectedDirectionId":"connection-lattice","selectionRationale":"$24"},"designBrief":{"schemaVersion":"dodot-design-brief-v1","selectedDirectionId":"connection-lattice","projectMetaphor":"One window, every connection — a single glass plane tiled into heterogeneous conduits (local shell, SSH, SFTP, RDP/VNC) that commute between the operator's machine and remote worlds.","signatureVisual":"A non-uniform grid of connection cells (no app chrome): each tile is a distinct medium — a live session cursor line, a file-stream column, a pixel plane — knit together by shared dividers, reading as one connected field rather than a product screenshot.","compositionFingerprint":"Irregular connection lattice of heterogenous pane types sharing live gutters, with a mono cipher override for idle states and a single amber approval gate.","heroGeometry":"A 2x3 lattice of irregular tiles where cell sizes encode connection type and activity; one live cursor thread flows across the shared gutter, so the eye reads 'many mediums, one window'.","sectionSequence":["The Lattice Hero: one window holding many mediums simultaneously","Why It Stays Open: local-first, no telemetry, instant launch (value of keeping the plane open all day)","Media Streak: reading each tile (terminal, stream, pixel) as its own medium","The Approval Gate: AI proposes inside the pane, human confirms before it acts","IT Ops Plane: sites, hosts, racks as connectable nodes on the same lattice","Workspace Isolation: separate worlds as separate lattices/compartments","Get the Plane: cross-platform downloads"],"surfaceModel":"A single continuous working surface split by hairline gutters — panes are recessed wells with differentiated depth (live action vs idle), dividers are the only color-accent architecture, no floating cards.","palette":"Deep graphite working surface, near-black wells, one restrained signal hue reserved for live activity + one approval-amber reserved strictly for the human gate.","typography":"Mono-first voice with a spatial sans for hierarchy: mono for connection/idle labels and the signature cipher, sans for narrative headlines to keep human voice distinct from machine stream.","desktopComposition":"Full-bleed lattice reaching the viewport edges; hero cells hold explanatory density within the pane frame; dividers carry the section-to-section transition; copy sits inside pane gutters as annotations rather than overlaid slabs.","mobileTransformation":"The 2x3 lattice folds into a vertical 'drawer stack': live panes collapse to horizontal channel strips you can open one at a time, each strip retains the gutter identity; approval gate becomes a full-width confirmation drawer.","mediaStrategy":"No media region: no qualified local screenshots exist, so the hero and sections are built purely from evidence-driven lattice/typography composition; no fake screenshots.","evidencePlan":["Hero lattice cell types map directly to verified facts: local/SSH/SFTP/RDP-VNC mediums, multi-pane mixed layout, one window.","'Why It Stays Open' section cites evidence-backed value: local-first, no telemetry, tiny download/instant launch.","Approval Gate section represents the verified claim that the AI assistant is not autonomous and requires human approval.","IT Ops Plane section represents the verified IT Ops module for sites, hosts, racks and repeatable/batch work.","Workspace Isolation section represents the verified Workspaces capability to keep separate worlds apart."],"localeContract":{"zh-CN":"标题/slogan使用『一个窗口，管理所有连接』；副题使用『面向运维与 Vibe Coder 的本地优先桌面终端工作台』；正文与章节文案以中文单句密度书写，卡片/内格注解使用中文自然句式，保持信息密度合理。","en":"Headline/slogan uses 'One window for every connection' with the one-line 'Local-first desktop terminal workspace for sysadmins & vibe coders'; body copy written in natural English sentence rhythm for each section, with concise pane annotations."},"forbiddenPatterns":["No browser/terminal/dashboard/editor shell chrome frame drawn around content","No three equal metric cards under a slogan","No glowing grid or particle field as decoration","No feature-card wall that accepts any project's copy","No fake tabs, status bars, or synthetic terminal prompts"]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"The two pages faithfully implement the frozen 'connection-lattice' direction. The signature visual — a non-uniform 6-column lattice of heterogeneous connection tiles (local shell / SSH / SFTP / RDP-VNC / web-files / AI) sharing hairlines, with a mono idle cipher and a single amber human-gate tile — is genuinely present in the hero and never degenerates into a terminal shell. All seven brief sections are realized in order with matching data-dodot-section across zh-CN and en. No media is forged (material assetManifest is empty) and no screenshot shell is drawn; every claim (local-first, no telemetry, multi-pane mixing, approval-gated AI, IT Ops sites/hosts/racks, Workspaces isolation, v3000.0.1 cross-platform downloads) traces to material.json facts. Mobile CSS re-layouts the lattice into a vertical strip stack carrying gutter identity and turns copy columns single-pane, a genuine recomposition. Both locales keep the same structure with natural, equivalent copy. No forbidden default and no fake control found.","checks":{"projectFit":{"passed":true,"evidence":"Both files implement the frozen direction 'connection-lattice' (design-brief.json selectedDirectionId) with its exact projectMetaphor 'One window, every connection'. Hero lattice tiles map to verified connection mediums (local shell, SSH, SFTP, RDP/VNC, web/files/doc viewer, AI assistant) from material.json description and overview claim. All seven brief sections appear in order: lattice-hero, stays-open, media-streak, approval-gate, it-ops, workspaces, get; zh-CN(7) and en(7) are identical in sequence."},"evidenceBound":{"passed":true,"evidence":"Every substantive claim is traceable to material.json extraction/summary facts: local-first+no-telemetry+instant-launch (stays-open, readme headings 'Tiny download, instant launch'); multi-pane mixed layouts SSH next to SFTP (media-streak, verified claim); AI not autonomous, requires human approval (approval-gate, verified claim); IT Ops module managing sites/hosts/racks with batch+automation (it-ops, verified); Workspaces separation (workspaces, readme heading); Windows/macOS/Linux cross-platform and v3000.0.1 downloads for all three (get, verified releases claim). No numeric star/fork metric is displayed; CTA hrefs are the verified experienceUrl https://kkterm.ryantsai.com/ and repository https://github.com/ryantsai/kkterm."},"signatureVisual":{"passed":true,"evidence":"The brief-defined signature visual — irregular lattice of heterogeneous connection cells with shared live gutters, mono cipher override for idle states, and a single amber approval gate — is concretely built: .lattice is a non-uniform 6-col grid (t-1..t-6 spans 3/2/1/1/2/3) of distinct mediums, each with its own medium glyph (live cursor thread, file-stream column, pixel plane), idle tiles use .idle-pulse mono cipher, and the t-6 tile carries the sole amber .gate-rule stamp. It reads as one connected field, not a product screenshot."},"mobileTransformation":{"passed":true,"evidence":"At max-width:820px the .lattice folds from the 6-column full-bleed plane into a single-column vertical 'drawer stack' of tile strips (grid-template-columns:1fr, gap:10px, transparent gutter background), each strip retaining gutter identity via a border-left:3px hairline (signal for live, amber for awaiting-confirm), idle-pulse ciphers are removed, and .cols becomes 1fr. This is genuine recomposition (drawer stack) rather than stacked desktop columns, and reduces the hero into vertical channel strips exactly as the brief prescribes."},"localeParity":{"passed":true,"evidence":"zh-CN and en share identical brief, section sequence, and all seven data-dodot-section ids. Copy is equivalent and natural per language: zh-CN slogan '一个窗口，管理所有连接' vs en 'One window, every connection'; both keep technical labels (SSH/SFTP/RDP/VNC, PROPOSE-HELD-EXECUTE) consistent. zh-CN uses denser natural CJK sentence rhythm while en reads with natural English sentence rhythm; both reflect the locale contract. Structure counts match (18 structural markers each)."},"antiTemplate":{"passed":true,"evidence":"No forbidden default is present: no three-equal metric cards, no generic feature-card wall (list items carry project-specific connection/ops copy), no browser/terminal/dashboard/editor chrome shell, no decorative glowing grid or particle field (the lattice is structural with project-specific medium tiles). antiTemplateContext in material.json is empty so no composition fingerprint or section sequence conflicts."},"noFakeUi":{"passed":true,"evidence":"No ,

一个窗口，管理所有连接。

为何你会让它开上一整天

每一格，都有自己的介质

机器提议，确认之后才执行

站点、主机与机架，同一张连接图

用 Workspaces 让不同世界各自独立

把这张连接图带回你的机器

One window,every connection.

Why people leave it open all day

Each tile is its own medium

Machine proposes. Confirm, then it acts.

Sites, hosts, and racks, on one connection map

Keep your worlds apart with Workspaces

Bring the plane onto your machine

一个窗口，
管理所有连接。

One window,
every connection.