Skip to content
Back to the open standards index
Cited by

Implementations of the open standards.

External tools, courses, papers, and mentions that implement or cite any of our three CC BY 4.0 open standards: the Lyric Scoring Standard, the Banned Clichés List, or the What We Refuse To Build standard. Public registry, verifiable links, honest count.

What we track

All three are published under CC BY 4.0 — citation by name + version is the only requirement. If you’re using any of them and you’re not on this page, email us.

Known implementations

0 verified

Zero external implementations on record — yet. The standard shipped on npm at @songforgeai/scoring-rubric@1.2.0 in April 2026. We track honestly: every adoption signal lands here within 24 hours of verification, not before.

1

Be the first external implementer.

The fastest path: install the npm package, run a scoring pass against any lyric, ship a public artifact (blog post, repo, paper, course module) that cites the standard by name + version. Email us the link; we add it to this page within 24h.

$ npm install @songforgeai/scoring-rubric
Email us your project →
2

Three cite-as templates — pick the one that fits your medium.

Drop one of these into your tool’s docs, your paper’s references, or your course syllabus. Verbatim citation under CC BY 4.0 is the full attribution requirement.

Plain text
“Scored against the Lyric Scoring Standard v1.2.0 (SongForgeAI, 2026), CC BY 4.0.”
Markdown
[Lyric Scoring Standard v1.2.0](https://songforgeai.com/scoring/standard) — SongForgeAI, 2026, CC BY 4.0.
BibTeX
@techreport{nigro2026lyricscoringstandard,
  title       = {The Lyric Scoring Standard},
  author      = {Nigro, Todd},
  institution = {SongForgeAI},
  year        = {2026},
  month       = {April},
  number      = {v1.2.0},
  url         = {https://songforgeai.com/scoring/standard},
  note        = {Licensed under CC BY 4.0}
}
3

What counts as an entry.

Anything verifiable by a public link works. The spirit of the registry is honesty over volume — we document real implementations, not announcements.

  • Tool: a product (commercial or open-source) that imports the npm package and scores lyrics against the rubric.
  • Paper: an academic paper (any venue) that cites the whitepaper or evaluates against the rubric.
  • Course: a music or songwriting course that uses the rubric as a teaching artifact.
  • Mention: a substantive citation in a public blog post, podcast, or industry artifact (not a passing reference).

No gatekeeping. We verify in 5 minutes; once verified, your entry lives here under your name with the link you provided.

Internal references

7 surfaces

Where the standard lives + is referenced within the codebase + content. These are NOT external adoption signals — the count above stays honest about that. They prove the rubric is real + load-bearing internally; visitors evaluating "is this a serious standard?" get both axes.

How to cite

The Lyric Scoring Standard is published under CC BY 4.0. Citation by name + version is the only requirement.

Plain
Nigro, T. (2026). The Lyric Scoring Standard, version 1.2.0. SongForgeAI. https://songforgeai.com/scoring/standard. Licensed under CC BY 4.0.
BibTeX
@techreport{nigro2026lyricscoringstandard, title = {The Lyric Scoring Standard}, author = {Nigro, Todd}, institution = {SongForgeAI}, year = {2026}, month = {April}, number = {v1.2.0}, url = {https://songforgeai.com/scoring/standard}, note = {Licensed under CC BY 4.0} }

How to implement

The npm package ships the rubric JSON + four helper functions (scoreToGrade, scoreToPercentileLabel, computeComposite, isCompatibleRubricVersion). Zero runtime dependencies; works in Node ≥ 18 and modern browsers.

$ npm install @songforgeai/scoring-rubric

Why this page exists

Standards win when adopted, not when published. The cited-by surface is the public ledger of adoption — every entry is a verifiable, dated proof point that someone outside SongForgeAI implemented or referenced the rubric.

Today the count is zero. The page still exists, because radical transparency about adoption beats marketing language about momentum. When the count grows, this page grows with it. When it doesn’t, the absence is documented.

The same discipline applies to the cadence rituals on the engineering side (Quality Council every 3 days, Trust Decay Audit every 14 days, Bet Review every 45 days). External proof works the same way: accumulated, dated, never deleted.