Changelog

Este conteúdo não está disponível em sua língua ainda.

The LLMO Framework follows a content-versioning policy designed for a documentation site that evolves: only changes to concepts and content claims trigger a version bump. Design refinements, copy edits, and translation backfills happen continuously without version churn.

Versioning Policy

Bump	Triggers
MAJOR	Breaking change to the framework — a component is renamed or removed, scoring scale changes, fundamental terminology shifts
MINOR	New framework component, new guide article, new case study, new research entry
PATCH	Substantive section added to an existing article (a new sub-heading, example block, or checklist item)

The current version, the package.json version field, and the git tag vX.Y.Z always agree.

The full machine-readable history lives in CHANGELOG.md on GitHub. Below is the human-readable summary.

v1.3.1 — 2026-05-08

Headline: The case study that bragged about closing five coherence surfaces failed at six. ken found the sixth in the time it took to read the v1.3.0 page.

Fixed

src/styles/custom.css — removed .site-title::after { content: 'v1.0' }. A version badge was hardcoded into the header CSS at the project’s first commit and never updated. v1.0 → v1.1 → v1.2 → v1.3 — four releases survived without anyone noticing the visual layer was lying. The Footer (added in v1.2.0) reads from src/data/version.ts and is now the single canonical display surface.
Self-Audit case study — added a Postscript: The Sixth Surface section in EN + JA. The case study originally enumerated five surfaces of drift; the postscript records the sixth (CSS visual layer), found within an hour of publication, and generalizes the lesson: when you enumerate “every place this fact lives,” include the visual layer, not just the data layer.

Why

Every release of this framework reveals what the previous release didn’t see. v1.1.0 introduced Coherence Signals; v1.2.0 violated them on llms.txt; v1.3.0 documented the violation as a case study; v1.3.1 documents the case study’s own incompleteness. The pattern is the framework working — the only way to be sure you’ve found every coherence surface is to publish your enumeration and let other readers find what you missed.

v1.3.0 — 2026-05-08

Headline: The framework records its own coherence failure as a first-class case study.

New

Case study: When the Framework Author Violates the Framework — this site’s own self-audit. v1.1.0 introduced Coherence Signals; v1.2.0 shipped with five out-of-sync version surfaces (package.json, version.ts, CHANGELOG.md, EN/JA changelog pages, git tags). The codex second-pass review caught the irony in 4 minutes. The case study documents the drift, the detection, the 10-step fix, and three patterns that generalize: release process is itself a coherence surface; tooling earns its keep when bypassed; frameworks don’t exempt their authors.
Coherence Signals: Release Process is a Coherence Surface — new sub-section that generalizes the v1.2.0 episode. Frames a version number as a fact in the LLMO sense, then defines the four-step prevention pattern: generate from one source / make version visible at runtime / gate on cross-checks / second-pass review before tagging.

Why this is its own release

We chose to record the episode as a first-class case study rather than bury it in a changelog footnote. Two reasons. First, it generalizes beyond release coherence — any framework author shipping coherence violations in their own coherence framework is the same failure mode at different scales. Second, hiding the failure would itself be a coherence violation between what we say (transparency, single source of truth) and what we do.

v1.2.0 — 2026-05-08

Headline: Two field-tested patterns added — Identity-as-Code and Citation Preferred — plus codex-second-pass cleanup that brings the site itself into Coherence Signals compliance.

Expanded

Authority Signals — added Identity-as-Code: One Person, One @id, Cited Everywhere. Defines the per-page-duplication anti-pattern and the URL-based @id pattern, with rules for multi-language sites (shared Person/Organization, per-language WebSite). Three new checklist items.
Retrieval Signals — added two sub-sections under llms.txt:
- Add a “Citation Preferred” Section: name canonical entry points per topic so AI cites the right URL when several cover the same subject.
- Generate llms.txt at Build Time: drop manual maintenance; build script reads the content collection and emits llms.txt, llms-full.txt, and /ai/publications.md from one source of truth.
Checklist additions for both: @id strategy and llms.txt drift prevention.

Fixed (Coherence cleanup)

