docs(governance): SSOT bundle — initial SSOT files (2026-06-20)#67
docs(governance): SSOT bundle — initial SSOT files (2026-06-20)#67KooshaPari wants to merge 1 commit into
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Review limit reached
More reviews will be available in 46 minutes and 5 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
codeant-ai
Bot
added
the
size:S
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
| @@ -0,0 +1,28 @@ | |||
| # phenoUtils — Specification | |||
There was a problem hiding this comment.
Suggestion: Do not add SPEC.md at the repository root; move this specification document into the appropriate docs/ governance/spec subdirectory and keep only the allowed root Markdown files (README.md, CLAUDE.md, AGENTS.md) at root level. [custom_rule]
Severity Level: Minor
Why it matters? 🤔
The repo root contains a newly added Markdown file named SPEC.md, and the custom rule only allows README.md, CLAUDE.md, or AGENTS.md at the repository root. This file is neither of the allowed exceptions, so the suggestion correctly identifies a real rule violation.
(Use Cmd/Ctrl + Click for best experience)
Prompt for AI Agent 🤖
This is a comment left during a code review.
**Path:** SPEC.md
**Line:** 1:1
**Comment:**
*Custom Rule: Do not add `SPEC.md` at the repository root; move this specification document into the appropriate `docs/` governance/spec subdirectory and keep only the allowed root Markdown files (`README.md`, `CLAUDE.md`, `AGENTS.md`) at root level.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a8e953e0bd
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -0,0 +1,28 @@ | |||
| # phenoUtils — Specification | |||
There was a problem hiding this comment.
This commit creates SPEC.md at the repository root, but the applicable /workspace/phenoUtils/AGENTS.md documentation rule says "Never create .md files at root level (except README.md, CLAUDE.md, AGENTS.md)". Because SPEC.md is not an allowed exception, this SSOT doc violates the repo's stated governance/quality gate; place it under the documented docs/... structure or update the governance exception instead.
Useful? React with 👍 / 👎.
|
|
||
| ## Why | ||
|
|
||
| This repo exists to provide a focused capability as part of the Phenotype fleet's substrate layer. See `AGENTS.md` for fleet context and `llms.txt` for agent-facing documentation. |
There was a problem hiding this comment.
This line sends readers to llms.txt, but a repo-wide search of this commit's tracked files shows no llms.txt anywhere. Anyone following the new spec will hit a dead reference for the promised agent-facing documentation; either commit the referenced file or remove this pointer.
Useful? React with 👍 / 👎.
1 participant
User description
Summary
Initial SSOT bundle for
phenoUtils. Adds the following governance files:SPEC.mdContext
Part of fleet-wide SSOT audit batch (T3B, 2026-06-20). Audit findings:
findings/2026-06-20-T3A-fleet-ssot-audit.mdin the phenotype-apps meta-repo.Generated files
AGENTS.md— onboarding doc (template-based, see meta-repo AGENTS.md)WORKLOG.md— v2.1 schema per ADR-025 (Date | Task ID | Layer | Action | Files | Notes | device)SPEC.md— 1-page spec stub (placeholder content)llms.txt— agent context file (5 sections)CHANGELOG.md— initial entryLICENSE-MIT— full MIT license text.github/dependabot.yml— 3 ecosystems: cargo, pip, github-actionsCODEOWNERS— @KooshaPari as default owner.github/PULL_REQUEST_TEMPLATE.md— basic checklistTest plan
/cc @KooshaPari
CodeAnt-AI Description
Add the initial specification page for phenoUtils
What Changed
SPEC.mdthat states whatphenoUtilsis, why the repo exists, and where to find fleet-wide governance and build guidanceImpact
✅ Clearer repo purpose✅ Easier onboarding for new contributors✅ Faster access to governance and status information💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.