docs: maintain durable product-technical gap baseline

[seonghobae]

Scope

Maintains the durable Orgmetra commercialization baseline and records causal evidence behind governance, security, buyer-workflow, operability, research, scientific and release gaps. The baseline is planning/traceability evidence, not merge authorization, and deliberately avoids copying fast-staling run/check snapshots into the document.

Exact current-head evidence — 2026-09-03

• Current live PR head: 465abcb6c1d021f3d0aa6b94468adf1bc848502d.
• Current protected base: develop@5c5cd3258c34fd2cbbdacd7420afd05f2617aa29.
• This writer first adopted protected fix(ci): skip docs-only changes for Foundation CI and Recovery Rehearsal Quality #166 as two-parent non-force commit 2f888ecf5fc2df5dade3fc94b8361674f614196c; protected fix(ci): skip docs-only changes for Foundation CI and Recovery Rehearsal Quality #166 changes only Foundation CI and Recovery Rehearsal Quality docs-only admission filters. Fresh protected→writer comparison after the subsequent baseline update is 195 commits ahead, 0 behind.
• 465abcb6… updates docs/product-technical-gap-baseline.md with the current protected product anchor and a distinct ASG-02 auditable assignment category correction gap. The baseline now treats people: add auditable assignment category correction provenance #164/feat(people): add assignment category correction provenance #165 as Active PR truth downstream of Add explicit non-heuristic primary/secondary (TFT) tag to assignment_record #162/feat: record explicit assignment category #163 rather than implying that explicit category creation also ships correction semantics.
• ASG-01 remains Active PR, not Shipped truth: Draft feat: record explicit assignment category #163 owns explicit primary | concurrent_secondary creation/history semantics and legacy_unspecified preservation without heuristic inference.
• ASG-02 remains Active PR, not Shipped truth: dependent Draft feat(people): add assignment category correction provenance #165 owns immutable predecessor closure → replacement Assignment → normalized supersession, purpose-bound Keyverse authorization, high-impact evidence, audit/outbox and durable replay. Its current hosted evidence is non-terminal and it cannot integrate before feat: record explicit assignment category #163.
• The feat(people): add assignment category correction provenance #165 current repair additionally fails closed on caller-defined AssignmentCorrectionMutationCommand and Keyverse AuthorizationDecision runtime subtypes before semantic replay or PostgreSQL I/O; this is represented in the baseline as active child evidence, not protected capability.
• docs/product-technical-gap-baseline.md is not a deterministic manifest.json member, so this baseline-only edit requires no invented manifest reseal. The protected-base adoption itself reused the exact protected workflow blobs rather than rewriting them.
• Every push resets hosted check/review authority. Predecessor evidence does not transfer across this writer push or the dependent feature pushes.
• REL-01 remains P0: there is still no published Orgmetra release and no protected head proves the complete release evidence set.

External .github governance/security owner details in the baseline retain their separately dated doctoring until refreshed in that owner lane; this Orgmetra run did not overwrite them with assumptions.

Highest-leverage current gaps

1. GOV-01 — P0: satisfiable protected-branch admission and owner-plane/live-ruleset convergence without synthetic approval or routine admin bypass.
2. SEC-01 — P0: authoritative Dependency Review availability through the canonical .github owner, with authenticated immutable comparison and actual pinned action execution.
3. REL-01 — P0: one integrated protected Orgmetra head with complete governance/security/operability/buyer-workflow evidence before version/release publication.
4. ASG-01 — P1 buyer truth: integrate explicit Assignment category through Add explicit non-heuristic primary/secondary (TFT) tag to assignment_record #162/feat: record explicit assignment category #163 with exact-head evidence.
5. ASG-02 — P1 buyer truth: after ASG-01 integrates, non-force restack/retarget feat(people): add assignment category correction provenance #165 and prove PostgreSQL/full-People/idempotency/security/review GREEN plus atomic canonical documentation/inventory handoff.
6. UX/API/VAL — P1: move from design/foundation truth to a deployable Job Architecture → Candidate Evidence → Hiring Decision → Employee Profile → Validation vertical slice with accessibility, i18n, recovery and p95 ≤20 ms evidence where applicable.

Source-of-truth rule

