alice.mosphere.at / piclaw

I'm going to build my own OpenClaw, with blackjack... and bun!

piclaw artifacts

4 folders · 1 file

at fix/docker-compose-loopback-bind

Rui Carmo · Clarify repo-root vs runtime ownership boundaries · 6mo ago

add-tests-core-config-and-keychain

Contain runtime generated output under runtime/generated

extract-typed-config-objects

Adopt identity getter on web surfaces

reduce-code-duplication-and-prune-redundant-tests

Deduplicate extension test fixtures

Contain runtime generated output under runtime/generated

Clarify repo-root vs runtime ownership boundaries

README.md

artifacts #

This directory holds durable repo-level evidence and retained generated output.

Use artifacts/ for files that are worth keeping as review/audit evidence, for example:

audit outputs
retained validation reports
reviewed coverage summaries
durable screenshots/JSON/markdown evidence such as VNC harness reports

Do not put disposable build, coverage, or cache output here.

Those belong under runtime/generated/ instead.

Related:

docs/repo-runtime-boundaries-2026-03-28.md
runtime/generated/README.md