PHPackages decodelabs/chorus - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. decodelabs/chorus ActiveLibrary[Utility & Helpers](/categories/utility) decodelabs/chorus ================= Meta / architecture repository for Decode Labs v0.1.3(5mo ago)01.3k2MITPHP Since Nov 21Pushed 5mo agoCompare [ Source](https://github.com/decodelabs/chorus)[ Packagist](https://packagist.org/packages/decodelabs/chorus)[ RSS](/packages/decodelabs-chorus/feed)WikiDiscussions develop Synced 1mo ago READMEChangelog (4)Dependencies (1)Versions (6)Used By (2) Decode Labs — Chorus ==================== [](#decode-labs--chorus) **Chorus** is the meta-layer for the Decode Labs ecosystem. Where the individual packages contain user-facing code and documentation, Chorus provides the **architectural map**, **cross-cutting decisions**, and **package index** that define how the entire suite fits together. Chorus is not a runtime library. It is the **reference point for humans and AI assistants** when designing, documenting, and evolving Decode Labs packages and projects built on top of them. --- Purpose ------- [](#purpose) Chorus exists to: - Describe the **overall architecture** of the Decode Labs ecosystem. - Maintain a **canonical index** of all packages, including their roles, milestones, and dependencies. - Host **cross-package documentation**, such as coding standards, naming rules, error-handling strategy, and architectural principles. - Record **Decision Documents (ADRs)** that explain the rationale behind major choices. - Provide a stable place for **high-level specifications** and design discussions that span multiple repositories. Package-specific documentation remains in each package’s own repository. Chorus focuses only on the parts that *bind those packages together*. --- What Chorus Contains -------------------- [](#what-chorus-contains) ### 1. Package Index [](#1-package-index) A machine-readable description of every Decode Labs package: - Name - Repository location - Role and responsibility - Language - Dependencies - Milestone/stability - Documentation references ### 2. Architecture Documentation [](#2-architecture-documentation) System-level guides explaining: - How packages relate to one another - Intended dependency directions - Architectural “clusters” - Core concepts shared across repositories ### 3. Decision Records (ADRs) [](#3-decision-records-adrs) A curated log of cross-cutting decisions: - Error model - Logging and observability - Naming conventions and coding standards - Discovery mechanisms (e.g. Archetype) - Deprecation and backwards-compatibility strategy ADRs help ensure long-term consistency as the ecosystem grows. ### 4. Workflow & Standards [](#4-workflow--standards) Guidelines that define how Decode Labs packages should: - Be structured - Expose public APIs - Document behaviour - Introduce or evolve features - Interact with AI assistants, Cursor, and code generators ### 5. Templates [](#5-templates) Standard templates for package documentation: - README templates - Package specification templates - Feature specification templates - Change specification templates - AGENTS.md templates **Note:** Templates live in Chorus, but the actual specs and documentation created from these templates live in their respective package repositories. ### 6. Change Specs [](#6-change-specs) Meta-level change specifications that describe ecosystem-wide behavioural changes and migration plans: - Located in `docs/meta/releases//...` - Coordinate changes across multiple repositories - Define migration strategies for libraries, frameworks, and client projects **Note:** Change Specs live in Chorus because they coordinate ecosystem-wide migrations. Package-specific implementation specs (package specs and feature specs) live in package repositories. --- What Chorus Does *Not* Contain ------------------------------ [](#what-chorus-does-not-contain) - **Runtime code** - **Package-specific implementation specs** (package specs live in `docs/meta/spec.md` in each package repo) - **Feature specs** (live in `docs/meta/features/` in each package repo) - **User-facing package documentation** (READMEs, usage examples, etc.) - **Tests** - **Implementations** Those belong in their respective package repositories. Chorus is purely an **architectural and organisational layer**. --- Contributing ------------ [](#contributing) Contributions to Chorus should focus on: - Improving architectural clarity - Adding or refining decision documents - Updating the package index - Enhancing cross-package documentation - Recording discussions and design rationale Changes that affect a specific package’s behaviour should be made in that package’s repository, with Chorus updated only if the change has architectural or ecosystem-wide significance. --- Licence ------- [](#licence) Chorus is licensed under the MIT License. See [LICENSE](./LICENSE) for the full license text. ### Health Score 33 — LowBetter than 75% of packages Maintenance70 Regular maintenance activity Popularity17 Limited adoption so far Community10 Small or concentrated contributor base Maturity29 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~3 days Total 4 Last Release 169d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/8a241d64d12b3b5ee94197862ec1ec30b82ed2efa34a0cd7f4c3565a021daddd?d=identicon)[betterthanclay](/maintainers/betterthanclay) --- Top Contributors [![betterthanclay](https://avatars.githubusercontent.com/u/1273586?v=4)](https://github.com/betterthanclay "betterthanclay (36 commits)") --- Tags documentationarchitecturemeta ### Embed Badge ![Health badge](/badges/decodelabs-chorus/health.svg) ``` [![Health](https://phpackages.com/badges/decodelabs-chorus/health.svg)](https://phpackages.com/packages/decodelabs-chorus) ``` ### Alternatives [eusonlito/laravel-meta A package to manage Header Meta Tags 196525.1k2](/packages/eusonlito-laravel-meta)[zoha/laravel-meta a package for working with models meta 236121.7k](/packages/zoha-laravel-meta)[symfony/ai-platform PHP library for interacting with AI platform provider. 51927.7k136](/packages/symfony-ai-platform)[phpmentors/domain-kata Kata for domain models 73426.9k9](/packages/phpmentors-domain-kata)[torann/laravel-meta-tags A package to manage Header Meta Tags 65273.3k4](/packages/torann-laravel-meta-tags)[genericmilk/docudoodle Generate documentation for your Laravel application using OpenAI 15120.5k](/packages/genericmilk-docudoodle) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)