The README makes claims. This file backs them up with evidence.
Developer Ecosystem is the central hub for all development workflow tools—git operations, repository management, scaffolding, and developer experience.
Evidence: The monorepo structure at satellites/git-tools/, satellites/repo-management/, satellites/scaffolding/, and satellites/developer-ux/ (see /var/mnt/eclipse/repos/developer-ecosystem/README.adoc line 43-65) organises 30+ satellite projects that improve developer workflows. Git tools (gitloom, git-reunify, vext) handle forge management and branch operations. Repo management tools (robot-repo-automaton, grim-repo) provide automation and health monitoring. Scaffoldia generates idiomatic project structures. These subsystems prove the central hub claim.
Caveat: The monorepo brings together tools but lacks a unified API surface — each satellite is consumed independently by external projects. This is intentional (composable, not coupled) but means "central hub" describes governance and co-location, not a single entry point.
This primary brings together projects that improve how developers: * Git Tools — Forge management, branch workflows, repo unification * Repo Management — Automation, analysis, health monitoring * Scaffolding — Project templates, boilerplate generation * Developer UX — IDE extensions, documentation tools, reconciliation
Evidence: Each satellite contains functioning implementations. polysafe-gitfixer (line 91-94) is a polyglot git backup merger. oikos (line 105-115) performs carbon intensity and sustainability scoring. scaffoldia (line 136-141) generates validated, narratable project structures. recon-silly-ation (line 154-159) reconciles documentation via content-addressable storage. The categorisation is exhaustive and each category has working code.
Caveat: Some satellites are "future-ready" rather than production-deployed (e.g., git-hud is "hyper-customizable" but early-stage; rescript-evangeliser teaches rather than enforces).
| Technology | Learn More |
|---|---|
ReScript |
https://rescript-lang.org (satellites: rescript-evangeliser, cadre-router) |
Deno |
https://deno.land (satellites: scaffoldia scripts, developer-ux automation) |
Rust |
https://www.rust-lang.org (git tools performance layer) |
Elixir |
https://elixir-lang.org (oikos, vext) |
Zig |
https://ziglang.org (FFI bridge for git operations) |
Idris2 ABI |
https://www.idris-lang.org (formal specs for forge adapters) |
All satellites in this monorepo use the hyperpolymath ABI/FFI standard (Idris2 + Zig) where FFI is needed. Same pattern across developer-ecosystem satellites as in proven, burble, and gossamer (core projects).
Integration examples:
- developer-ecosystem/satellites/git-tools/gitvisor/ — uses Idris2 ABI proofs for git invariant verification
- developer-ecosystem/rescript-ecosystem/ — ReScript frontends call Zig FFI bindings for performance
- developer-ecosystem/well-known-ecosystem/ — Zig FFI for cryptographic identity verification
| Path | What’s There |
|---|---|
|
6 git operation tools (gitloom, git-reunify, vext, git-seo, polysafe-gitfixer, gitvisor) |
|
4 repository automation tools (oikos, robot-repo-automaton, grim-repo, robot-vacuum-cleaner) |
|
Scaffoldia project generator with modular templates |
|
3 developer experience enhancers (rescript-evangeliser, recon-silly-ation, nickel-config-reporter) |
|
ReScript language tools and web packages (tea-router, websocket, gRPC, postgres, redis) |
|
Deno runtime tools (beamdeno, bundeno, deno-bunbridge) |
|
V language bindings (v-zig-ffi, v-idris-abi) |
|
RFC 9116 security.txt and .well-known/* tooling |
|
Homebrew and Winget integration for hyperpolymath tools |