Skip to content

Polychro — Roadmap

Current focus

  • Verbose mode with internal JSON
  • Packaged rulesets for Ikanos, Spectral, AGENT.md, etc.

Spec-driven ruleset family

A curated family of rulesets for the specs that drive runtime behavior but have no linter of their own today — beyond OpenAPI:

  • polychro:capability — validate Ikanos capability YAML: cross-object integrity (every flow call: resolves to a declared operation, every exposed tool ref: resolves to a flow), resource-conflict detection (no two servers on the same address:port, unique tool names), and security invariants (secrets injected via binds rather than inline, tool-annotation consistency).
  • polychro:skill / polychro:agents-md — structural rules for agent instruction files (SKILL.md, AGENTS.md): required sections, frontmatter validity, heading hierarchy, and internal-link resolution.

These extend the shipped governance, ai-safety, and security rulesets to the capability and instruction-file formats.

IDE Integration

  • VS Code extension with real-time diagnostics
  • Language Server Protocol (LSP) support

Ecosystem Expansion

  • Additional built-in rulesets for OpenAPI and AsyncAPI
  • Community ruleset registry
  • Ruleset sharing and composition
  • Additional HTML profiles (AMP, accessibility-strict)
  • Optional external link reachability checks (off by default)
  • Dedicated XML format-aware module (polychro-xml) — XSD/RelaxNG validation, namespace consistency, DTD restrictions
  • Additional external-process bridges (e.g. OPA / Conftest, kube-linter, tfsec)
  • Native (non-composite) GitHub Action runtime for faster cold starts

Performance

  • Incremental validation (re-lint only changed sections)
  • Parallel validator execution for large documents
  • Caching layer for repeated validations

Distribution

  • Homebrew formula
  • Docker image
  • npm wrapper package (shipped — polychro-node)
  • pip wrapper package (shipped — polychro-python)
  • Go module (shipped — polychro-go)

Contributing

See CONTRIBUTING.md for how to get involved. Feature requests and ruleset contributions are welcome via GitHub Issues.

Next Steps

  • Releases — See what has already shipped
  • Architecture — Understand the design constraints behind the roadmap
  • Features — Compare planned work with the current surface area