Repository navigation
docs: assign corporate-master resolution ownership - #83
Merged
seonghobae merged 1 commit intoAug 26, 2026
Merged
seonghobae merged 1 commit into
seonghobae merged 1 commit into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
seonghobae
merged commit Aug 26, 2026
f592e7d
into
cursor/ontology-catalog-plane-90aa
3 of 4 checks passed
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
7 tasks
seonghobae
pushed a commit
that referenced
this pull request
Sep 9, 2026
The merge order in this document rests, in every item, on receiving a current-head opencode-agent APPROVE. Before rewriting that order I checked whether the rest of the org waits for the same receipt. It does not. This repository's protected main has had no merge since #66 on 2026-08-17. #83 merged on 2026-08-26 but into #73's branch, not main. That is 23 days, 35 open PRs, and 22 merges in the repository's whole history. The org is not stalled over the same window: 7,454 merges total, several on 2026-09-09 itself. The stall is local to this repo. Sampling the most recent merge in six in-scope repositories, none of the six carried an opencode-agent APPROVED verdict on the head that merged, and four had no reviews at all. The clearest case is the governance owner itself: .github #2028 merged at af7c6e3 while its only opencode-agent verdict was CHANGES_REQUESTED bound to 1d9c70b. Recorded with its limits: base refs were not checked, so some of those may be stack merges into a PR branch rather than protected main, and the sample is one PR per repo across six repos. This is written as a decision for the maintainer, not an action. Either the rest of the org under-applies the gate or this repo is waiting on a receipt that will not arrive, and neither is an agent's call. Lowering the gate, self-approving, and bypassing protection stay forbidden here exactly as everywhere else in this document. What the measurement adds is the cost of the wait: main has carried HIGH CVE-2026-69247 for 23 days, with 35 PRs queued behind it, and that is urgent independent of how the gate question is settled. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QpbqAeggRho3fQA1gn34UY
seonghobae
pushed a commit
that referenced
this pull request
Oct 1, 2026
…-17 — the stall is 53 days, not 23 21시간 유휴 뒤 루프가 21회 발화했는데 `main`도 92개 PR head도 하나도 움직이지 않았습니다. 그래서 이 문서가 들고 있던 날짜 수치를 다시 재어 보았고, 기준 자체가 틀려 있었습니다. `main`의 tip `e48aa13`은 **`#34`**(committer 2026-08-09T17:52:09Z)이고 그 직전 커밋은 2026-07-13의 `#12`입니다. 이 문서는 마지막 병합을 `#66`(2026-08-17T16:37:09Z) 이라고 적어 왔지만 **`#66`은 `main`에 없습니다** — squash든 merge commit이든 `main`에 올랐다면 로그에 나타나야 하는데 없습니다(`#83`이 `main`이 아니라 `#73`의 브랜치로 병합된 것과 같은 패턴일 수 있습니다). 따라서 날짜와 PR을 둘 다 정정하고, 남아 있던 "23일째" 세 군데와 2026-09-14의 "28일" 주석을 현재 값으로 갱신했습니다 — 2026-08-09 → 2026-10-01 = **53일**입니다. headline 수치가 30일 understated되어 있었습니다. 비용의 성격도 바뀐 것을 적었습니다. `#28`은 여전히 `draft: true` / `mergeable_state: blocked` / head `103c9eb`이고 `updated_at`은 2026-09-30T10:42:44Z 입니다. 즉 어제 12:43Z의 green(trivy-fs 포함)은 **하루 동안 유효한 채 병합되지 않은 상태**입니다. 증거가 없어서 막힌 것이 아니라 증거가 완비된 채 멈춰 있습니다. 왜 멈춰 있는지는 단정하지 않았습니다 — owner의 순서가 `#81`을 먼저 두고 있고 `#81` 자기 head의 required check 결과는 아직 읽지 못했습니다. 표 46블록 파이프 수 일관, 펜스 17/17 균형으로 검증했습니다. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QpbqAeggRho3fQA1gn34UY
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Assigns the ecosystem corporate-master entity-resolution contract to Semantic
Data Portal's existing ontology/catalog governance plane. This PR is stacked on
#73 because that branch introduces the tenant-scoped catalog identity, alias,
concept-binding, stewardship, and persistence boundary that the contract owns.
Contract
sdp.corporate-master-resolution/v1.unique,miss, andtie.unique;missandtieremain unbound.limitations, candidates, and result digest.
weight, first-match tie break, catalog mutation, or executable-endpoint claim.
Ecosystem boundary evidence
identity, aliases, ontology terms, mappings, and stewardship.
corporate binding.
identity authority.
contract after an implementation is released and pinned.
Verification
uv run --extra dev pytest -q tests/test_catalog_plane.py tests/test_catalog_plane_sql.py tests/test_migrations.py— 25 passed.git diff --check— clean.APA 7th form in ADR 0002.
Implementation remains a follow-up requiring an accepted method ADR and
synthetic unique/miss/tie recovery tests. Until then consumers fail closed as
unavailable rather than restore local heuristics.