---
id: public-site-and-comms/001
title: Consider porting land-of-lor/docs/historic/ artifacts into the deliverables log as backdated entries
epic: public-site-and-comms
state: backlog
priority: 3
blocked_by: []
estimate: M
created: 2026-08-06
updated: 2026-08-06
claimed_by: null
claimed_at: null
delivers: []
review_artifact: null
---

## What to do

`land-of-lor/docs/historic/` holds real, dated artifacts of this project's history — the Gen-1
interactive tools (`lor-periodic-table.html`, `lor-kernel-sim-v0.html`, `lor-graph-of-changes.html`)
and the 19 July "great inversion" explainer doc among them. These are exactly what the
deliverables log exists to hold: dated project history, made public. Some of them may be worth
porting into `deliverables/` as earlier, backdated entries rather than staying invisible in a
human-owned docs folder. **Not a site-archive folder** — that concept is explicitly dropped; this
is about the existing deliverables log, extended backwards.

This is deliberately **not ready** — Kris picks which specific documents (if any) get ported, and
when. Do not act on this without that direction.

## The one design detail this will raise (flagged now, not solved now)

Deliverable numbering currently starts at 001 and counts forward. Backdated entries slotting in
*before* 001 need either a date-based ordering scheme instead of (or alongside) sequential
numbers, or a numbering convention that tolerates prepending (e.g. negative/zero-indexed, or a
separate date-sort that doesn't care about the number at all). **Settle this at port time, once
there's a concrete document to port and a concrete date to give it — not now, in the abstract.**

## Definition of done

Not applicable until Kris names specific documents to port. When he does: each ported entry gets
real deliverable frontmatter (`number` or equivalent, `date` matching the artifact's actual
origin, `title`, `summary`, `epic`, `artifacts`), and the numbering question above is resolved
concretely for that entry.

## Where the work lands

This workspace repo (`deliverables/`), reading source material from `land-of-lor/docs/historic/`
per the human-owned/read-only rule in this workspace's `CLAUDE.md` — read only, never move or
alter the source docs themselves.

## Docs to read first

`land-of-lor/docs/historic/` (the actual candidate artifacts); `deliverables/README` conventions
(the existing three entries, for format); this workspace `CLAUDE.md`'s "Who edits what" section.