Skip to content

ro: mint has_quality, has_interpretation, interprets (0xA0–0xA2) - #261

Merged
AdaWorldAPI merged 1 commit into
mainfrom
claude/ro-mint-quality-interpretation
Aug 10, 2026
Merged

AdaWorldAPI merged 1 commit into
mainfrom
claude/ro-mint-quality-interpretation

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

Completes the clinical-compartment predicate union measured downstream: of the six predicates in use across the compartment slot maps, is_a / part_of / has_phenotype / disease_has_location were already minted — these three were the whole remainder.

byte name curie
0xA0 has_quality RO:0000086
0xA1 has_interpretation SCTID:363713009
0xA2 interprets SCTID:363714003

has_quality is plain RO. The observation pair has no RO term carrying the observation-model semantics, so their CURIEs use the registered SCTID: prefix exactly as OBO ontologies publish such xrefs — the byte is the normalized predicate; the CURIE records provenance and is never a second dispatch key.

The unminted-byte refusal guard now derives its probe from the palette max instead of hardcoding 0xA0, so the next mint moves the probe rather than failing it (which is what this mint did to the hardcoded probe — the guard fired correctly).

10 tests pass.

🤖 Generated with Claude Code


Generated by Claude Code

Completes the clinical-compartment predicate union measured downstream:
is_a/part_of/has_phenotype/disease_has_location were already minted; these
three were the whole remainder. has_quality is plain RO (RO:0000086). The
observation pair has no RO term, so their CURIEs use the registered SCTID:
prefix as OBO ontologies do for such xrefs — the byte is the normalized
predicate, the CURIE records provenance, never a second dispatch key.

The unminted-byte refusal guard now derives its probe from the palette max
instead of hardcoding 0xA0, so the next mint moves the probe rather than
failing it.

Generated by [Claude Code](https://claude.ai/code)
@cursor

cursor Bot commented Aug 10, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_698f620f-1a43-4a60-8b37-0d6f65d58a96)

@AdaWorldAPI
AdaWorldAPI merged commit be30674 into main Aug 10, 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.

2 participants