Skip to content

Latest commit

 

History

History
52 lines (40 loc) · 2.34 KB

File metadata and controls

52 lines (40 loc) · 2.34 KB

Roadmap

This roadmap describes project direction. It does not promise a release date, package publication, deployment, adoption, or integration.

Current source baseline

The source tree currently includes:

  • a framework-independent core for text and CSV parsing.
  • versioned normalized results, validation, conflicts, corrections, warnings, assessment, and JSON, CSV, and iCalendar exports;
  • locale aliases for English and Filipino layouts, named dates, bounded date ranges, and numbered week sections;
  • bounded PDF.js and Tesseract provider adapters.
  • an optional structured recovery adapter that requires explicit consent.
  • agent and CLI packages with bounded input and structured errors.
  • React correction and preview helpers.
  • a no-account web playground and schema routes.
  • Vue and Node consumer examples.
  • synthetic text, CSV, image, PDF, and export interoperability fixtures.
  • fixture-backed browser, keyboard, reduced-motion, and accessibility checks.
  • privacy-safe claims and reproducible release evidence documentation.

These capabilities are present in the repository source. The package version and normalized result schema version remain unchanged until a release.

Next work

The next work items are selected through focused issues and pull requests. Likely areas include:

  1. Add parser dialects through synthetic fixtures and deterministic tests.
  2. Improve provider adapters while preserving the local deterministic path.
  3. Expand consumer examples and clean-install checks when a public API needs evidence.
  4. Improve review and correction flows with accessible, keyboard-first tests.
  5. Keep package, deployment, security, and interoperability evidence current.

An item enters the roadmap when it has a clear user problem, a package owner, safe input boundaries, and a reproducible verification plan. A pull request or passing test shows repository state. It does not show package publication, deployment, adoption, or third-party provider retention.

How to propose work

Open a GitHub issue with a synthetic example and the smallest useful behavior. Explain the expected normalized result, limits, privacy impact, and verification command.

See CONTRIBUTING.md, the architecture guide, and the claims ledger before proposing a change.