docs(product-goal-directive): replace directive text with owner's 2026-09-02 revision - #1698
Closed
seonghobae wants to merge 2 commits into
Closed
docs(product-goal-directive): replace directive text with owner's 2026-09-02 revision#1698seonghobae wants to merge 2 commits into
seonghobae wants to merge 2 commits into
Conversation
…6-09-02 revision
The owner supplied a substantially revised nine-section standing
directive (pasted directly into session, not via PR) that expands the
PR-repair-not-close policy, adds a full i18n/DB-translation-ledger
subsection, adds an ontology-ownership split and a "core foundation"
canonical-owner taxonomy, softens the Rust-only mandate into an
ADR-documented exception path, and adds explicit CI model-routing and
timeout rules. Per this file's own stated policy ("edit this file in
place... do not fork a second copy elsewhere"), replaced all nine
quoted sections verbatim; kept and updated both reconciliation notes
(§5 naming, §8 CI pool routing) against the new text rather than
carrying forward stale guidance — the §5 wardnet example no longer
appears in the new text, and the §8 orchestrator/free pin is now the
owner-confirmed live state for both OpenCode Review and Strix per
ADR-0003's 2026-08-30/2026-09-02 amendments.
Full revision rationale in docs/doctoring/product-goal-directive.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reachedNext included review available in 8 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
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 |
…record Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Comment on lines
+77
to
+81
| owner explicitly confirmed on 2026-09-02 (in the `/loop` input for the contextual-orchestrator | ||
| integration work: *"Contextual-Orchestrator의 모델은 GitHub Actions Workflow 이용에 관해 | ||
| `orchestrator/free`로 고정"*) that **both** OpenCode Review and Strix are pinned to `orchestrator/free` | ||
| — resolving the ADR-0003-flagged "Strix switched without owner review" risk the 2026-08-30 note below | ||
| was tracking. Treat the free-pin for both consumers as settled; do not re-flag it as an unreviewed risk. |
Contributor
There was a problem hiding this comment.
🟡 Availability risk falsely marked resolved
The owner explicitly confirmed status conflicts with the binding risk record, which remains open and unreviewed. Agents can suppress remediation for outages that disable Strix.
Prompt for agents
Reconcile docs/product-goal-directive.md, AGENTS.md, and docs/adr/0003-contextual-orchestrator-vendored-free-zdr.md. The new owner text directs GitHub Actions to use orchestrator/free, but the durable ADR and AGENTS.md still state that the resulting Strix availability risk is open and unreviewed; the ADR's 2026-09-02 amendment concerns Bytez discovery, not owner acceptance. Distinguish confirmation of the route from explicit review or acceptance of its known outage trade-off. Remove the instruction to suppress the risk unless owner acceptance is actually recorded, or update every binding record with the new decision and its consequences.
Was this helpful? React with 👍 or 👎 to provide feedback.
| ## 2. Concurrent operation, PR repair (not close), and root-cause fixes | ||
|
|
||
| > 동시 작업·PR 운영·근본 수정 원격 Agent의 동시 Commit·Push를 경합으로 단정해 Force Push·중단하지 말고 변경 취지·이유를 확인해 이어간다. Commit·Push 전 병합 여부를 확인하고 삭제 근거를 남긴다. Self-modifying/Source-fix Workflow는 목적 달성 후 삭제하고 잔존 시 관찰·제거한다. 가능한 PR은 Stack하고 not-merge-ready를 merge-ready로 전환한다. 유관 프로젝트 원인이 엮이면 함께 처리하고 Stacked PR을 중앙 OpenCode Agent가 리뷰하지 않으면 ContextualWisdomLab/.github를 수정한다. Agent 간 대화·Spawn을 활용한다. 수동 해법은 모두 코드·설정에 반영한다. PYTHONPATH=. 누락은 설정하고 GitHub Actions·런타임 오류는 로그·Root Cause Analysis로 제거한다. 전체 GitHub Checks 실패를 확인·수정한다. ContextualWisdomLab 내부 라이브러리 문제라면 원시 공급자 오류까지 고쳐 PR한다. 개발 프로세스에 https://github.com/DietrichGebert/ponytail 및 https://github.com/obra/superpowers 를 사용하되 superpowers의 "무조건 질문" 규칙은 무시한다. https://github.com/tirth8205/code-review-graph 와 https://github.com/colbymchenry/codegraph 도 사용하고 인덱싱은 스스로 수행한다. 이는 명시적으로 허가됐다. | ||
| > 동시 작업·PR 운영·근본 수정 동시 Commit·Push를 경합으로 단정하거나 Force Push하지 말고 취지를 잇는다. Commit 전 병합·삭제 근거를 남기고 목적을 마친 Self-modifying/Source-fix Workflow는 제거한다. PR을 Stack해 merge-ready로 만들고 유관 원인도 고친다. Stacked PR 리뷰가 빠지면 .github를 수리하고 Agent 대화·Spawn을 쓴다. single-writer·DDD 위반, 잘못된 base·충돌, ADR 번호 충돌, 성급한 Accepted, 미보호 dependency, 누락된 test·fixture·contract는 Close가 아닌 repair finding이다. Draft·Proposed로 낮추고 owner stack에 non-force restack·retarget해 수리한다. single-writer는 delta 폐기가 아닌 통합이다. 직접 못 고치면 successor가 delta를 완전 승계하고 predecessor를 잇는다. foundation 미착지 시 prerequisite를 완성하며 PR은 유지한다. 오폐쇄는 reopen·successor로 복구한다. Close는 사용자 명시, 유효 delta 없음, 악성 변경, 완전 승계에만 허용하며 표시는 종결이 아니다. 수동 해법은 코드·설정화하고 PYTHONPATH=.·Actions·runtime 오류는 로그 RCA로 없앤다. 내부 결함은 canonical owner·원시 공급자에서 고쳐 통합 CI와 release까지 잇는다. 경계나 공통 수요가 없을 때만 ADR로 제외한다. ponytail·superpowers를 쓰되 "무조건 질문"은 무시하고 code-review-graph·codegraph를 인덱싱한다. 한국어 문구·문서·번역에는 https://github.com/epoko77-ai/im-not-ai 를 적용하되 의미·사실·수치·고유명사를 보존한다. |
Contributor
There was a problem hiding this comment.
📝 Info: New prose tool meets license policy
The mandated epoko77-ai/im-not-ai repository is public, active, and MIT-licensed. It satisfies the binding permissive-license convention.
Was this helpful? React with 👍 or 👎 to provide feedback.
Comment on lines
+55
to
+59
| flagging: "위반명은 치환한다" now explicitly permits snake_case, camelCase, *or* PascalCase (snake_case | ||
| preferred) for identifiers generally, which is looser than the old "snake_case only" reading — but for | ||
| **database objects specifically**, `docs/CWL-MASTER-CONTEXT.md` §7's grandfather clause still governs: | ||
| 2+-word snake_case is required for **new** DB objects; existing CamelCase/PascalCase DB objects are | ||
| grandfathered and must not be force-renamed on the strength of this section's general wording alone. |
Contributor
There was a problem hiding this comment.
📝 Info: Database grandfathering remains intact
The adjacent reconciliation limits the broader casing rule for databases. New objects require multiword snake_case, while existing CamelCase and PascalCase objects remain grandfathered.
Was this helpful? React with 👍 or 👎 to provide feedback.
seonghobae
added
documentation
ChatGPT Codex Connector
Contributor
Author
|
Closing — fully superseded by #1692. While investigating a Devin review comment, I found #1692 already exists for this exact file (
Per this directive's own §2 (repair-vs-close policy, now merged into the standing text): this is the "successor has fully absorbed the valid delta" case, not an abandonment — closing without merging is the correct action here, not a bare close of unresolved work. 🤖 Closed by Claude Code |
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.
Summary
The owner supplied a substantially revised nine-section standing directive (pasted directly into an interactive session). Per
docs/product-goal-directive.md's own policy ("edit this file in place... do not fork a second copy elsewhere"), replaced all nine quoted sections verbatim with the new text.Notable substantive changes (full list in
docs/doctoring/product-goal-directive.md):orchestrator/freeCI pin explicit and mechanical (no provider/model/group name, no paid fallback, fail closed).Both reconciliation notes (§5 naming, §8 CI pool routing) were re-checked against the new text rather than carried forward unchanged:
CWL-MASTER-CONTEXT.md§7).orchestrator/freepin is now the owner-confirmed live state for both OpenCode Review and Strix (per ADR-0003's 2026-08-30/2026-09-02 amendments) — updated the note to reflect that instead of flagging it as still-unreviewed.Test plan
tests/for any contract test pinningproduct-goal-directive.mdprose — none foundAGENTS.md/CLAUDE.md/CWL-MASTER-CONTEXT.md's existing links to this file still make sense unchanged (they link generically, don't quote content)docs/adr/0003-contextual-orchestrator-vendored-free-zdr.md's actual amendment history🤖 Generated with Claude Code