master-zapier-plan-draft/packages/verae-zapier-simulator/NATS.md
George Lambert f3dc0e6eee
Some checks are pending
offline / test (push) Waiting to run
Add Zapier interface simulator, tree-node Merkle lookups, and user docs
In-process trace console validates hops, faults, recoveries, and
suggested changes before zapier-platform push. User guide covers
signup through central-chain and bulk-summary tree-node hash lookup.
2026-09-11 12:58:03 -04:00

15 lines
967 B
Markdown

# NATS — verae-zapier-simulator
The simulator does **not** subscribe to live NATS. It replays the same addresses in-process so a trace console can validate messaging before the Zapier app is pushed.
| Simulated address | Publisher (in trace) | Subscriber (in trace) |
|-------------------|----------------------|------------------------|
| HTTPS Zapier → zappier-edge → middleware | zapier-platform-app | zappier-edge |
| `verae.zapier.jobs.watch` | middleware-http | job-poller |
| `verae.zapier.jobs.events` | job-poller | middleware wait, webhook-deliver |
| `verae.zapier.webhooks.deliver` | middleware | webhook-deliver → HTTPS Zapier hook |
| `verae.archive.put` | splitter / merkle builder | archive-* / tree-node-* |
| `verae.archive.query` | archive-aggregator (broadcast) | every WORM and tree node |
| `verae.archive.reply.<id>` | node on bloom hit only | aggregator |
Live NATS stays on NS1 loopback. Do not point this UI at a public NATS URL.