BitShovel
中

GitHub weekly chart, official API, and README · First found 2026-08-29

Archify: turn code and system descriptions into maps

Turn a codebase or system description into a map, then search nodes, trace connections and export it. Archify keeps the map in structured JSON for later revisions.

Archify: from descriptions to a structured map
Discovered 2026-08-29; purpose reviewed Sep 9, 2026; illustrated: 2026-09-09 · Open full-size image

中文

Structure the relationships before rendering

Start with a codebase or a written system description. The agent produces typed JSON, which Archify compiles into HTML/SVG. Relationships remain in a structured source file that can be revised and rendered again.

中文

Inspect connections authored in the map

The viewer searches nodes and traces upstream, downstream and routed connections already recorded in the map. These authored relationships do not establish runtime impact.

Share a self-contained HTML file or export PNG/SVG. The article retains the author’s MCO example, while the illustrated pages explain the workflow from input to inspection and export.

The discovery date remains 2026-08-29. This explanation follows a 2026-09-09 reading of the author’s README; later feature descriptions are not backdated to the historical chart observation.

Archify: trace connections and export
Discovered 2026-08-29; purpose reviewed Sep 9, 2026; illustrated: 2026-09-09 · Open full-size image
MCO Runtime Architecture example export published by the Archify author
The author’s MCO runtime architecture example, retained in full. It demonstrates an output style, not Archify’s own system architecture. · Open full-size image
Sources and notes

sources中文

Sources and notes

Retained summary and context

GitHub weekly chart and Star counts show attention only; the description is a maintainer self-description. Not proof of quality, adoption, or commercial value.

Sources and evidence · 2 links

Each link has a purpose and scope. Link counts do not establish independent confirmation; direct support applies only to the statements specified below.

Source timeline
  1. · GitHub weekly Trending ranked #5, recording 11,099 stars for the week.
Collection record

First discovered:

Collection and source publication have distinct dates.

Editorial record

Corrected

· Beijing time (UTC+8)

The title now names the use or discussion covered in the article, removing collection ranks, unqualified promotional wording and overstatement. Original sources, historical prices and dates remain; this edit does not represent a new release or price change.

Sources and full record

This dates our review of the wording and sources, not a project release or product update.

Full record: before, after and sources (JSON)

Corrections and feedback