feat: add ChittyCanon compliance files

[chitcommit]

Summary

• Adds the 4 required ChittyCanon (dimension 3) compliance files to the .github org config repo
• The repo that documents 7 compliance dimensions should itself be compliant

Files Added

File	Purpose
CLAUDE.md	Development guide — documents workflows, agents, and repo structure
CHARTER.md	Service charter — infrastructure tier, documentation compliance profile
CODEOWNERS	Review requirements for org-wide impacting changes
.chittyconnect.yml	ChittyConnect integration config

Compliance Dimensions

Dimension	Status
ChittyConnect	Added .chittyconnect.yml
ChittyBeacon	N/A (not a deployable service)
ChittyCanon	Added CLAUDE.md, CHARTER.md, CODEOWNERS
ChittyRegister	N/A (not a deployable service)
ChittyRouter	N/A (no domain)
ChittyTrust	N/A (not a deployable service)
Health Endpoint	N/A (not a Worker)

Test plan

• Verify CLAUDE.md renders correctly on GitHub
• Verify CODEOWNERS is recognized by GitHub (Settings > Branches)
• Verify .chittyconnect.yml passes schema validation

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@chitcommit has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 7 minutes and 26 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/compliance-files

---

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 and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e78daed91b

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove guidance that suggests direct pushes to main

The development snippet instructs contributors to “push to main,” which conflicts with the charter’s governance rule that “all changes via PR (no direct pushes to main)” (CHARTER.md:60). If someone follows CLAUDE.md here, they can bypass CODEOWNERS review and the required PR workflow, undermining the compliance and review guarantees this repo is meant to enforce. Please align the development instructions with the charter’s required PR-based process.

Useful? React with 👍 / 👎.