Skip to content

Labels

Labels

  • Architect/design decision work (ARCHITECT: prefix issues)
  • DDD refactoring, pure-seam boundary, module decomposition, naming
  • Tutorial, textbook exercises, demo alphabet, LCC+ games, curriculum docs
  • LCC+, interactive debugger, fun.js, src/extra/ — extended or optional toolchain features
  • Agentic workflow, claim/close scripts, skills, velocity tracking, data analysis
  • Core assembler, interpreter, linker, oracle parity, correctness
  • Temporary — needs an area:* label assigned before work begins
  • Playground, demo site, syntax highlighting, code-in-slides, GitHub Pages
  • Waiting on another issue
  • Something isn't working
  • CI/CD pipeline, GitHub Actions, deployment
  • DATA-role work: data analysis, CSV enrichment, notebook re-runs
  • Needs a human architectural/design decision (Charlie or Prof. Dos Reis) before code work
  • Low urgency — intentionally set aside; revisit when higher-priority work clears
  • Improvements or additions to documentation
  • This issue or pull request already exists
  • New feature or request
  • Exploratory change — outcome uncertain, treat as a trial
  • Work outside this codebase; tracked here for visibility, to be transferred out later
  • Good for newcomers
  • Extra attention is needed
  • Blocked on a human architectural or policy decision
  • Requires human judgment or action
  • a task for only humans to do, not meant for AI agents to handle
  • This doesn't seem right
  • A question+answer pair worth preserving as a reusable lesson
  • Done synchronously by a human and Claude agent together
  • Concerns OG-LCC vs LCC.js behavioral parity
  • Has an @todo puzzle marker in source code