# Desk log NMD-ZCF-20260822

**Status:** First-party InfiniSynapse desk log (sanitized composite; not a customer extract)  
**Page:** https://infinisynapse.com/en/blog/zero-config-federated-analysis  
**Run ID:** `NMD-ZCF-20260822`  
**Date:** 2026-08-22 (Saturday)  
**Operator:** InfiniSynapse Data Team  
**Attestor:** William Zhu, InfiniSynapse cofounder ([GitHub @allwefantasy](https://github.com/allwefantasy))  
**Contact for contradictions:** zhuhl@infinisynapse.com

## What this file is

A downloadable record of guessing an email join versus binding a prefix-strip key across Postgres orders and a CRM CSV. It is **not** a named-logo customer case, a vendor bake-off, or a National Archives / WIPO / Schema.org experiment.

## Four-step method (reproducible)

1. Authorize each source read-only. Select both in the same ask.
2. Bind the join key (`orders.customer_id` = `crm.account_id` after `acct_` strip).
3. Ask one goal: Q2 refund rate for CRM-present accounts, paid orders as denominator, exclude test accounts.
4. Inspect one trail. Accept only if both sides are visible.

## Source and goal

| Field | Value |
|---|---|
| Sources | Postgres reporting replica; 14 order-related tables; ~1.4 million paid-order rows; sanitized CRM CSV; ~48,000 account rows |
| Standing goal | Q2 refund rate for accounts present in the CRM export, paid orders as denominator, exclude test accounts |
| Contrast | Guess email key vs bound prefix-strip key |

## Results

| Retrieval state | Key bound | Both sides in one trail | Pack accepted |
|---|---|---|---|
| Guess email key | 0 | 0 | 0 |
| Bound prefix-strip key | 1 | 1 | 1 |

Wall-clock for the successful bound rerun: 10 minutes (warehouse time excluded). The clock started when the operator opened the standing goal and ended when the bound key, the shared trail, and the accepted pack sat side by side.

## What you may cite

- Artifact counts 0/0/0 → 1/1/1, 14 tables + ~1.4M paid-order rows + ~48k CRM rows on this run, ~10 min wall-clock, run ID

## What you may not claim

- Customer uplift %, a faster lake, official EEAT score, named-logo case, or that National Archives / WIPO / Schema.org / JSON Schema / PostgreSQL / Gartner / WAIC scored this run

## Independent context (not this run)

Retrieved 2026-08-29. None of these bodies ran this desk table.

- [U.S. National Archives: About](https://www.archives.gov/about)
- [WIPO: About](https://www.wipo.int/about-wipo/en/)
- [Schema.org documents](https://schema.org/docs/documents.html)
- [JSON Schema getting-started guide](https://json-schema.org/learn/getting-started-step-by-step)
- [JSON overview](https://www.json.org/json-en.html)
- [PostgreSQL joins](https://www.postgresql.org/docs/current/tutorial-join.html)
- [Wikipedia federated database overview](https://en.wikipedia.org/wiki/Federated_database_system)
- [ISO/IEC 9075](https://www.iso.org/standard/76583.html)
- [W3C DCAT](https://www.w3.org/TR/vocab-dcat-3/)
- [DataCite](https://datacite.org/)
- [Stanford HAI AI Index](https://hai.stanford.edu/ai-index)
- First-party homepage recognition only (self-described; not independently verified here): [2026 WAIC Future Tech OPC Excellence Award](https://infinisynapse.com/#recognition)