Commit d2e4aa8

<span class="section-anchor" id="case-reproduce"></span>

Start with the [interactive HTML](cases/mco-runtime.architecture.html) and its [typed JSON source](cases/mco-runtime.architecture.json). No installation is needed to inspect these files. Follow the Answer Transport → Invocation Artifacts relationship, then compare it with the pinned code links below: the edge describes data ownership, not a direct function call.

To render the same authored input locally, use Node.js 18 or newer, Git, and a fresh directory. These commands pin the stable Archify checkout used for this replay; they do not run MCO or invoke a model:

git clone https://github.com/tt-a1i/archify.git archify-mco-case

cd archify-mco-case

git checkout --detach ba701d20a55ed6f139484d9ead7ff45671fe40eb

git clone https://github.com/mco-org/mco.git mco-source

git -C mco-source checkout --detach 9f1a1cf1afdc04d7b5406782b40dfec76d9bc798

node archify/bin/archify.mjs render architecture docs/cases/mco-runtime.architecture.json mco-replay.html --repo-root mco-source

Open `mco-replay.html` in a browser. This replays an existing model; it does not rediscover the repository or establish a new validation or visual-review result. Check that the provider adapters, answer transport, invocation runtime and artifact writer are still distinct, and use the source links to verify who calls the decoder and who writes files. Rendering with another Archify revision may produce different output.

<span class="section-anchor" id="case-use-your-repo"></span>

