# history/

Archived material and the project's **meta-history**: finished/canceled workplans kept for
the record, plus durable **reviews, critical assessments, and decision records** — the
reasoning behind the specs, captured at a point in time.

Use a `yymmdd-` prefix. Archived material is **out of scope** for regular tasks (consult only
for research or diagnostics); assessment/review records are point-in-time and may seed active
workplans, but are not edited after the fact — supersede with a new dated record and link back.

Distinct from the **coordination journal** (a runtime Git-backed record of *content* change
flows inside an information space, an INTENT domain concept); `history/` is the *project's own*
design evolution.

| Date | Record | Subject |
|------|--------|---------|
| 2026-06-15 | `260615-core-architecture-blueprint-review.md` | Critical review of `spec/CoreArchitectureBlueprint.md` (commit 9b5b393); inputs to `SHARD-WP-0005` |
| 2026-06-15 | `260615-core-architecture-blueprint-review-2.md` | Round-2 review of the hardened blueprint (post-`SHARD-WP-0005`, f21b7b5); inputs to `SHARD-WP-0006` |
| 2026-06-15 | `260615-reuse-surface-contributions.md` | shard-wiki's reuse-surface registrations, proposed gaps (G1/G2), and consumptions (`SHARD-WP-0013` T3) |