Skip to content

docs(release): Lore product identity and the v0.10.3 search contract [roadmap:v0.10.3] - #67

Merged
tcballard merged 4 commits into
mainfrom
claude/rac-v0.10-implementation-12w6e1
Jun 12, 2026
Merged

docs(release): Lore product identity and the v0.10.3 search contract [roadmap:v0.10.3]#67
tcballard merged 4 commits into
mainfrom
claude/rac-v0.10-implementation-12w6e1

Conversation

@tcballard

@tcballard tcballard commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

Documentation-and-decisions follow-up to the v0.10.x merge: positions Lore as the product, records the naming and search-quality decisions, and pins the v0.10.3 implementation contract.

Adds:

  • README rewritten around the grounding story: Lore is the product, RAC — Requirements as Code — is the open-source engine underneath; the package, CLI, and MCP server keep the rac name for now
  • ADR-036 (Accepted): the Lore product identity — names, the canonical relationship statement, and the explicit rule that renaming any shipped surface is a separate future decision
  • ADR-037 (Accepted): token-boundary search matching, replacing raw substring matching (the lore vs Explorer collision becomes a named regression case)
  • ADR-038 (Accepted): body-text search tier with additive snippet fields; embeddings, fuzzy matching, stemming, and opaque scoring permanently rejected for Core
  • rac/roadmaps/v0.10.x-guide/v0.10.3-search-quality.md: the pinned implementation contract for both ADRs — one Core matching implementation, additive response fields, re-pinned goldens, and a measurement re-run gating the demo recording
  • Working corpus pointer in CLAUDE.md moved to v0.10.3

Roadmap / ADR Trace

Roadmap:

  • rac/roadmaps/v0.10.x-guide/v0.10.3-search-quality.md (new)

Decisions:

  • rac/decisions/adr-036-lore-product-identity.md (new, Accepted)
  • rac/decisions/adr-037-token-boundary-search-matching.md (new, Accepted)
  • rac/decisions/adr-038-body-text-search-tier.md (new, Accepted)

Scope

Included

  • README repositioning and factual corrections: the shipped tool name is get_summary (an earlier draft said get_repository_summary), config blocks use the rac-guide server label consistent with docs/mcp.md and demo.md, and the Claude Desktop / Cursor block carries an absolute --root (GUI clients do not spawn servers with the repo as working directory)
  • The three decision artifacts and the roadmap contract

Excluded

  • Any implementation of the search changes (that is v0.10.3 work, gated on this contract)
  • Any rename of the package, CLI, or MCP server (explicitly reserved by ADR-036)
  • The demo recording and measurement (happen after v0.10.3 lands, per the roadmap's sequencing)

Verification

rac validate rac/                      # 103 valid, 0 invalid
rac relationships rac/ --validate      # 0 issues
rac review rac/                        # no priority 1-2 findings

All artifact IDs minted via rac new; ADR-036/037/038 resolve by alias; relationship sections cross-link the decisions, the design, and the roadmap.

Review Path

  1. README.md — the Lore/RAC framing
  2. rac/decisions/adr-036-lore-product-identity.md
  3. rac/decisions/adr-037-*.md, adr-038-*.md — the search semantics decisions
  4. rac/roadmaps/v0.10.x-guide/v0.10.3-search-quality.md — the implementation contract
  5. CLAUDE.md — corpus pointer

Notes For Reviewer

  • ADR-037 makes the search semantics change an announced behavior change: goldens re-pin in the implementing PR, and the grounding measurement re-runs before the demo is recorded — the roadmap sequences the recording after that gate.
  • The README's 90-second demo link is still a placeholder anchor by design; it is filled at launch.

Implementation Process

Implemented with AI assistance under the roadmap contract. Final scope, review, and acceptance decisions were made by the maintainer.

…:v0.10.0]

Rewrites the README around the grounding story: Lore is the product,
RAC (Requirements as Code) is the open-source engine underneath, and
the package, CLI, and MCP server keep the rac name for now.
…:v0.10.0]

Records the two-step search quality plan as proposed decisions:
ADR-037 (token-boundary matching) and ADR-038 (body-text tier with
snippets), candidates for a v0.10.x extension.
….10.3]

Accepts ADR-037 (token-boundary matching) and ADR-038 (body-text tier
with snippets) and pins their implementation contract: one Core
matching implementation, additive snippet fields, re-pinned goldens,
and a measurement re-run before the demo recording. Points the working
corpus at v0.10.3.
@tcballard
tcballard merged commit 306fb0b into main Jun 12, 2026
2 checks passed
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.

1 participant