Partner walkthrough

Ten stops, ten minutes No AI Training

A guided tour of every surface a partner, investor, or pilot customer should see — in the order that builds the picture. Each stop has its real URL, what to look for, and the proof that backs it. The first three stops are on the live swarm console; the rest sit on dedicated surfaces. Click any badge below to jump.

Target reliability · 99.78% Real URLs · click any badge below to jump

Walkthrough

01 02 03 04 05 06 07 08 09 10

Live swarm console ↗

See real sensor nodes report on a real network.

What you see: Live grid of 6 sensor nodes in a sample zone. Each card shows battery state, last reading, online/weak/wet status. Coordination heartbeat polls every 30 seconds; the System health expand panel shows target reliability + root identity.
Look for: The Live pill pulses. A node card flips to 'wet' when the simulator runs. The sticky lockup bar shows BioEchem × EpochCore and the proprietary banner.
Proof: Every reading is signed at the chip. The receipt-chip column shows the rolling hash.

Click a receipt — see the signed proof bundle ↗

Open the audit envelope behind a single event.

What you see: Click any receipt-chip in the event log. The proof-bundle modal shows: the canonical JSON, a tamper-proof hybrid signature, a curl command to verify offline, copy-JSON and download-bundle buttons.
Look for: The bundle carries a RAS anchor — the canonical root every signed record chains back to. Verifier protocol on /verifier.
Proof: Partners can verify the signature on their own infrastructure with no shared secret. The verifier walkthrough is on /agents.

Monthly audit report ↗

Show what an end-of-month evidence package looks like.

What you see: Month picker, KPI strip (uptime, alerts handled, anomalies caught), per-node battery passport summary, signed event log table, full bundle-hash signature block at the bottom, print-to-PDF button.
Look for: The signature block at the bottom carries the same ras_anchor as the live console. The print-to-PDF output is the form an insurer or regulator would file.
Proof: Independent of who hosts the dashboard — the proof bundle is self-verifying.

Weather Director ↗

The forecast layer that decides when to escalate a wet-event read.

What you see: Geolocation-based 7-day forecast, next 6-hour precipitation curve, and three watch tiles — flood, frost, heat. Each tile is mapped to a specific BioSwarm event expectation (e.g., flood watch + ≥2 nodes wet ⇒ consensus event).
Look for: Weather pulls from Open-Meteo (no API key needed; works for any partner anywhere).
Proof: The same surface a pilot operator sees. Forecast joins sensor reality at the consensus rules.

26-role system map ↗

See every named role in the platform — what's ready, what's planned.

What you see: Plain-English taxonomy of every software role. AgriOrchestrator, HiveRouter, LeafGuard, BatteryPassportKeeper, FloodConsensusDispatcher, and 21 more. Each entry has a 'also known as' alias + a status badge.
Look for: This is the page Pei + IBM see. No 'AI / agent / quantum / algorithm' marketing language.
Proof: Same root identity (40668c…) ties every role back to the canonical RAS authority.

8 BioSwarm × warehouse-mapping pilots ↗

Show the partner-facing pilot surface bound under molecule-gen.org.

What you see: Eight specific use-case pages: refill kit fulfillment, hydroponic rack mapping, greenhouse bench mapping, mushroom cultivation rooms, compost pile provenance, seed-bank lineage, cold-chain receiving, end-to-end leaf-to-crate.
Look for: Each pilot page has a persona panel — Marta (greenhouse), Liz (hydroponic), Dr. Kim (seed bank), Rashid (compost), Pei (refill), Mike (capital).
Proof: Dual-RAS anchored: served from e5586ef9… (molecule-gen root) and chains subject-matter to 40668c… (BioSwarm root). Nothing laundered.

Pricing + pilot terms ↗

See the three tiers and what each one buys.

What you see: Pilot tier (single-zone, $1,500/month, 60-day audit-grade trial) · Pro tier (multi-zone with operator support, $4,500/month) · Enterprise tier (custom — partner integration, dedicated channel, full export). Mike Beard investor CTA at the bottom.
Look for: Plain copy, no enterprise theatre. Founder-editable dollar amounts.
Proof: Tier scope maps directly to the surfaces in this walkthrough.

Add your first node ↗

10-minute path from unboxing to first signed reading.

What you see: Five-step wizard with progress bar: unbox + power · QR-scan + register · set thresholds · BLE-pair Wi-Fi credentials (sealed, never plaintext) · receive first signed reading on the dashboard.
Look for: BLE pairing uses ECDH + AES-256-GCM with node serial as AAD. Wi-Fi credentials never cross BLE in the clear.
Proof: Arduino UNO R4 WiFi reference platform; hardware-rooted identity from ECC608 Trust&Go on the carrier board.

Operator request queue ↗

Where the threshold + alert-routing requests actually go.

What you see: Operator-only surface. Admin-key gate (sessionStorage). Filter by request kind, status, tenant. Resolve / Reject / Snooze / Reopen actions. Each submission persists to KV for 30 days; the workflow is real even if the channel wiring (SMS / webhook) is deferred to a later session.
Look for: Two real workflows already firing: Resend email to the founder + Slack/Discord webhook (if those keys are set). Notification is fire-and-forget — the queue is the durable source of truth.
Proof: Sealed authorization on every list/mutation call, with constant-time bearer comparison.

Ready to take the next step?

This walkthrough is what we show partners before a pilot kickoff. If any stop above raised a question, the right next move is either a 30-minute call or a pilot scoping conversation — whichever fits.

Already convinced? The pilot tier covers a single zone for 60 days with audit-grade evidence — enough to validate the wedge with real readings, real proof bundles, and a real operator queue.

See pricing & pilot terms Onboard a node Audit it yourself Investor brief