You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
epic: internal AI guardrails thin distribution for Cor-Incorporated #1
Added README/doc positioning guidance in the working branch so future sessions use the same framing:
this repository should be described as a Cor-Incorporated fork of OpenCode
compatibility with upstream should be preserved where practical
guardrails should ship as a thin internal distribution layer, not a deep rewrite
renaming the repository or published package should be treated as a separate branding/distribution decision, after install paths, package names, and release ownership are ready together
This keeps the fork legible without breaking the current upstream-compatible shape of the repo.
Context: the AIDD H17 work moved to an operate-and-observe phase on 2026-10-24 (H17 control 216a955e accepted in aidd-governance#216, the report contract shipped to every entry in claude-code-skills#441, the design rule for shell state guards recorded as ADR-012). This issue was not on the H17 path, had no activity since its last update, and will be watched through real use (the guard ledger and the weekly tally in the operations guide) instead of as an open item. Reopen if real operation shows the problem.
Activity
terisuke commentedon Apr 3, 2026
Child issues:
terisuke commentedon Apr 3, 2026
Child issues:
terisuke commentedon Apr 3, 2026
Added README/doc positioning guidance in the working branch so future sessions use the same framing:
This keeps the fork legible without breaking the current upstream-compatible shape of the repo.
terisuke commentedon Apr 3, 2026
MVP readiness is now tracked explicitly in #16. The current planning split is:
The local planning mirrors this in docs/ai-guardrails/mvp-readiness.md and the expanded issue pack under docs/ai-guardrails/issues/.
terisuke commentedon Apr 8, 2026
PR #139 progress update
PR #139 (
fix/guardrail-review-findings-phase7) addresses:Phase 6 (Dogfooding fixes):
git merge-baseno longer falsely blockedPhase 7 (Bug fixes / Test coverage):
proc.kill()Verification: 34 tests / 255 expect() / all pass. Build + typecheck + deploy firing verified.
terisuke commentedon Apr 8, 2026
Epic progress update (2026-04-08)
Closed today (4 issues)
Remaining open (3 issues)
Metrics
terisuke commentedon Apr 11, 2026
Issue Sweep 進捗 (2026-04-11 Session 2)
クローズ済み
PR オープン (CI 検証中)
残り
ロードマップ進捗
fix(agents-md): address CRITICAL data-loss bugs + clean-room score fo…
fix(agents-md): preserve child hand-written sections + sync threshold…
fix(workspace): address re-review round 2 findings (LSP ENOENT + ast-…
terisuke commentedon Oct 25, 2026
Closed by owner decision (Terada Kousuke, 2026-10-25), posted verbatim:
Context: the AIDD H17 work moved to an operate-and-observe phase on 2026-10-24 (H17 control
216a955eaccepted in aidd-governance#216, the report contract shipped to every entry in claude-code-skills#441, the design rule for shell state guards recorded as ADR-012). This issue was not on the H17 path, had no activity since its last update, and will be watched through real use (the guard ledger and the weekly tally in the operations guide) instead of as an open item. Reopen if real operation shows the problem.