[Choose your agent and install Archify →](start.html?type=architecture&input=repository#install)

Use this prompt in your configured coding agent, from the repository you want it to inspect:

This scope suits a review of component responsibilities and file ownership. For exact message order, use a sequence diagram; for a live incident or latency claim, bring logs, traces or measurements. An architecture picture alone cannot answer those questions. Your repository may have different components; the MCO names are evidence for this case only.

<span class="section-anchor" id="case-reproduce"></span>

先打开[交互 HTML](cases/mco-runtime.architecture.html)和[结构化 JSON 源文件](cases/mco-runtime.architecture.json)。查看成品不需要安装。沿 Answer Transport → Invocation Artifacts 这条关系阅读，再对照下方固定版本的代码链接：这条边表达数据职责，不代表直接函数调用。

要在本地渲染同一份输入，需要 Node.js 18 或更新版本、Git 和一个新目录。以下命令固定本次重放使用的 Archify 稳定版源码，不会运行 MCO 或调用模型：

git clone https://github.com/tt-a1i/archify.git archify-mco-case

cd archify-mco-case

git checkout --detach ba701d20a55ed6f139484d9ead7ff45671fe40eb

git clone https://github.com/mco-org/mco.git mco-source

git -C mco-source checkout --detach 9f1a1cf1afdc04d7b5406782b40dfec76d9bc798

node archify/bin/archify.mjs render architecture docs/cases/mco-runtime.architecture.json mco-replay.html --repo-root mco-source

用浏览器打开 `mco-replay.html`。这是对已有模型的重放，不会重新分析仓库，也不代表取得了新的验证或视觉审核结论。检查 provider 适配器、答案传输、调用运行时和产物写入器是否仍然分开，再沿源码链接核对谁调用解码器、谁写文件。换用其他 Archify 版本，输出可能不同。

<span class="section-anchor" id="case-use-your-repo"></span>

[选择 Agent 并安装 Archify →](start.html?type=architecture&input=repository#install)

在要分析的仓库里，把下面的提示词交给已配置好的 Coding Agent：

这个范围适合审查组件职责和文件归属。要看精确消息顺序，应使用时序图；要判断线上事故或延迟，需要日志、trace 或测量数据，架构图本身无法回答。你的仓库可能有不同组件，MCO 的组件名称只属于本案例的证据。

<a class="type-more" href="cases/mco-runtime.html">

<span data-en="From repository evidence to an architecture diagram" data-zh="从仓库证据到架构图">From repository evidence to an architecture diagram</span>

<span class="type-more-sub" data-en="Read the MCO case · replay the source · try your own repo" data-zh="阅读 MCO 案例 · 复现源文件 · 换成自己的仓库">Read the MCO case · replay the source · try your own repo</span>

<span class="type-more-arrow" aria-hidden="true">→</span>

</a>

Base: `ba701d20a55ed6f139484d9ead7ff45671fe40eb` (main, 2026-10-19).

Candidate: the commit containing this receipt. Checks ran on its complete working diff before commit; no product or output changes followed.

The homepage navigation's Install Skill anchor resolved to `#quickstart`, although Start already supports agent and install-scope selection. The architecture type panel linked only to the general gallery. The existing MCO case had pinned evidence and limits but no replay command or direct repository-mode installation action. These are inspection findings, not measured conversion failures.

- Homepage Install Skill opens localized Start at `#install`.

- The architecture type panel links to the existing localized MCO case.

- The case provides the original HTML and JSON, a replay pinned to both repositories, an adaptation prompt, boundaries and repository-mode Start.

- Original artifact/source bytes and all generation behavior remain unchanged.

- `npm --prefix website run check`: 0 errors, 0 warnings, one existing clipboard deprecation hint.

- Default build: 14 pages. `npm --prefix website test`: 79 passed, 7 browser tests skipped by their opt-in conditions, 0 failed.

- Cloudflare build: 14 pages. `ARCHIFY_SITE_TARGET=cloudflare node --test website/test/mco-source-case.test.mjs website/test/seo-content.test.mjs website/test/deployment-target.test.mjs`: 18 passed.

- Existing homepage and MCO real Chrome browser suites: 2 passed, 0 skipped on each host build. Covers English/Chinese, light/dark, widths 1440/390/320, text bounds, section navigation, language continuity, gallery links and artifact load.

- Replay command ran successfully using this Archify base and the existing local MCO checkout containing `9f1a1cf1afdc04d7b5406782b40dfec76d9bc798`, passed as `--repo-root`. It produced `/tmp/archify-mco-replay.html`. The initial probe without `--repo-root` failed as designed; the documented commands now include cloning and pinning that repository. The full network clone commands were not repeated for the replay.

- Ego keyboard checks: focus homepage Install Skill and Enter → `/archify/start.html#install`; focus Chinese homepage MCO link and Enter → `/archify/zh/cases/mco-runtime.html`; case repository-mode action and Enter → Start preserving `type=architecture&input=repository#install`. No installation was executed.

- `git diff --check`: passed.

Browser-suite screenshots, inspected by Codex (not human acceptance):

- [Desktop replay, English light, 1440×1000](desktop-replay.png)

- [Mobile replay, Chinese light, 390×1000](mobile-zh-replay.png)

- [Mobile adaptation prompt, English dark, 320×1000](mobile-en-prompt.png)

Screenshots are bounded page tiles; their top may continue a preceding tile. Text remains readable and within the viewport. Full local browser manifests and tiles are in ignored `website/.browser-evidence/{github,cloudflare}/`.

No new tracking was added. Existing Start session events were unchanged. This PR establishes usable links and content, not SEO ranking, traffic growth or installation conversion improvements. Live production acceptance awaits an authorized merge and deployment.

const start = nodes(article).find(node => node.tagName === 'a' && attr(node, 'href')?.includes('input=repository'));

assert.ok(start, 'the case offers a repository-mode installation next step');

const startUrl = new URL(attr(start, 'href'), base);

assert.equal(startUrl.pathname, new URL(`${prefix}start${cloudflare ? '' : '.html'}`, origin).pathname);

assert.equal(startUrl.searchParams.get('type'), 'architecture');

assert.equal(startUrl.hash, '#install');

const replay = nodes(article).find(node => node.tagName === 'pre');

assert.ok(text(replay).includes('--repo-root mco-source'), 'replay can verify declared repository evidence');