Skip to content

.inclusion-config.md

Latest commit

 

History

History
96 lines (66 loc) · 3.23 KB

.inclusion-config.md

File metadata and controls

96 lines (66 loc) · 3.23 KB
Raw

Inclusion Plugin Configuration

Generated by /gotrino-inclusion:teach-charter on 2026-04-09 Last updated: 2026-04-09

Project Context

Setting Value
Framework Node.js CLI + Go TUI
Language TypeScript + Go
i18n setup None (planned — future voice languages)
a11y tooling None in devDependencies; TUI has --accessible and --report modes
Test location src/**/*.test.ts, tui/**/*_test.go
Docs location docs/
Decisions location None — use docs/

Scope Decisions

Conscious decisions about what's in/out of scope. The plugin respects these.

Area Status Rationale Decided By Date
i18n In scope (future) Global audience; non-English voice languages planned @philsherry 2026-04-09
RTL Out of scope CLI/TUI tool; no RTL markets or UI surfaces planned @philsherry 2026-04-09
WCAG compliance In scope (WCAG 2.2 AA) Web-facing outputs (manifests, captions); TUI has accessible mode @philsherry 2026-04-09
Inclusive language In scope (all areas) Code, docs, and studio tape narration examples @philsherry 2026-04-09
Form inclusivity Out of scope CLI tool with no forms @philsherry 2026-04-09

Priorities

Area Priority Notes
Inclusive language 1 Code comments, variable names, docs, narration scripts
Diverse names in examples 2 Studio tapes and fixture data
i18n readiness 3 Future non-English voices; captions and manifests
Cultural assumptions in examples 4 Studio tape content and PROMPT.md files
Form inclusivity — Out of scope

Active Checks

Based on scope decisions:

  • language-check
  • names-check
  • examples-audit
  • i18n-check (in scope — flag readiness issues for future voice languages)
  • RTL checks (disabled: no RTL surfaces planned)
  • inclusion-audit (will skip RTL and form sections)

Acknowledged Findings

Specific findings that have been reviewed and acknowledged. These won't be flagged again.

Finding Location Rationale Date
Voice IDs embed gender (northern_english_male, southern_english_female) voices.yaml, studio/example/meta.yaml Names are upstream piper-tts identifiers — not ours to change 2026-04-09

Decision Log

2026-04-09: Initial Setup

Project configured as a global-audience developer tool. i18n in scope for future non-English voice support. RTL suppressed (CLI/TUI, no RTL surfaces). WCAG 2.2 AA applies to web-facing outputs (manifests, captions, web player). Inclusive language checks cover all areas: code, docs, and studio tape narration scripts. Form inclusivity out of scope (no forms in this tool).

— @philsherry

2026-04-09: Voice ID naming

Voice identifiers (alan, alba, northern_english_male, southern_english_female) are upstream piper-tts names. Playback uses them verbatim — we play the hand we're dealt. Gendered naming in voice IDs is acknowledged and out of our control. Won't be re-flagged.

— @philsherry

Review Schedule

  • Review i18n scope and voice language progress: 2026-10-09 (6 months)