Niyam

The engineering problem

Policy documents are written for people, while enforcement systems need explicit, testable conditions. A naive converter can make a confident mistake and hide the reasoning. Niyam separates source text, extracted requirements, generated checks, evidence, and approval so a reviewer can inspect each step.

The product boundary

• Preserve the source passage behind each interpreted requirement.
• Generate a proposed check without treating generated code as approved policy.
• Run verification in a constrained environment and retain the result.
• Show uncertainty and missing evidence instead of inventing certainty.
• Require an explicit person to approve a consequential change.

What the project demonstrates

The useful portfolio signal is not “AI reads policy.” It is the review boundary: provenance, deterministic checks, failure visibility, and a human decision record. The project reached the top 30% of its hackathon field, but that placement is context rather than proof of technical correctness.

Honest limits

Niyam is a project and demonstration, not legal advice or an autonomous compliance system. Generated interpretations require domain review, and a passing check does not prove that an organization satisfies every obligation in a real policy.

Code and author

See Aarav Chandel's GitHub profile for currently public project work and implementation evidence.