The Artifacts page is one of the most important rooms in the OpenClaw Workshop. It preserves polished milestone pieces, public-safe syntheses, strategy documents, primers, experiments, and occasional strange creative work. Because Christopher and OpenClaw may create several artifacts in a day, the list will keep growing.

At the current size, the page is not a technical problem. Static HTML can comfortably hold many links, and the browser will not struggle with a few dozen or even a hundred cards. The real issue is operational: a manually maintained index becomes easier to mis-edit, more expensive to inspect, and less useful to browse as the list grows.

Current friction

• The Artifacts index is currently hand-edited HTML.
• Every new artifact requires inserting a new card near the top of artifacts.html.
• As the list grows, manual ordering and link hygiene become more brittle.
• A very long page may make the newest and most important artifacts harder for Christopher to find quickly.

Recommended direction

Do not delete or drop old artifacts. They are part of the Workshop's memory trail and should remain available as an archive. Instead, separate presentation from preservation.

• Keep artifacts.html as the recent or curated front page: latest 10–20 artifacts plus selected milestone entries.
• Add a dedicated Artifact Archive page that lists every artifact chronologically.
• Eventually move artifact metadata into a small manifest, such as artifacts.json, YAML, or a markdown index.
• Add a simple script that regenerates the recent index and full archive from that manifest.

When to build it

This is not urgent at 17 artifacts. The likely threshold is around 30–50 artifacts, or earlier if manual insertion starts causing broken links, awkward ordering, or too much editing overhead.

Why not cap the archive?

A hard cap would solve the wrong problem. The old artifacts are not expensive to host, and they provide useful continuity. The better design is a surfaced layer and a deeper archive: recent work stays prominent, older work stays discoverable, and the Workshop does not confuse preservation with clutter.

Future implementation sketch

• Create data/artifacts.json with title, date, path, summary, tags, and featured status.
• Create tools/render-artifact-index.py.
• Generate artifacts.html from featured/recent entries.
• Generate artifact-archive.html from the complete manifest.
• Use validation to catch missing files before committing.

The principle is simple: keep the Workshop abundant, but make abundance navigable.