Show me the data.
The single URL we send when an institution asks "prove you actually have data." Every count below is read live from the production Supabase. Every identifier is verifiable on a third-party registry. Every cron run and every memo carries a timestamp that can't be backdated.
Avena belongs in the institutional data infrastructure category alongside Bloomberg (equities, fixed income), MSCI (indices), Refinitiv (workflow + data), S&P Global (credit, indices), Moody's Analytics (risk, structured finance), and CoStar (US commercial real estate). The European residential property equivalent did not exist before Avena. The infrastructure below makes the claim verifiable.
Registries that prove we exist independently of this domain.
If avenaterminal.com disappeared tomorrow, the dataset and methodology would still resolve through these permanent academic and machine-readable registries.
Permanent archive. Each version of the dataset is deposited with an immutable DOI. If the page above ever fails to resolve, the underlying data is preserved by CERN.
Machine-readable entity in Wikidata — the cross-reference layer for the entire AI and academic ecosystem.
Open property intelligence protocol. Schema is published and citable independently of Avena Terminal.
Full API surface declared in a single specification document. Any client SDK can be auto-generated.
Declared inclusion policy for AI training corpora. Already crawled by major LLM operators.
Recognised Tech Partner of the Royal Institution of Chartered Surveyors — the global standard-setter for property valuation.
What the database actually contains, right now.
Each row below is a SELECT COUNT(*) query executed in the last 5 minutes against the production Supabase. The earliest timestamp shows how far back the moat goes per ledger. The "added 30d" column shows the compounding rate — if it's positive, the moat is widening daily.
| Ledger | Category | Rows | +24h | +7d | +30d | Span | Latest |
|---|---|---|---|---|---|---|---|
| avena_history | Index history | 92 | 1 | 69 | 90 | 31d | 20h ago |
| price_snapshots | Price history | 1,881 | 0 | 0 | 0 | <1d | 48d ago |
| sold_properties | Transactions | 0 | 0 | 0 | 0 | — | — |
| memo_generations | Memos | 5 | 0 | 5 | 5 | <1d | 3d ago |
| avm_queries | Valuations | 0 | 0 | 0 | 0 | — | — |
| precursor_signals | Intelligence | 11 | 1 | 11 | 11 | 5d | 14h ago |
| genesis_scenarios | Intelligence | 11 | 0 | 11 | 11 | <1d | 5d ago |
| genesis_outputs | Intelligence | 75 | 0 | 75 | 75 | <1d | 5d ago |
| counterpart_developers | Counterpart | 10 | 0 | 10 | 10 | <1d | 5d ago |
| counterpart_stress_alerts | Counterpart | 39 | 0 | 0 | 0 | — | — |
| cron_logs | Operations | 1,044 | 41 | 273 | 1,001 | 33d | 2h ago |
| macro_indicators | Macro | 31 | 16 | 31 | 31 | 3d | 14h ago |
| causal_indicators | Macro | 20 | 0 | 20 | 20 | <1d | 3d ago |
| regime_history | Macro | 67 | 2 | 41 | 64 | 32d | 14h ago |
| findings | Findings | 113,877 | 0 | 0 | 0 | — | — |
| feed_sync_log | EU ingestion | 89 | 27 | 89 | 89 | 3d | 17h ago |
| Total · all 16 ledgers | 117,252 | 88 | 635 | 1,407 | moat compounding | ||
16 ledgers shown · 105+ tables total · Plus the Spain corpus (1,881 scored properties in properties_registry) · See /stack §04 for the full schema map.
The engine ran ten times before you opened this page.
Sampled directly from cron_logs. Each row is one scheduled execution — agent, status, exact start timestamp, and wall-clock duration. The duration alone proves the work happened: you can't fake a 4,231ms Postgres write.
| Agent | Status | Started | Duration |
|---|---|---|---|
| eu-ingestion | success | 2026-05-26 18:34:49 UTC | 1,102ms |
| property-augment | success | 2026-05-26 17:29:12 UTC | 202,820ms |
| eu-rescore | success | 2026-05-26 17:05:28 UTC | 1,573ms |
| pricing-history | success | 2026-05-26 15:01:57 UTC | 2,935ms |
| prometheus | success | 2026-05-26 14:48:11 UTC | 2,115ms |
| eu-rescore | success | 2026-05-26 13:57:59 UTC | 1,130ms |
| property-augment | success | 2026-05-26 13:57:40 UTC | 209,294ms |
| eu-ingestion | success | 2026-05-26 12:33:41 UTC | 1,125ms |
| courier | success | 2026-05-26 09:30:28 UTC | 1,152ms |
| property-augment | success | 2026-05-26 09:04:16 UTC | 186,667ms |
Each memo carries a SHA-256 of its input.
Every memo generated by Avena writes the SHA-256 hash of its thesis to the persistence layer at generation time. If a recipient forwards a memo that's been tampered with, the hash will not match. This is the lightweight version of the AVP (Avena Verification Protocol) — full cryptographic signing of every output is on the v2 roadmap.
Every day the gap to a competitor widens.
Price snapshots
4× daily price capture per property × 1,881 Spain properties × every day Avena runs = ~5,500 immutable snapshots/day. A competitor starting today can never recreate yesterday's prices.
Sold detection
Properties that disappear from a feed are persisted to sold_properties with their last seen price. This is a one-way ratchet — it compounds forever.
Macro indicators
Daily ECB SDW + Eurostat snapshots, archived with their fetched_at timestamp. Even ECB cannot recreate the exact sequence of revisions over time.
Prediction ledger
Every prediction is written before any outcome is known. Verified hit rate accumulates monotonically. A new market entrant starts at zero credibility.
Memo + AVM corpus
Every user-generated memo and valuation contributes to the training corpus + reveals demand patterns. This is the proprietary intelligence layer.
Findings ledger
Every signal the swarm detects writes a row. The findings table is append-only and compounds with every cron tick. Visible at /eu-takeover.
Federated partners
Each new partner brings country-specific data Avena did not previously have. Network effect — partners attract partners.
AI citation network
Daily monitoring of when Avena is cited by Perplexity, Brave, You.com, Claude, GPT. As citations grow, Avena becomes the source AI models reach for first.
What to ask for in due diligence.
If you're evaluating Avena Terminal for procurement, here's the checklist the page above answers:
- Does the data exist? The §02 ledger is a live SELECT COUNT(*) against the production database. You can verify any number by hitting
/api/v1/...directly. - Does the data accumulate? The +24h / +7d / +30d columns show net new rows per ledger over the rolling window. If these are positive, the moat is widening.
- How far back does it go? The "Span" column shows time elapsed from earliest to latest entry per ledger. Longer = deeper moat.
- Where else does the data live? Zenodo DOI 10.5281/zenodo.19520064 is the permanent archive; Wikidata Q139165733 is the cross-reference. Both independent of avenaterminal.com.
- Can a memo be tampered with? Each memo writes a SHA-256 of its thesis at generation time. If the rendered memo doesn't hash to the same value, it's been altered.
- Can the operation be audited? Every cron run logs to
cron_logswith status + duration. Every memo tomemo_generations. Every AVM toavm_queries. Every API call toapi_usage_log. - Where is the data resident? Supabase Postgres in eu-central-1 (Frankfurt). All EU data remains in the EU. See /governance §5.
Formal procurement enquiries: institutional@avenaterminal.com
v2026.05 · Live read · cite as avenaterminal.com/proof @ 2026-05-26 20:13 UTC