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:T504b, Fulcrum · AI 驱动的软件交付指挥中心

AI 驱动的软件交付指挥中心

Fulcrum

围绕支点，平衡并行的 AI 代理工作负载。

Fulcrum 面向技术型独立开发者与 CTO：并行运行多个 Claude Code 任务，通过看板、项目管理、多渠道消息与部署，把分散的开发工作汇聚到一个能持续保持水平的交付支点上。

从源码开始

作者 knowsuchagency 语言 TypeScript 方向 agents · ai · coding

支点原理

每次计划、每个渠道、每步部署，都是保持横梁水平的配重。

Fulcrum 的中心是一个固定支点。任务的重量顺着对称的平行时间轨道分布，只要编排得当，交付横梁就始终处于水平状态——这就是并行代理编排所追求的那种稳定。

水平状态——规矩的基线承托着支点之下。

支点

L1Git 工作树各自隔离的并行任务轨道

L2Scratch 目录轻量快速的临时工作区

L3手动任务由你定义的受控交付项

配重在线，横梁保持水平

任务类型

三种植重的板块，适配不同的工作流。

Git 工作树

在每个任务各自的工作树中并行运作，彼此隔离，共享交付主线。

并行

Scratch 目录

轻量、快速的临时工作区，适合不需要完整版本上下文的尝试与迭代。

轻量

手动任务

直接定义与控制的交付项，与自动编排并行，保持同一水平面的可见性。

受控

渠道

在消息里发号施令，收每天的简报。

把对话接入你已经在用的平台，AI 助手自动发送每日简报，工作流不离开聊天本身。

随时下达调度意图

入站

邮件驱动的简报与记录

入站

DISCORD

团队共享的交付频道

入站

即时的移动端调度

入站

SLACK

贴合既有工作流的通知

入站

架构

MCP 优先：工具、发现与代理的中缝。

MCP 优先

tools · discovery

以 MCP 为中心，暴露丰富的工具并把智能的工具发现接进横梁；外部代理沿连接缝集成进同一平衡面。

主动委派

memory · planning

结合持久记忆与可感知日程的规划，让 AI 助理解读上下文主动推进，而不是被动等待指令。

MCP工具智能工具发现内建于横梁

EXT外部代理沿连接缝接入同一平衡面

MEM持久记忆驱动主动式日程规划

部署

生产级部署，把平衡延伸到发布端。

Docker Compose

可复现的生产部署，一套编排完成交付。

Traefik

接近发布端点的流量路由，保持入口稳定。

Cloudflare DNS / 隧道

域名与隧道接入，让任何远程环境都在指挥范围内。

让横梁动起来。

项目提供桌面应用（macOS、Linux）、远程服务器安装脚本与 Claude Code 插件等上手途径；最快的起点仍是一行命令。

$ npx @knowsuchagency/fulcrum@latest up

源码 → github.com/knowsuchagency/fulcrum

23:T4d0d, Fulcrum · AI-powered command center for shipping software

AI-powered command center for shipping software

Fulcrum

One pivot balancing many parallel agent workloads.

Fulcrum is an AI-driven command center for technical solopreneurs and CTOs, running multiple Claude Code tasks in parallel with kanban, project management, and deployment — all held level on a single delivery pivot.

Start from source

Author knowsuchagency Language TypeScript Topics agents · ai · coding

The pivot

Every plan, every channel, every deploy is a counterweight keeping the delivery beam level.

Fulcrum sits on a fixed pivot. Load travels down symmetric parallel time-lanes, and as long as it is orchestrated, the delivery beam stays level — the steady state of parallel agent shipping.

Level state — the ruled baseline holds beneath the pivot.

Pivot

L1Git worktreesIsolated parallel lane per task

L2Scratch dirsLightweight throwaway workspaces

L3Manual tasksDelivery you define and control

Counterweight online, beam level

Task types

Three kinds of weight blocks, each suited to a different workflow.

Git worktrees

Run each job in its own worktree, isolated yet feeding the same delivery line.

Parallel

Scratch directories

Lightweight throwaway workspaces for quick experiments without versioned context.

Lightweight

Manual tasks

Delivery you define and control directly, visible on the same level plane.

Controlled

Channels

Give orders from chat, get the daily briefing back.

Route conversations through platforms you already use. The AI assistant sends automated daily briefings so the workflow never leaves the message thread.

Direct scheduling intent on the go

inbound

Mail-driven briefings and history

inbound

DISCORD

A shared delivery channel for teams

inbound

Immediate scheduling from mobile

inbound

SLACK

Notifications that fit your existing flow

inbound

Architecture

MCP-first: seams for tools, discovery, and external agents.

MCP-first

tools · discovery

Core around MCP, exposing a wide toolset with smart tool discovery; external agents join the same balanced plane along these connection seams.

Proactive delegation

memory · planning

Persistent memory and schedule-aware planning let the assistant read context and move work forward, not simply wait for commands.

MCPToolsSmart discovery built into the beam

EXTExternalAgents join via connection seams

MEMMemoryPersistent state drives proactive planning

Deployment

Production-grade delivery extends the balance to the shipping edge.

Docker Compose

Reproducible production setup, one orchestration away from delivery.

Traefik

Traffic routing near the edge keeps the ingress steady.

Cloudflare DNS / tunnels

DNS and tunneling put any remote environment inside command reach.

Put the beam in motion.

Get started via desktop apps for macOS and Linux, an install script for remote servers, or a Claude Code plugin. The fastest on-ramp remains a single command.

$ npx @knowsuchagency/fulcrum@latest up

Source → github.com/knowsuchagency/fulcrum

