Where we are

Nizen is built slowly on purpose. Progress is measured by gates, not calendar dates: each phase has to genuinely work before the next one starts. Here is where things honestly stand.

Now: Phase 0, foundations

Nothing user-facing ships from this phase. Everything depends on it. This is the part most projects skip and later regret.

• Strictness taxonomy. The classification every feature depends on: composable exclusion rules (meat, seafood, egg, dairy, honey, allium, root vegetables, and more) with named diets like vegan, zhai, Jain, and pork-free built on top as data. Calendar-conditional eating, such as the lunar 1st and 15th or Nine Emperor Gods, is handled by one general mechanism. Done and tested.
• Reputation event log. An append-only record of every contribution, so trust and recognition are earned facts, never mutable scores. Done and tested.
• Data pipeline. Seeding vegetarian venues in the Klang Valley from open sources, with the origin of every record tracked, then confirmed by a human before it counts. Built and proven against live data.
• Verification portal. The tool humans use to confirm machine-gathered records, so the dataset’s core promise does not rot. Built.

Next: Phase 1, the app

A React Native app for the seed community: a directory with strictness filters, a lunar-calendar reminder for zhai days, an ingredient-label scanner tuned to your practice, and a contribution game where adding data is the fun part.

Later: Phase 2, reach

Public web pages for every venue, so merchants get found beyond their existing circle. Curated lists. Merchant self-service. Growth beyond the temple network.

The honest part

Nizen is early. The foundations are real and tested; the app is not built yet. We would rather show you exactly where we are than pretend to be further along.