Document designed vs running NATS subjects and cluster TCP/leaf/public endpoints, per-address I/O, Zapier→Verae job path, and unwired modules.
3.3 KiB
3.3 KiB
Sources (other documentation that names routes)
This inventory is compiled from code and from these docs. Do not invent extra verae.* names.
Master maps
| Path | What it names |
|---|---|
packages/docs-master/modules-and-nats.md |
Module catalog, subject table, HTTPS vs NATS |
packages/docs-master/MESSAGE-FLOWS.md |
Create/wait/includeAttached/batch Merkle |
packages/docs-master/archive-nats.md |
Archive put/query/reply |
docs/02-architecture/nats-subjects.md |
verae.zapier.* payloads + streams |
docs/02-architecture/modules-and-nats.md |
Same catalog as docs-master |
docs/02-architecture/overview.md |
Poller / events / webhooks |
packages/overview/03-nats-cluster.md |
Cluster URLs, who may connect |
packages/overview/06-address-routing.md |
Address pattern + plane mapping |
packages/verae-ops/06-linking-services.md |
How services attach |
packages/verae-nats-cluster/scripts/ensure-streams.sh |
Live stream create |
packages/verae-nats-cluster/conf/nats.conf.tmpl |
:4222 / :6222 / :7422 / monitor :8222 |
packages/verae-nats-cluster/conf/public-edge.conf.tmpl |
Public leaf :4222, WS :14422 |
packages/verae-fleet/overlays/ns1/fleet.json |
Enabled vs in-process workers |
packages/verae-keep units.px-worker.json |
Worm/tree on LXC 510 |
packages/verae-zapier-middleware/src/nats/subjects.js |
Product subjects + consumers |
packages/zappier-account-balance/src/subjects.js |
Billing subjects |
packages/verae-access-authz/src/subjects.js + policy.js |
Authz + plane allow lists |
packages/zappier/src/billing-nats.ts |
Edge billing client |
Per-package NATS.md (Forgejo module copies also live under docs-master/modules/)
| Package | Addresses |
|---|---|
verae-zapier-middleware |
jobs.watch out, jobs.events in, archive.query via aggregator |
verae-jobs-events |
jobs.events; exclusive → verae.internal.jobs.events |
verae-request-splitter |
archive.put |
verae-archive-worm |
archive.put / query / reply.<id> |
verae-tree-node |
same, kind: tree |
verae-archive-aggregator |
query out, reply.<id> in |
zappier-account-balance |
verae.billing.* |
zappier (edge) |
package NATS.md is stale (“does not publish”); code publishes usage/payment/credit/customer.put when NATS_URL is set. Use docs-master/modules/zappier/NATS.md |
zappier-customer-service |
statement.get, balance.adjust |
zappier-sales-pricing |
statement.get |
zappier-accounting-export |
statement.get |
zappier-identity |
identity.bind / lookup |
verae-access-authz |
authz.check / authz.deny |
verae-access-web |
access.web.in / access.web.billing.* |
verae-access-api |
access.api.* |
verae-access-zapier |
access.zapier.* then HTTPS to middleware |
verae-access-leaf |
access.leaf.in |
verae-access-staff |
access.staff.* |
verae-nats-process |
verae.example.process.* (template) |
verae-nats-accounts |
policy only (INTERNAL vs LEAF) |
verae-zapier-simulator |
in-process replay of product addresses |
verae-keep / verae-fleet / verae-uptime / verae-backup |
no product subjects |
Simulator src/pipeline.js and src/monitors.js list the same product addresses for traces; they are not live subscribers.