24:T4d8,The project is literally named 'fulcrum', and its core mechanism is the balanced pivoting of many parallel agent workloads, task types, and deployment concerns toward a single shipping outcome. The lever-and-counterweight composition expresses this named mechanism directly: a central pivot holding balanced parallel time-lanes is the exact shape of 'parallel agent orchestration with kanban', and the level-lane geometry naturally carries the three task types (Git worktree, Scratch, Manual) as weight blocks. It reads as a mechanism, not a landing page, and ranks highest on project fit and signature-visual originality. 'Dispatch Switchboard' strongly expresses multi-channel routing but under-represents the centrality the project claims and risks reading as a generic message-routing diagram. 'Orbital Command' expresses MCP tool breadth and scheduling well but drifts toward decorative radial geometry that is a weaker match for the concrete kanban/deployment mechanism. All three avoid forbidden defaults; the lever direction wins because it makes the project's own name the composition, delivers a distinct signature visual and mobile transformation (beam-to-spine rotation), and has the clearest evidence mapping for every section.25:T48b,Both zh-CN and en pages faithfully implement the lever-counterweight direction. The hero is a real inline-SVG lever beam with a central triangular fulcrum pivot, symmetric parallel time-lanes and task weight blocks (Git worktree, Scratch, Manual, Daily briefings) plus a lime balance tick; palette, technical grotesk + mono typography, and the seven-section sequence match the brief exactly. All stated facts map to material.json evidence and no invented metrics appear. Both locales implement a genuine beam-to-spine mobile recomposition (vertical portrait spine with a 'Pivot' capstone, inline per-lane weight labels, lime spine-tick, and footer ruled baseline) rather than mere stacking. The two locales are structurally equivalent and naturally translated, with technical terms kept verbatim per the localeContract. No forbidden template patterns, device shells, fake controls, or decorative gradient/glow fields are present (the only gradient is a functional 50/50 orange/lime split-rule on the quick-start banner). One non-blocking completeness note: Google Calendar/CalDAV named in the evidencePlan are only surfaced generically as schedule-aware planning.26:T48b,Both zh-CN and en pages faithfully implement the lever-counterweight direction. The hero is a real inline-SVG lever beam with a central triangular fulcrum pivot, symmetric parallel time-lanes and task weight blocks (Git worktree, Scratch, Manual, Daily briefings) plus a lime balance tick; palette, technical grotesk + mono typography, and the seven-section sequence match the brief exactly. All stated facts map to material.json evidence and no invented metrics appear. Both locales implement a genuine beam-to-spine mobile recomposition (vertical portrait spine with a 'Pivot' capstone, inline per-lane weight labels, lime spine-tick, and footer ruled baseline) rather than mere stacking. The two locales are structurally equivalent and naturally translated, with technical terms kept verbatim per the localeContract. No forbidden template patterns, device shells, fake controls, or decorative gradient/glow fields are present (the only gradient is a functional 50/50 orange/lime split-rule on the quick-start banner). One non-blocking completeness note: Google Calendar/CalDAV named in the evidencePlan are only surfaced generically as schedule-aware planning.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","cmt2zh0ux00vb62717ut6dwql:zh-CN:beautified",{"project":{"id":"cmt2zh0ux00vb62717ut6dwql","slug":"knowsuchagency-fulcrum","name":"fulcrum","description":"并行编排 AI 代理，集中管理开发任务。","authorName":"knowsuchagency","authorVerification":{"verified":false,"verifiedAt":null},"category":"development_tools","subcategory":"data_ai_tools","experienceUrl":null,"qualityScore":41,"featured":false,"officialSite":null,"views":{"original":{"available":true},"official":{"available":false,"reason":"disabled_by_policy"},"beautified":{"available":true,"reason":null},"defaultView":"beautified"},"beautifiedView":{"revisionId":"cmt2zh0vb00vn6271d27l4o24","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":"lever-counterweight","name":"Lever & Counterweight","projectMetaphor":"A fulcrum is the balance point where many parallel agent workloads pivot toward a shipping horizon. The command center is the fixed pivot; every scheduled task, channel, and deployment is a counterweight that keeps the delivery beam level.","signatureVisual":"A balanced lever beam drawn as horizontal parallel time-lanes that converge on a central triangular fulcrum pivot; weight blocks representing live tasks (Git worktree, Scratch, Manual) sit along each lane, with the beam staying level through parallel orchestration.","heroGeometry":"A single central fulcrum triangle at the bottom center with two symmetric beam arms extending left and right, each arm a stack of parallel horizontal lanes carrying task-weight blocks.","sectionSequence":["hero","pivot-principle","task-types","channels","architecture","deployment","quick-start"],"surfaceModel":"Paper-and-ink mechanical diagrams: flat matte surfaces separated by sharp structural rules, transparent task blocks floating over guide-lane lines, and a hard-edged shadow only under the pivot and the weight blocks. No blur; seams are lines, not gaps.","palette":"Warm blueprint on off-white: deep ink (#1b1f24), traction orange (#e8590c) as the pivot hot-spot, cool steel blue (#2f5fa8) for lanes, pale paper (#f6f2ea), and a single accent lime (#84cc16) marking the balanced/online state.","typography":"Technical grotesk for headings (inset metrics feel), monospace for lane labels, weights, and channel tags; tabular figures so parallel counts align down columns.","desktopComposition":"Left-anchored 12-column grid: hero places the lever diagram as the dominant right-block while copy and CTA sit on the left shoulder; section layout alternates between a full-width balanced beam and a split pivot/arm pairing; the level state measure spans the base as a ruled baseline.","mobileTransformation":"The horizontal beam is rotated into a single vertical spine of stacked lanes (portrait levers); weight blocks stack in reading order while the pivot moves to the top of the visual as a capstone; per-lane labels move inline; the ruled baseline becomes the page's own bottom edge.","mediaStrategy":"No local or remote media exists (assetManifest is empty). Remove the media region entirely; the lever/weight diagram IS the signature visual, built entirely from layout rules, blocks, and lanes rather than any product screenshot.","forbiddenPatterns":["no centered three-metric-card hero under a slogan","no browser/terminal/dashboard/editor shells","no decorative gradient, glow, or particle fields","no fake charts, tabs, search bars, or metric widgets","no unsupported product metrics or counts"],"compositionFingerprint":"A level ruled baseline runs beneath a central fulcrum pivot whose symmetric parallel time-lanes carry stacked task-weight blocks, with the balance state rendered as a lime alignment tick."},{"id":"dispatch-switchboard","name":"Dispatch Switchboard","projectMetaphor":"Fulcrum is a telegraph dispatch office: many inbound channels (WhatsApp, Email, Discord, Telegram, Slack) arrive at a central switchboard and are routed onto parallel agent tracks toward delivery.","signatureVisual":"A converging/divering rail-yard: five inbound channel nodes merge into a central dispatch trunk, then fan out again into parallel agent delivery tracks; switches shown as small mechanical points on the rails.","heroGeometry":"Two inverse cones: a left-hand cone of inbound channel streams collapsing into a central trunk node, a right-hand cone expanding from the trunk into parallel delivery rails.","sectionSequence":["hero","routing","inbound-channels","task-dispatch","scheduling","deployment","quick-start"],"surfaceModel":"Schematic wiring and rails: thin connective strokes as primary structure, node dots as joints, matte dark surface with bright signal strokes; a faint directional flow implied by line weight, no blur, no glow.","palette":"Signal dark on pale: near-black control surface (#12141a), signal amber (#f5a623) for the trunk, royal violet (#7c5cff) for inbound channels, service green (#28c76f) for routed tracks, and paper white (#f4f2ec) for labels and panel edges.","typography":"Upright officious sans for hierarchy (switchboard tag plates), mono for channel identifiers and route numbers, uppercase labels with letter-spacing for route designators.","desktopComposition":"Wide-panel layout: hero centers the switchboard diagram horizontally with copy beside it; a full-bleed routing rail runs across mid-page; channel and dispatch sections split as two side-by-side rail groups; quick-start closes on a small switch point.","mobileTransformation":"The two cones collapse into stacked inbound columns; channel nodes reorder into a vertical queue that feeds the trunk, and delivery tracks stack as running rows below; route labels move beside each node instead of on horizontal rails.","mediaStrategy":"No local or remote media (assetManifest empty). Media region removed; the switchboard routing diagram is the signature visual, expressed with strokes and nodes only.","forbiddenPatterns":["no centered metric-card hero","no device/browser/editor shells","no faux chat bubbles or message mockups","no generic gradient or particle background","no fake interaction controls"],"compositionFingerprint":"Two inverse stream-cones meeting at a central dispatch node, inbound channels converging then fanning out into parallel delivery rails, with junction switches at each split."},{"id":"orbital-command","name":"Orbital Command","projectMetaphor":"The command center is a fixed core around which independent agent satellites orbit on stable rings; each tool, task type, and schedule cycle holds its own orbital lane at a safe, balanced radius.","signatureVisual":"A radial orbit diagram: a central command core with concentric orbital rings; agent dots and tool nodes sit on distinct rings per task type, while periodic arcs mark the daily-planning and hourly-sweep cycles along the outer band.","heroGeometry":"A central core circle with three concentric orbit rings; task-type nodes placed on the inner ring, tool/discovery nodes on the middle, and schedule-cycle ticks distributed around the outer band.","sectionSequence":["hero","command-core","task-orbits","tool-constellation","schedule-cycles","deployment","quick-start"],"surfaceModel":"Astronomical field sheet: a deep uninterrupted surface as celestial space, thin dashed orbit lines, solid node marks for objects, and a strict hard-edged structure with depth by node size rather than shadow or blur.","palette":"Night-map palette: deep space indigo (#141b33), orbit-line slate (#8a93ad), core coral (#ff5c63), task-ring violet (#8b7cff), tool-ring cyan (#36c5c5), schedule tick gold (#f0b429).","typography":"Sharp geometric sans for headings that echos orbital trajectory (angular cuts), condensed widths for node labels, and small caps with wide tracking for schedule-cycle markers.","desktopComposition":"Centered radial hero where the orbit diagram is the dominant object ring; copy orbits around it rather than beside it; sections radiate outward, each pulling one ring and its band into focus; a circular-end cap resolves quick-start.","mobileTransformation":"The concentric rings are peeled open into a horizontal spoke list: the core becomes the section title, each ring becomes a numbered band scrolling vertically in orbital order, and the outer schedule ticks render as a small legend strip along the bottom.","mediaStrategy":"No local or remote media (assetManifest empty). Media region removed; the orbit/constellation structure is the signature visual, drawn with rings, dashed orbits, and node marks only.","forbiddenPatterns":["no metric-card hero row","no feature-card wall accepting generic copy","no browser/terminal/editor/dashboard shells","no decorative grid or particle effects","no fake satellite-deployment readouts or counters"],"compositionFingerprint":"A fixed center core encircled by three concentric orbit rings carrying distinct node types (task, tool, schedule), with dashed orbital paths and periodic schedule ticks on the outermost band."}],"selectedDirectionId":"lever-counterweight","selectionRationale":"$24"},"designBrief":{"schemaVersion":"dodot-design-brief-v1","selectedDirectionId":"lever-counterweight","projectMetaphor":"A fulcrum is the balance point where many parallel agent workloads pivot toward a shipping horizon. The command center is the fixed pivot; every scheduled task, channel, and deployment is a counterweight that keeps the delivery beam level.","signatureVisual":"A balanced lever beam drawn as horizontal parallel time-lanes that converge on a central triangular fulcrum pivot; weight blocks representing live tasks (Git worktree, Scratch, Manual) sit along each lane, with the beam staying level through parallel orchestration.","compositionFingerprint":"A level ruled baseline runs beneath a central fulcrum pivot whose symmetric parallel time-lanes carry stacked task-weight blocks, with the balance state rendered as a lime alignment tick.","heroGeometry":"A single central fulcrum triangle at the bottom center with two symmetric beam arms extending left and right, each arm a stack of parallel horizontal lanes carrying task-weight blocks.","sectionSequence":["hero","pivot-principle","task-types","channels","architecture","deployment","quick-start"],"surfaceModel":"Paper-and-ink mechanical diagrams: flat matte surfaces separated by sharp structural rules, transparent task blocks floating over guide-lane lines, and a hard-edged shadow only under the pivot and the weight blocks. No blur; seams are lines, not gaps.","palette":"Warm blueprint on off-white: deep ink (#1b1f24), traction orange (#e8590c) as the pivot hot-spot, cool steel blue (#2f5fa8) for lanes, pale paper (#f6f2ea), and a single accent lime (#84cc16) marking the balanced/online state.","typography":"Technical grotesk for headings (inset metrics feel), monospace for lane labels, weights, and channel tags; tabular figures so parallel counts align down columns.","desktopComposition":"Left-anchored 12-column grid: hero places the lever diagram as the dominant right-block while copy and CTA sit on the left shoulder; section layout alternates between a full-width balanced beam and a split pivot/arm pairing; the level state measure spans the base as a ruled baseline.","mobileTransformation":"The horizontal beam is rotated into a single vertical spine of stacked lanes (portrait levers); weight blocks stack in reading order while the pivot moves to the top of the visual as a capstone; per-lane labels move inline; the ruled baseline becomes the page's own bottom edge.","mediaStrategy":"No local or remote media exists (assetManifest is empty). Remove the media region entirely; the lever/weight diagram IS the signature visual, built entirely from layout rules, blocks, and lanes rather than any product screenshot.","evidencePlan":["Render the central fulcrum pivot and symmetric parallel time-lanes as the hero signature visual, with GitHub worktree, Scratch, and Manual task blocks placed along the lanes (evidence: three task types).","Dedicate a task-types section that lists the three task types as weight blocks; enumerate multi-channel communication (WhatsApp, Email, Discord, Telegram, Slack) and daily briefings as lane labels in the channels section.","Surface architecture as MCP-first with tool-discovery and external-agent integration rendered as connection seams on the beam, using only the evidence language (no invented counts).","Show deployment (Docker Compose, Traefik routing, Cloudflare DNS/tunnels) plus calendar-based proactive scheduling as counterweight blocks, and close with the verified quick-start command 'npx @knowsuchagency/fulcrum@latest up'.","Verify desktop and 390px compositions preserve the beam-to-spine concept with different spatial decisions, and confirm no forbidden pattern and no unsupported fact in both zh-CN and en."],"localeContract":{"zh-CN":"AI 驱动的软件交付指挥中心——围绕支点平衡并行的 AI 代理工作负载；核心技术名词（Git 工作树、Scratch 目录、手动任务、MCP、Docker Compose、Traefik、Cloudflare）保留英文原词，说明文字使用自然的简体中文。","en":"AI-powered command center for shipping software—balances parallel agent workloads on a lever pivot; product terms (Git worktrees, Scratch directories, Manual tasks, MCP, Docker Compose, Traefik, Cloudflare) kept verbatim in English with natural English prose."},"forbiddenPatterns":["no centered three-metric-card hero under a slogan","no browser/terminal/dashboard/editor shells","no decorative gradient, glow, or particle fields","no fake charts, tabs, search bars, inputs, or metric widgets","no unsupported product metrics, counts, logos, or testimonials","no desktop columns merely stacked on mobile without recomposition"]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"$25","checks":{"projectFit":{"passed":true,"evidence":"Selected direction lever-counterweight is realized end-to-end: hero SVG lever with central #e8590c fulcrum triangle, symmetric beam arms as parallel steel time-lanes carrying weight blocks for Git worktree / Scratch / Manual / Daily briefings, and a lime balance tick. Palette (#1b1f24/#e8590c/#2f5fa8/#f6f2ea/#84cc16) and typography (technical grotesk headings, mono lane labels, tabular figures) match the palette/typography fields. Section sequence in both locales equals the brief sectionSequence: hero, pivot-principle, task-types, channels, architecture, deployment, quick-start."},"evidenceBound":{"passed":true,"evidence":"Every claim has material backing: parallel Claude Code tasks with kanban/project management/deployment (claim 1), three task types Git worktrees/Scratch dirs/Manual (claim 2), five channels + daily briefings (claim 3), MCP-first with tool discovery and external-agent integration (claim 4; the '100+' count is prudently omitted in favor of 'wide toolset'), Docker Compose / Traefik / Cloudflare (claim 5), desktop apps for macOS/Linux + install script + Claude Code plugin (claim 7), and the verified command 'npx @knowsuchagency/fulcrum@latest up' (readme.commands). No unsupported metrics, counts, logos, or testimonials are presented."},"signatureVisual":{"passed":true,"evidence":"The signature lever visual genuinely exists as inline SVG in the hero of both locales: central orange triangular pivot with a vertical stem, two symmetric parallel lanes per arm, transparent weight blocks (Git 工作树/Git worktrees, Scratch 目录/Scratch dirs, 手动任务/Manual, 每日简报/Daily briefings) floating over guide-lane lines, hard-edged offset shadows, and a lime balance tick at the pivot base. It is built from layout rules, blocks, and lanes per the mediaStrategy, not a product screenshot."},"mobileTransformation":{"passed":true,"evidence":"Both locales implement a genuine beam-to-spine rotation at max-width 820px: the horizontal .beam and .beam-caption are hidden and revealed as a vertical .spine recomposition in the pivot-principle and architecture sections, with a '支点'/'Pivot' capstone triangle at top, stacked spine-rows each carrying a level marker (L1/L2/L3 or MCP/EXT/MEM), an inline weight block, and an inline label, ending with a lime spine-tick. The footer levelline + levelstate ('水平'/'level') resolves the ruled baseline at the page's own bottom edge per mobileTransformation. Verified 27 spine occurrences in zh-CN and 28 in en, with spine-cap 3/3 and levelstate 2/2 in both, so the transformation exists in both locales and is not mere stacking."},"localeParity":{"passed":true,"evidence":"zh-CN and en are structurally equivalent: identical seven-section layout, same hero/beam SVG geometry, same five channels and three deployment items, same quick-start command, and the same .spine mobile recomposition (27 vs 28 spine occurrences, spine-cap and levelstate both present in both). Copy is semantically equivalent and natural, e.g. zh '围绕支点，平衡并行的 AI 代理工作负载。' vs en 'One pivot balancing many parallel agent workloads.' Technical terms are kept in English in zh-CN (Git 工作树, Scratch 目录, 手动任务, MCP, Docker Compose, Traefik, Cloudflare) exactly as the localeContract requires."},"antiTemplate":{"passed":true,"evidence":"No centered three-metric-card hero under a slogan; no browser/terminal/dashboard/editor/device shells; no decorative gradient, glow, or particle field (the only gradient is a hard-edged 50/50 orange/lime split-rule atop the quick-start banner, which is a balance indicator, not a decorative background). The 3-column task grid presents the three evidence-based task types as weight blocks, not a generic feature-card wall. Section surfaces use flat paper-and-ink rules with hard-edged shadows only under blocks/pivot, consistent with the surfaceModel."},"noFakeUi":{"passed":true,"evidence":"No fake charts, tabs, search bars, inputs, metric widgets, counters, or unbacked readouts. The CTA is a real link to github.com/knowsuchagency/fulcrum; the '$ npx @knowsuchagency/fulcrum@latest up' is the verified README install command with '$' as a prompt label; channel tags and 'inbound'/'入站'/'level'/'水平' are text state labels, not interactive controls. QA reports fakeControlCount=0 and emptyLinkCount=0 across all four viewports."}},"issues":[{"code":"evidence-plan-omission-calendar","severity":"warning","locale":"all","description":"evidencePlan item 4 explicitly requested calendar-based proactive scheduling (Google Calendar, CalDAV) to be surfaced as counterweight blocks, but the page only expresses generic schedule-aware planning ('可感知日程的规划' / 'schedule-aware planning') and never names Google Calendar or CalDAV.","repairInstruction":"Optionally add Google Calendar / CalDAV as named lane labels or weight blocks in the architecture or deployment section, supported by the material.json calendar claim, to fully satisfy evidencePlan item 4. Non-blocking."}]},"repairEvidence":[{"attempt":1,"before":{"qaPassed":true,"designReviewApproved":false,"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":1187,"cjkCount":647,"latinLetterCount":313,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":3382,"h1Top":135.1875,"bottomInset":352.984375,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"c909cff99ddedc961e3a38afddfd643f739bbfd206787c90f227b6f5b19d31e4","middle":"7978489746eb921905240989e49cfb2616219cfd83d657bd589ff4760709c835","bottom":"5774dcd73e6bb85acd86b8f63db78f286a715e1e95bf8a96a39e7f4db700b0f1"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":1169,"cjkCount":635,"latinLetterCount":313,"scrollWidth":390,"clientWidth":390,"scrollHeight":4066,"h1Top":103.1875,"bottomInset":364.875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"44850e85cc02730f6e5d233bfd430c6b21375388168ec793ef49481f867d9931","middle":"d827f2433ee040732df93f3f55da7c0f20e9bd74edf65c87b7a7b4956d899de0","bottom":"ffa9dc18520e61309ab5eadbe22b4ad0462ef403473b33b554740428771583ac"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":2798,"cjkCount":0,"latinLetterCount":2287,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":3750,"h1Top":154.375,"bottomInset":353.671875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"b00001ff7e82060e1ac5cc4320dc56539204d48dc51ad20d8ed6ef39686bb947","middle":"6ff9ac6f10beaeac22f124f7ef18f445ad9e27b0085204de3ee726a7490df9e7","bottom":"257e2a9788a1ab07496a898be05dbb8ba515a2ec0da5d42904a1b3128f8cd616"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":3026,"cjkCount":0,"latinLetterCount":2462,"scrollWidth":390,"clientWidth":390,"scrollHeight":4956,"h1Top":122.375,"bottomInset":364.46875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"bbe0ea0e95fe57875b59daf70c40bb72a2e01c660c53f0c15f436cedfafc9ef4","middle":"0b18faac58c23dddbeea4a0ccce330f02aba3ab4a02e010e4e61ebee432f89ff","bottom":"7220e5f1f0e61e72261cea429d707d3330427052cf6f4844176370dc75be9025"},"consoleErrors":[],"networkRequests":[]}]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"revise","summary":"The lever-counterweight direction is faithfully realized: a real inline-SVG lever diagram with a central triangular pivot, symmetric parallel time-lanes, task weight blocks, and a lime balance tick drives the hero and pivot sections, and the requested section sequence, palette, typography, and evidence mapping are supported. However, the brief's mobileTransformation is not achieved and the two locales diverge structurally: zh-CN shows zero mobile recomposition (the beam is hidden with no spine replacement, verified 0 vs 15 'spine' hits in en), and even the en spine is a text list rather than the specified portrait-lever recomposition (pivot capstone, inline lane labels, baseline as the page's bottom edge). These two blocking failures force a revise.","checks":{"projectFit":{"passed":true,"evidence":"Selected direction is lever-counterweight; page implements the project-name-as-composition: hero lever diagram, pivot-principle section, task-types, channels, architecture, deployment, quick-start match the brief sectionSequence exactly. Palette (ink #1b1f24, traction orange #e8590c, steel #2f5fa8, paper #f6f2ea, lime #84cc16), technical-grotesk headings, monospace lane/channel tags, tabular figures all present. Left-anchored 12-col hero with lever as dominant right block matches desktopComposition."},"evidenceBound":{"passed":true,"evidence":"Every factual claim maps to material.json evidence: three task types (Git worktrees, Scratch dirs, Manual), channels (WhatsApp/Email/Discord/Telegram/Slack), daily briefings, MCP-first architecture with tool discovery and external-agent seams, deployment (Docker Compose, Traefik, Cloudflare DNS/tunnels), desktop apps (macOS/Linux), install script, Claude Code plugin, and the verified command 'npx @knowsuchagency/fulcrum@latest up'. The page correctly avoids inventing unsupported counts (it says 'wide toolset' with smart tool discovery rather than repeating the '100+ tools' claim), and mentions kanban/project management consistent with summary."},"signatureVisual":{"passed":true,"evidence":"The signature visual genuinely exists as inline SVG, not a screenshot: the hero '.lever' (viewBox 0 0 560 340) draws a central orange triangular pivot on a ruled baseline, symmetric steel parallel lanes extending left/right, task-weight blocks (Git worktrees, Scratch dirs, Manual, Daily briefings), and a lime balance tick (circle at pivot). A second balanced '.beam' SVG repeats the concept in the pivot-principle section. Meets 'built entirely from layout rules, blocks, and lanes'."},"mobileTransformation":{"passed":false,"evidence":"The brief requires the horizontal beam to rotate into a vertical spine (portrait levers) with the pivot as a capstone, inline lane labels, and the baseline as the page bottom edge. zh-CN implements NONE of this: at max-width:820px the '.beam' is display:none with no replacement, so the pivot-principle visual vanishes and no spine is offered (verified 0 'spine' occurrences in zh-CN vs 15 in en). The en locale shows its '.spine' on mobile, but only as plain two/three-row text lists in the pivot and architecture sections, not the brief's portrait-lever recomposition carrying weight blocks. This collapses toward the forbidden 'desktop merely stacked on mobile without recomposition' pattern."},"localeParity":{"passed":false,"evidence":"zh-CN and en are not structurally equivalent. en implements a mobile '.spine' recomposition (15 occurrences) plus a '.beam-caption' and a 'level' levelstate in the footer; zh-CN contains none of these (0 'spine' occurrences, no beam-caption, no levelstate), so the mobile treatment and the pivot-principle/architecture presentation differ materially between the two locales. Section copy is translated equivalently and naturally when present, but the layout experience diverges."},"antiTemplate":{"passed":true,"evidence":"No centered three-metric-card hero under a slogan (the hero is a lever diagram with left copy). No browser/terminal/dashboard/editor shells or device/desktop mockups. No decorative gradient/glow/particle field; the only gradient is a thin orange-to-lime structural level bar atop the quick-start block, not a decorative background. No fake charts, tabs, search bars, or metric widgets. Composition is a mechanism (lever/balance), not a template landing page."},"noFakeUi":{"passed":true,"evidence":"All interactive elements are real: the CTA links to the actual GitHub repo, the quick-start code block is the verified README command 'npx @knowsuchagency/fulcrum@latest up', and the source link resolves to github.com/knowsuchagency/fulcrum. Dots, ticks, and level marks are non-interactive decorative state indicators, not controls. QA report confirms fakeControlCount=0 and emptyLinkCount=0."}},"issues":[{"code":"MOBILE_RECOMPOSITION_MISSING","severity":"blocking","locale":"zh-CN","description":"The brief's mobileTransformation (horizontal beam rotated into a vertical portrait-lever spine, pivot as top capstone, per-lane labels inline, ruled baseline as the page's bottom edge) is not implemented in zh-CN. The pivot-principle '.beam' SVG is simply display:none under 820px and the hero lever keeps its horizontal geometry, with no spine replacement (0 'spine' occurrences in zh-CN vs 15 in en). This renders mobile as desktop columns merely stacked, which is a forbidden pattern.","repairInstruction":"In zh-CN.html add a portrait-lever recomposition for mobile: reveal a vertical '.spine' in the pivot-principle (and architecture) sections with stacked lane rows (portrait levers) carrying the worktree/scratch/manual weight labels inline, position the pivot as a top capstone, and let the ruled baseline resolve at the page bottom edge — mirroring the en spine but with the lever weight semantics restored. Do not simply hide the beam."},{"code":"LOCALE_STRUCTURAL_DIVERGENCE","severity":"blocking","locale":"all","description":"zh-CN and en diverge structurally rather than being equivalent recompositions: en ships a mobile '.spine' list (in pivot-principle and architecture), a '.beam-caption', and a 'level' levelstate in the footer, while zh-CN omits all of these. A reviewer given both pages cannot confirm the two locales present the same design experience; the mobile transformation exists only in en.","repairInstruction":"Bring zh-CN to parity with en (or apply an equivalent recomposition to both): add the same mobile spine/caption/levelstate treatment to zh-CN so both locales show the identical lever-to-spine recomposition and balance-state cueing, with all text naturally localized."},{"code":"MOBILE_SPINE_IS_GENERIC_LIST","severity":"warning","locale":"all","description":"Even in en, the mobile '.spine' is a plain two/three-row text list (e.g. '01 Pivot', '02 Parallel lanes', '03 Delivery beam') rather than the brief's requested portrait-lever recomposition that carries weight blocks with the pivot as a capstone. It conveys the concept but does not fully realize the beam-to-spine rotation or the inline weight-block carrying.","repairInstruction":"Optionally upgrade the en (and resulting zh-CN) spine to a genuine portrait lever: stacked lane rows each holding a weight block with an inline label, the orange pivot triangle moved to the top as a capstone, and the lime balance tick retained at the bottom edge to echo the ruled baseline."}]}},"after":{"qaPassed":true,"designReviewApproved":true,"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":1210,"cjkCount":665,"latinLetterCount":313,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":3415,"h1Top":135.1875,"bottomInset":352.796875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"c909cff99ddedc961e3a38afddfd643f739bbfd206787c90f227b6f5b19d31e4","middle":"42bffacbbc37bd88fc13a1a014df0d2ff6996932c80c61ad8d073e4f0c3ef7ab","bottom":"0e1b1c3b7b0072938b2abf8653e534737c21fc480617accd1201e7ad1b43650c"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":1313,"cjkCount":730,"latinLetterCount":335,"scrollWidth":390,"clientWidth":390,"scrollHeight":4448,"h1Top":103.1875,"bottomInset":363.9375,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"44850e85cc02730f6e5d233bfd430c6b21375388168ec793ef49481f867d9931","middle":"33fbb8327f2bfc317d64f4f1af5860ca45cc0672a2e9ea176376713aa84d71ae","bottom":"d25d32c23a18e3d509387d4e3a59ceda17a3fb27bda7784e4a87671af547c169"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":2798,"cjkCount":0,"latinLetterCount":2287,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":3750,"h1Top":154.375,"bottomInset":353.671875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"b00001ff7e82060e1ac5cc4320dc56539204d48dc51ad20d8ed6ef39686bb947","middle":"6ff9ac6f10beaeac22f124f7ef18f445ad9e27b0085204de3ee726a7490df9e7","bottom":"257e2a9788a1ab07496a898be05dbb8ba515a2ec0da5d42904a1b3128f8cd616"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":3029,"cjkCount":0,"latinLetterCount":2484,"scrollWidth":390,"clientWidth":390,"scrollHeight":5014,"h1Top":122.375,"bottomInset":364.265625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"bbe0ea0e95fe57875b59daf70c40bb72a2e01c660c53f0c15f436cedfafc9ef4","middle":"200714116f592ded375b75f686fec8c2b648d97515178e4bd42a1cbb6e3f9437","bottom":"2d634ea60c0d44dec6509c6bed5c9b04526dc0a4b4a4382f8be133b2aca5037d"},"consoleErrors":[],"networkRequests":[]}]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"$26","checks":{"projectFit":{"passed":true,"evidence":"Selected direction lever-counterweight is realized end-to-end: hero SVG lever with central #e8590c fulcrum triangle, symmetric beam arms as parallel steel time-lanes carrying weight blocks for Git worktree / Scratch / Manual / Daily briefings, and a lime balance tick. Palette (#1b1f24/#e8590c/#2f5fa8/#f6f2ea/#84cc16) and typography (technical grotesk headings, mono lane labels, tabular figures) match the palette/typography fields. Section sequence in both locales equals the brief sectionSequence: hero, pivot-principle, task-types, channels, architecture, deployment, quick-start."},"evidenceBound":{"passed":true,"evidence":"Every claim has material backing: parallel Claude Code tasks with kanban/project management/deployment (claim 1), three task types Git worktrees/Scratch dirs/Manual (claim 2), five channels + daily briefings (claim 3), MCP-first with tool discovery and external-agent integration (claim 4; the '100+' count is prudently omitted in favor of 'wide toolset'), Docker Compose / Traefik / Cloudflare (claim 5), desktop apps for macOS/Linux + install script + Claude Code plugin (claim 7), and the verified command 'npx @knowsuchagency/fulcrum@latest up' (readme.commands). No unsupported metrics, counts, logos, or testimonials are presented."},"signatureVisual":{"passed":true,"evidence":"The signature lever visual genuinely exists as inline SVG in the hero of both locales: central orange triangular pivot with a vertical stem, two symmetric parallel lanes per arm, transparent weight blocks (Git 工作树/Git worktrees, Scratch 目录/Scratch dirs, 手动任务/Manual, 每日简报/Daily briefings) floating over guide-lane lines, hard-edged offset shadows, and a lime balance tick at the pivot base. It is built from layout rules, blocks, and lanes per the mediaStrategy, not a product screenshot."},"mobileTransformation":{"passed":true,"evidence":"Both locales implement a genuine beam-to-spine rotation at max-width 820px: the horizontal .beam and .beam-caption are hidden and revealed as a vertical .spine recomposition in the pivot-principle and architecture sections, with a '支点'/'Pivot' capstone triangle at top, stacked spine-rows each carrying a level marker (L1/L2/L3 or MCP/EXT/MEM), an inline weight block, and an inline label, ending with a lime spine-tick. The footer levelline + levelstate ('水平'/'level') resolves the ruled baseline at the page's own bottom edge per mobileTransformation. Verified 27 spine occurrences in zh-CN and 28 in en, with spine-cap 3/3 and levelstate 2/2 in both, so the transformation exists in both locales and is not mere stacking."},"localeParity":{"passed":true,"evidence":"zh-CN and en are structurally equivalent: identical seven-section layout, same hero/beam SVG geometry, same five channels and three deployment items, same quick-start command, and the same .spine mobile recomposition (27 vs 28 spine occurrences, spine-cap and levelstate both present in both). Copy is semantically equivalent and natural, e.g. zh '围绕支点，平衡并行的 AI 代理工作负载。' vs en 'One pivot balancing many parallel agent workloads.' Technical terms are kept in English in zh-CN (Git 工作树, Scratch 目录, 手动任务, MCP, Docker Compose, Traefik, Cloudflare) exactly as the localeContract requires."},"antiTemplate":{"passed":true,"evidence":"No centered three-metric-card hero under a slogan; no browser/terminal/dashboard/editor/device shells; no decorative gradient, glow, or particle field (the only gradient is a hard-edged 50/50 orange/lime split-rule atop the quick-start banner, which is a balance indicator, not a decorative background). The 3-column task grid presents the three evidence-based task types as weight blocks, not a generic feature-card wall. Section surfaces use flat paper-and-ink rules with hard-edged shadows only under blocks/pivot, consistent with the surfaceModel."},"noFakeUi":{"passed":true,"evidence":"No fake charts, tabs, search bars, inputs, metric widgets, counters, or unbacked readouts. The CTA is a real link to github.com/knowsuchagency/fulcrum; the '$ npx @knowsuchagency/fulcrum@latest up' is the verified README install command with '$' as a prompt label; channel tags and 'inbound'/'入站'/'level'/'水平' are text state labels, not interactive controls. QA reports fakeControlCount=0 and emptyLinkCount=0 across all four viewports."}},"issues":[{"code":"evidence-plan-omission-calendar","severity":"warning","locale":"all","description":"evidencePlan item 4 explicitly requested calendar-based proactive scheduling (Google Calendar, CalDAV) to be surfaced as counterweight blocks, but the page only expresses generic schedule-aware planning ('可感知日程的规划' / 'schedule-aware planning') and never names Google Calendar or CalDAV.","repairInstruction":"Optionally add Google Calendar / CalDAV as named lane labels or weight blocks in the architecture or deployment section, supported by the material.json calendar claim, to fully satisfy evidencePlan item 4. Non-blocking."}]}},"changedFiles":["artifact/zh-CN.html","artifact/en.html"]}],"provenance":{"executor":"opencode","model":"deepseek/deepseek-v4-flash","opencodeVersion":"1.1.58","promptVersion":"dodot-showcase-deepseek-v4","inputHash":"aa81225075a8fc48f4515be3943a3bfb538cb0fbed10e8dc3ada313e61095b4c","artifactHash":"ddeffb2cb9b80f45889c62069225fd067e0e717d4fa340140d78ec3d3ad1f75b","designSkill":"dodot-showcase-design"},"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":1210,"cjkCount":665,"latinLetterCount":313,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":3415,"h1Top":135.1875,"bottomInset":352.796875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"c909cff99ddedc961e3a38afddfd643f739bbfd206787c90f227b6f5b19d31e4","middle":"42bffacbbc37bd88fc13a1a014df0d2ff6996932c80c61ad8d073e4f0c3ef7ab","bottom":"0e1b1c3b7b0072938b2abf8653e534737c21fc480617accd1201e7ad1b43650c"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":1313,"cjkCount":730,"latinLetterCount":335,"scrollWidth":390,"clientWidth":390,"scrollHeight":4448,"h1Top":103.1875,"bottomInset":363.9375,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"44850e85cc02730f6e5d233bfd430c6b21375388168ec793ef49481f867d9931","middle":"33fbb8327f2bfc317d64f4f1af5860ca45cc0672a2e9ea176376713aa84d71ae","bottom":"d25d32c23a18e3d509387d4e3a59ceda17a3fb27bda7784e4a87671af547c169"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":2798,"cjkCount":0,"latinLetterCount":2287,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":3750,"h1Top":154.375,"bottomInset":353.671875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"b00001ff7e82060e1ac5cc4320dc56539204d48dc51ad20d8ed6ef39686bb947","middle":"6ff9ac6f10beaeac22f124f7ef18f445ad9e27b0085204de3ee726a7490df9e7","bottom":"257e2a9788a1ab07496a898be05dbb8ba515a2ec0da5d42904a1b3128f8cd616"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":6,"sectionCount":7,"textLength":3029,"cjkCount":0,"latinLetterCount":2484,"scrollWidth":390,"clientWidth":390,"scrollHeight":5014,"h1Top":122.375,"bottomInset":364.265625,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"bbe0ea0e95fe57875b59daf70c40bb72a2e01c660c53f0c15f436cedfafc9ef4","middle":"200714116f592ded375b75f686fec8c2b648d97515178e4bd42a1cbb6e3f9437","bottom":"2d634ea60c0d44dec6509c6bed5c9b04526dc0a4b4a4382f8be133b2aca5037d"},"consoleErrors":[],"networkRequests":[]}]}},"generatorVersion":"opencode-1.1.58:deepseek/deepseek-v4-flash:dodot-showcase-deepseek-v4","publishedAt":"2026-08-20T06:25:45.292Z"},"rawExtraction":{"projectRevisionId":"cmt2zh0v400vh62713zj4pmw4","projectVersion":1,"sources":[{"canonicalKey":"github:knowsuchagency/fulcrum","role":"primary","revisionVersion":1,"url":"https://github.com/knowsuchagency/fulcrum"}],"facts":[{"key":"repository_owner","value":"knowsuchagency","evidence":[{"path":"repository.owner","excerpt":"knowsuchagency"}]},{"key":"repository_name","value":"fulcrum","evidence":[{"path":"repository.name","excerpt":"fulcrum"}]},{"key":"description","value":"What if Openclaw, Vibe Kanban, Vibetunnel, and Dokploy had a baby?","evidence":[{"path":"repository.description","excerpt":"What if Openclaw, Vibe Kanban, Vibetunnel, and Dokploy had a baby?"}]},{"key":"primary_language","value":"TypeScript","evidence":[{"path":"repository.language","excerpt":"TypeScript"}]},{"key":"topics","value":"agents, ai, coding","evidence":[{"path":"repository.topics","excerpt":"agents, ai, coding"}]},{"key":"source_count","value":"1","evidence":[{"path":"projectRevision.sources","excerpt":"github:knowsuchagency/fulcrum"}]}],"taxonomy":{"category":"development_tools","subcategory":"data_ai_tools","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"What if Openclaw, Vibe Kanban, Vibetunnel, and Dokploy had a baby?"}]},"lifecycle":{"stage":"active","confidence":0.75,"evidence":[{"path":"repository.pushedAt","excerpt":"2026-08-16T06:30:52.000Z"}]},"userIntents":[{"slug":"build_software","label":"构建或改进软件","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"What if Openclaw, Vibe Kanban, Vibetunnel, and Dokploy had a baby?"}]},{"slug":"automate_work","label":"自动化工作流程","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"What if Openclaw, Vibe Kanban, Vibetunnel, and Dokploy had a baby?"}]},{"slug":"create_content","label":"创作内容或设计","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"What if Openclaw, Vibe Kanban, Vibetunnel, and Dokploy had a baby?"}]},{"slug":"analyze_data","label":"分析与理解数据","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"What if Openclaw, Vibe Kanban, Vibetunnel, and Dokploy had a baby?"}]}],"readme":{"headings":["Project Fulcrum","What It Does","MCP-First Architecture","Proactive Digital Concierge","Intelligent Message Handling","Persistent Memory","Daily Planning","Scheduled Briefings","Hourly Sweeps","Quick Start","Desktop App","Install Script (Remote Servers)","Claude Code Plugin","Features","Kanban Board & AI Assistant","Task Types","Parallel Agent Orchestration","Projects","Project Workspace","Task Dependencies"],"commands":["npx @knowsuchagency/fulcrum@latest up","npx @knowsuchagency/fulcrum@latest up"]},"changeSet":[{"field":"repository","beforeHash":"85f1cbfa642d6992633aefad9db2bbd242e8f0aba7c2127f61585cdc247db245","afterHash":"24b40d6e2cf4c258610027e492986c9f73f05cb6a85a5571a39701e7940024b8"}]},"publishedAt":"2026-08-16T12:31:30.118Z","updatedAt":"2026-08-21T13:26:51.057Z","summary":{"id":"cmt2zh0v600vj6271lwxl4yq8","projectType":"product","oneLine":"并行编排 AI 代理，集中管理开发任务。","overview":"Fulcrum 是一个面向技术型独立开发者和 CTO 的 AI 驱动指挥中心，用于并行运行多个 Claude Code 任务，通过看板、项目管理和部署功能集中管理开发流程。它支持 Git 工作树、Scratch 目录和手动任务，并通过 WhatsApp、Email 等渠道与 AI 助手交互，提供主动式日程规划和每日简报。采用 MCP 优先架构，暴露 100+ 工具，支持外部代理集成。","highlights":["并行代理编排","MCP 优先架构","多渠道消息集成","生产级部署"],"bestFor":["技术型独立开发者","需要并行 AI 代理的 CTO","希望远程管理开发流程的团队"],"caveats":["需要配置 Claude Code 等代理","桌面应用仅支持 macOS 和 Linux","部分功能依赖外部服务（如消息平台）"],"categorySuggestion":"development_tools","subcategorySuggestion":"coding_agents","lifecycleStages":["idea_requirements","frontend","backend_data","deployment_growth"],"audienceIntents":["build","integrate","operate","evaluate"],"confidence":0.85,"evidence":[{"claim":"Fulcrum 是一个 AI 驱动的软件交付指挥中心，支持并行运行多个 Claude Code 任务，并提供看板、项目管理和部署功能。","sourceType":"readme","locator":"https://github.com/knowsuchagency/fulcrum"},{"claim":"提供三种任务类型：Git 工作树、Scratch 目录和手动任务，以适应不同的工作流。","sourceType":"readme","locator":"https://github.com/knowsuchagency/fulcrum"},{"claim":"支持通过 WhatsApp、Email、Discord、Telegram 或 Slack 与 AI 助手交互，并自动发送每日简报。","sourceType":"readme","locator":"https://github.com/knowsuchagency/fulcrum"},{"claim":"采用 MCP 优先架构，暴露 100+ 工具，支持智能工具发现和外部代理集成。","sourceType":"readme","locator":"https://github.com/knowsuchagency/fulcrum"},{"claim":"提供 Docker Compose 生产部署，支持 Traefik 路由和 Cloudflare DNS/隧道。","sourceType":"readme","locator":"https://github.com/knowsuchagency/fulcrum"},{"claim":"支持日历集成（Google Calendar 和 CalDAV），AI 助手可感知日程进行规划。","sourceType":"readme","locator":"https://github.com/knowsuchagency/fulcrum"},{"claim":"提供桌面应用（macOS 和 Linux）以及 CLI 安装方式。","sourceType":"readme","locator":"https://github.com/knowsuchagency/fulcrum"}],"publishedAt":"2026-08-17T13:28:38.896Z"},"github":{"url":"https://github.com/knowsuchagency/fulcrum","ownerAvatarUrl":"https://avatars.githubusercontent.com/u/11974795?v=4","starsCount":90,"forksCount":24,"language":"TypeScript","syncedAt":"2026-08-17T13:25:41.060Z","license":null,"defaultBranch":"main","archived":false,"disabled":false,"lastChangedAt":"2026-08-16T06:30:52.000Z","missing":false},"tags":[],"updates":[]},"entryPoint":"discovery","claim":{"state":"unclaimed","verified":false},"initialView":"beautified","community":{"viewer":null,"state":{"likesCount":0,"creativeCount":0,"followersCount":0,"commentsCount":0,"liked":false,"creative":false,"followed":false},"comments":{"comments":[],"nextCursor":null}}}]}],"$L27"]