docs(ddd): restore queue authority and bounded-context ownership - #435
docs(ddd): restore queue authority and bounded-context ownership#435seonghobae wants to merge 251 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (7)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough문서 권위를 crate 중심에서 bounded context 중심으로 재구성했습니다. 시간 의존성 계약, ADR 식별자 정규화, 연구 주장 경계, delivery 기준선과 문서 검증 규칙을 갱신했습니다. Changes문서 권위 및 아키텍처
Estimated code review effort: 4 (Complex) | ~45 minutes Merge Risk: 🟡 Moderate · up to This documentation and validation change establishes architecture, queue, and release guidance, but unresolved documentation inaccuracies and incomplete release evidence could misclassify work or treat an incomplete release as eligible. The PR is not merge-ready until these bounded documentation issues are corrected or explicitly accepted by the appropriate owner. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
|
Write path recovered this cycle. Exact head is Live GitHub re-read at 2026-09-01T10:19:29Z: 136 open PRs (91 draft, 45 non-draft) on protected main Independent human review request is blocked: the only repository collaborator is the author. Copilot review was requested on this head and does not count as independent APPROVE. No self-approval. Queued/pending/skipped/cancelled/stale/predecessor-head checks are non-passing. |
Unpaywall and OpenAlex re-read 2026-09-01T10:22Z remain closed (is_oa false, 0 OA locations). Full texts stay unread. Mean-gate authority is still Putnick and Bornstein (2016, PMC5145197). Rubin T_m remains the complete-data combining rule, not Mislevy PVs.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Refresh the checked-in operator register after the #488 root-cause rustdoc audit. Preserve protected-main and owner boundaries, distinguish hosted RED from proactive source-audit repair, and keep current exact-head queued checks from being promoted to GREEN. Signed-off-by: Seongho Bae <me@seonghobae.me>
|
Fresh standards/traceability finding for the existing documentation-authority lane (2026-09-09 UTC+9):
For the #435 docs refresh, preserve AERA/APA/NCME 2014, IEEE 754-2019, and ISO/IEC 60559:2020 as the current published authorities and record the active revisions separately with retrieval dates; do not promote draft/revision work to normative evidence. The live scientific lineage has also advanced since this Draft's embedded snapshot: #488 is now |
1 participant
Queue authority and operator baseline
This Draft remains the TEPP delivery/queue-authority vehicle. Protected product evidence remains
main@a243f18da4a4ca8a8d068c39922537f1f8ed6ad0until a normal protected merge advances it. PR=0 is valid only through protected merge or a verified successor that inherits every valid delta/test/fixture/contract/evidence item; simple Close is not queue reduction.The live organization ruleset
18156473is active on the default branch. It currently requires one approving review, dismisses stale reviews on push, requires review-thread resolution, requires the central OpenCode/review scheduler/security/Strix/Semgrep/Noema/CodeQL workflows, and rejects deletion/non-fast-forward updates. Administrative bypass exists but is not routine delivery evidence.The checked-in
docs/product-technical-gap-baseline.mdis still not code-current: its opening snapshot remains August 2026. Preserve historical snapshot evidence, but refresh the full file before treating it as current authority.docs/TRACEABILITY.mdstill shows its 2026-08-24 baseline and lacks the direct#491 -> neutral-zero/Wide256 -> #488 module/API/test/evidence -> resource-budget decisiontrace.Foundation prerequisite #492
#492 remains
794ba9e6dda9f043aa499920fdf609b81b075d7e, Ready for Review, mergeable, and unmerged on protected main. Rust Foundation34011189084, Documentation Quality, Security Scan, and SAST Semgrep are terminal GREEN. Historical CodeQL PR34011189081remains failure and is not merge evidence.Canonical owner
.github#1929has already repaired the old dispatcher-actor mismatch. On 2026-09-08 the failed #492 actions/python CodeQL compatibility jobs were rerun on the unchanged TEPP head; attempt-2 jobs101902297829and101902297963both failed closed because no authenticated terminal exact-head verdict had been published. That clean read-after-dispatch specimen is now recorded at.github#1929. Cross-repository commit-status publication also retains the observed HTTP 403Resource not accessible by integrationfailure path. #492 auto-merge is enabled but remains correctly blocked by canonical terminal CodeQL evidence and a qualifying independent approval. TEPP does not fabricate receipts, churn the leaf head, impersonate actors, self-approve, or weaken this control.Validation Evidence inheritance
#488 remains the owner-correct Validation Evidence landing vehicle, stacked on #492, Draft/open/mergeable. Current exact head is
50e267fe9f45707498c2ee14f7d3aca698e5274f. Production exact admission remainsn=4..=16; route order remainsneutral_zero_linear -> pairwise_reference -> generic_fallback. Independent directi128/u128pair-distance evidence spans every admitted count;[-2^53,0,1,2^53]remains the mixed-sign witness with exactP=2^109+3and public result bits0x432a20bd700c2c3e.n>16remains characterization-only under #491.Predecessor
7cf41504257c3ff99d532530e5a3a4fa3b7fb0f0completed authored-line enforcement at2037/2041 = 99.80%, with exactlymonte_carlo.rs:98-99andreport.rs:116-117uncovered, before the coverage job was later cancelled during branch enforcement. That branch result is unknown and does not transfer.90b132d2...then exposed a test-only Rust 1.98cast_precision_lossfinding at the maximum-replication-count RMSE support endpoint; current50e267...repairs the representation with exact pointer-width-specific binary64 support values, without changing production arithmetic or coverage policy.Current #488 Documentation Quality
34175702972is terminal GREEN. Rust Foundation34175702814has terminal GREEN Rust 1.98 format/Clippy/no-retry nextest/doctest/rustdoc/dependency policy (101904588278), repository/Python contracts (101904588145), and Live PostgreSQL (101904588103). Production line/branch coverage101904588163is still executing on the exact head; no current-head coverage or merge-readiness claim is made yet. Fresh #488 review enumeration has no qualifying approval.The predecessor authored-line classifier took roughly 12m34s for 2,041 authored lines and branch classification was still running at cancellation. Treat that as a checker-operability finding, not a reason to change thresholds, exclusions, denominators, source, or skip policy. Any optimization must preserve exact source-classification semantics.
Owner boundaries and remaining proof
Reusable static/generalized psychometric arithmetic remains a released/versioned fast-mlsirm boundary; immutable
v0.9.1remains the confirmed release. Semantic LLM routing remains an immutable released contextual-orchestratororchestrator/freeboundary. TEPP and contextual-orchestrator currently have no GitHub release, so mutable contextual-orchestrator main cannot become a TEPP production dependency.Issue #491 still requires exact-head 100% owned-production authored line+branch coverage, causal repair of actual findings, exact denominator/candidate/midpoint/ties-to-even/overflow-refusal preservation, truthful production route telemetry, Rust 1.98.0
--releaseCPU/allocator/RSS evidence with recorded hardware/build flags, normal #492 landing with canonical CodeQL receipt and qualifying review, direct TRACEABILITY linkage, and code-current operator gap documentation.Preserve Draft/Proposed state while unresolved and integrate non-force. Do not force push, destructively rebase, self-approve, weaken gates, consume mutable sibling heads, or claim queued/predecessor checks as shipped evidence.
Exact-head contract repair — 2026-09-08
Current head:
352ae6ad382be60a610b3534fdd70e52536d57da.Exact predecessor jobs exposed three leaf failures: the gap baseline lacked the canonical
Closure evidencemarker, the required exact-head inventory heading/rows, and the ADR identity test mixedimport unittestwithfrom unittest import mock. This head restores the schema-bound priority inventory using live #492/#488 evidence and consistently usesunittest.mock. The two CodeQL compatibility jobs were dispatch-pending control-plane failures, not leaf findings. All predecessor results are non-authoritative; this Draft remains blocked until fresh current-head documentation, Rust, coverage, security, and review evidence is terminal.Latest exact authority:
8a11257046e72be585f22ddee4f12efcd7fe6b14. The gap inventory intentionally records other live PR heads only; this PR's own head is carried here in PR metadata because embedding it in the same commit would be self-referential.Canonical ADR authority repair
Latest exact authority:
3130d2c7688dba2e0386b2229a91f09d7c3f9668. The fresh planning run advanced past the gap inventory and exposed duplicate top-level metadata in ADR 0003/0005/0009/0013/0014. This head preserves each ADR's latest, most complete existing status/maturity text and removes only competing duplicateDecision status,Implementation maturity, andDatedeclarations. No ADR was promoted; each file now has exactly one declaration of each authority field.Central scheduler contract repair
Latest exact authority:
a9b9ceeb6ac61f66091e08a38b3bee94939df39f. Exact predecessor job101918398404proved that the leaf contract test still required localcron: "47 * * * *"after protected-main documentation and the workflow had already moved scheduling authority to the central scheduler. This head keeps the leaf workflow as a manualworkflow_dispatchentrypoint, requires the organization commercial-entrypoint marker, and fails if a localscheduleorcronis reintroduced. No workflow permission, credential, security gate, or production behavior was weakened. All predecessor results are non-authoritative; fresh exact-head checks are required.Fresh verification on the central-scheduler repair
On
a9b9ceeb6ac61f66091e08a38b3bee94939df39f, repository/Python contracts job101919111201is GREEN, directly verifying the repaired dispatch contract. Planning/governance101919068515, Rust format/Clippy/nextest/rustdoc/dependency policy101919111295, Live PostgreSQL101919111311, CodeQL Python analysis101919065964, current-head admission, and queue scan are also GREEN. Production line/branch coverage remains in progress; Semgrep, compatibility CodeQL, Noema, and remaining admission/review jobs are queued. This Draft therefore remains non-mergeable by policy despite being mechanically mergeable and having zero unresolved threads.