https://github.com/sparshsam/ecosystem-standards
Canonical repository, documentation, security, and publication standards for Sparsh Sam's public and private software ecosystem.
https://github.com/sparshsam/ecosystem-standards
calm-software documentation governance infrastructure open-source open-source-governance publication-readiness repository-standards rfc security security-policy software-architecture
Last synced: 1 day ago
JSON representation
Canonical repository, documentation, security, and publication standards for Sparsh Sam's public and private software ecosystem.
- Host: GitHub
- URL: https://github.com/sparshsam/ecosystem-standards
- Owner: sparshsam
- License: mit
- Created: 2026-06-04T19:48:07.000Z (25 days ago)
- Default Branch: main
- Last Pushed: 2026-06-17T23:19:53.000Z (12 days ago)
- Last Synced: 2026-06-18T01:14:24.208Z (12 days ago)
- Topics: calm-software, documentation, governance, infrastructure, open-source, open-source-governance, publication-readiness, repository-standards, rfc, security, security-policy, software-architecture
- Size: 43.9 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
- Governance: GOVERNANCE.md
Awesome Lists containing this project
README
# Ecosystem Standards
[](LICENSE)
[](CONTRIBUTING.md)
[]()
[](https://github.com/sparshsam/ecosystem-standards/actions/workflows/ci.yml)
[](https://github.com/sparshsam/ecosystem-standards/releases)
**Canonical repository, documentation, security, and publication standards for Sparsh Sam's public and private software ecosystem.**
## Purpose
This repository is the single source of truth for how repositories in this ecosystem are created, structured, documented, secured, classified, released, and represented publicly.
It exists because:
- **Consistency matters.** Every repository should feel like part of the same ecosystem regardless of age, maturity, or visibility.
- **Security requires policy.** Environment files, secrets, and history management follow defined standards — not ad-hoc decisions.
- **Public/private boundaries must be explicit.** What can be said about a private system, what cannot, and where the line sits.
- **Agents need rules.** Automated tooling, AI assistants, and CI/CD pipelines must operate within the same governance framework as human contributors.
- **Publications must be earned.** Citeable releases, DOIs, and research outputs follow a maturity model — not a publication checkbox.
## Prime Directive
> Every repository must be clear, restrained, secure, maintainable, and accurately represented.
## Who Must Follow This
- **Human contributors** creating or maintaining any repository in the ecosystem.
- **AI agents** (Codex, Claude Code, ChatGPT, Hermes, or future tools) operating on ecosystem repositories.
- **Automated workflows** — CI/CD, release pipelines, security scanners, and publication tooling.
- **Repository classification** — every new repository must be classified as public or private and follow the corresponding standard.
## Structure
| Path | Purpose |
|------|---------|
| `standards/` | Canonical policies: doctrine, security, architecture, release, RFC, agent governance |
| `templates/` | Reusable starting points for public repos, private repos, RFCs, and GitHub workflows |
| `checklists/` | Practical checklists for agents and humans before creating, releasing, or publishing |
| `examples/` | Safe language models and unsafe patterns for profile entries and public references |
## How Standards Evolve
1. **Proposal** — a new standard or amendment is drafted as an RFC (see `standards/rfc-standard.md`).
2. **Review** — the proposal is reviewed for consistency, security, and tone alignment.
3. **Adoption** — once accepted, the standard is merged and becomes canonical.
4. **Deprecation** — superseded standards are moved to an archive status with a pointer to their replacement.
Minor clarifications, typo fixes, and template updates may be applied directly without RFC.
## Private System Boundary
This repository describes standards for **both public and private** repositories. Standards that reference private systems (such as TW Oracle) use restrained, high-level language. Implementation details, proprietary workflows, and operational data remain confidential. See `standards/public-private-boundary.md` for the exact boundary rules.
## GitHub Profile Connection
The ecosystem profile README at `github.com/sparshsam` lists ecosystem repositories in two categories: **Public Ecosystem** and **Private / Proprietary Systems**. This standards repository defines how repos qualify for each category and how they are described. See `standards/github-profile-integration.md`.
## License
This repository is licensed under the MIT License — see [LICENSE](LICENSE). The standards and templates are intended to be freely used, adapted, and cited.
---
*Last updated: June 2026*