Verae Time × Zapier

README

site/overview/README.md

README

Verae Time × Zapier — system overview

High-level description of the whole system: what it is, which independent git repositories implement it, how it stays up, how it behaves when the local network fails, and how it talks to the central Verae NATS.IO 3-server cluster. New work is added by new address routing, not by teaching Zapier about NATS.

This repo: https://git.georgelambert.org/marchon/overview
Bring online: https://zapier.georgelambert.org/packages/verae-ops/GETTING-STARTED.pdf
Live catalog (PDF by default): https://zapier.georgelambert.org/ · Markdown indexes
Clone: ssh://git@git.georgelambert.org:2223/marchon/overview.git

Table of contents

  1. System — what runs where; Zapier never speaks NATS
  2. Modules and repositories — every independent Forgejo repo
  3. NATS.IO 3-server cluster — JetStream, subjects, who may connect
  4. Uptime — replica floors, restart, SSH spread
  5. Local network failures — reconnect, silence, pending, failover
  6. Address routing — how to add unplanned functions
  7. External resources — searches, storage, chain
  8. Architectural diagrams — SVG + mermaid
  9. Expansion template — verae-nats-process
  10. Documentation index — pointer into all other docs

One-screen picture

System context

Zapier → HTTPS zappier-edge → HTTPS verae-middleware → NATS cluster → workers, WORM archives, tree nodes. Chain HTTPS is api.veraetime.net (or MOCK). Fleet keeps minimum copies, including tree nodes.

Independent repositories (Forgejo)

Repo Role
overview This document
verae-ops Docker, Proxmox, VMs, dedicated hardware
verae-nats-process Model for a new addressed process
master-zapier-plan-draft Monorepo snapshot
zappier-edge Metered public HTTPS
verae-middleware Zapier HTTP + NATS workers
verae-zapier-app Zapier Platform app
verae-activate Activate-now app
verae-request-splitter Hash vs attachments
verae-archive-worm Bloom WORM node
verae-archive-aggregator Archive reply merge
verae-tree-node Merkle leaf proofs
verae-fleet Replica floor + SSH hosts
verae-zapier-simulator Trace console
zapier-user-docs Signup → lookup
zapier-docs-master Per-module SUMMARY + NATS

Clone any of them: git clone ssh://git@git.georgelambert.org:2223/marchon/<name>.git (SSH port 2223).

Operator console (loopback)

Fleet, message Trace, and Docs share one shell at http://127.0.0.1:3850/ (verae-fleet). Not public. See CONSOLE.pdf.

Fleet tab
Trace tab
Docs tab

Start at the top. Architecture is second. Everything else is reference.

1. High-level (non-technical)

Document What it is
This overview Whole system in one place
Modules and repositories Short names of every independent repo
zapier-docs-master One-line SUMMARY + NATS per module
zapier-user-docs Signup → register a hash → lookup

2. Architecture

Document What it is
NATS 3-server cluster Who may connect; private URLs
Uptime Replica floors, restart, SSH hosts
Local network failures Reconnect, bloom silence, failover
Address routing Unplanned functions as new subjects
External resources Chain, WORM, tree-node search
Diagrams SVG + mermaid
Fleet Operator replica control
Module NATS map Address table
Archive / bloom Multipart and multi-receipt
Tree nodes Bulk Merkle leaves
Composition zappier + middleware HTTPS

3. Remaining documentation

Document What it is
Documentation index A–Z and catalog URLs
Expansion template / verae-nats-process Copy this to add an address
Operator console Screenshots of Fleet / Trace / Docs
Simulator Standalone trace (also inside the console)
Zapier developer setup CLI / login / push
Live catalog https://zapier.georgelambert.org/ (PDF) · Markdown indexes

Credits

Design: Scott Lindsey, George Lambert, NATS.IO, and Grok-Code by Grok.com.