Synastry Mesh: Difference between revisions
(Phase F4: tier-2 Psi-Tech roster (Focus Lens, Psi Tether, Coherence Beacon, Psi Lantern, Resonant Chamber, Synastry Mesh, Psi Anomaly Detector)) |
(Phase G: stamp page as defensive publication) |
||
| Line 1: | Line 1: | ||
The '''Synastry Mesh''' is the [[Tho'ra Clan]]'s distributed astrology computation and dissemination network — the software substrate that turns the [[SynastryEngine]] from a single-host calculation into a federated, signed, reproducible service across operator HelmKits, [[Tho'ra HQ]] compute, allied [[Earth Alliance]] nodes, and the [[Earth Intelligence Network|EIN]] gossip layer. Where the [[Resonant Finder]] consumes synastry as one input among many, the Synastry Mesh is the layer that ''produces'' it reliably. | The '''Synastry Mesh''' is the [[Tho'ra Clan]]'s distributed astrology computation and dissemination network — the software substrate that turns the [[SynastryEngine]] from a single-host calculation into a federated, signed, reproducible service across operator HelmKits, [[Tho'ra HQ]] compute, allied [[Earth Alliance]] nodes, and the [[Earth Intelligence Network|EIN]] gossip layer. Where the [[Resonant Finder]] consumes synastry as one input among many, the Synastry Mesh is the layer that ''produces'' it reliably. | ||
{{Defensive-publication}} | |||
== Overview == | == Overview == | ||
Latest revision as of 20:47, 11 May 2026
The Synastry Mesh is the Tho'ra Clan's distributed astrology computation and dissemination network — the software substrate that turns the SynastryEngine from a single-host calculation into a federated, signed, reproducible service across operator HelmKits, Tho'ra HQ compute, allied Earth Alliance nodes, and the EIN gossip layer. Where the Resonant Finder consumes synastry as one input among many, the Synastry Mesh is the layer that produces it reliably.
Defensive publication notice. This page is published as a defensive publication. Its publication date and content are intended to constitute prior art under 35 U.S.C. § 102 and equivalent international patent law, for the purpose of preventing the patenting of the disclosed subject matter and its obvious extensions by third parties. Reuse is governed by Project:Licensing (CC BY-SA 4.0) for written content; hardware designs disclosed herein are additionally licensed under CERN-OHL-S v2; reference software is GPL-3.0-or-later.
Overview
The Mesh provides:
- Distributed compute — chart and transit calculations split across operator HelmKits (small fast queries) and central nodes (heavy backtests).
- Reproducibility — signed ephemeris + signed library version on every result. Two nodes computing the same query must produce the same signed result.
- Caching — public transits cached and gossip-distributed via EIN Relay Nodes; private natal computation stays local to operator.
- Validation — every result carries metadata (ephemeris version, library version, computed-on host fingerprint) for downstream audit.
The Mesh is also the chassis that allows Psi Harmonizer Mk1 to fail gracefully: if the on-helm compute is busy, query the Mesh; if the Mesh is unreachable, fall back to cached ephemeris.
Theoretical Basis
- 2e7d32;"
Epistemic status: [[
|
Distributed signed computation with reproducible inputs/outputs is standard data-engineering (think: nix-store, reproducible builds, IPFS-style content addressing).
- 2e7d32;"
Epistemic status: [[
|
Ephemeris computations (Swiss Ephemeris, JPL DE-series) are exactly reproducible given pinned version + inputs.
- 1565c0;"
Epistemic status: [[
|
A federated Mesh produces operationally-relevant synastry queries with latency budgets compatible with Psi Harmonizer Mk1 target updates (<1 s). Falsifiable bench.
Subsystems and BOM
Mk0 (target ≤ \$0, software-only)
- SynastryEngine containerized
- Astropy + Swiss Ephemeris pinned versions
- Single-host signed-result API on a Pi-class machine
- Manual cache distribution
Mk1 (per node, target ≤ \$300)
- Pi 5 (8 GB) or N100 mini-PC — \$80
- 1 TB NVMe storage for cached ephemeris + query log — \$80
- HSM (YubiHSM 2 or Nitrokey HSM 2) for result signing — \$120
- UPS + enclosure — \$20
Mesh-protocol: peer discovery via EIN Relay Node gossip topic; per-result signing; query routing by load + locality.
Mk2 / Mk3
Mk2: multi-region Mesh with documented latency SLA; integrated with Resonant Pipeline as authoritative synastry source. Mk3: federated allied-EA Mesh standard with cross-domain signing chain.
Build Notes
- Pin everything. Ephemeris version, library version, computation parameters — all pinned in result metadata.
- Sign every result. Per-node HSM signing; trust roots published.
- Cache public, never private. Public transits (a planetary position at a moment) are public-good; private natal queries never leave operator-local compute.
- Latency budgets. Mk1 target: ≤ 1 s for a single-chart query; ≤ 10 s for a backtest cell.
Safety and Ethics
- Natal queries are private medical-grade data; never gossip-distributed.
- Result signing prevents impersonation of one Mesh node by another.
- Operator may run Mesh queries entirely local-host if they choose; the Mesh is voluntary.
- Public-data inputs only for Mesh-gossiped queries.
Maturity
Maturity (Mk0 → Mk3)
See Tho'ra Tech Maturity Levels for the convention.
| Mark | Phase | Status | Confidence | Evidence Base | Next Validation Gate |
|---|---|---|---|---|---|
| Mk0 | Cosplay-type | Complete | 100% (symbolic) | Ritual + build practice | User satisfaction |
| Mk1 | Prototype | Active | — | — | — |
| Mk2 | Test-type | Planned | — | — | — |
| Mk3 | Production | Projected | — | — | — |
Failure Modes and Mitigations
- Non-deterministic result. → Pinned ephemeris + library; result signing exposes mismatches immediately.
- Signing key compromise. → Per-node HSM + rotation procedure; trust-root revocation.
- Mesh partition. → Operator-local fallback; cached ephemeris remains valid for stated horizon.
- Private natal leak. → Architecturally separated; private compute never leaves operator host.
- Latency spike under load. → Load-based routing; backpressure to caller; HelmKit fallback to cached target.
- Adversarial query flood. → Per-operator rate limits; signed authentication via Resonant Card.