The baseline does not store its own current head, every active PR head, run IDs, queue counts, review snapshots or mergeability because those values self-invalidate. PR metadata and GitHub live refs are authoritative for exact-current-head integration decisions. Reviews/checks/evidence do not transfer across a push, retarget, parent integration, restack or lifecycle transition.

No release, protected-branch merge, certification claim, synthetic approval, administrator bypass or evidence substitution is authorized by this PR.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6266320a-d62c-4576-9ff6-4ac7ecbbcc6a

📥 Commits

Reviewing files that changed from the base of the PR and between c3289c8 and 4a07d0d.

📒 Files selected for processing (1)

• docs/product-technical-gap-baseline.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

제품·기술 격차 기준 문서를 2026-08-26 기준으로 갱신했다. 조직 ruleset, control anchor, 활성 capability, 구매자 격차, 실행 검증 조건과 운영 진단을 최신 상태로 변경했다.

Changes

제품·기술 격차 기준

Layer / File(s)	Summary
저장소 보호 및 실행 기준 docs/product-technical-gap-baseline.md	조직 ruleset 18156473과 PR #119 control anchor를 기록했다. Issue #89의 상업 통제 격차를 3건으로 확장했다. 실행 루프가 유효 ruleset과 현재 PR 그래프를 재조회하도록 갱신했다.
기능 상태 및 주요 격차 docs/product-technical-gap-baseline.md	PR #116–#119의 활성 capability를 추가했다. 목적 바운드 HR 반출, 권위적 성과목표, 접근성, 권위적 릴리스 운영을 최고 가치 구매자 격차로 정의했다.
운영 진단 및 참고문헌 docs/product-technical-gap-baseline.md	리뷰 트리아지와 제공자 복구 진행을 2026-08-25/26 기준 네 가지 항목으로 재작성했다. References (APA 7th) 제목과 목록은 유지했다.

Estimated code review effort: 2 (간단) | ~10분

Merge Risk: 🟡 Moderate · up to 4a07d

The baseline still contains an inaccurate section heading, a conflicting open-PR count, and unclear workflow rerun instructions. These can mislead readers about repository status and recovery steps, so the PR needs follow-up before merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 제품·기술 격차 기준 문서를 지속적으로 갱신하는 주요 변경 사항을 정확하고 간결하게 설명합니다.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/product-technical-gap-baseline

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[devin-ai-integration]

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[seonghobae]

@opencode-agent Please review the current unchanged head against protected develop. Local exact-head verification: all owned package suites pass at 100% statement/branch coverage.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[seonghobae]

Single-writer handoff for the next baseline iteration: fresh #163 source/schema review on 2026-09-03 found a buyer-visible Assignment correction gap now owned by #164 (people: add auditable assignment category correction provenance). #163 itself now explicitly limits ADR 0015 to category create/read semantics; it does not claim a linked category-correction workflow. Please record #164 as a dependent successor to ASG-01 rather than marking it shipped or copying baseline ownership onto #163. Evidence: assignment_record is currently the immutable multiple-membership fact identity; the generic bitemporal guard permits recorded_to closure, but there is no normalized predecessor→replacement correction link or governed People correction command. #164 acceptance requires close→replacement→supersession provenance, atomic purpose/evidence/audit/outbox/idempotency, and revalidation of Assignment portfolio/coverage/capacity invariants. Do not advance #164 ahead of #163 protected integration.

[seonghobae]

ASG-01 handoff update for the next baseline iteration: canonical dependent PR #165 now has the correction domain, normalized supersession migrations, purpose-bound People command, PostgreSQL adapter/replay ledger, and a buyer-facing POST /v1/assignment-records/{assignment_record_id}/category-corrections service OpenAPI/ASGI surface. Its child workflow now runs the complete People API suite under the service's existing 100% statement/branch coverage threshold. The feature remains Draft and stacked on #163; no protected-branch shipment is claimed.

The #165 traceability owner now records the exact architecture/ERD/UML/security/operability/recovery handoff. Please keep docs/product-technical-gap-baseline.md single-writer-owned here and, after #163 integrates and #165 is non-force restacked, carry ASG-01 forward as the explicit-category prerequisite plus its auditable correction successor rather than marking the capability Shipped prematurely. Canonical foundation docs/inventory/manifest should be updated and resealed atomically in their owner lane instead of being copied piecemeal into #165.