offline / test (push) Waiting to run

Details

Split NATS modules: splitter, WORM bloom archive, aggregator, docs-master

Each module has SUMMARY.md and NATS.md (who sends/receives, subject
addresses, payload). Tests: splitter 3, worm 3, aggregator 2.
Forgejo repos pushed separately; this commit keeps them in the monorepo.

2026-09-11 12:33:40 -04:00

1.2 KiB

Raw Blame History

Message flows

1. Create timestamp (async)

Zapier → POST https://zappier-edge/v1/timestamp (x-api-key)
zappier-edge meters → POST middleware/zapier/v1/timestamp
splitter: chain sha256; optional verae.archive.put
middleware → chain create or existing lookup
middleware publishes verae.zapier.jobs.watch { jobId, tenantId, … }
HTTP 202 { jobId } back to Zapier
job-poller consumes watch, GET chain status
On terminal: verae.zapier.jobs.events
webhook-deliver POSTs Zapier REST Hook if subscribed

2. Wait

Same as (1) but HTTP holds until jobs.events or WAIT_TIMEOUT_MS → { status: pending, jobId }.

3. Hash already registered

Step 4 returns original jobId + original seal. No second chain write. receipts[0].kind = seal. Later archive attaches become receipts[1…] if includeAttached.

4. includeAttached

After seal is known, aggregator publishes verae.archive.query. Each WORM: bloom miss = no packet; hit = verae.archive.reply.<correlationId>. Aggregator merges into wait JSON.

5. Multipart attachments

Splitter emits one archive.put per file (kind: file, contentSha256). Chain never stores bytes.

1.2 KiB Raw Blame History