Skip to content

docs: identifier durability — recorded cases and the machine-readable remedy - #1

Open
damienriehl wants to merge 1 commit into
CatholicOS:mainfrom
damienriehl:docs/identifier-durability
Open

docs: identifier durability — recorded cases and the machine-readable remedy#1
damienriehl wants to merge 1 commit into
CatholicOS:mainfrom
damienriehl:docs/identifier-durability

Conversation

@damienriehl

Copy link
Copy Markdown

Adds an Identifier durability section to docs/schema.md plus a new open question, and fixes the README's scheme example to match docs/schema.md and the data (the old martyrologium_romanum_cei_2004 example exists nowhere in the registry — that recorded contradiction is itself one of the section's cases).

No existing identifier is changed, deprecated, or renamed by this PR. All argument lives in the position paper — this PR only demonstrates this repository's recorded cases and the remedied form: CatholicOS/foundation-docs#58 (discussion: CatholicOS/foundation-docs#57).

🤖 Generated with Claude Code

https://claude.ai/code/session_01MoZuH8vKiwL2rsX3a1zSqc

… remedy

Cites the position paper 'Identifier Durability: Machine-Readable Canonical IRIs'.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MoZuH8vKiwL2rsX3a1zSqc
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@damienriehl, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: fac050f3-6b81-4d13-b87e-e30ee8ebb432

📥 Commits

Reviewing files that changed from the base of the PR and between ecb147b and 29c8102.

📒 Files selected for processing (2)
  • README.md
  • docs/schema.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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