Skip to content

docs(profile): mandate chittyseed-fractal template for new repos #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chitcommit merged 1 commit into from
Apr 24, 2026
Merged

docs(profile): mandate chittyseed-fractal template for new repos #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion profile/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,24 @@ Explore our projects organized by purpose and technology:
All our repositories follow consistent standards:

- ✅ Clear documentation (README, CONTRIBUTING, LICENSE)
- ✅ Proper tagging and descriptions
- ✅ Proper tagging and descriptions
- ✅ Code quality practices
- ✅ Community guidelines
- ✅ **Fractal trinity layout** (identity / authority / connectivity / scopes)
- ✅ Compliance triad: CHARTER.md + CHITTY.md + CLAUDE.md
- ✅ Canonical entity types: P/L/T/E/A (Person, Location, Thing, Event, Authority)
Comment on lines +44 to +46
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Align “fractal trinity” terminology across the doc.

trinity is defined with 4 elements at Line 44 but 3 elements at Line 56. Please make both sections use the same definition to avoid compliance ambiguity.

Suggested doc fix 
-- ✅ **Fractal trinity layout** (identity / authority / connectivity / scopes)
+- ✅ **Fractal layout** (identity / authority / connectivity / scopes)
-The template encodes the fractal trinity layout (identity / authority / connectivity), provides the standard `scope.json` manifest, CHARTER/CHITTY/CLAUDE templates, package.json with `validate:fractal` + `certify` scripts, and a CI workflow that gates merges on fractal-layout compliance.
+The template encodes the fractal layout (identity / authority / connectivity / scopes), provides the standard `scope.json` manifest, CHARTER/CHITTY/CLAUDE templates, package.json with `validate:fractal` + `certify` scripts, and a CI workflow that gates merges on fractal-layout compliance.

Also applies to: 56-56

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@profile/README.md` around lines 44 - 46, The README uses "Fractal trinity"
inconsistently—one place lists four elements in the bullet "Fractal trinity
layout (identity / authority / connectivity / scopes)" while another place
defines it as three elements; pick the correct canonical definition (either 3 or
4 elements) and update all occurrences to match. Search for the exact phrase
"Fractal trinity" and the terms "identity / authority / connectivity / scopes"
and replace or edit the other definition so both sections use the same set and
wording, ensuring related mentions (e.g., "trinity") and any compliance
references remain consistent.


## Starter Template (BINDING for new repos)

**[chittyseed-fractal](https://github.com/chittyfoundation/chittyseed-fractal)** — every new ChittyApps repo MUST start from this template. Click "Use this template" on the GitHub repo page, or run:

```bash
gh repo create chittyapps/<your-app> --template chittyfoundation/chittyseed-fractal --public
```
Comment on lines +50 to +54
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Avoid hardcoding --public in the mandatory bootstrap command.

Making --public the default in a binding standard can unintentionally expose internal repositories. Recommend documenting visibility as an explicit choice (--private or --public) with private as default.

Suggested doc fix 
-**[chittyseed-fractal](https://github.com/chittyfoundation/chittyseed-fractal)** — every new ChittyApps repo MUST start from this template. Click "Use this template" on the GitHub repo page, or run:
+**[chittyseed-fractal](https://github.com/chittyfoundation/chittyseed-fractal)** — every new ChittyApps repo MUST start from this template. Click "Use this template" on the GitHub repo page, or run (choose visibility explicitly):

 ```bash
-gh repo create chittyapps/<your-app> --template chittyfoundation/chittyseed-fractal --public
+gh repo create chittyapps/<your-app> --template chittyfoundation/chittyseed-fractal --private
+# or
+gh repo create chittyapps/<your-app> --template chittyfoundation/chittyseed-fractal --public
</details>

<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
**[chittyseed-fractal](https://github.com/chittyfoundation/chittyseed-fractal)** — every new ChittyApps repo MUST start from this template. Click "Use this template" on the GitHub repo page, or run (choose visibility explicitly):
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@profile/README.md` around lines 50 - 54, Update the README snippet that
currently hardcodes the gh command with "--public": replace the single mandatory
example "gh repo create chittyapps/<your-app> --template
chittyfoundation/chittyseed-fractal --public" with guidance that visibility must
be an explicit choice and show both variants (use "--private" as the recommended
default and provide the "--public" alternative), and add a short note near the
example stating that repositories should default to private unless public
sharing is intentionally chosen.


The template encodes the fractal trinity layout (identity / authority / connectivity), provides the standard `scope.json` manifest, CHARTER/CHITTY/CLAUDE templates, package.json with `validate:fractal` + `certify` scripts, and a CI workflow that gates merges on fractal-layout compliance.

Validation contract: `chittycanon://core/services/chittyschema#meta/fractal-layout`

---

Expand Down
Loading