Contact person: Business Client

Phone:Show

Email:Show

Location: Chennai, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need an automated validator that runs my software documentation through a configurable rules engine and flags any violations in plain-language reports. The rules themselves already exist; what’s missing is the tool that reads a document, applies each rule, and returns a clear pass / fail summary alongside line-level or section-level feedback.

Supported formats
• PDF
• Word (DOC / DOCX)
• Markdown

Key expectations
• The rules file can be updated without touching the core code—JSON, YAML, or another structured approach is fine as long as it’s well-documented.
• Validation can be triggered from both a command line and an HTTP endpoint; the HTTP path is mainly for CI pipelines (GitHub Actions, GitLab, etc.).
• Output: console log, machine-readable JSON, and an optional annotated version of the original document highlighting each issue.
• Unit tests covering the main parsing and rule-matching logic.

Acceptance criteria
1. A sample run against three provided documents (one in each format) shows rule hits and passes.
2. All dependencies and build steps are listed in a concise README.
3. I can drop a new rule into the config, rerun, and see the validator pick it up without code changes.

When you reply, please focus on your direct experience building similar parsers or linters—frameworks, languages, and any performance considerations you’ve tackled. A brief note on how you would structure the rules engine will help me gauge fit quickly." (client-provided description)