2026-06-08 13:55:27 +02:00
|
|
|
# history/
|
|
|
|
|
|
history+workplan: CoreArchitectureBlueprint review; SHARD-WP-0005 hardening
Records the critical review (history/260615-...) and establishes SHARD-WP-0005
to fold its findings (A-1, B-1..B-3, C-1..C-3, D-1..D-4) into the blueprint:
correctness (state re-frame, identity/equivalence split, consistency model),
scale (incremental-first union, equivalence indexing, cache invalidation),
elegance (orthogonal spectra, layered provenance, common-case projection,
policy module), security/history scaling, and a known-open-problems section.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 01:01:19 +02:00
|
|
|
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.
|
2026-06-08 13:55:27 +02:00
|
|
|
|
history+workplan: CoreArchitectureBlueprint review; SHARD-WP-0005 hardening
Records the critical review (history/260615-...) and establishes SHARD-WP-0005
to fold its findings (A-1, B-1..B-3, C-1..C-3, D-1..D-4) into the blueprint:
correctness (state re-frame, identity/equivalence split, consistency model),
scale (incremental-first union, equivalence indexing, cache invalidation),
elegance (orthogonal spectra, layered provenance, common-case projection,
policy module), security/history scaling, and a known-open-problems section.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 01:01:19 +02:00
|
|
|
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.
|
2026-06-08 13:55:27 +02:00
|
|
|
|
history+workplan: CoreArchitectureBlueprint review; SHARD-WP-0005 hardening
Records the critical review (history/260615-...) and establishes SHARD-WP-0005
to fold its findings (A-1, B-1..B-3, C-1..C-3, D-1..D-4) into the blueprint:
correctness (state re-frame, identity/equivalence split, consistency model),
scale (incremental-first union, equivalence indexing, cache invalidation),
elegance (orthogonal spectra, layered provenance, common-case projection,
policy module), security/history scaling, and a known-open-problems section.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 01:01:19 +02:00
|
|
|
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 01:56:42 +02:00
|
|
|
| 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 22:28:29 +02:00
|
|
|
| 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) |
|
