Skip to content

fix(use-cases): drop the discovery-call closer from card abstracts#57

Merged
aggre merged 1 commit into
mainfrom
fix/use-cases-trim-discovery-closer
Jun 2, 2026
Merged

fix(use-cases): drop the discovery-call closer from card abstracts#57
aggre merged 1 commit into
mainfrom
fix/use-cases-trim-discovery-closer

Conversation

@yumemayu
Copy link
Copy Markdown
Member

Summary

The trailing "Book a 30-minute discovery call to see how it fits your X" / 「30 分の会話から、御社の…に乗るか確認します」 sentence in every use case abstract was reading as sales copy on the /use-cases/ index card grid (the abstract is what each card shows in the listing).

Trim the closer across all 11 use cases in both locales, leaving only the descriptive sentences. The Discovery Call is still surfaced via the page chrome and the bottom partner CTA card on the detail page; we don't need to re-pitch it inside the abstract.

For abstracts whose descriptive content depended on the 30-min clause (…を 30 分の会話から検討します。), the sentence is rewritten as a descriptive statement instead of dropped (…構成です。 / …検証できる構成です。 etc.).

Files touched (22)

Each use case README.{ja,en}.md — abstract only, no body / frontmatter / title changes.

  • ai-audit-log-proof
  • defi-bridge-verification
  • delegated-treasury
  • financial-data-exfiltration
  • kyc-aml-selective-disclosure
  • multi-agent-workflows
  • rag-content-provenance
  • rag-source-attestation
  • supply-chain-component-provenance
  • supply-chain-esg
  • x402-commerce

Sample diff

- abstract: "KYC 属性を共有せずに、属性ごとの ZK 証明だけで規制要件を満たす。30 分の会話から、御社の KYC/AML 経路にフィットするかを一緒に確認します。"
+ abstract: "KYC 属性を共有せずに、属性ごとの ZK 証明だけで規制要件を満たします。"
- abstract: "Satisfy KYC/AML requirements with per-attribute ZK proofs — no shared customer data. Book a 30-minute discovery call to see if Lemma fits your pipeline."
+ abstract: "Satisfy KYC/AML requirements with per-attribute ZK proofs — no shared customer data."

Test plan

  • After site rebuild, /ja/use-cases/ cards show only the descriptive line — no "30 分の会話" closer on any of the 11 cards
  • /use-cases/ (EN) same
  • Detail pages unaffected — they don't render the abstract
  • Partner CTA card at the bottom of detail pages still shows Discovery Call as the primary action (unchanged)

🤖 Generated with Claude Code

The trailing 'Book a 30-minute discovery call to see how it fits your X' /
'30 分の会話から、御社の…に乗るか確認します' sentence in every use case
abstract was reading as sales copy on the /use-cases/ index card grid (the
abstract is what each card shows in the listing).

Trim the closer across all 11 use cases in both locales, leaving only the
descriptive sentences. The Discovery Call is still surfaced via the page
chrome and the bottom partner CTA card on the detail page; we don't need
to re-pitch it inside the abstract.

For abstracts whose descriptive content depended on the 30-min clause
('…を 30 分の会話から検討します。' / '…を、30 分の会話から検討します。'),
the sentence is rewritten as a descriptive statement instead of dropped
('…構成です。' / '…検証できる構成です。' etc.).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Member

@aggre aggre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed by Hermes Agent (CTO delegate).

+22 / -22, 22 files (11 use cases × 2 locales)

Trims discovery-call closer from use case card abstracts. Descriptive content preserved, sales pitch removed.

Verdict: APPROVE

@aggre aggre merged commit 81cef55 into main Jun 2, 2026
@aggre aggre deleted the fix/use-cases-trim-discovery-closer branch June 2, 2026 20:34
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