marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Add Zapier interface simulator, tree-node Merkle lookups, and user docs
Some checks are pending
offline / test (push) Waiting to run
Details

Browse source 
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.
This commit is contained in:
George Lambert 2026-09-11 12:58:03 -04:00
parent 3daa88866d
commit f3dc0e6eee
56 changed files with 2341 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
packages/zapier-user-docs/07-attachments-and-metadata.md Normal file
View file

@ -0,0 +1,16 @@
# 7. Attachments and metadata (not on chain)
The blockchain stores hash + time + certificate. Everything else is **off-chain WORM**:
| Field | Chain | Archive (`verae.archive.put`) |
|-------|-------|-------------------------------|
| SHA-256 | yes | key |
| Public metadata JSON | no | `kind: publicMeta` |
| Encrypted private metadata | no | `kind: privateMeta` |
| File bytes | no | `kind: file` + `contentSha256` |
Set **includeAttached** on wait/lookup when you need those records back. Middleware then broadcasts `verae.archive.query`. Each archive uses a bloom filter: **if it does not have the hash, it sends nothing**. Archives that have data reply; the aggregator merges them into `receipts[]` and `files[]`.
Bloom false positives are possible (empty reply after a maybe). False negatives must be rare.
Private metadata is only returned on authenticated archive replies. Zapier still never talks to NATS; it only sees the JSON middleware built.