Skip to content

docs: refresh project status after going public and the site launch - #80

Merged
jposluns merged 1 commit into
mainfrom
claude/docs-status-refresh
Jul 7, 2026
Merged

docs: refresh project status after going public and the site launch#80
jposluns merged 1 commit into
mainfrom
claude/docs-status-refresh

Conversation

@jposluns

@jposluns jposluns commented Jul 7, 2026

Copy link
Copy Markdown
Owner

You flagged that CLAUDE.md still said Phase 1 was in progress. It was. This is a full accuracy pass over the non-recipe docs, driven by an audit of every documentation/config file against the actual state (import, curation, e-book, public-readiness, and the live site all shipped; repo public).

Corrected

  • CLAUDE.md: replaced the stale "Active work / Phase 1 in progress on claude/phase-1-import" section with a current "Project status"; present-tensed the intro (published, public, live site); fixed the "static-site phase begins" note.
  • GOVERNANCE.md: "Publication gate (Phase 4)" marked satisfied; states the repo is now public.
  • docs/about-this-archive.md: "Looking ahead" (a pending proposal) replaced with "The website" (live at new.blimacake.com).
  • docs/phase-1-runbook.md: banner marking it completed/historical; corrected the "check out claude/phase-1-import" and "repo stays private" lines.
  • _meta/taxonomy.yml: comment no longer says "three below / added incrementally"; states all 16 categories are populated (also fixed a grammar defect).
  • .working/resume.md and .working/README.md: added the 2026-07-07 state (e-book, public-readiness, live site, repo public); listed resume.md/review-todo.md in the index.
  • .claude/rules/README.md and project-overview.md: past-tensed the "optional site phase"; noted the collection is already public and live.
  • docs/site-deploy.md + .github/workflows/pages.yml header: setup marked complete (was written as pending).
  • tools/README.md: documented the curation, build, and guard tools (it listed only 5 of ~16).
  • ADR 0001: added a superseding note for the go-public decision; the decision record itself is left intact (ADRs are immutable).

Contact email

Standardized on jeff@posluns.ca per your decision: updated GOVERNANCE.md and the copyright-concern issue template (README/NOTICE already used it).

Also

Added the live site link to README.md (a top callout and in the browse section).

Verified

No recipe content changed. Dash guard clean; markdownlint 0 errors across all 13 changed Markdown files; taxonomy.yml and pages.yml still valid YAML. Left genuinely historical records (dated CHANGELOG entries, import-log, ADR context) as-is.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HpG2vky2XhDtfc6y16TRis


Generated by Claude Code

Bring the non-recipe docs in line with reality: import, curation, the
e-book, public-readiness, and the live website have all shipped and the
repo is public.

- CLAUDE.md: replace the stale 'Active work / Phase 1 in progress'
  section with a current 'Project status'; present-tense the intro; fix
  the static-site 'when it begins' note.
- GOVERNANCE.md: publication gate marked satisfied; repo public.
- docs/about-this-archive.md: 'Looking ahead' -> 'The website' (live).
- docs/phase-1-runbook.md: marked completed/historical (branch merged).
- _meta/taxonomy.yml, .working/resume.md, .working/README.md,
  .claude/rules/*: past-tense the completed phases; note the live site.
- docs/site-deploy.md + pages.yml header: setup complete.
- tools/README.md: document the curation, build, and guard tools.
- ADR 0001: add a superseding note for the go-public decision (record
  left intact).
- Standardize the public contact on jeff@posluns.ca (GOVERNANCE, issue
  template); add the live site link to README.

No recipe content changed.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HpG2vky2XhDtfc6y16TRis
@jposluns
jposluns merged commit 1c18d0e into main Jul 7, 2026
4 checks passed
@jposluns
jposluns deleted the claude/docs-status-refresh branch July 7, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants