Skip to content

Commit 4029d95

Browse files
committed
Add sponsor badge
1 parent 3cd50ee commit 4029d95

1 file changed

Lines changed: 214 additions & 0 deletions

File tree

README.md

Lines changed: 214 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,214 @@
1+
[![Sponsor](https://img.shields.io/badge/Sponsor-%E2%9D%A4-pink?logo=github)](https://github.com/sponsors/hyperpolymath)
2+
3+
image:https://img.shields.io/badge/License-MPL_2.0-blue.svg[MPL-2.0-or-later,link="https://opensource.org/licenses/MPL-2.0"]
4+
image:https://img.shields.io/badge/Philosophy-Palimpsest-indigo.svg[Palimpsest,link="https://github.com/hyperpolymath/palimpsest-license"]
5+
6+
7+
// SPDX-License-Identifier: MPL-2.0-or-later
8+
// SPDX-FileCopyrightText: 2024-2025 hyperpolymath
9+
10+
= Developer Ecosystem
11+
12+
:author: hyperpolymath
13+
:revnumber: 0.1.0
14+
:revdate: 2025-12-26
15+
:toc: left
16+
:toclevels: 3
17+
:icons: font
18+
:source-highlighter: rouge
19+
20+
image:https://img.shields.io/badge/RSR-Gold-ffd700[RSR Gold]
21+
image:https://img.shields.io/badge/CCCP-Certified-c41e3a[CCCP Certified]
22+
23+
== License & Philosophy
24+
25+
This project must declare **MPL-2.0-or-later** for platform/tooling compatibility.
26+
27+
Philosophy: **Palimpsest**. The Palimpsest-MPL (PMPL) text is provided in `license/PMPL-1.0.txt`, and the canonical source is the palimpsest-license repository.
28+
29+
== What is Developer Ecosystem?
30+
31+
*Developer Ecosystem* is the central hub for all development workflow tools—git operations, repository management, scaffolding, and developer experience.
32+
33+
This primary brings together projects that improve how developers:
34+
35+
* *Git Tools* — Forge management, branch workflows, repo unification
36+
* *Repo Management* — Automation, analysis, health monitoring
37+
* *Scaffolding* — Project templates, boilerplate generation
38+
* *Developer UX* — IDE extensions, documentation tools, reconciliation
39+
40+
== Satellite Structure
41+
42+
[source]
43+
----
44+
developer-ecosystem/
45+
├── satellites/
46+
│ ├── git-tools/ # Git forge & workflow tools
47+
│ │ ├── git-hud/ # Unified git platform dashboard
48+
│ │ ├── gitloom/ # Branch management & weaving
49+
│ │ ├── git-reunify/ # Safe repo reunification
50+
│ │ ├── git-seo/ # Git repo discoverability
51+
│ │ ├── polysafe-gitfixer/ # Git backup merger
52+
│ │ └── vext/ # IRC commit notifications
53+
│ │
54+
│ ├── repo-management/ # Repository automation & analysis
55+
│ │ ├── oikos/ # Ecological code analysis
56+
│ │ ├── robot-repo-automaton/ # Automated repo management
57+
│ │ ├── grim-repo/ # Audit-grade repo tooling
58+
│ │ └── robot-vacuum-cleaner/ # Repo tidying bot
59+
│ │
60+
│ ├── scaffolding/ # Project generation
61+
│ │ └── scaffoldia/ # Community-driven scaffolding
62+
│ │
63+
│ └── developer-ux/ # Developer experience tools
64+
│ ├── rescript-evangeliser/ # ReScript teaching extension
65+
│ ├── recon-silly-ation/ # Doc reconciliation system
66+
│ └── nickel-config-reporter/ # Config auditing
67+
----
68+
69+
== Git Tools
70+
71+
Repositories focused on Git operations across multiple forges (GitHub, GitLab, Gitea, Bitbucket).
72+
73+
=== git-hud
74+
75+
A hyper-customizable dashboard for unified Git platform management.
76+
Starting with GitHub and GitLab integration, expanding to become the definitive interface for developers who demand control.
77+
78+
=== gitloom
79+
80+
Git workflow weaving and branch management.
81+
Advanced branch operations with safety guarantees.
82+
83+
=== git-reunify
84+
85+
Safe repo reunification tool—merge diverged repos without losing work.
86+
Handles developer reconciliation scenarios where repos have drifted apart.
87+
88+
=== git-seo
89+
90+
Make your Git repositories discoverable with SEO optimization tools.
91+
Metadata, descriptions, and tagging for better findability.
92+
93+
=== polysafe-gitfixer
94+
95+
A polyglot implementation of a git backup merger tool.
96+
Each component written in the language providing the strongest safety guarantees for that concern.
97+
98+
=== vext
99+
100+
High-performance IRC notification daemon for version control systems.
101+
Real-time commit notifications from Git repos to IRC channels with connection pooling.
102+
103+
== Repo Management
104+
105+
Repositories focused on automated repository analysis, health monitoring, and maintenance.
106+
107+
=== oikos
108+
109+
*Ecological & Economic Code Analysis Platform*
110+
111+
_οἶκος_ (oikos): the shared Greek root of ecology and economy.
112+
113+
Features:
114+
* Carbon intensity scoring
115+
* Sustainability metrics
116+
* Pareto-optimal code health
117+
* GitHub/GitLab integration
118+
119+
=== robot-repo-automaton
120+
121+
Automated repository management bot.
122+
Handles routine maintenance, updates, and health checks.
123+
124+
=== grim-repo
125+
126+
Modular audit-grade tooling for narratable, scaffolded, and legible repositories.
127+
Ensures repos meet quality and documentation standards.
128+
129+
=== robot-vacuum-cleaner
130+
131+
A comprehensive, production-grade robot vacuum cleaner simulation system.
132+
Includes repository tidying capabilities.
133+
134+
== Scaffolding
135+
136+
Repositories focused on project template generation and structure.
137+
138+
=== scaffoldia
139+
140+
A developer-centred, modular, and community-driven repo scaffolding engine.
141+
142+
* Generates idiomatic, validated, narratable project structures
143+
* Supports multiple languages, tools, and themes
144+
* Audience-aware stance configuration
145+
146+
== Developer UX
147+
148+
Repositories focused on improving the developer experience.
149+
150+
=== rescript-evangeliser
151+
152+
"Celebrate good, minimize bad, show better"
153+
154+
A VS Code extension that teaches JavaScript developers ReScript through progressive code transformation, without shame.
155+
156+
=== recon-silly-ation
157+
158+
Documentation Reconciliation System.
159+
160+
Automatically reconcile, deduplicate, and resolve conflicts in Git repository documentation using:
161+
* Content-addressable storage
162+
* Graph-based conflict resolution
163+
164+
=== nickel-config-reporter
165+
166+
Ingests config files, clones to Nickel format, emits AsciiDoc audit reports.
167+
168+
== Relationship to Other Primaries
169+
170+
[cols="1,2"]
171+
|===
172+
| Primary | Relationship
173+
174+
| *rhodium-standard-repositories*
175+
| RSR compliance standards for developer-ecosystem satellites
176+
177+
| *poly-mcps*
178+
| poly-git-mcp uses developer-ecosystem git tools
179+
180+
| *neural-foundations*
181+
| oikos uses AI for code analysis (neurosymbolic potential)
182+
183+
| *cccp*
184+
| Language policy governs all implementations
185+
|===
186+
187+
== Notable Standalone Projects
188+
189+
Some developer tools remain standalone due to their unique nature:
190+
191+
* *valence-shell* — Reversible thermodynamic shell (fundamental paradigm shift)
192+
* *cicd-hyper-a* — Reusable CI/CD templates (infrastructure, not tooling)
193+
194+
== Contributing
195+
196+
Contributions should focus on *developer workflow improvements*:
197+
198+
1. Git forge integrations
199+
2. Repository analysis algorithms
200+
3. Scaffolding templates
201+
4. Developer experience enhancements
202+
203+
== License
204+
205+
MIT + Palimpsest-0.8
206+
207+
---
208+
209+
_"Developer tools that respect developer autonomy. No lock-in, no shame, no anxiety."_
210+
211+
212+
== Architecture
213+
214+
See link:TOPOLOGY.md[TOPOLOGY.md] for a visual architecture map and completion dashboard.

0 commit comments

Comments
 (0)