public/llms.txt (8 languages) — was stuck at “5 components / 15 points” while the rest of the site advertised the new 6th component. The site that defines Coherence Signals violated Coherence Signals on its own AI-readable surface. Updated to 6 components / 18 points; added Coherence Signals, Two-Pass Review, Self-Audit case study, Changelog entries.
/ai/*.md (8 languages) — same 5→6 component update. Canonical host normalized (www.propel-lab.co.jp → propel-lab.co.jp); Kindle 4→14 books / Qiita 39,000+→80,000+ aligned with profile data.
CI gate: new scripts/verify-json-ld.mjs runs in GitHub Actions before deploy. Verifies every <script type="application/ld+json"> block parses, every page emits the site-wide Organization/WebSite/Person, and the 404 page does not carry article-shaped schema.
framework/coherence-signals — added boundary clarification with Structural Formatting at the top of the article (“Structural asks ‘is each surface well-formed?’; Coherence asks ‘do surfaces agree?’”).
framework/overview — Citation Signals checklist scope corrected to “content pages” (site root and error pages exempt).
case-studies/propel-lab-self-audit — each finding now labeled with its source site (kaoriq / propel-lab / both); description and title clarify two-site scope.
scripts/bump-version.sh — SUMMARY now passed via env vars (immune to ' and " in the input); idempotency guard refuses to overwrite an existing version section or git tag; python heredocs are quoted.
src/components/Head.astro — multi-language fallback detection: when a non-EN locale URL serves the English fallback content, JSON-LD inLanguage and OG og:locale are set to en to match the actual body language. The 404 page no longer carries TechArticle.

Why

Three sites (mypcrig.com, legacydram.com, kenimoto.dev) implementing the framework hit the same two failure modes within a single review session: identity fragmentation across languages and pages, and llms.txt entries that quietly drifted out of sync with the actual content. Both patterns now have explicit framework guidance instead of being folded into checklists.

A codex second-pass review on the v1.1.0 release surfaced the most ironic miss possible: the site that defines Coherence Signals had llms.txt stuck at “5 components / 15 points” while the rest of the site advertised the new 6th component. That’s fixed.

v1.1.0 — 2026-05-08

Headline: The framework grew from 5 to 6 components. Maximum score is now 18 (was 15).

New

6th framework component: Coherence Signals — the discipline of making sure the same fact tells the same story across every surface AI reads (HTML, JSON-LD, Markdown, llms.txt, /ai/*.md). Added because too many real-world implementations ship with cross-file drift that slips past every other LLMO check.
LLMO Audit: Two-Pass Review — a methodology for auditing your own LLMO implementation. Self-review first, then an independent AI agent in a read-only sandbox. Includes the Codex CLI invocation pattern with the </dev/null stdin gotcha and a structured prompt template.
Case study: Self-Audit on the Propel-Lab Reference Site — 20 findings (11 caught by self-review, 9 caught only by the second pass), including silent JSON-LD drops the team had been running with for months. Demonstrates that implementing LLMO and auditing LLMO are different attention modes.

Expanded

Structural Formatting — two new sections:
- Scope JSON-LD Entities to Page Subject: site-wide layout emits only Organization / WebSite / Person; page-relevant entities (Service[], Book[], MusicGroup, FAQPage) belong on the pages they describe.
- Verify the JSON-LD Actually Emits: output verification as a discrete framework concern. Build-time checks for silent drops; integration with Schema.org Validator and Rich Results Test.

Re-scored

Framework Overview — restructured for 6 components, scoring band recalibrated to an 18-point maximum, self-assessment checklist extended with three new Coherence-related checks.

v1.0.0 — 2026-04-30

Initial public release of the LLMO Framework documentation site with 5 framework components, 8 languages, and full sections on Getting Started, the Framework, Case Studies, and Research.

How to Track Updates

Watch the GitHub repository: kenimo49/llmo-guide
Subscribe to releases: GitHub releases are tagged vX.Y.Z matching the version above
RSS / Atom: Starlight’s built-in feed (when enabled) follows pubDate, which is bumped on framework changes only