Reproducible enquiry-routing starter

A small rules package you can run offline.

Use fictional enquiries to reproduce assignment, missing-detail checks, duplicate detection and a reviewed reply. This downloadable starter gives an implementing operator the rules, fixtures and checks behind a bounded example.

MIT licence · fictional data only · tested with Node.js 22.23.2 on 8 October 2026. Read the full setup without downloading.

Start with the five reproducible checks.

Extract the archive into a new folder and open a terminal inside it. Use an existing Node.js installation; the recorded test version is above. Run these commands:

node --version
node verify.mjs

The JSON report should show five cases, five passed and zero failed: complete request, missing details, normalized duplicate, repeated approval and failure/recovery. It includes the synthetic inputs, expectations and observed states. Save your result; do not treat our retained run as proof of yours.

The checks deliberately approve fictional drafts to exercise the rules. For a manual rehearsal, follow the README: initialize a local state, submit a fixture, inspect the request and reply file, then explicitly approve it. No command can send a message.

Inspect the rules before changing them.

• Normal requests go to the Service coordinator; quote requests go to the Quotes team; a priority word sends the request to the Duty manager.
• An empty area or a message shorter than 20 characters prepares a clarification that still needs approval.
• The duplicate key compares normalized email, area and message in the local queue. It does not merge every request from the same person.
• A simulated failure retains the draft. Restore clears the previous approval and returns the same record for a new review.

The field contract and readable source are included. These word and length rules are examples, not a complete assessment of a plumbing job. Check your real tools’ native features before adding a connection.

Know what persists and how to stop it.

The public browser demo keeps state in memory. This package’s wrapper writes a local sample-state.json in your current directory. Its pause command blocks new submissions, approvals and restores. Resume does not replay anything. These file and pause features belong to the package, not the browser demo.

Run one process at a time and use synthetic details only. There is no multiuser lock, authentication, encryption, scheduler or live connector. The queue holds at most 20 records. Reset removes the local state and duplicate memory; it cannot undo an external action. Delete the extracted folder to uninstall.

Fireflax repository maintainers own this versioned artifact. No individual ongoing support assignment is established. Before adapting it, name your own maintenance owner, record the version and set a review date.

Use the example to clarify your handoff.

A live connection still needs actual field IDs, account permissions, reliable identifiers, checks for external effects and accepted recovery ownership. The package does not establish compatibility with your CRM.