Skip to content

governance: Language / package anti-pattern policy fails on main — banned-language bindings vs standards rsr-antipattern.yml #150

@hyperpolymath

Description

@hyperpolymath

Context

After #148 + #149 greened main, this is the only remaining red check on the repo. It is not fixable from proven alone — the rule lives in hyperpolymath/standards (governance.ymlgovernance-reusable.yml@mainrsr-antipattern.yml), which a proven-scoped session cannot read.

Likely cause (inferred, not confirmed)

The check is named Language / package anti-pattern policy, and the repo contains bindings in languages the estate bans (per .claude/CLAUDE.md: no Python/Cython/TypeScript). Strong candidates it flags:

  • bindings/typescript/package.json + tsconfig.json
  • bindings/hy/pyproject.toml (Hy is a Python dialect)
  • bindings/javascript/package.json

(bindings/deno/ and bindings/csharp/ also exist; deno is explicitly allowed in CLAUDE.md, so those are probably fine.)

I could not confirm the exact rule because I'm scoped to hyperpolymath/proven only.

To resolve

  1. Give a session access to both hyperpolymath/proven and hyperpolymath/standards.
  2. Read rsr-antipattern.yml to confirm what it flags on proven.
  3. Decide: delete/relocate the banned-language bindings, or amend the policy / allowlist in standards.

Acceptance

  • governance / Language / package anti-pattern policy passes on proven PRs and main.

Refs #148, #149.


Filed by Claude Code — https://claude.ai/code/session_01MN5vzRR4MK2dkDNaHqqRDy

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions