dev-api: add developer portal, OpenAPI spec, and Flatenbadet case study
- New /developers/ page with API docs, SDKs, pricing, use cases - OpenAPI 3.0 spec for Orders, Missions, Photos, Analytics - Case study: Glasskiosken i Flatenbadet — complete ROI analysis - Updated /order/ with recurring missions and frequency dropdown
This commit is contained in:
Bernt
@@ -0,0 +1,106 @@
|
||||
# Glossary System — Landvex Ecosystem
|
||||
|
||||
## Overview
|
||||
|
||||
A **living database** of terms used across quiXzoom, AMOS, and Landvex. Automatically updated, SEO-optimized, and responsive.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
glossary/
|
||||
├── glossary-data.json # Master data file (JSON)
|
||||
├── index.html # Dynamic renderer (quixzoom.com/glossary/)
|
||||
├── update-glossary.js # Auto-revision script
|
||||
├── deploy.sh # Deployment script
|
||||
├── smp-tag-helper.js # SMP tag auto-linker
|
||||
├── dist/ # Generated static files
|
||||
│ ├── index.html # All terms
|
||||
│ ├── glossary-quixzoom.html # quiXzoom terms only
|
||||
│ ├── glossary-aamos.html # AMOS terms only
|
||||
│ └── glossary-landvex.html # Landvex terms only
|
||||
└── README.md
|
||||
```
|
||||
|
||||
## Features
|
||||
|
||||
### ✅ Dynamic JSON Database
|
||||
- All terms stored in `glossary-data.json`
|
||||
- Categories: Platform, Technical, Payment, Legal, Core, AMOS Engine, Landvex, quiXzoom, Product
|
||||
- Cross-domain support (terms can belong to multiple domains)
|
||||
|
||||
### ✅ Auto-Revision
|
||||
- Daily cron job at 02:00 UTC
|
||||
- Scans source files for new SMP tags
|
||||
- Updates glossary automatically
|
||||
- Regenerates all static files
|
||||
|
||||
### ✅ SEO Optimized
|
||||
- Structured data (Schema.org DefinedTermSet)
|
||||
- Canonical URLs per domain
|
||||
- Meta descriptions and Open Graph tags
|
||||
- Robots: index, follow
|
||||
|
||||
### ✅ Responsive Design
|
||||
- Mobile-first approach
|
||||
- Sticky navigation with A-Z jump
|
||||
- Live search with instant filtering
|
||||
- Domain filter buttons
|
||||
|
||||
### ✅ SMP Tag System
|
||||
- HTML: `<span data-smp="term-id">Term</span>`
|
||||
- Auto-converts to glossary links
|
||||
- Tooltips with short definitions
|
||||
|
||||
## Usage
|
||||
|
||||
### Adding a New Term
|
||||
|
||||
1. Edit `glossary-data.json`
|
||||
2. Add term object:
|
||||
```json
|
||||
{
|
||||
"id": "unique-id",
|
||||
"name": "Term Name",
|
||||
"category": "technical",
|
||||
"short": "Brief description",
|
||||
"long": "Full definition...",
|
||||
"context": "Example usage...",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": ["other-term-id"],
|
||||
"domains": ["quixzoom", "aamos"]
|
||||
}
|
||||
```
|
||||
|
||||
3. Run `node update-glossary.js`
|
||||
4. Deploy with `./deploy.sh`
|
||||
|
||||
### Using SMP Tags
|
||||
|
||||
In HTML:
|
||||
```html
|
||||
<span data-smp="amos">AMOS</span> is our AI platform.
|
||||
```
|
||||
|
||||
Include helper:
|
||||
```html
|
||||
<script src="/glossary/smp-tag-helper.js"></script>
|
||||
```
|
||||
|
||||
## Domains
|
||||
|
||||
| Domain | URL | Terms |
|
||||
|--------|-----|-------|
|
||||
| All | quixzoom.com/glossary/ | 100 |
|
||||
| quiXzoom | quixzoom.com/glossary/ | 79 |
|
||||
| AMOS | aamos.ai/glossary/ | 53 |
|
||||
| Landvex | landvex.com/glossary/ | 41 |
|
||||
|
||||
## Auto-Revision Schedule
|
||||
|
||||
- **Daily**: 02:00 UTC
|
||||
- **Job ID**: `737ba486-ffd1-45b9-8b04-3069888d5012`
|
||||
- **Actions**: Scan → Update → Generate → Deploy
|
||||
|
||||
## Last Updated
|
||||
|
||||
2026-07-14
|
||||
Executable
+30
@@ -0,0 +1,30 @@
|
||||
#!/bin/bash
|
||||
# Deploy glossary to all domains
|
||||
|
||||
set -e
|
||||
|
||||
DIST_DIR="/home/bernt/.openclaw/workspace/glossary/dist"
|
||||
DATA_FILE="/home/bernt/.openclaw/workspace/glossary/glossary-data.json"
|
||||
|
||||
echo "🚀 Deploying Glossary..."
|
||||
|
||||
# Deploy to quixzoom.com
|
||||
echo "📤 Deploying to quixzoom.com..."
|
||||
aws s3 cp "$DIST_DIR/index.html" s3://quixzoom.com/glossary/index.html --content-type "text/html; charset=utf-8"
|
||||
aws s3 cp "$DATA_FILE" s3://quixzoom.com/glossary/glossary-data.json --content-type "application/json"
|
||||
aws cloudfront create-invalidation --distribution-id E1XAMPLE --paths "/glossary/*" > /dev/null 2>&1 || true
|
||||
|
||||
# Deploy to landvex.com
|
||||
echo "📤 Deploying to landvex.com..."
|
||||
aws s3 cp "$DIST_DIR/index.html" s3://landvex.com/glossary/index.html --content-type "text/html; charset=utf-8"
|
||||
aws s3 cp "$DIST_DIR/glossary-landvex.html" s3://landvex.com/glossary/landvex.html --content-type "text/html; charset=utf-8"
|
||||
aws s3 cp "$DATA_FILE" s3://landvex.com/glossary/glossary-data.json --content-type "application/json"
|
||||
aws cloudfront create-invalidation --distribution-id E2XAMPLE --paths "/glossary/*" > /dev/null 2>&1 || true
|
||||
|
||||
# Deploy to aamos.ai
|
||||
echo "📤 Deploying to aamos.ai..."
|
||||
aws s3 cp "$DIST_DIR/glossary-aamos.html" s3://aamos.ai/glossary/index.html --content-type "text/html; charset=utf-8"
|
||||
aws s3 cp "$DATA_FILE" s3://aamos.ai/glossary/glossary-data.json --content-type "application/json"
|
||||
aws cloudfront create-invalidation --distribution-id E3XAMPLE --paths "/glossary/*" > /dev/null 2>&1 || true
|
||||
|
||||
echo "✅ Glossary deployed to all domains!"
|
||||
Vendored
+1068
@@ -0,0 +1,1068 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Glossary — aamos</title>
|
||||
<meta name="description" content="Every term used on aamos. Defined precisely and kept current.">
|
||||
<link rel="canonical" href="https://aamos.ai/glossary">
|
||||
<meta name="robots" content="index, follow">
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "DefinedTermSet",
|
||||
"name": "aamos Glossary",
|
||||
"description": "Complete glossary of terms",
|
||||
"publisher": {"@type": "Organization", "name": "Landvex Inc", "url": "https://www.landvex.com"}
|
||||
}
|
||||
</script>
|
||||
<style>*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
|
||||
:root {
|
||||
--bg: #ffffff; --bg-off: #f5f5f7; --bg-card: #ffffff;
|
||||
--text: #1d1d1f; --text-secondary: #6e6e73;
|
||||
--blue: #0066FF; --blue-light: #e8f0ff;
|
||||
--green: #00a550; --green-light: #e6f7ee;
|
||||
--purple: #7b2fff; --purple-light: #f0e8ff;
|
||||
--orange: #e8660a; --orange-light: #fff0e6;
|
||||
--pink: #ff3366; --pink-light: #ffe8f0;
|
||||
--radius: 18px; --radius-sm: 8px; --border: #d2d2d7;
|
||||
--nav-height: 64px; --shadow-hover: 0 12px 40px rgba(0,0,0,.10);
|
||||
}
|
||||
@media (prefers-color-scheme: dark) {
|
||||
:root {
|
||||
--bg: #000000; --bg-off: #1c1c1e; --bg-card: #1c1c1e;
|
||||
--text: #f5f5f7; --text-secondary: #98989f; --border: #3a3a3c;
|
||||
--blue-light: rgba(0,102,255,.15); --green-light: rgba(0,165,80,.15);
|
||||
--purple-light: rgba(123,47,255,.15); --orange-light: rgba(232,102,10,.15);
|
||||
--pink-light: rgba(255,51,102,.15); --shadow-hover: 0 12px 40px rgba(0,0,0,.5);
|
||||
}
|
||||
}
|
||||
html { scroll-behavior: smooth; }
|
||||
body {
|
||||
font-family: -apple-system, BlinkMacSystemFont, 'SF Pro Display', 'SF Pro Text', 'Helvetica Neue', Arial, sans-serif;
|
||||
background: var(--bg); color: var(--text); line-height: 1.6; -webkit-font-smoothing: antialiased;
|
||||
}
|
||||
.nav {
|
||||
position: sticky; top: 0; z-index: 100; height: var(--nav-height);
|
||||
background: rgba(255,255,255,.82); -webkit-backdrop-filter: blur(20px) saturate(180%);
|
||||
backdrop-filter: blur(20px) saturate(180%); border-bottom: 1px solid var(--border);
|
||||
display: flex; align-items: center; gap: 16px; padding: 0 24px;
|
||||
}
|
||||
@media (prefers-color-scheme: dark) { .nav { background: rgba(0,0,0,.82); } }
|
||||
.nav-logo { font-size: 1.25rem; font-weight: 800; color: var(--text); text-decoration: none; letter-spacing: -.04em; white-space: nowrap; flex-shrink: 0; }
|
||||
.nav-logo .x { color: var(--blue); }
|
||||
.nav-divider { width: 1px; height: 20px; background: var(--border); flex-shrink: 0; }
|
||||
.nav-title { font-size: .9375rem; font-weight: 600; color: var(--text-secondary); white-space: nowrap; flex-shrink: 0; }
|
||||
main { max-width: 860px; margin: 0 auto; padding: 0 24px 80px; }
|
||||
.page-header { padding: 64px 0 48px; text-align: center; }
|
||||
.page-header h1 { font-size: clamp(2.5rem, 6vw, 4rem); font-weight: 800; letter-spacing: -.04em; line-height: 1.05; color: var(--text); margin-bottom: 16px; }
|
||||
.page-header p { font-size: 1.125rem; color: var(--text-secondary); max-width: 480px; margin: 0 auto; }
|
||||
.letter-section { margin-bottom: 48px; }
|
||||
.letter-heading { display: flex; align-items: center; gap: 16px; margin-bottom: 20px; padding-bottom: 12px; border-bottom: 1px solid var(--border); }
|
||||
.letter-heading h2 { font-size: 2rem; font-weight: 800; color: var(--text-secondary); letter-spacing: -.04em; line-height: 1; width: 36px; flex-shrink: 0; }
|
||||
.letter-count { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-card { background: var(--bg-card); border: 1px solid var(--border); border-radius: var(--radius); padding: 28px 32px; margin-bottom: 16px; transition: box-shadow .2s, transform .2s; }
|
||||
.term-card:hover { box-shadow: var(--shadow-hover); transform: translateY(-2px); }
|
||||
.term-header { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; margin-bottom: 10px; flex-wrap: wrap; }
|
||||
.term-name { font-size: 1.3125rem; font-weight: 700; color: var(--text); letter-spacing: -.02em; line-height: 1.2; }
|
||||
.term-category { display: inline-block; padding: 4px 12px; border-radius: 20px; font-size: .75rem; font-weight: 600; letter-spacing: .02em; text-transform: uppercase; white-space: nowrap; flex-shrink: 0; margin-top: 2px; }
|
||||
.cat-platform { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-technical { background: var(--green-light); color: var(--green); }
|
||||
.cat-payment { background: var(--purple-light); color: var(--purple); }
|
||||
.cat-legal { background: var(--orange-light); color: var(--orange); }
|
||||
.cat-core { background: var(--bg-off); color: var(--text-secondary); }
|
||||
.cat-amos { background: var(--pink-light); color: var(--pink); }
|
||||
.cat-landvex { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-quixzoom { background: var(--green-light); color: var(--green); }
|
||||
.cat-product { background: var(--orange-light); color: var(--orange); }
|
||||
.term-short { font-size: 1rem; font-weight: 500; color: var(--text); margin-bottom: 12px; line-height: 1.5; }
|
||||
.term-long { font-size: .9375rem; color: var(--text-secondary); line-height: 1.65; margin-bottom: 16px; }
|
||||
.term-context { background: var(--bg-off); border-radius: var(--radius-sm); padding: 14px 18px; margin-bottom: 14px; }
|
||||
.term-context-label { font-size: .75rem; font-weight: 700; text-transform: uppercase; letter-spacing: .06em; color: var(--blue); display: block; margin-bottom: 6px; }
|
||||
.term-context p { font-size: .875rem; color: var(--text-secondary); line-height: 1.6; }
|
||||
.term-related { display: flex; align-items: center; flex-wrap: wrap; gap: 6px; }
|
||||
.term-related > span { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-related a { display: inline-block; padding: 3px 10px; border-radius: 20px; font-size: .8125rem; font-weight: 500; color: var(--blue); background: var(--blue-light); text-decoration: none; transition: background .12s, color .12s; }
|
||||
.term-related a:hover { background: var(--blue); color: #fff; }
|
||||
.last-updated { text-align: center; font-size: .8125rem; color: var(--text-secondary); margin-top: 48px; padding-top: 24px; border-top: 1px solid var(--border); }
|
||||
.term-card:target { border-color: var(--blue); box-shadow: 0 0 0 3px rgba(0,102,255,.15); }
|
||||
@media (max-width: 600px) { .nav { gap: 10px; padding: 0 16px; } .term-card { padding: 20px 18px; } .page-header { padding: 40px 0 32px; } }
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<nav class="nav">
|
||||
<a href="/" class="nav-logo">qui<span class="x">X</span>zoom</a>
|
||||
<div class="nav-divider"></div>
|
||||
<span class="nav-title">Glossary</span>
|
||||
</nav>
|
||||
<main>
|
||||
<header class="page-header">
|
||||
<h1>Every term.<br>Defined.</h1>
|
||||
<p>The complete aamos reference — from field observations to decision intelligence.</p>
|
||||
</header>
|
||||
<section class="letter-section" id="a">
|
||||
<div class="letter-heading">
|
||||
<h2>A</h2>
|
||||
<span class="letter-count">16 terms</span>
|
||||
</div>
|
||||
<article id="ai-review" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AI review</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Automated quality and specification check run on every submission before payment is triggered.</p>
|
||||
<p class="term-long">AI review is the first gate a submitted set of photos passes through. The system checks geo-accuracy (is the submission within the mission geofence?), image quality (sharpness, exposure, occlusion), specification compliance (correct angles, required elements present), and EXIF integrity (timestamp within time window, GPS data present and consistent). The result is either an approval — triggering payout — or a rejection with a reason code that the Zoomer can act on.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits 6 photos of a road segment. AI review verifies GPS coordinates match the mission location, timestamp falls within the claimed time window, and all required vantage points are covered — typically completing within 90 seconds of upload.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#approval">Approval</a><a href="#rejection">Rejection</a><a href="#submission">Submission</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Adaptive Autonomous Multi-Agent Operating System — the AI capability platform that powers Landvex intelligence products.</p>
|
||||
<p class="term-long">AMOS is not an AI system. It is an AI Capability Platform — a suite of specialised engines that process observations into structured intelligence. AMOS ingests raw field data from quiXzoom, applies computer vision, pattern recognition, and cross-referencing, and produces outputs: indices, scores, change flags, and predictive signals. AMOS is the analytical layer between reality and decisions. It is developed and sold by Landvex Inc, Houston, TX.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>quiXzoom collects 12,000 observations of bridge conditions across Sweden. AMOS processes these into an Infrastructure Risk Index — a single score per bridge that maintenance planners can prioritise by.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#index">Index</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#amos-vision">AMOS Vision</a><a href="#amos-identity">AMOS Identity</a><a href="#amos-fraud">AMOS Fraud</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-change-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Change Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Detects changes between observations over time.</p>
|
||||
<p class="term-long">The AMOS Change Engine compares current observations against historical baselines to identify additions, removals, and modifications. It powers change detection at scale, enabling proactive maintenance and early problem identification. The engine operates across multiple time scales from hours to years.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A property manager receives a quarterly change report showing that 3 buildings have new roof damage, 2 have added unauthorized structures, and 1 has removed safety equipment — all flagged automatically by the Change Engine.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#change-detection">Change detection</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-compliance" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Compliance</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Regulatory control, documentation verification, and compliance checking engine.</p>
|
||||
<p class="term-long">AMOS Compliance verifies that assets, processes, and documentation meet regulatory requirements. It checks for required signage, accessibility features, fire safety equipment, and other compliance markers. The engine maintains up-to-date regulatory rule sets for multiple jurisdictions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A retail chain uses AMOS Compliance to verify that all 200 stores meet accessibility requirements. The engine has flagged 15 stores missing required wheelchair ramps and 8 stores with inadequate emergency lighting.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-inspection">AMOS Inspection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-evidence-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Evidence Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Creates traceable evidence chains for audit, insurance, and legal proceedings.</p>
|
||||
<p class="term-long">The AMOS Evidence Engine maintains an immutable, auditable chain of custody for every observation. It records capture metadata, processing history, analysis results, and access logs in a tamper-evident format suitable for legal admissibility. Evidence packages include cryptographic hashes and timestamps.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>An insurance dispute reaches court. The AMOS Evidence Engine produces a complete evidence package showing: when the observation was captured, by which device, with what GPS accuracy, what AI analysis was performed, and who accessed the data — all cryptographically signed.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#exif">EXIF</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-fraud" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Fraud</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Skimming detection, manipulated ATM/utility meter detection, and insurance fraud prevention engine.</p>
|
||||
<p class="term-long">AMOS Fraud detects fraudulent manipulation of physical devices and systems. It identifies skimming devices on ATMs, tampered utility meters, falsified insurance claims, and other physical fraud vectors. The engine combines visual analysis with pattern matching against known fraud signatures.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A bank receives a quiXzoom observation of an ATM showing a suspicious card reader attachment. AMOS Fraud analyses the image, compares against known skimming device patterns, and flags a high-probability fraud alert within seconds.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-identity" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Identity</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Identity verification, document control, liveness detection, and fraud prevention engine.</p>
|
||||
<p class="term-long">AMOS Identity verifies that a person is who they claim to be. It processes government-issued IDs, performs liveness checks, and detects document tampering or synthetic identity fraud. The engine is used for KYC processes, access control, and high-trust verification scenarios.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes identity verification by submitting their passport and a selfie. AMOS Identity verifies the document's authenticity and matches the selfie to the ID photo with 99.7% accuracy.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#liveness-check">Liveness check</a><a href="#identity-verification">Identity verification</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-infrastructure" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Infrastructure</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Road, bridge, pole, sign, and property condition monitoring engine.</p>
|
||||
<p class="term-long">AMOS Infrastructure monitors the built environment: roads, bridges, utility poles, traffic signs, buildings, and other fixed assets. It detects deterioration, damage, and changes over time, producing condition indices and maintenance prioritisation scores. The engine is the core capability behind Landvex's infrastructure intelligence products.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality receives monthly Infrastructure Condition Index updates for all 400 bridges in their county. AMOS Infrastructure has flagged 12 bridges showing progressive deterioration that requires inspection within 30 days.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#index">Index</a><a href="#change-detection">Change detection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-inspection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Inspection</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">General quality control and industrial inspection engine.</p>
|
||||
<p class="term-long">AMOS Inspection provides general-purpose quality control and inspection capabilities for industrial applications. It detects manufacturing defects, assembly errors, and quality deviations from specification. The engine is configurable for specific industry standards and can be trained on custom defect libraries.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A manufacturer uses AMOS Inspection to quality-check 10,000 units per day. The engine detects surface scratches, dimensional deviations, and colour mismatches with 99.2% accuracy, reducing manual inspection workload by 80%.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#quality-score">Quality score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-prediction-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Prediction Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Estimates likely future development based on current observations and historical patterns.</p>
|
||||
<p class="term-long">The AMOS Prediction Engine uses historical data, environmental factors, and deterioration models to forecast future asset conditions. It estimates remaining useful life, predicts failure probabilities, and identifies optimal intervention timing. Predictions include confidence intervals and are updated as new observations arrive.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>AMOS Prediction Engine forecasts that Bridge 247 will reach critical condition (Index below 40) in 18 months based on current deterioration rate and traffic load. The recommendation: schedule major maintenance within 12 months to avoid emergency closure.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#index">Index</a><a href="#amos-risk-engine">AMOS Risk Engine</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-reality-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Reality Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Verifies that an image shows actual reality, not manipulated or synthetic content.</p>
|
||||
<p class="term-long">The AMOS Reality Engine detects image manipulation, deepfakes, and synthetic content. It analyses EXIF data, pixel-level artifacts, and lighting consistency to verify that an observation depicts real physical reality. This is critical for legal admissibility and insurance validity.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>An insurance claim includes photos of storm damage. The AMOS Reality Engine verifies that the images are authentic, unmanipulated, and captured at the claimed location and time — providing the foundation for claims processing.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#exif">EXIF</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-risk-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Risk Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Converts observations into risk scores and prioritisation rankings.</p>
|
||||
<p class="term-long">The AMOS Risk Engine transforms raw observations into actionable risk assessments. It combines condition data, environmental factors, historical failure rates, and consequence analysis to produce risk scores that prioritise maintenance and intervention. Risk scores are normalised and comparable across asset types and geographies.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A county's 400 bridges are ranked by risk score. The top 10 highest-risk bridges (scores above 85) receive immediate inspection orders, while the bottom 200 (scores below 30) are scheduled for routine maintenance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#index">Index</a><a href="#confidence-score">Confidence Score</a><a href="#decision-intelligence">Decision Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-safety" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Safety</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">PPE detection, workplace hazard identification, and risk assessment engine.</p>
|
||||
<p class="term-long">AMOS Safety analyses visual data to detect personal protective equipment (PPE) compliance, identify workplace hazards, and assess safety risks. It can detect missing hard hats, unsafe scaffolding, blocked emergency exits, and other safety violations from standard photographs.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A construction site manager receives daily safety observations from quiXzoom. AMOS Safety has flagged 3 instances of missing fall protection and 1 blocked fire exit across 50 observations — enabling immediate corrective action.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-vision" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Vision</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Object recognition, anomaly detection, and damage assessment engine.</p>
|
||||
<p class="term-long">AMOS Vision is the computer vision engine that identifies objects, detects anomalies, and assesses damage in visual data. It powers infrastructure inspection, property condition monitoring, and safety compliance checking. The engine can detect cracks, corrosion, vegetation encroachment, and other physical defects from standard photographs.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In AMOS</span>
|
||||
<p>A bridge inspection observation shows surface cracking. AMOS Vision measures crack width, length, and pattern, comparing against historical data to determine if the damage is new or progressive.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#change-detection">Change detection</a><a href="#amos-infrastructure">AMOS Infrastructure</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="analysis-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Analysis Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The processing tier where raw observations are transformed into structured intelligence by AMOS.</p>
|
||||
<p class="term-long">The Analysis Layer sits between the Observation Layer and the Decision Layer. Here, AMOS ingests verified field observations and applies analytical models: object detection, condition scoring, change analysis, pattern recognition, and anomaly detection. The outputs are normalised indices, confidence scores, and contradiction flags. The Analysis Layer is where data becomes insight — where thousands of individual observations are synthesised into coherent, actionable intelligence.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A thousand roof observations from across a property portfolio enter the Analysis Layer. AMOS identifies that 8% show hail damage, 2% have gutter degradation, and 90% are unchanged. The Analysis Layer outputs a Property Condition Index with regional breakdowns and recommended inspection priorities.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation-layer">Observation Layer</a><a href="#decision-layer">Decision Layer</a><a href="#reality-layer">Reality Layer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="api" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">API</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Application Programming Interface — the programmatic interface through which orderers access mission data, submission results, and platform services.</p>
|
||||
<p class="term-long">The quiXzoom API is a REST-style HTTP API that allows orderers to submit mission briefs, monitor mission status, retrieve completed submission packages (images, metadata, GeoJSON), and receive real-time updates via webhooks. Responses are in JSON format. The API uses OAuth 2.0 for authentication and HMAC-SHA256 for webhook signature verification.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company integrates the quiXzoom API into their claims management system. When a claim is filed for a specific address, an API call automatically creates a mission, and approved submission data flows directly back into the claims system without manual intervention.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#webhook">Webhook</a><a href="#oauth">OAuth</a><a href="#json">JSON</a><a href="#hmac-sha256">HMAC-SHA256</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="c">
|
||||
<div class="letter-heading">
|
||||
<h2>C</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="change-detection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Change detection</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The automated identification of differences between current observations and historical baseline data — surfacing what has changed in the physical world.</p>
|
||||
<p class="term-long">Change detection is a core AMOS capability that compares new observations against prior data to identify additions, removals, or modifications to physical assets. It powers infrastructure monitoring, property condition tracking, and environmental surveillance. Change detection operates at multiple scales: from pixel-level differences in repeated photographs to structural changes identified through computer vision. Each detected change is scored by confidence and severity, and flagged as a Contradiction when it represents an unexpected deviation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a retail park shows three new storefronts and one demolished unit compared to the baseline from six months ago. AMOS change detection automatically flags these modifications, updates the asset registry, and alerts the property manager to verify the changes.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#contradiction">Contradiction</a><a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="confidence-score" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Confidence Score</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A statistical measure of certainty attached to an observation or analysis output, expressed as a percentage.</p>
|
||||
<p class="term-long">The Confidence Score quantifies how certain the system is about a specific observation or derived insight. It is computed from multiple signals: EXIF integrity, GPS accuracy, image clarity, cross-validation against historical data, and agreement with other observations of the same asset. A high confidence score (90%+) indicates strong reliability; a low score triggers manual review or additional observation requests. Confidence scores are essential for decision-making — they tell the customer not just what was observed, but how much to trust it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection observation receives a 94% confidence score based on sharp imagery, precise GPS, and consistency with the previous inspection. An insurer uses this high-confidence observation to approve a maintenance claim without sending an engineer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="contradiction" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Contradiction</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A mismatch between observed reality and expected or previously recorded reality — a signal that something has changed or requires attention.</p>
|
||||
<p class="term-long">A Contradiction is flagged when an observation deviates significantly from the expected state: a building that was intact now shows damage, a road that was clear now has a sinkhole, or an asset that was present is now missing. Contradictions are not errors — they are valuable signals. They trigger alerts, escalate priority, and often indicate the most urgent decisions a customer must make. The Contradiction engine cross-references observations against historical data, design specifications, and regulatory baselines.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a commercial roof shows new water staining not present in the previous observation. AMOS flags this as a Contradiction, alerting the property manager to schedule repairs before the rainy season — preventing a €50,000 claim.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#confidence-score">Confidence Score</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="control-intelligence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Control Intelligence</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">Descriptive intelligence that tells you the current state of your physical assets — what is, not what to do.</p>
|
||||
<p class="term-long">Control Intelligence answers the question: 'What is the current condition of my assets?' It is the foundational layer of insight derived from observations, describing reality as it exists today: which bridges are sound, which buildings have damage, which roads need repair. Control Intelligence is objective, measurable, and verifiable. It is the raw material from which Decision Intelligence is forged — you cannot decide what to do until you know what is.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality receives Control Intelligence showing that 12% of its road bridges have surface cracking, 3% have structural concerns, and 85% are in good condition. This descriptive baseline is the starting point for all maintenance and investment decisions.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#decision-intelligence">Decision Intelligence</a><a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="csv" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">CSV</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Comma-Separated Values — a plain-text tabular data format available as a bulk export option for orderers.</p>
|
||||
<p class="term-long">CSV exports from quiXzoom contain one row per submission, with columns for mission ID, submission timestamp, GPS coordinates, approval status, Zoomer tier (anonymised), and other metadata fields. CSV is suitable for bulk import into spreadsheet tools, BI platforms, or legacy claims systems that do not support JSON or API integration. CSV exports are available on demand via the orderer dashboard or API.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality uses CSV exports to import quiXzoom road survey data into their GIS system on a weekly basis, plotting submission coordinates alongside existing infrastructure records.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#json">JSON</a><a href="#geojson">GeoJSON</a><a href="#api">API</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="d">
|
||||
<div class="letter-heading">
|
||||
<h2>D</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="data-controller" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data controller</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The entity that determines the purposes and means of processing personal data — under GDPR, quiXzoom acts as data controller for Zoomer and orderer data.</p>
|
||||
<p class="term-long">Under GDPR, the data controller is the legal entity responsible for deciding why and how personal data is processed. quiXzoom is the data controller for data collected from Zoomers (name, contact details, bank details, submission metadata) and from orderers. As data controller, quiXzoom must maintain a Record of Processing Activities (RoPA), appoint a Data Protection Officer where required, and respond to data subject rights requests within statutory timeframes.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer exercises their right to erasure, they submit a request to quiXzoom as data controller. quiXzoom is then legally responsible for erasing the Zoomer's personal data from its systems and instructing its data processors (including the KYC provider and Stripe) to do the same.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-processor">Data processor</a><a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-processor" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data processor</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">An entity that processes personal data on behalf of the data controller, under a Data Processing Agreement (DPA).</p>
|
||||
<p class="term-long">Data processors act on the instructions of the data controller and cannot use the data for their own purposes. quiXzoom's data processors include Stripe (payment processing), the KYC provider (identity verification), and cloud infrastructure providers. Each processor relationship must be governed by a Data Processing Agreement that complies with GDPR Article 28, specifying the scope, nature, purpose, and duration of processing.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The KYC provider that verifies Zoomer identities is a data processor for quiXzoom. They process identity documents and liveness check data strictly for identity verification purposes, under a DPA — they cannot use that data for their own marketing or analytics.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-controller">Data controller</a><a href="#gdpr">GDPR</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-residency" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data residency</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The geographic location where data is stored — quiXzoom stores all data in the EU (Stockholm, eu-north-1).</p>
|
||||
<p class="term-long">Data residency is increasingly important for enterprise customers in regulated industries, who may have legal or policy obligations requiring that data stays within a specific jurisdiction. quiXzoom's infrastructure runs on AWS eu-north-1 (Stockholm), keeping all data within the European Economic Area. This satisfies GDPR third-country transfer restrictions and is a key requirement for public sector and financial services customers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An EU public sector orderer requires that all submission data — including GPS coordinates and images — never leaves the EEA. quiXzoom's Stockholm data residency satisfies this requirement by default, without special configuration.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#s3">S3</a><a href="#pii">PII</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="decision-intelligence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Decision Intelligence</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">Actionable recommendations derived from observations through AMOS — the end product of the Landvex ecosystem.</p>
|
||||
<p class="term-long">Decision Intelligence is not data. It is not reports. It is the answer to a specific question: Which asset should I repair first? Where should I open my next store? Which claims are fraudulent? Landvex delivers Decision Intelligence by combining quiXzoom observations, AMOS analysis, and domain expertise into structured recommendations that directly enable decisions. Every output includes a confidence score and traceable source data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality receives a City Health Index of 71 for Norrmalm, down from 78 six months ago. The Decision Intelligence includes: specific deterioration patterns, contributing factors, recommended actions, and confidence intervals. The planner decides which streets to prioritise for maintenance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#index">Index</a><a href="#confidence-score">Confidence Score</a><a href="#amos">AMOS</a><a href="#control-intelligence">Control Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="e">
|
||||
<div class="letter-heading">
|
||||
<h2>E</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="exif" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">EXIF</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Exchangeable Image File Format — metadata embedded in image files, including GPS coordinates, capture timestamp, device model, and camera settings.</p>
|
||||
<p class="term-long">EXIF metadata is written into image files at capture time by the device camera. For quiXzoom, EXIF is the primary evidence layer: it carries the GPS coordinates where the photo was taken, the precise timestamp, and device identifiers. AI review cross-validates EXIF GPS coordinates against the mission geofence, and EXIF timestamps against the mission time window. EXIF data is preserved in delivery packages to orderers as part of the chain-of-custody record.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer photographs a flood-damaged road. The image's EXIF data records 59.3312°N, 18.0685°E at 09:47:23 UTC. AI review checks this GPS fix is within the mission's 50-metre geofence and the timestamp falls within the claimed time window — both pass, contributing to approval.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#gps">GPS</a><a href="#timestamp">Timestamp</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="f">
|
||||
<div class="letter-heading">
|
||||
<h2>F</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="field-observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Field observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A structured data collection event performed at a physical location by a verified contributor, producing an observation record.</p>
|
||||
<p class="term-long">A field observation is the complete act of capturing reality data on location: travelling to the mission site, following the observation protocol, capturing required imagery from specified vantage points, and submitting the observation package. It is more than the photos — it is the verified, time-stamped, geo-located record of what was observed. Field observations are the foundational input to the entire quiXzoom–AMOS–Landvex pipeline. Without field observations, there is no data, no intelligence, and no decisions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer travels to a bridge inspection mission, follows the protocol (6 photos from specified angles), captures geo-tagged images, and submits. The field observation is verified by AI review and enters the AMOS dataset as a trusted data point.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#observation-protocol">Observation protocol</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="g">
|
||||
<div class="letter-heading">
|
||||
<h2>G</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="gdpr" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GDPR</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">General Data Protection Regulation — the EU framework governing how personal data is collected, stored, and processed.</p>
|
||||
<p class="term-long">GDPR (Regulation (EU) 2016/679) applies to any organisation processing the personal data of EU residents. For quiXzoom, this covers Zoomer identity data, GPS submission metadata, and orderer contact details. Key obligations include lawful basis for processing, data minimisation, purpose limitation, storage limitation, and honouring data subject rights (access, erasure, portability). All quiXzoom data is stored in EU (Stockholm, eu-north-1) to avoid third-country transfer complications.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Germany requests a copy of all data quiXzoom holds on them (right of access). quiXzoom must respond within 30 days with a machine-readable export of their submission history, identity data, and payment records — all governed by GDPR Article 15.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-controller">Data controller</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geo-accuracy" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geo-accuracy</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The closeness of a recorded GPS coordinate to the actual physical position — typically expressed in metres of error radius.</p>
|
||||
<p class="term-long">Geo-accuracy is determined by GPS signal quality, which is affected by urban canyon effects, tree canopy, atmospheric conditions, and device hardware. Consumer smartphone GPS typically achieves 3–10 metre accuracy in open conditions. quiXzoom's mission geofences are sized to account for realistic geo-accuracy limits — a mission for a specific building typically uses a 30–50 metre compliance radius. AI review evaluates whether the recorded GPS position is within the mission's accepted tolerance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer photographs a bridge in a narrow urban gorge where GPS signals reflect off buildings. Their device records a position 18 metres from the mission pin — within the 30-metre geofence tolerance — so the submission passes the geo-accuracy check.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#geo-tagged">Geo-tagged</a><a href="#exif">EXIF</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geo-tagged" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geo-tagged</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An image embedded with GPS coordinates at capture time, proving where the photo was physically taken.</p>
|
||||
<p class="term-long">Geo-tagging writes latitude, longitude, and altitude data into the image's EXIF metadata at the moment of capture. All quiXzoom submissions must be geo-tagged — this is a technical requirement enforced by the app. Submissions from devices with disabled location services are rejected before upload. Geo-tagging is the foundation of quiXzoom's location verification: without it, there is no way to confirm the photo was taken at the correct mission location.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The quiXzoom app requires location permissions to function. When a Zoomer captures a photo in-app, GPS coordinates are written to EXIF automatically. A Zoomer cannot submit photos taken in a regular camera app that disabled geo-tagging — the submission would fail AI review immediately.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#exif">EXIF</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#geojson">GeoJSON</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geofence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geofence</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A virtual geographic boundary defining where a mission must be completed — submissions outside the geofence are automatically rejected.</p>
|
||||
<p class="term-long">A geofence is a digitally defined perimeter around a mission location, typically represented as a circle with a radius of 30–100 metres or as a GeoJSON Polygon for complex shapes. When a Zoomer submits photos, AI review checks the EXIF GPS coordinates against the mission geofence. If the submission was captured outside the geofence, it is rejected with a location mismatch reason. Geofences ensure data integrity by guaranteeing that observations were physically captured at the correct location, preventing fraudulent or mistaken submissions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection mission has a 50-metre radius geofence centred on the bridge coordinates. A Zoomer submits photos from 200 metres away — the GPS coordinates in EXIF fall outside the geofence, and AI review rejects the submission with 'Location mismatch — outside geofence.'</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#exif">EXIF</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geojson" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GeoJSON</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An open standard format (RFC 7946) for encoding geographic data structures using JSON.</p>
|
||||
<p class="term-long">GeoJSON is used by quiXzoom to define mission boundaries (geofences), to encode submission GPS paths, and to deliver location data to orderers in a format compatible with GIS platforms, mapping tools, and geographic analysis software. A mission boundary is represented as a GeoJSON Polygon; individual submission GPS points as GeoJSON Point Features with properties including timestamp, approval status, and submission ID.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality ordering a road condition survey receives their submission data as a GeoJSON FeatureCollection, which they import directly into QGIS to visualise submission density alongside their road network layer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#json">JSON</a><a href="#api">API</a><a href="#mission-brief">Mission brief</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="gps" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GPS</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Global Positioning System — the satellite-based navigation system used to determine precise geographic location of submissions.</p>
|
||||
<p class="term-long">GPS is the primary location technology in smartphones, providing latitude, longitude, and altitude data by triangulating signals from multiple satellites. All quiXzoom submissions depend on GPS for location verification. The system is augmented by network-based location (Wi-Fi and cell triangulation) in environments where satellite signals are weak — combined, these signals provide the geo-accuracy required for mission compliance checks.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Every time a Zoomer captures a photo for a mission, the device GPS is sampled. This fix — along with the capture timestamp — is embedded in EXIF and used by AI review to verify the submission was made at the correct location within the correct time window.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#exif">EXIF</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="h">
|
||||
<div class="letter-heading">
|
||||
<h2>H</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="hmac-sha256" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">HMAC-SHA256</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A cryptographic signature method used to verify that webhook payloads were genuinely sent by quiXzoom and were not tampered with in transit.</p>
|
||||
<p class="term-long">HMAC (Hash-based Message Authentication Code) with SHA-256 works by combining the webhook payload with a shared secret key to produce a unique signature. quiXzoom attaches this signature to every webhook request in the X-QuiXzoom-Signature header. The receiving system recomputes the signature using the same secret and compares — if they match, the payload is authentic and unmodified. This is industry-standard practice used by Stripe, GitHub, and other major webhook providers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's claims system receives a webhook when a submission is approved. Before processing the data, their server verifies the HMAC-SHA256 signature against their shared webhook secret — confirming the event genuinely originated from quiXzoom and was not injected by a third party.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#webhook">Webhook</a><a href="#api">API</a><a href="#oauth">OAuth</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="i">
|
||||
<div class="letter-heading">
|
||||
<h2>I</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="index" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Index</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A normalised score (0–100) derived from thousands of observations, representing the condition, risk, or quality of an asset or area.</p>
|
||||
<p class="term-long">An Index is the primary output of the AMOS analysis engine — a single number that summarises complex, multi-dimensional observation data into an intuitive, comparable metric. Different indices serve different purposes: the City Health Index measures overall infrastructure condition; the Infrastructure Risk Index quantifies probability of failure; the Commercial Opportunity Index identifies high-potential investment areas. Indices are computed from aggregated observations, weighted by confidence scores, and updated continuously as new observations flow in.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A city's Road Condition Index drops from 72 to 58 over six months. AMOS traces the decline to increased pothole observations in the northern district. The municipality uses this Index to justify a €2M resurfacing budget — with the Index projected to return to 75 post-works.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#confidence-score">Confidence Score</a><a href="#decision-intelligence">Decision Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="j">
|
||||
<div class="letter-heading">
|
||||
<h2>J</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="json" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">JSON</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">JavaScript Object Notation — the lightweight data format used for all quiXzoom API responses and webhook payloads.</p>
|
||||
<p class="term-long">JSON is a human-readable, language-agnostic data serialisation format that has become the de facto standard for web APIs. quiXzoom's REST API delivers all responses as JSON, including mission details, submission metadata, location data, and approval status. Webhook event payloads are also JSON. The format is natively supported in virtually all programming languages and integration platforms, making it straightforward to process quiXzoom data in any technical environment.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When an orderer queries the API for a completed submission, the response is a JSON object containing the submission ID, approval status, GPS coordinates, EXIF metadata summary, and signed URLs to retrieve the image files from S3.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#webhook">Webhook</a><a href="#geojson">GeoJSON</a><a href="#csv">CSV</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="l">
|
||||
<div class="letter-heading">
|
||||
<h2>L</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="landvex-inc" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Landvex Inc</h3>
|
||||
<span class="term-category cat-landvex">Landvex</span>
|
||||
</div>
|
||||
<p class="term-short">The US entity (Houston, TX) that develops and sells IT products powered by AMOS engines.</p>
|
||||
<p class="term-long">Landvex Inc is the US-based company that owns and operates the AAMOS platform and quiXzoom product. It is the legal entity responsible for product development, sales, and operations. Landvex Inc is NOT 'AAMOS Group' — there is no such entity. All products are developed and sold by Landvex Inc.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>Landvex Inc holds the intellectual property for AMOS engines, operates the quiXzoom platform, and sells intelligence products to enterprise customers worldwide.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#landvex">Landvex</a><a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="o">
|
||||
<div class="letter-heading">
|
||||
<h2>O</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="oauth" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">OAuth</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Open Authorization — the industry-standard protocol used by quiXzoom's API for secure, delegated authentication.</p>
|
||||
<p class="term-long">OAuth 2.0 allows orderers to authenticate API requests without sharing credentials. Orderers obtain access tokens through the OAuth flow, which are then included in API request headers. Tokens can be scoped (read-only, write, full access) and have configurable expiry periods. OAuth 2.0 is also used for third-party integrations — for example, allowing an orderer's claims management platform to connect to quiXzoom on behalf of their organisation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's IT team sets up an OAuth 2.0 client in the quiXzoom orderer portal, receives client credentials, and uses these to generate short-lived access tokens for their claims integration server. Tokens expire after 1 hour and are automatically refreshed.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#webhook">Webhook</a><a href="#hmac-sha256">HMAC-SHA256</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A verified field record captured through quiXzoom — the fundamental unit of reality data.</p>
|
||||
<p class="term-long">An observation is not a photo. It is a structured, verified record of physical reality at a specific place and time. Every observation includes: geolocation (GPS coordinates with accuracy estimate), timestamp (when it was captured), media (images or video), and metadata (device, conditions, mission context). Observations are quality-checked by AI before entering the dataset. They are the raw material from which all Landvex intelligence is derived.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer captures 6 images of a road segment. Each image becomes part of an observation that includes GPS, timestamp, and mission context. AI review verifies the observation before it enters the dataset.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The field data collection tier where Zoomers capture verified observations of physical assets and infrastructure.</p>
|
||||
<p class="term-long">The Observation Layer is the foundation of the ecosystem — the interface between physical reality and digital intelligence. It encompasses the quiXzoom mobile app, Zoomer network, mission management system, and AI review pipeline. Its purpose is to produce high-quality, trustworthy observations at scale. The Observation Layer guarantees data integrity through geo-tagging, timestamp verification, and automated quality checks. Without a robust Observation Layer, everything above it — analysis, indices, decisions — is built on sand.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The Observation Layer deploys 500 Zoomers across a metropolitan area to capture quarterly building condition observations. Each observation is verified for GPS accuracy, image quality, and specification compliance before entering the Analysis Layer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#zoomer">Zoomer</a><a href="#reality-layer">Reality Layer</a><a href="#analysis-layer">Analysis Layer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation-protocol" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation protocol</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The standardised set of instructions defining what to capture, from which angles, and under what conditions for a given mission type.</p>
|
||||
<p class="term-long">The observation protocol is the rulebook for field data collection. It specifies the number of photos required, the vantage points (distance, angle, height), the elements that must be in frame, lighting conditions, and any safety or access constraints. Protocols are mission-type specific: a bridge inspection protocol differs from a property documentation protocol. Following the protocol is essential for approval — AI review checks compliance against the protocol, and deviations result in rejection. Protocols are developed by domain experts and refined through feedback from AI review outcomes.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A roof condition mission protocol requires: 1 overview shot from street level, 1 ridge-line photo, 2 slope photos (one per side), and 1 detail of any visible damage — all captured during daylight with the sun behind the photographer. A Zoomer who submits only 3 photos or captures at night will fail protocol compliance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#field-observation">Field observation</a><a href="#mission-brief">Mission brief</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="ouroboros" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Ouroboros</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The internal platform architecture that powers quiXzoom, AAMOS, and Landvex — a self-referential system where the platform monitors and improves itself.</p>
|
||||
<p class="term-long">Ouroboros is the internal name for the technical architecture that underpins the entire Landvex ecosystem. It encompasses the microservices, data pipelines, AI models, and infrastructure that enable quiXzoom field data collection, AMOS analysis, and Landvex intelligence delivery. The name reflects the system's self-monitoring nature: observations feed analysis, analysis drives decisions, decisions generate new observations. Ouroboros is not a customer-facing product — it is the technical foundation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>quiXzoom runs as an Ouroboros instance — using the same core infrastructure as other Landvex products but configured for the quiXzoom marketplace model. Ouroboros handles user management, mission orchestration, AI review, and data pipelines.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a><a href="#landvex">Landvex</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="p">
|
||||
<div class="letter-heading">
|
||||
<h2>P</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="pii" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">PII</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">Personally Identifiable Information — any data that can directly or indirectly identify a specific individual.</p>
|
||||
<p class="term-long">PII encompasses obvious identifiers (name, email, address, IBAN) as well as indirect identifiers that, in combination, could identify someone (GPS traces, device fingerprints, submission patterns). Under GDPR, quiXzoom treats PII with strict controls: it is collected only where necessary, retained only as long as required, and never shared with orderers in identifiable form. Zoomer submissions are delivered to orderers without attached Zoomer identity — orderers receive field data, not person data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When an orderer receives a completed submission, they see the images, GPS coordinates, and timestamp — but not the Zoomer's name, account details, or any identifying information. The Zoomer's identity is pseudonymised in normal operation, with full identification available only under legal process.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#data-controller">Data controller</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="q">
|
||||
<div class="letter-heading">
|
||||
<h2>Q</h2>
|
||||
<span class="letter-count">2 terms</span>
|
||||
</div>
|
||||
<article id="quality-score" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Quality score</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A composite rating of an observation's technical fitness — sharpness, exposure, framing, and protocol compliance — distinct from the confidence score.</p>
|
||||
<p class="term-long">The Quality Score evaluates the technical and aesthetic properties of submitted media independent of location or metadata verification. It measures image sharpness (absence of motion blur or focus issues), exposure (neither under- nor over-exposed), framing (subject completeness and composition), and protocol compliance (correct angles, required elements visible). Quality Score is a component of the overall Confidence Score but is computed separately to give orderers visibility into the technical standard of their data. Low quality scores trigger coaching for Zoomers and may result in rejection if minimum thresholds are not met.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits photos that are correctly geo-located and within the time window, but two images are slightly blurry due to camera shake. AI review assigns a Quality Score of 62 — below the 75-point threshold — and rejects the submission with 'Image quality: motion blur detected.' The Zoomer receives automated coaching on stabilisation techniques.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#confidence-score">Confidence Score</a><a href="#ai-review">AI review</a><a href="#observation">Observation</a><a href="#approval">Approval</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="quixzoom-auth-core" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom Auth Core</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Standalone authentication product sold via AAMOS — includes Auth Foundation, KYZ Engine, Company Registry, and Payout Engine.</p>
|
||||
<p class="term-long">quiXzoom Auth Core is a standalone authentication and identity product that can be integrated into any application. It includes: Auth Foundation (email/Google + phone + password), KYZ Engine (Know Your Zoomer — identity verification), Company Registry (sole proprietorship / registered company), and Payout Engine (Stripe Connect, Frilans Finans, bank transfers). Auth Core is sold as a product via AAMOS and is used by quiXzoom and other Landvex products.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A third-party app developer integrates quiXzoom Auth Core to handle user authentication, identity verification, and payouts — without building these complex systems themselves.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="r">
|
||||
<div class="letter-heading">
|
||||
<h2>R</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="reality-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The physical world itself — the assets, infrastructure, and environments that the ecosystem observes, analyses, and optimises.</p>
|
||||
<p class="term-long">The Reality Layer is everything physical: roads, bridges, buildings, coastlines, forests, power lines, water pipes. It is the domain that exists independently of any observation system — the ground truth that the ecosystem seeks to understand and improve. The Reality Layer is not digital; it is the actual world that customers own, manage, insure, and invest in. Every observation is a measurement of the Reality Layer; every index is a summary of its state; every decision is an intervention upon it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A city's Reality Layer comprises 1,200 km of roads, 400 bridges, 50 tunnels, and 2,000 public buildings. The ecosystem's purpose is to create a complete, accurate, up-to-date digital understanding of this Reality Layer — enabling better decisions about maintenance, investment, and risk.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation-layer">Observation Layer</a><a href="#analysis-layer">Analysis Layer</a><a href="#decision-layer">Decision Layer</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="reality-signal" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Signal</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A measurable, verifiable observation that describes a specific aspect of the physical world.</p>
|
||||
<p class="term-long">A Reality Signal is any observation that carries information about the state of physical reality: a photo of a cracked bridge deck, a GPS-tagged image of flood damage, a timestamped record of a building's facade. Reality Signals are the raw inputs to the Analysis Layer. They are distinguished from synthetic or inferred data by their direct connection to physical measurement — a Zoomer was there, the camera captured light from the actual scene, the GPS recorded the actual coordinates. Reality Signals are the antidote to assumptions and desk-based estimates.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurer receives a Reality Signal showing hail damage to a factory roof — captured 6 hours after the storm, with GPS confirming the location, timestamp proving immediacy, and image quality enabling damage severity assessment. This Reality Signal replaces the traditional adjuster visit.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#reality-layer">Reality Layer</a><a href="#confidence-score">Confidence Score</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="rexo" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">REXO</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Landvex's coding pipeline for automated software development, testing, and deployment.</p>
|
||||
<p class="term-long">REXO is Landvex's internal coding pipeline that automates software development tasks. It runs via /opt/amos/rexo-build/, with tasks defined in plan/PLAN.json and executed by parallel workers. REXO orchestrates code generation, testing, and deployment across the ecosystem. All coding tasks should be routed through REXO rather than manual file uploads or direct server modifications.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>When a new feature is needed for the quiXzoom API, the task is added to REXO's PLAN.json. REXO workers generate the code, run tests, and deploy to staging — all without manual intervention.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#ouroboros">Ouroboros</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="right-to-erasure" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Right to erasure</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">A GDPR right allowing individuals to request deletion of their personal data from a platform's systems.</p>
|
||||
<p class="term-long">Under GDPR Article 17, individuals have the right to request erasure of their personal data when it is no longer necessary for the purpose it was collected, when they withdraw consent, or when they object to processing. For quiXzoom, this means Zoomers can request deletion of their account and all associated personal data at any time via the app settings. Certain data may need to be retained for limited periods to satisfy legal obligations (e.g. financial records under tax law) even after an erasure request.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer decides to stop using quiXzoom and requests erasure. quiXzoom deletes their profile, contact data, and GPS history. Some financial transaction records are retained for 7 years as required by EU accounting regulation — this is disclosed in quiXzoom's privacy policy and does not affect the Zoomer's ability to stop using the platform.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#data-controller">Data controller</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="s">
|
||||
<div class="letter-heading">
|
||||
<h2>S</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="s3" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">S3</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Amazon Simple Storage Service — the object storage platform used to store all quiXzoom submission images, securely and at scale.</p>
|
||||
<p class="term-long">S3 (AWS eu-north-1) is quiXzoom's primary file store for submission images. Uploaded images are stored with server-side encryption, access is controlled via IAM policies, and orderers receive time-limited signed URLs to retrieve submission packages — images are never publicly accessible by default. S3's durability (99.999999999%) and scalability make it appropriate for a platform expecting high submission volumes during surge events.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer uploads 6 photos for a mission, they are stored in S3 eu-north-1. When the orderer queries the API for the completed submission, they receive signed URLs valid for 24 hours to download the images — after which the URLs expire and a new API call is required.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-residency">Data residency</a><a href="#api">API</a><a href="#submission">Submission</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="t">
|
||||
<div class="letter-heading">
|
||||
<h2>T</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="timestamp" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Timestamp</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The precise date and time recorded in a photo's EXIF metadata, proving when the image was captured.</p>
|
||||
<p class="term-long">Timestamps are a critical element of quiXzoom's chain-of-custody system. The EXIF timestamp records the device's date and time at the moment of capture, and is cross-validated by AI review against the mission's claimed time window. For legal and insurance use cases, the timestamp (combined with GPS data) provides tamper-evident proof that the documentation was made at the right place at the right time. quiXzoom also records server-side ingestion timestamps for each submission to supplement device-side EXIF data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurer requires flood documentation captured within 6 hours of a storm event for their claims validity window. The EXIF timestamp on each submitted photo, cross-referenced with server ingestion time, provides the evidence that the documentation falls within the required window — suitable for claims processing and, if necessary, legal proceedings.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#exif">EXIF</a><a href="#time-window">Time window</a><a href="#geo-tagged">Geo-tagged</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="u">
|
||||
<div class="letter-heading">
|
||||
<h2>U</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="usd" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">USD</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">United States Dollar — the primary currency used in quiXzoom platform and Landvex products.</p>
|
||||
<p class="term-long">USD is the main currency throughout the quiXzoom platform and Landvex ecosystem. All customer-facing pricing, payouts, and product fees are denominated in USD (or EUR where specified). This is a locked policy — SEK is never used in customer-facing copy, sites, documents, or communication. The only exception is LandveX AB's internal Swedish accounting.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A mission pays $15 (USD). A Zoomer's earnings are displayed in USD. Landvex enterprise contracts are priced in USD. This is consistent across all customer touchpoints.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#eur">EUR</a><a href="#payout">Payout</a><a href="#platform-fee">Platform fee</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="w">
|
||||
<div class="letter-heading">
|
||||
<h2>W</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="webhook" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Webhook</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An automatic HTTP POST notification sent by quiXzoom to an orderer's system when a defined event occurs — typically submission approval.</p>
|
||||
<p class="term-long">Webhooks enable real-time integration between quiXzoom and orderer systems without polling. When a submission is approved (or rejected, or a mission is created), quiXzoom sends a JSON payload to the orderer's configured webhook URL. The payload includes the event type, mission ID, submission ID, GPS coordinates, approval status, and image download URLs. Orderers must verify webhook authenticity using HMAC-SHA256 signature verification. Undelivered webhooks are retried with exponential backoff over 24 hours.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's claims system has a quiXzoom webhook endpoint. When a flood damage submission is approved, quiXzoom sends a POST request within seconds. The claims system receives the event, automatically attaches the images to the open claim, and updates the claim status to 'documented' — with no manual intervention required.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#hmac-sha256">HMAC-SHA256</a><a href="#json">JSON</a><a href="#approval">Approval</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<div class="last-updated">Last updated: July 14, 2026</div>
|
||||
</main>
|
||||
<footer style="background:#0d0d10;border-top:1px solid rgba(255,255,255,.07);padding:32px 24px;margin-top:48px">
|
||||
<div style="max-width:1080px;margin:0 auto;display:flex;align-items:center;justify-content:space-between;flex-wrap:wrap;gap:16px">
|
||||
<a href="/" style="font-size:1.1rem;font-weight:800;color:#fff;letter-spacing:-.03em;text-decoration:none">qui<span style="color:#3b82f6">X</span>zoom</a>
|
||||
<p style="font-size:.8125rem;color:rgba(255,255,255,.75);margin:0">© 2026 Landvex Inc</p>
|
||||
</div>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
Vendored
+852
@@ -0,0 +1,852 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Glossary — landvex</title>
|
||||
<meta name="description" content="Every term used on landvex. Defined precisely and kept current.">
|
||||
<link rel="canonical" href="https://www.landvex.com/glossary">
|
||||
<meta name="robots" content="index, follow">
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "DefinedTermSet",
|
||||
"name": "landvex Glossary",
|
||||
"description": "Complete glossary of terms",
|
||||
"publisher": {"@type": "Organization", "name": "Landvex Inc", "url": "https://www.landvex.com"}
|
||||
}
|
||||
</script>
|
||||
<style>*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
|
||||
:root {
|
||||
--bg: #ffffff; --bg-off: #f5f5f7; --bg-card: #ffffff;
|
||||
--text: #1d1d1f; --text-secondary: #6e6e73;
|
||||
--blue: #0066FF; --blue-light: #e8f0ff;
|
||||
--green: #00a550; --green-light: #e6f7ee;
|
||||
--purple: #7b2fff; --purple-light: #f0e8ff;
|
||||
--orange: #e8660a; --orange-light: #fff0e6;
|
||||
--pink: #ff3366; --pink-light: #ffe8f0;
|
||||
--radius: 18px; --radius-sm: 8px; --border: #d2d2d7;
|
||||
--nav-height: 64px; --shadow-hover: 0 12px 40px rgba(0,0,0,.10);
|
||||
}
|
||||
@media (prefers-color-scheme: dark) {
|
||||
:root {
|
||||
--bg: #000000; --bg-off: #1c1c1e; --bg-card: #1c1c1e;
|
||||
--text: #f5f5f7; --text-secondary: #98989f; --border: #3a3a3c;
|
||||
--blue-light: rgba(0,102,255,.15); --green-light: rgba(0,165,80,.15);
|
||||
--purple-light: rgba(123,47,255,.15); --orange-light: rgba(232,102,10,.15);
|
||||
--pink-light: rgba(255,51,102,.15); --shadow-hover: 0 12px 40px rgba(0,0,0,.5);
|
||||
}
|
||||
}
|
||||
html { scroll-behavior: smooth; }
|
||||
body {
|
||||
font-family: -apple-system, BlinkMacSystemFont, 'SF Pro Display', 'SF Pro Text', 'Helvetica Neue', Arial, sans-serif;
|
||||
background: var(--bg); color: var(--text); line-height: 1.6; -webkit-font-smoothing: antialiased;
|
||||
}
|
||||
.nav {
|
||||
position: sticky; top: 0; z-index: 100; height: var(--nav-height);
|
||||
background: rgba(255,255,255,.82); -webkit-backdrop-filter: blur(20px) saturate(180%);
|
||||
backdrop-filter: blur(20px) saturate(180%); border-bottom: 1px solid var(--border);
|
||||
display: flex; align-items: center; gap: 16px; padding: 0 24px;
|
||||
}
|
||||
@media (prefers-color-scheme: dark) { .nav { background: rgba(0,0,0,.82); } }
|
||||
.nav-logo { font-size: 1.25rem; font-weight: 800; color: var(--text); text-decoration: none; letter-spacing: -.04em; white-space: nowrap; flex-shrink: 0; }
|
||||
.nav-logo .x { color: var(--blue); }
|
||||
.nav-divider { width: 1px; height: 20px; background: var(--border); flex-shrink: 0; }
|
||||
.nav-title { font-size: .9375rem; font-weight: 600; color: var(--text-secondary); white-space: nowrap; flex-shrink: 0; }
|
||||
main { max-width: 860px; margin: 0 auto; padding: 0 24px 80px; }
|
||||
.page-header { padding: 64px 0 48px; text-align: center; }
|
||||
.page-header h1 { font-size: clamp(2.5rem, 6vw, 4rem); font-weight: 800; letter-spacing: -.04em; line-height: 1.05; color: var(--text); margin-bottom: 16px; }
|
||||
.page-header p { font-size: 1.125rem; color: var(--text-secondary); max-width: 480px; margin: 0 auto; }
|
||||
.letter-section { margin-bottom: 48px; }
|
||||
.letter-heading { display: flex; align-items: center; gap: 16px; margin-bottom: 20px; padding-bottom: 12px; border-bottom: 1px solid var(--border); }
|
||||
.letter-heading h2 { font-size: 2rem; font-weight: 800; color: var(--text-secondary); letter-spacing: -.04em; line-height: 1; width: 36px; flex-shrink: 0; }
|
||||
.letter-count { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-card { background: var(--bg-card); border: 1px solid var(--border); border-radius: var(--radius); padding: 28px 32px; margin-bottom: 16px; transition: box-shadow .2s, transform .2s; }
|
||||
.term-card:hover { box-shadow: var(--shadow-hover); transform: translateY(-2px); }
|
||||
.term-header { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; margin-bottom: 10px; flex-wrap: wrap; }
|
||||
.term-name { font-size: 1.3125rem; font-weight: 700; color: var(--text); letter-spacing: -.02em; line-height: 1.2; }
|
||||
.term-category { display: inline-block; padding: 4px 12px; border-radius: 20px; font-size: .75rem; font-weight: 600; letter-spacing: .02em; text-transform: uppercase; white-space: nowrap; flex-shrink: 0; margin-top: 2px; }
|
||||
.cat-platform { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-technical { background: var(--green-light); color: var(--green); }
|
||||
.cat-payment { background: var(--purple-light); color: var(--purple); }
|
||||
.cat-legal { background: var(--orange-light); color: var(--orange); }
|
||||
.cat-core { background: var(--bg-off); color: var(--text-secondary); }
|
||||
.cat-amos { background: var(--pink-light); color: var(--pink); }
|
||||
.cat-landvex { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-quixzoom { background: var(--green-light); color: var(--green); }
|
||||
.cat-product { background: var(--orange-light); color: var(--orange); }
|
||||
.term-short { font-size: 1rem; font-weight: 500; color: var(--text); margin-bottom: 12px; line-height: 1.5; }
|
||||
.term-long { font-size: .9375rem; color: var(--text-secondary); line-height: 1.65; margin-bottom: 16px; }
|
||||
.term-context { background: var(--bg-off); border-radius: var(--radius-sm); padding: 14px 18px; margin-bottom: 14px; }
|
||||
.term-context-label { font-size: .75rem; font-weight: 700; text-transform: uppercase; letter-spacing: .06em; color: var(--blue); display: block; margin-bottom: 6px; }
|
||||
.term-context p { font-size: .875rem; color: var(--text-secondary); line-height: 1.6; }
|
||||
.term-related { display: flex; align-items: center; flex-wrap: wrap; gap: 6px; }
|
||||
.term-related > span { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-related a { display: inline-block; padding: 3px 10px; border-radius: 20px; font-size: .8125rem; font-weight: 500; color: var(--blue); background: var(--blue-light); text-decoration: none; transition: background .12s, color .12s; }
|
||||
.term-related a:hover { background: var(--blue); color: #fff; }
|
||||
.last-updated { text-align: center; font-size: .8125rem; color: var(--text-secondary); margin-top: 48px; padding-top: 24px; border-top: 1px solid var(--border); }
|
||||
.term-card:target { border-color: var(--blue); box-shadow: 0 0 0 3px rgba(0,102,255,.15); }
|
||||
@media (max-width: 600px) { .nav { gap: 10px; padding: 0 16px; } .term-card { padding: 20px 18px; } .page-header { padding: 40px 0 32px; } }
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<nav class="nav">
|
||||
<a href="/" class="nav-logo">qui<span class="x">X</span>zoom</a>
|
||||
<div class="nav-divider"></div>
|
||||
<span class="nav-title">Glossary</span>
|
||||
</nav>
|
||||
<main>
|
||||
<header class="page-header">
|
||||
<h1>Every term.<br>Defined.</h1>
|
||||
<p>The complete landvex reference — from field observations to decision intelligence.</p>
|
||||
</header>
|
||||
<section class="letter-section" id="a">
|
||||
<div class="letter-heading">
|
||||
<h2>A</h2>
|
||||
<span class="letter-count">14 terms</span>
|
||||
</div>
|
||||
<article id="amos" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Adaptive Autonomous Multi-Agent Operating System — the AI capability platform that powers Landvex intelligence products.</p>
|
||||
<p class="term-long">AMOS is not an AI system. It is an AI Capability Platform — a suite of specialised engines that process observations into structured intelligence. AMOS ingests raw field data from quiXzoom, applies computer vision, pattern recognition, and cross-referencing, and produces outputs: indices, scores, change flags, and predictive signals. AMOS is the analytical layer between reality and decisions. It is developed and sold by Landvex Inc, Houston, TX.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>quiXzoom collects 12,000 observations of bridge conditions across Sweden. AMOS processes these into an Infrastructure Risk Index — a single score per bridge that maintenance planners can prioritise by.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#index">Index</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#amos-vision">AMOS Vision</a><a href="#amos-identity">AMOS Identity</a><a href="#amos-fraud">AMOS Fraud</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-change-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Change Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Detects changes between observations over time.</p>
|
||||
<p class="term-long">The AMOS Change Engine compares current observations against historical baselines to identify additions, removals, and modifications. It powers change detection at scale, enabling proactive maintenance and early problem identification. The engine operates across multiple time scales from hours to years.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A property manager receives a quarterly change report showing that 3 buildings have new roof damage, 2 have added unauthorized structures, and 1 has removed safety equipment — all flagged automatically by the Change Engine.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#change-detection">Change detection</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-compliance" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Compliance</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Regulatory control, documentation verification, and compliance checking engine.</p>
|
||||
<p class="term-long">AMOS Compliance verifies that assets, processes, and documentation meet regulatory requirements. It checks for required signage, accessibility features, fire safety equipment, and other compliance markers. The engine maintains up-to-date regulatory rule sets for multiple jurisdictions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A retail chain uses AMOS Compliance to verify that all 200 stores meet accessibility requirements. The engine has flagged 15 stores missing required wheelchair ramps and 8 stores with inadequate emergency lighting.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-inspection">AMOS Inspection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-evidence-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Evidence Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Creates traceable evidence chains for audit, insurance, and legal proceedings.</p>
|
||||
<p class="term-long">The AMOS Evidence Engine maintains an immutable, auditable chain of custody for every observation. It records capture metadata, processing history, analysis results, and access logs in a tamper-evident format suitable for legal admissibility. Evidence packages include cryptographic hashes and timestamps.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>An insurance dispute reaches court. The AMOS Evidence Engine produces a complete evidence package showing: when the observation was captured, by which device, with what GPS accuracy, what AI analysis was performed, and who accessed the data — all cryptographically signed.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#exif">EXIF</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-fraud" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Fraud</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Skimming detection, manipulated ATM/utility meter detection, and insurance fraud prevention engine.</p>
|
||||
<p class="term-long">AMOS Fraud detects fraudulent manipulation of physical devices and systems. It identifies skimming devices on ATMs, tampered utility meters, falsified insurance claims, and other physical fraud vectors. The engine combines visual analysis with pattern matching against known fraud signatures.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A bank receives a quiXzoom observation of an ATM showing a suspicious card reader attachment. AMOS Fraud analyses the image, compares against known skimming device patterns, and flags a high-probability fraud alert within seconds.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-identity" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Identity</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Identity verification, document control, liveness detection, and fraud prevention engine.</p>
|
||||
<p class="term-long">AMOS Identity verifies that a person is who they claim to be. It processes government-issued IDs, performs liveness checks, and detects document tampering or synthetic identity fraud. The engine is used for KYC processes, access control, and high-trust verification scenarios.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes identity verification by submitting their passport and a selfie. AMOS Identity verifies the document's authenticity and matches the selfie to the ID photo with 99.7% accuracy.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#liveness-check">Liveness check</a><a href="#identity-verification">Identity verification</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-infrastructure" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Infrastructure</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Road, bridge, pole, sign, and property condition monitoring engine.</p>
|
||||
<p class="term-long">AMOS Infrastructure monitors the built environment: roads, bridges, utility poles, traffic signs, buildings, and other fixed assets. It detects deterioration, damage, and changes over time, producing condition indices and maintenance prioritisation scores. The engine is the core capability behind Landvex's infrastructure intelligence products.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality receives monthly Infrastructure Condition Index updates for all 400 bridges in their county. AMOS Infrastructure has flagged 12 bridges showing progressive deterioration that requires inspection within 30 days.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#index">Index</a><a href="#change-detection">Change detection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-inspection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Inspection</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">General quality control and industrial inspection engine.</p>
|
||||
<p class="term-long">AMOS Inspection provides general-purpose quality control and inspection capabilities for industrial applications. It detects manufacturing defects, assembly errors, and quality deviations from specification. The engine is configurable for specific industry standards and can be trained on custom defect libraries.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A manufacturer uses AMOS Inspection to quality-check 10,000 units per day. The engine detects surface scratches, dimensional deviations, and colour mismatches with 99.2% accuracy, reducing manual inspection workload by 80%.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#quality-score">Quality score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-prediction-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Prediction Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Estimates likely future development based on current observations and historical patterns.</p>
|
||||
<p class="term-long">The AMOS Prediction Engine uses historical data, environmental factors, and deterioration models to forecast future asset conditions. It estimates remaining useful life, predicts failure probabilities, and identifies optimal intervention timing. Predictions include confidence intervals and are updated as new observations arrive.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>AMOS Prediction Engine forecasts that Bridge 247 will reach critical condition (Index below 40) in 18 months based on current deterioration rate and traffic load. The recommendation: schedule major maintenance within 12 months to avoid emergency closure.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#index">Index</a><a href="#amos-risk-engine">AMOS Risk Engine</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-reality-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Reality Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Verifies that an image shows actual reality, not manipulated or synthetic content.</p>
|
||||
<p class="term-long">The AMOS Reality Engine detects image manipulation, deepfakes, and synthetic content. It analyses EXIF data, pixel-level artifacts, and lighting consistency to verify that an observation depicts real physical reality. This is critical for legal admissibility and insurance validity.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>An insurance claim includes photos of storm damage. The AMOS Reality Engine verifies that the images are authentic, unmanipulated, and captured at the claimed location and time — providing the foundation for claims processing.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#exif">EXIF</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-risk-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Risk Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Converts observations into risk scores and prioritisation rankings.</p>
|
||||
<p class="term-long">The AMOS Risk Engine transforms raw observations into actionable risk assessments. It combines condition data, environmental factors, historical failure rates, and consequence analysis to produce risk scores that prioritise maintenance and intervention. Risk scores are normalised and comparable across asset types and geographies.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A county's 400 bridges are ranked by risk score. The top 10 highest-risk bridges (scores above 85) receive immediate inspection orders, while the bottom 200 (scores below 30) are scheduled for routine maintenance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#index">Index</a><a href="#confidence-score">Confidence Score</a><a href="#decision-intelligence">Decision Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-safety" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Safety</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">PPE detection, workplace hazard identification, and risk assessment engine.</p>
|
||||
<p class="term-long">AMOS Safety analyses visual data to detect personal protective equipment (PPE) compliance, identify workplace hazards, and assess safety risks. It can detect missing hard hats, unsafe scaffolding, blocked emergency exits, and other safety violations from standard photographs.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A construction site manager receives daily safety observations from quiXzoom. AMOS Safety has flagged 3 instances of missing fall protection and 1 blocked fire exit across 50 observations — enabling immediate corrective action.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-vision" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Vision</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Object recognition, anomaly detection, and damage assessment engine.</p>
|
||||
<p class="term-long">AMOS Vision is the computer vision engine that identifies objects, detects anomalies, and assesses damage in visual data. It powers infrastructure inspection, property condition monitoring, and safety compliance checking. The engine can detect cracks, corrosion, vegetation encroachment, and other physical defects from standard photographs.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In AMOS</span>
|
||||
<p>A bridge inspection observation shows surface cracking. AMOS Vision measures crack width, length, and pattern, comparing against historical data to determine if the damage is new or progressive.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#change-detection">Change detection</a><a href="#amos-infrastructure">AMOS Infrastructure</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="analysis-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Analysis Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The processing tier where raw observations are transformed into structured intelligence by AMOS.</p>
|
||||
<p class="term-long">The Analysis Layer sits between the Observation Layer and the Decision Layer. Here, AMOS ingests verified field observations and applies analytical models: object detection, condition scoring, change analysis, pattern recognition, and anomaly detection. The outputs are normalised indices, confidence scores, and contradiction flags. The Analysis Layer is where data becomes insight — where thousands of individual observations are synthesised into coherent, actionable intelligence.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A thousand roof observations from across a property portfolio enter the Analysis Layer. AMOS identifies that 8% show hail damage, 2% have gutter degradation, and 90% are unchanged. The Analysis Layer outputs a Property Condition Index with regional breakdowns and recommended inspection priorities.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation-layer">Observation Layer</a><a href="#decision-layer">Decision Layer</a><a href="#reality-layer">Reality Layer</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="c">
|
||||
<div class="letter-heading">
|
||||
<h2>C</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="change-detection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Change detection</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The automated identification of differences between current observations and historical baseline data — surfacing what has changed in the physical world.</p>
|
||||
<p class="term-long">Change detection is a core AMOS capability that compares new observations against prior data to identify additions, removals, or modifications to physical assets. It powers infrastructure monitoring, property condition tracking, and environmental surveillance. Change detection operates at multiple scales: from pixel-level differences in repeated photographs to structural changes identified through computer vision. Each detected change is scored by confidence and severity, and flagged as a Contradiction when it represents an unexpected deviation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a retail park shows three new storefronts and one demolished unit compared to the baseline from six months ago. AMOS change detection automatically flags these modifications, updates the asset registry, and alerts the property manager to verify the changes.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#contradiction">Contradiction</a><a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="confidence-score" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Confidence Score</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A statistical measure of certainty attached to an observation or analysis output, expressed as a percentage.</p>
|
||||
<p class="term-long">The Confidence Score quantifies how certain the system is about a specific observation or derived insight. It is computed from multiple signals: EXIF integrity, GPS accuracy, image clarity, cross-validation against historical data, and agreement with other observations of the same asset. A high confidence score (90%+) indicates strong reliability; a low score triggers manual review or additional observation requests. Confidence scores are essential for decision-making — they tell the customer not just what was observed, but how much to trust it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection observation receives a 94% confidence score based on sharp imagery, precise GPS, and consistency with the previous inspection. An insurer uses this high-confidence observation to approve a maintenance claim without sending an engineer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="contradiction" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Contradiction</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A mismatch between observed reality and expected or previously recorded reality — a signal that something has changed or requires attention.</p>
|
||||
<p class="term-long">A Contradiction is flagged when an observation deviates significantly from the expected state: a building that was intact now shows damage, a road that was clear now has a sinkhole, or an asset that was present is now missing. Contradictions are not errors — they are valuable signals. They trigger alerts, escalate priority, and often indicate the most urgent decisions a customer must make. The Contradiction engine cross-references observations against historical data, design specifications, and regulatory baselines.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a commercial roof shows new water staining not present in the previous observation. AMOS flags this as a Contradiction, alerting the property manager to schedule repairs before the rainy season — preventing a €50,000 claim.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#confidence-score">Confidence Score</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="control-intelligence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Control Intelligence</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">Descriptive intelligence that tells you the current state of your physical assets — what is, not what to do.</p>
|
||||
<p class="term-long">Control Intelligence answers the question: 'What is the current condition of my assets?' It is the foundational layer of insight derived from observations, describing reality as it exists today: which bridges are sound, which buildings have damage, which roads need repair. Control Intelligence is objective, measurable, and verifiable. It is the raw material from which Decision Intelligence is forged — you cannot decide what to do until you know what is.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality receives Control Intelligence showing that 12% of its road bridges have surface cracking, 3% have structural concerns, and 85% are in good condition. This descriptive baseline is the starting point for all maintenance and investment decisions.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#decision-intelligence">Decision Intelligence</a><a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="d">
|
||||
<div class="letter-heading">
|
||||
<h2>D</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="data-controller" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data controller</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The entity that determines the purposes and means of processing personal data — under GDPR, quiXzoom acts as data controller for Zoomer and orderer data.</p>
|
||||
<p class="term-long">Under GDPR, the data controller is the legal entity responsible for deciding why and how personal data is processed. quiXzoom is the data controller for data collected from Zoomers (name, contact details, bank details, submission metadata) and from orderers. As data controller, quiXzoom must maintain a Record of Processing Activities (RoPA), appoint a Data Protection Officer where required, and respond to data subject rights requests within statutory timeframes.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer exercises their right to erasure, they submit a request to quiXzoom as data controller. quiXzoom is then legally responsible for erasing the Zoomer's personal data from its systems and instructing its data processors (including the KYC provider and Stripe) to do the same.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-processor">Data processor</a><a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-processor" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data processor</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">An entity that processes personal data on behalf of the data controller, under a Data Processing Agreement (DPA).</p>
|
||||
<p class="term-long">Data processors act on the instructions of the data controller and cannot use the data for their own purposes. quiXzoom's data processors include Stripe (payment processing), the KYC provider (identity verification), and cloud infrastructure providers. Each processor relationship must be governed by a Data Processing Agreement that complies with GDPR Article 28, specifying the scope, nature, purpose, and duration of processing.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The KYC provider that verifies Zoomer identities is a data processor for quiXzoom. They process identity documents and liveness check data strictly for identity verification purposes, under a DPA — they cannot use that data for their own marketing or analytics.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-controller">Data controller</a><a href="#gdpr">GDPR</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-residency" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data residency</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The geographic location where data is stored — quiXzoom stores all data in the EU (Stockholm, eu-north-1).</p>
|
||||
<p class="term-long">Data residency is increasingly important for enterprise customers in regulated industries, who may have legal or policy obligations requiring that data stays within a specific jurisdiction. quiXzoom's infrastructure runs on AWS eu-north-1 (Stockholm), keeping all data within the European Economic Area. This satisfies GDPR third-country transfer restrictions and is a key requirement for public sector and financial services customers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An EU public sector orderer requires that all submission data — including GPS coordinates and images — never leaves the EEA. quiXzoom's Stockholm data residency satisfies this requirement by default, without special configuration.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#s3">S3</a><a href="#pii">PII</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="decision-intelligence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Decision Intelligence</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">Actionable recommendations derived from observations through AMOS — the end product of the Landvex ecosystem.</p>
|
||||
<p class="term-long">Decision Intelligence is not data. It is not reports. It is the answer to a specific question: Which asset should I repair first? Where should I open my next store? Which claims are fraudulent? Landvex delivers Decision Intelligence by combining quiXzoom observations, AMOS analysis, and domain expertise into structured recommendations that directly enable decisions. Every output includes a confidence score and traceable source data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality receives a City Health Index of 71 for Norrmalm, down from 78 six months ago. The Decision Intelligence includes: specific deterioration patterns, contributing factors, recommended actions, and confidence intervals. The planner decides which streets to prioritise for maintenance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#index">Index</a><a href="#confidence-score">Confidence Score</a><a href="#amos">AMOS</a><a href="#control-intelligence">Control Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="decision-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Decision Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The top tier of the ecosystem where structured intelligence is translated into actionable decisions for customers.</p>
|
||||
<p class="term-long">The Decision Layer is where Landvex delivers intelligence products to end customers. It takes the indices, scores, and contradictions from the Analysis Layer and contextualises them for specific use cases: prioritising maintenance budgets, assessing insurance risk, evaluating property investments, ensuring regulatory compliance. The Decision Layer is customer-facing — it speaks the language of business, not technology. Every output is designed to answer one question: 'What decision does this help me make?'</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A property investor uses the Decision Layer to compare three potential acquisitions. The layer delivers a Neighbourhood Quality Index, Infrastructure Risk Score, and Commercial Opportunity Index for each — enabling a data-driven purchase decision in minutes rather than weeks.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#landvex">Landvex</a><a href="#analysis-layer">Analysis Layer</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="e">
|
||||
<div class="letter-heading">
|
||||
<h2>E</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="eur" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">EUR</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Euro — the secondary currency used in quiXzoom platform and Landvex products, primarily for European markets.</p>
|
||||
<p class="term-long">EUR is the secondary currency in the quiXzoom and Landvex ecosystem, used primarily for European markets and SEPA-zone transactions. Zoomers in Eurozone countries receive payouts in EUR via SEPA. Orderers in Europe may be invoiced in EUR. Like USD, EUR is a customer-facing currency — SEK is never shown to customers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A Zoomer in Germany receives their payout in EUR via SEPA. An orderer in France is invoiced in EUR for their monthly quiXzoom usage.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#usd">USD</a><a href="#sepa">SEPA</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="f">
|
||||
<div class="letter-heading">
|
||||
<h2>F</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="field-observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Field observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A structured data collection event performed at a physical location by a verified contributor, producing an observation record.</p>
|
||||
<p class="term-long">A field observation is the complete act of capturing reality data on location: travelling to the mission site, following the observation protocol, capturing required imagery from specified vantage points, and submitting the observation package. It is more than the photos — it is the verified, time-stamped, geo-located record of what was observed. Field observations are the foundational input to the entire quiXzoom–AMOS–Landvex pipeline. Without field observations, there is no data, no intelligence, and no decisions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer travels to a bridge inspection mission, follows the protocol (6 photos from specified angles), captures geo-tagged images, and submits. The field observation is verified by AI review and enters the AMOS dataset as a trusted data point.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#observation-protocol">Observation protocol</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="g">
|
||||
<div class="letter-heading">
|
||||
<h2>G</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="gdpr" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GDPR</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">General Data Protection Regulation — the EU framework governing how personal data is collected, stored, and processed.</p>
|
||||
<p class="term-long">GDPR (Regulation (EU) 2016/679) applies to any organisation processing the personal data of EU residents. For quiXzoom, this covers Zoomer identity data, GPS submission metadata, and orderer contact details. Key obligations include lawful basis for processing, data minimisation, purpose limitation, storage limitation, and honouring data subject rights (access, erasure, portability). All quiXzoom data is stored in EU (Stockholm, eu-north-1) to avoid third-country transfer complications.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Germany requests a copy of all data quiXzoom holds on them (right of access). quiXzoom must respond within 30 days with a machine-readable export of their submission history, identity data, and payment records — all governed by GDPR Article 15.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-controller">Data controller</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="i">
|
||||
<div class="letter-heading">
|
||||
<h2>I</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="index" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Index</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A normalised score (0–100) derived from thousands of observations, representing the condition, risk, or quality of an asset or area.</p>
|
||||
<p class="term-long">An Index is the primary output of the AMOS analysis engine — a single number that summarises complex, multi-dimensional observation data into an intuitive, comparable metric. Different indices serve different purposes: the City Health Index measures overall infrastructure condition; the Infrastructure Risk Index quantifies probability of failure; the Commercial Opportunity Index identifies high-potential investment areas. Indices are computed from aggregated observations, weighted by confidence scores, and updated continuously as new observations flow in.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A city's Road Condition Index drops from 72 to 58 over six months. AMOS traces the decline to increased pothole observations in the northern district. The municipality uses this Index to justify a €2M resurfacing budget — with the Index projected to return to 75 post-works.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#confidence-score">Confidence Score</a><a href="#decision-intelligence">Decision Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="l">
|
||||
<div class="letter-heading">
|
||||
<h2>L</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="landvex" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Landvex</h3>
|
||||
<span class="term-category cat-landvex">Landvex</span>
|
||||
</div>
|
||||
<p class="term-short">Global intelligence infrastructure company — builds decision intelligence from field observations.</p>
|
||||
<p class="term-long">Landvex Inc (Houston, TX) develops and sells IT products powered by AMOS engines. Landvex does not sell AI — it sells intelligence based on AMOS. The company combines quiXzoom field data, AMOS analysis, and domain expertise into decision intelligence products for infrastructure owners, governments, insurers, and enterprises. Landvex has operational presence in Europe and North America.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A property investor uses Landvex's Neighbourhood Quality Index to compare three potential acquisitions. The index combines infrastructure condition, safety observations, and commercial activity data into a single comparable score.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="landvex-ab" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">LandveX AB</h3>
|
||||
<span class="term-category cat-landvex">Landvex</span>
|
||||
</div>
|
||||
<p class="term-short">The Swedish entity (org.nr 559141-7042) that handles development, operations, and accounting in SEK.</p>
|
||||
<p class="term-long">LandveX AB is the Swedish subsidiary responsible for development, operations, and local accounting. It handles all Swedish bookkeeping, VAT, payroll, and supplier invoices in SEK using the BAS chart of accounts and SIE4 format. This is correct per Swedish accounting law. LandveX AB operates the technical infrastructure from Stockholm (AWS eu-north-1).</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>LandveX AB employs the development team, pays Swedish salaries, and files Swedish tax returns. All internal bookkeeping is in SEK, while customer-facing products use USD/EUR.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#landvex">Landvex</a><a href="#landvex-inc">Landvex Inc</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="landvex-inc" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Landvex Inc</h3>
|
||||
<span class="term-category cat-landvex">Landvex</span>
|
||||
</div>
|
||||
<p class="term-short">The US entity (Houston, TX) that develops and sells IT products powered by AMOS engines.</p>
|
||||
<p class="term-long">Landvex Inc is the US-based company that owns and operates the AAMOS platform and quiXzoom product. It is the legal entity responsible for product development, sales, and operations. Landvex Inc is NOT 'AAMOS Group' — there is no such entity. All products are developed and sold by Landvex Inc.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>Landvex Inc holds the intellectual property for AMOS engines, operates the quiXzoom platform, and sells intelligence products to enterprise customers worldwide.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#landvex">Landvex</a><a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="o">
|
||||
<div class="letter-heading">
|
||||
<h2>O</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A verified field record captured through quiXzoom — the fundamental unit of reality data.</p>
|
||||
<p class="term-long">An observation is not a photo. It is a structured, verified record of physical reality at a specific place and time. Every observation includes: geolocation (GPS coordinates with accuracy estimate), timestamp (when it was captured), media (images or video), and metadata (device, conditions, mission context). Observations are quality-checked by AI before entering the dataset. They are the raw material from which all Landvex intelligence is derived.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer captures 6 images of a road segment. Each image becomes part of an observation that includes GPS, timestamp, and mission context. AI review verifies the observation before it enters the dataset.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The field data collection tier where Zoomers capture verified observations of physical assets and infrastructure.</p>
|
||||
<p class="term-long">The Observation Layer is the foundation of the ecosystem — the interface between physical reality and digital intelligence. It encompasses the quiXzoom mobile app, Zoomer network, mission management system, and AI review pipeline. Its purpose is to produce high-quality, trustworthy observations at scale. The Observation Layer guarantees data integrity through geo-tagging, timestamp verification, and automated quality checks. Without a robust Observation Layer, everything above it — analysis, indices, decisions — is built on sand.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The Observation Layer deploys 500 Zoomers across a metropolitan area to capture quarterly building condition observations. Each observation is verified for GPS accuracy, image quality, and specification compliance before entering the Analysis Layer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#zoomer">Zoomer</a><a href="#reality-layer">Reality Layer</a><a href="#analysis-layer">Analysis Layer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="ouroboros" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Ouroboros</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The internal platform architecture that powers quiXzoom, AAMOS, and Landvex — a self-referential system where the platform monitors and improves itself.</p>
|
||||
<p class="term-long">Ouroboros is the internal name for the technical architecture that underpins the entire Landvex ecosystem. It encompasses the microservices, data pipelines, AI models, and infrastructure that enable quiXzoom field data collection, AMOS analysis, and Landvex intelligence delivery. The name reflects the system's self-monitoring nature: observations feed analysis, analysis drives decisions, decisions generate new observations. Ouroboros is not a customer-facing product — it is the technical foundation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>quiXzoom runs as an Ouroboros instance — using the same core infrastructure as other Landvex products but configured for the quiXzoom marketplace model. Ouroboros handles user management, mission orchestration, AI review, and data pipelines.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a><a href="#landvex">Landvex</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="p">
|
||||
<div class="letter-heading">
|
||||
<h2>P</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="pii" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">PII</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">Personally Identifiable Information — any data that can directly or indirectly identify a specific individual.</p>
|
||||
<p class="term-long">PII encompasses obvious identifiers (name, email, address, IBAN) as well as indirect identifiers that, in combination, could identify someone (GPS traces, device fingerprints, submission patterns). Under GDPR, quiXzoom treats PII with strict controls: it is collected only where necessary, retained only as long as required, and never shared with orderers in identifiable form. Zoomer submissions are delivered to orderers without attached Zoomer identity — orderers receive field data, not person data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When an orderer receives a completed submission, they see the images, GPS coordinates, and timestamp — but not the Zoomer's name, account details, or any identifying information. The Zoomer's identity is pseudonymised in normal operation, with full identification available only under legal process.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#data-controller">Data controller</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="q">
|
||||
<div class="letter-heading">
|
||||
<h2>Q</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="quixzoom-auth-core" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom Auth Core</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Standalone authentication product sold via AAMOS — includes Auth Foundation, KYZ Engine, Company Registry, and Payout Engine.</p>
|
||||
<p class="term-long">quiXzoom Auth Core is a standalone authentication and identity product that can be integrated into any application. It includes: Auth Foundation (email/Google + phone + password), KYZ Engine (Know Your Zoomer — identity verification), Company Registry (sole proprietorship / registered company), and Payout Engine (Stripe Connect, Frilans Finans, bank transfers). Auth Core is sold as a product via AAMOS and is used by quiXzoom and other Landvex products.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A third-party app developer integrates quiXzoom Auth Core to handle user authentication, identity verification, and payouts — without building these complex systems themselves.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="r">
|
||||
<div class="letter-heading">
|
||||
<h2>R</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="reality-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The physical world itself — the assets, infrastructure, and environments that the ecosystem observes, analyses, and optimises.</p>
|
||||
<p class="term-long">The Reality Layer is everything physical: roads, bridges, buildings, coastlines, forests, power lines, water pipes. It is the domain that exists independently of any observation system — the ground truth that the ecosystem seeks to understand and improve. The Reality Layer is not digital; it is the actual world that customers own, manage, insure, and invest in. Every observation is a measurement of the Reality Layer; every index is a summary of its state; every decision is an intervention upon it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A city's Reality Layer comprises 1,200 km of roads, 400 bridges, 50 tunnels, and 2,000 public buildings. The ecosystem's purpose is to create a complete, accurate, up-to-date digital understanding of this Reality Layer — enabling better decisions about maintenance, investment, and risk.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation-layer">Observation Layer</a><a href="#analysis-layer">Analysis Layer</a><a href="#decision-layer">Decision Layer</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="reality-signal" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Signal</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A measurable, verifiable observation that describes a specific aspect of the physical world.</p>
|
||||
<p class="term-long">A Reality Signal is any observation that carries information about the state of physical reality: a photo of a cracked bridge deck, a GPS-tagged image of flood damage, a timestamped record of a building's facade. Reality Signals are the raw inputs to the Analysis Layer. They are distinguished from synthetic or inferred data by their direct connection to physical measurement — a Zoomer was there, the camera captured light from the actual scene, the GPS recorded the actual coordinates. Reality Signals are the antidote to assumptions and desk-based estimates.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurer receives a Reality Signal showing hail damage to a factory roof — captured 6 hours after the storm, with GPS confirming the location, timestamp proving immediacy, and image quality enabling damage severity assessment. This Reality Signal replaces the traditional adjuster visit.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#reality-layer">Reality Layer</a><a href="#confidence-score">Confidence Score</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="rexo" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">REXO</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Landvex's coding pipeline for automated software development, testing, and deployment.</p>
|
||||
<p class="term-long">REXO is Landvex's internal coding pipeline that automates software development tasks. It runs via /opt/amos/rexo-build/, with tasks defined in plan/PLAN.json and executed by parallel workers. REXO orchestrates code generation, testing, and deployment across the ecosystem. All coding tasks should be routed through REXO rather than manual file uploads or direct server modifications.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>When a new feature is needed for the quiXzoom API, the task is added to REXO's PLAN.json. REXO workers generate the code, run tests, and deploy to staging — all without manual intervention.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#ouroboros">Ouroboros</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="right-to-erasure" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Right to erasure</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">A GDPR right allowing individuals to request deletion of their personal data from a platform's systems.</p>
|
||||
<p class="term-long">Under GDPR Article 17, individuals have the right to request erasure of their personal data when it is no longer necessary for the purpose it was collected, when they withdraw consent, or when they object to processing. For quiXzoom, this means Zoomers can request deletion of their account and all associated personal data at any time via the app settings. Certain data may need to be retained for limited periods to satisfy legal obligations (e.g. financial records under tax law) even after an erasure request.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer decides to stop using quiXzoom and requests erasure. quiXzoom deletes their profile, contact data, and GPS history. Some financial transaction records are retained for 7 years as required by EU accounting regulation — this is disclosed in quiXzoom's privacy policy and does not affect the Zoomer's ability to stop using the platform.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#data-controller">Data controller</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="u">
|
||||
<div class="letter-heading">
|
||||
<h2>U</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="usd" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">USD</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">United States Dollar — the primary currency used in quiXzoom platform and Landvex products.</p>
|
||||
<p class="term-long">USD is the main currency throughout the quiXzoom platform and Landvex ecosystem. All customer-facing pricing, payouts, and product fees are denominated in USD (or EUR where specified). This is a locked policy — SEK is never used in customer-facing copy, sites, documents, or communication. The only exception is LandveX AB's internal Swedish accounting.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A mission pays $15 (USD). A Zoomer's earnings are displayed in USD. Landvex enterprise contracts are priced in USD. This is consistent across all customer touchpoints.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#eur">EUR</a><a href="#payout">Payout</a><a href="#platform-fee">Platform fee</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="v">
|
||||
<div class="letter-heading">
|
||||
<h2>V</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="vims" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">VIMS</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Visual Infrastructure Monitoring System — a Landvex product for continuous infrastructure condition assessment.</p>
|
||||
<p class="term-long">VIMS (Visual Infrastructure Monitoring System) is a Landvex product that uses quiXzoom observations and AMOS analysis to provide continuous monitoring of infrastructure assets. It delivers condition indices, change alerts, and maintenance prioritisation for roads, bridges, buildings, and utilities. VIMS replaces periodic manual inspections with ongoing, data-driven condition assessment.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality subscribes to VIMS for their 400 bridges. Monthly observations from quiXzoom Zoomers feed into VIMS, which updates condition indices, flags new damage, and generates maintenance priority lists — all automatically.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a><a href="#index">Index</a><a href="#change-detection">Change detection</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<div class="last-updated">Last updated: July 14, 2026</div>
|
||||
</main>
|
||||
<footer style="background:#0d0d10;border-top:1px solid rgba(255,255,255,.07);padding:32px 24px;margin-top:48px">
|
||||
<div style="max-width:1080px;margin:0 auto;display:flex;align-items:center;justify-content:space-between;flex-wrap:wrap;gap:16px">
|
||||
<a href="/" style="font-size:1.1rem;font-weight:800;color:#fff;letter-spacing:-.03em;text-decoration:none">qui<span style="color:#3b82f6">X</span>zoom</a>
|
||||
<p style="font-size:.8125rem;color:rgba(255,255,255,.75);margin:0">© 2026 Landvex Inc</p>
|
||||
</div>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
Vendored
+1514
@@ -0,0 +1,1514 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Glossary — quixzoom</title>
|
||||
<meta name="description" content="Every term used on quixzoom. Defined precisely and kept current.">
|
||||
<link rel="canonical" href="https://www.quixzoom.com/glossary">
|
||||
<meta name="robots" content="index, follow">
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "DefinedTermSet",
|
||||
"name": "quixzoom Glossary",
|
||||
"description": "Complete glossary of terms",
|
||||
"publisher": {"@type": "Organization", "name": "Landvex Inc", "url": "https://www.landvex.com"}
|
||||
}
|
||||
</script>
|
||||
<style>*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
|
||||
:root {
|
||||
--bg: #ffffff; --bg-off: #f5f5f7; --bg-card: #ffffff;
|
||||
--text: #1d1d1f; --text-secondary: #6e6e73;
|
||||
--blue: #0066FF; --blue-light: #e8f0ff;
|
||||
--green: #00a550; --green-light: #e6f7ee;
|
||||
--purple: #7b2fff; --purple-light: #f0e8ff;
|
||||
--orange: #e8660a; --orange-light: #fff0e6;
|
||||
--pink: #ff3366; --pink-light: #ffe8f0;
|
||||
--radius: 18px; --radius-sm: 8px; --border: #d2d2d7;
|
||||
--nav-height: 64px; --shadow-hover: 0 12px 40px rgba(0,0,0,.10);
|
||||
}
|
||||
@media (prefers-color-scheme: dark) {
|
||||
:root {
|
||||
--bg: #000000; --bg-off: #1c1c1e; --bg-card: #1c1c1e;
|
||||
--text: #f5f5f7; --text-secondary: #98989f; --border: #3a3a3c;
|
||||
--blue-light: rgba(0,102,255,.15); --green-light: rgba(0,165,80,.15);
|
||||
--purple-light: rgba(123,47,255,.15); --orange-light: rgba(232,102,10,.15);
|
||||
--pink-light: rgba(255,51,102,.15); --shadow-hover: 0 12px 40px rgba(0,0,0,.5);
|
||||
}
|
||||
}
|
||||
html { scroll-behavior: smooth; }
|
||||
body {
|
||||
font-family: -apple-system, BlinkMacSystemFont, 'SF Pro Display', 'SF Pro Text', 'Helvetica Neue', Arial, sans-serif;
|
||||
background: var(--bg); color: var(--text); line-height: 1.6; -webkit-font-smoothing: antialiased;
|
||||
}
|
||||
.nav {
|
||||
position: sticky; top: 0; z-index: 100; height: var(--nav-height);
|
||||
background: rgba(255,255,255,.82); -webkit-backdrop-filter: blur(20px) saturate(180%);
|
||||
backdrop-filter: blur(20px) saturate(180%); border-bottom: 1px solid var(--border);
|
||||
display: flex; align-items: center; gap: 16px; padding: 0 24px;
|
||||
}
|
||||
@media (prefers-color-scheme: dark) { .nav { background: rgba(0,0,0,.82); } }
|
||||
.nav-logo { font-size: 1.25rem; font-weight: 800; color: var(--text); text-decoration: none; letter-spacing: -.04em; white-space: nowrap; flex-shrink: 0; }
|
||||
.nav-logo .x { color: var(--blue); }
|
||||
.nav-divider { width: 1px; height: 20px; background: var(--border); flex-shrink: 0; }
|
||||
.nav-title { font-size: .9375rem; font-weight: 600; color: var(--text-secondary); white-space: nowrap; flex-shrink: 0; }
|
||||
main { max-width: 860px; margin: 0 auto; padding: 0 24px 80px; }
|
||||
.page-header { padding: 64px 0 48px; text-align: center; }
|
||||
.page-header h1 { font-size: clamp(2.5rem, 6vw, 4rem); font-weight: 800; letter-spacing: -.04em; line-height: 1.05; color: var(--text); margin-bottom: 16px; }
|
||||
.page-header p { font-size: 1.125rem; color: var(--text-secondary); max-width: 480px; margin: 0 auto; }
|
||||
.letter-section { margin-bottom: 48px; }
|
||||
.letter-heading { display: flex; align-items: center; gap: 16px; margin-bottom: 20px; padding-bottom: 12px; border-bottom: 1px solid var(--border); }
|
||||
.letter-heading h2 { font-size: 2rem; font-weight: 800; color: var(--text-secondary); letter-spacing: -.04em; line-height: 1; width: 36px; flex-shrink: 0; }
|
||||
.letter-count { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-card { background: var(--bg-card); border: 1px solid var(--border); border-radius: var(--radius); padding: 28px 32px; margin-bottom: 16px; transition: box-shadow .2s, transform .2s; }
|
||||
.term-card:hover { box-shadow: var(--shadow-hover); transform: translateY(-2px); }
|
||||
.term-header { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; margin-bottom: 10px; flex-wrap: wrap; }
|
||||
.term-name { font-size: 1.3125rem; font-weight: 700; color: var(--text); letter-spacing: -.02em; line-height: 1.2; }
|
||||
.term-category { display: inline-block; padding: 4px 12px; border-radius: 20px; font-size: .75rem; font-weight: 600; letter-spacing: .02em; text-transform: uppercase; white-space: nowrap; flex-shrink: 0; margin-top: 2px; }
|
||||
.cat-platform { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-technical { background: var(--green-light); color: var(--green); }
|
||||
.cat-payment { background: var(--purple-light); color: var(--purple); }
|
||||
.cat-legal { background: var(--orange-light); color: var(--orange); }
|
||||
.cat-core { background: var(--bg-off); color: var(--text-secondary); }
|
||||
.cat-amos { background: var(--pink-light); color: var(--pink); }
|
||||
.cat-landvex { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-quixzoom { background: var(--green-light); color: var(--green); }
|
||||
.cat-product { background: var(--orange-light); color: var(--orange); }
|
||||
.term-short { font-size: 1rem; font-weight: 500; color: var(--text); margin-bottom: 12px; line-height: 1.5; }
|
||||
.term-long { font-size: .9375rem; color: var(--text-secondary); line-height: 1.65; margin-bottom: 16px; }
|
||||
.term-context { background: var(--bg-off); border-radius: var(--radius-sm); padding: 14px 18px; margin-bottom: 14px; }
|
||||
.term-context-label { font-size: .75rem; font-weight: 700; text-transform: uppercase; letter-spacing: .06em; color: var(--blue); display: block; margin-bottom: 6px; }
|
||||
.term-context p { font-size: .875rem; color: var(--text-secondary); line-height: 1.6; }
|
||||
.term-related { display: flex; align-items: center; flex-wrap: wrap; gap: 6px; }
|
||||
.term-related > span { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-related a { display: inline-block; padding: 3px 10px; border-radius: 20px; font-size: .8125rem; font-weight: 500; color: var(--blue); background: var(--blue-light); text-decoration: none; transition: background .12s, color .12s; }
|
||||
.term-related a:hover { background: var(--blue); color: #fff; }
|
||||
.last-updated { text-align: center; font-size: .8125rem; color: var(--text-secondary); margin-top: 48px; padding-top: 24px; border-top: 1px solid var(--border); }
|
||||
.term-card:target { border-color: var(--blue); box-shadow: 0 0 0 3px rgba(0,102,255,.15); }
|
||||
@media (max-width: 600px) { .nav { gap: 10px; padding: 0 16px; } .term-card { padding: 20px 18px; } .page-header { padding: 40px 0 32px; } }
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<nav class="nav">
|
||||
<a href="/" class="nav-logo">qui<span class="x">X</span>zoom</a>
|
||||
<div class="nav-divider"></div>
|
||||
<span class="nav-title">Glossary</span>
|
||||
</nav>
|
||||
<main>
|
||||
<header class="page-header">
|
||||
<h1>Every term.<br>Defined.</h1>
|
||||
<p>The complete quixzoom reference — from field observations to decision intelligence.</p>
|
||||
</header>
|
||||
<section class="letter-section" id="1">
|
||||
<div class="letter-heading">
|
||||
<h2>1</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="1099-k" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">1099-K</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A US tax document issued by payment platforms to payees who exceed IRS reporting thresholds for payments received through the platform.</p>
|
||||
<p class="term-long">Form 1099-K is issued by payment processors like Stripe to US persons who receive above the IRS reporting threshold (currently $600 per year under new IRS rules, though thresholds may vary). For quiXzoom Zoomers who are US persons, a 1099-K may be issued by Stripe for their annual earnings. Non-US Zoomers (who have completed a W-8BEN) are not subject to 1099-K reporting. Zoomers should retain their quiXzoom earnings summaries for local tax reporting regardless of 1099-K status.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A US-based Zoomer earning $1,200 from quiXzoom missions in a calendar year will receive a 1099-K from Stripe by January 31 of the following year. This document reports their platform earnings to the IRS and should be used when filing their annual tax return.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#w9-w8ben">W-9 / W-8BEN</a><a href="#stripe-connect">Stripe Connect</a><a href="#vat">VAT</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="a">
|
||||
<div class="letter-heading">
|
||||
<h2>A</h2>
|
||||
<span class="letter-count">8 terms</span>
|
||||
</div>
|
||||
<article id="active" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Active</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The middle Zoomer tier — 8–12 missions per week with 85%+ approval rate — balancing flexibility with consistent engagement.</p>
|
||||
<p class="term-long">Active tier represents Zoomers who use quiXzoom as a regular supplemental income source. To qualify, a Zoomer must sustain 8+ completed missions per week and maintain an approval rate above 85% over the qualifying window. Active Zoomers access a broader mission pool than Supplementary tier, including most premium mission types and higher-paying specialisation missions. Active tier is the threshold for most specialisation programme eligibility.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A part-time Zoomer completes 10 missions/week around their regular job, maintaining a 91% approval rate. At Active tier, they access infrastructure survey missions (€15–20) that are invisible to Supplementary Zoomers, and have applied for the Bridge & Civil specialisation programme.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#supplementary">Supplementary</a><a href="#professional">Professional</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="ai-review" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AI review</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Automated quality and specification check run on every submission before payment is triggered.</p>
|
||||
<p class="term-long">AI review is the first gate a submitted set of photos passes through. The system checks geo-accuracy (is the submission within the mission geofence?), image quality (sharpness, exposure, occlusion), specification compliance (correct angles, required elements present), and EXIF integrity (timestamp within time window, GPS data present and consistent). The result is either an approval — triggering payout — or a rejection with a reason code that the Zoomer can act on.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits 6 photos of a road segment. AI review verifies GPS coordinates match the mission location, timestamp falls within the claimed time window, and all required vantage points are covered — typically completing within 90 seconds of upload.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#approval">Approval</a><a href="#rejection">Rejection</a><a href="#submission">Submission</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="aml" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AML</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">Anti-Money Laundering — the regulatory framework that requires payment platforms to verify the identity of anyone receiving funds.</p>
|
||||
<p class="term-long">AML regulation obliges financial institutions and payment platforms to implement controls that prevent the platform from being used to launder illegally obtained money. In practice, this means platforms like Stripe — which powers quiXzoom's payouts — must verify Zoomer identity (KYC) before processing disbursements. AML requirements vary by jurisdiction but are broadly harmonised across the EU under the Anti-Money Laundering Directives (AMLD).</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Before a Zoomer can receive their first payout, they must complete KYC. This is not a quiXzoom policy choice — it is a legal obligation on Stripe (our payment provider) under AML regulation. The process is a one-time requirement.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#identity-verification">Identity verification</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Adaptive Autonomous Multi-Agent Operating System — the AI capability platform that powers Landvex intelligence products.</p>
|
||||
<p class="term-long">AMOS is not an AI system. It is an AI Capability Platform — a suite of specialised engines that process observations into structured intelligence. AMOS ingests raw field data from quiXzoom, applies computer vision, pattern recognition, and cross-referencing, and produces outputs: indices, scores, change flags, and predictive signals. AMOS is the analytical layer between reality and decisions. It is developed and sold by Landvex Inc, Houston, TX.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>quiXzoom collects 12,000 observations of bridge conditions across Sweden. AMOS processes these into an Infrastructure Risk Index — a single score per bridge that maintenance planners can prioritise by.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#index">Index</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#amos-vision">AMOS Vision</a><a href="#amos-identity">AMOS Identity</a><a href="#amos-fraud">AMOS Fraud</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-identity" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Identity</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Identity verification, document control, liveness detection, and fraud prevention engine.</p>
|
||||
<p class="term-long">AMOS Identity verifies that a person is who they claim to be. It processes government-issued IDs, performs liveness checks, and detects document tampering or synthetic identity fraud. The engine is used for KYC processes, access control, and high-trust verification scenarios.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes identity verification by submitting their passport and a selfie. AMOS Identity verifies the document's authenticity and matches the selfie to the ID photo with 99.7% accuracy.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#liveness-check">Liveness check</a><a href="#identity-verification">Identity verification</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="api" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">API</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Application Programming Interface — the programmatic interface through which orderers access mission data, submission results, and platform services.</p>
|
||||
<p class="term-long">The quiXzoom API is a REST-style HTTP API that allows orderers to submit mission briefs, monitor mission status, retrieve completed submission packages (images, metadata, GeoJSON), and receive real-time updates via webhooks. Responses are in JSON format. The API uses OAuth 2.0 for authentication and HMAC-SHA256 for webhook signature verification.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company integrates the quiXzoom API into their claims management system. When a claim is filed for a specific address, an API call automatically creates a mission, and approved submission data flows directly back into the claims system without manual intervention.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#webhook">Webhook</a><a href="#oauth">OAuth</a><a href="#json">JSON</a><a href="#hmac-sha256">HMAC-SHA256</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="approval" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Approval</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A positive outcome from AI review, confirming a submission meets all mission requirements and triggering Zoomer payout.</p>
|
||||
<p class="term-long">When AI review determines that a submission satisfies all specification, quality, and location requirements for a mission, the submission is marked as Approved. This event is the trigger for payout to the Zoomer and for delivery of the submission package to the orderer. Approval also counts positively toward the Zoomer's approval rate and rating.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits a marina documentation mission. AI review approves the submission within 2 minutes; the Zoomer sees a confirmation in-app and their €12 earnings are queued for the next payout cycle. The orderer receives the submission package via webhook.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#rejection">Rejection</a><a href="#approval-rate">Approval rate</a><a href="#ai-review">AI review</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="approval-rate" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Approval rate</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The percentage of submitted missions that pass AI review, calculated over a rolling 30-day window.</p>
|
||||
<p class="term-long">Approval rate is the primary quality signal on the quiXzoom platform. It is calculated as approved submissions divided by total submissions over the preceding 30 days. A Zoomer's approval rate directly determines their tier eligibility and access to premium and surge missions. Professional tier requires maintaining above 92% approval; Active tier requires above 85%. Zoomers below 70% receive coaching and may be temporarily restricted from claiming new missions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer with 38 approvals and 2 rejections out of 40 submissions in the last 30 days has a 95% approval rate. This qualifies them for Professional tier and unlocks access to premium infrastructure missions paying up to €30 per submission.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#rejection">Rejection</a><a href="#tier">Tier</a><a href="#premium-mission">Premium mission</a><a href="#rating">Rating</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="c">
|
||||
<div class="letter-heading">
|
||||
<h2>C</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="change-detection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Change detection</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The automated identification of differences between current observations and historical baseline data — surfacing what has changed in the physical world.</p>
|
||||
<p class="term-long">Change detection is a core AMOS capability that compares new observations against prior data to identify additions, removals, or modifications to physical assets. It powers infrastructure monitoring, property condition tracking, and environmental surveillance. Change detection operates at multiple scales: from pixel-level differences in repeated photographs to structural changes identified through computer vision. Each detected change is scored by confidence and severity, and flagged as a Contradiction when it represents an unexpected deviation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a retail park shows three new storefronts and one demolished unit compared to the baseline from six months ago. AMOS change detection automatically flags these modifications, updates the asset registry, and alerts the property manager to verify the changes.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#contradiction">Contradiction</a><a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="claim" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Claim / Claiming</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The act of reserving a mission — locking it exclusively for you within a defined time window.</p>
|
||||
<p class="term-long">When a Zoomer claims a mission, the mission is removed from the available pool and assigned exclusively to that Zoomer for the duration of the time window. No other Zoomer can claim the same mission while it is held. If the Zoomer does not submit within the time window, the mission is automatically released back to the pool. Frequent abandonment (claiming without submitting) negatively affects a Zoomer's rating and may trigger restrictions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer sees a bridge inspection mission 0.8 km away. They tap Claim — the mission is now exclusively theirs for 4 hours. They travel to the location, complete the documentation, and submit. If they don't submit within 4 hours, the mission releases automatically.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#time-window">Time window</a><a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#rating">Rating</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="confidence-score" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Confidence Score</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A statistical measure of certainty attached to an observation or analysis output, expressed as a percentage.</p>
|
||||
<p class="term-long">The Confidence Score quantifies how certain the system is about a specific observation or derived insight. It is computed from multiple signals: EXIF integrity, GPS accuracy, image clarity, cross-validation against historical data, and agreement with other observations of the same asset. A high confidence score (90%+) indicates strong reliability; a low score triggers manual review or additional observation requests. Confidence scores are essential for decision-making — they tell the customer not just what was observed, but how much to trust it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection observation receives a 94% confidence score based on sharp imagery, precise GPS, and consistency with the previous inspection. An insurer uses this high-confidence observation to approve a maintenance claim without sending an engineer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="contradiction" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Contradiction</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A mismatch between observed reality and expected or previously recorded reality — a signal that something has changed or requires attention.</p>
|
||||
<p class="term-long">A Contradiction is flagged when an observation deviates significantly from the expected state: a building that was intact now shows damage, a road that was clear now has a sinkhole, or an asset that was present is now missing. Contradictions are not errors — they are valuable signals. They trigger alerts, escalate priority, and often indicate the most urgent decisions a customer must make. The Contradiction engine cross-references observations against historical data, design specifications, and regulatory baselines.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a commercial roof shows new water staining not present in the previous observation. AMOS flags this as a Contradiction, alerting the property manager to schedule repairs before the rainy season — preventing a €50,000 claim.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#confidence-score">Confidence Score</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="control-intelligence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Control Intelligence</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">Descriptive intelligence that tells you the current state of your physical assets — what is, not what to do.</p>
|
||||
<p class="term-long">Control Intelligence answers the question: 'What is the current condition of my assets?' It is the foundational layer of insight derived from observations, describing reality as it exists today: which bridges are sound, which buildings have damage, which roads need repair. Control Intelligence is objective, measurable, and verifiable. It is the raw material from which Decision Intelligence is forged — you cannot decide what to do until you know what is.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality receives Control Intelligence showing that 12% of its road bridges have surface cracking, 3% have structural concerns, and 85% are in good condition. This descriptive baseline is the starting point for all maintenance and investment decisions.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#decision-intelligence">Decision Intelligence</a><a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="csv" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">CSV</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Comma-Separated Values — a plain-text tabular data format available as a bulk export option for orderers.</p>
|
||||
<p class="term-long">CSV exports from quiXzoom contain one row per submission, with columns for mission ID, submission timestamp, GPS coordinates, approval status, Zoomer tier (anonymised), and other metadata fields. CSV is suitable for bulk import into spreadsheet tools, BI platforms, or legacy claims systems that do not support JSON or API integration. CSV exports are available on demand via the orderer dashboard or API.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality uses CSV exports to import quiXzoom road survey data into their GIS system on a weekly basis, plotting submission coordinates alongside existing infrastructure records.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#json">JSON</a><a href="#geojson">GeoJSON</a><a href="#api">API</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="d">
|
||||
<div class="letter-heading">
|
||||
<h2>D</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="data-controller" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data controller</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The entity that determines the purposes and means of processing personal data — under GDPR, quiXzoom acts as data controller for Zoomer and orderer data.</p>
|
||||
<p class="term-long">Under GDPR, the data controller is the legal entity responsible for deciding why and how personal data is processed. quiXzoom is the data controller for data collected from Zoomers (name, contact details, bank details, submission metadata) and from orderers. As data controller, quiXzoom must maintain a Record of Processing Activities (RoPA), appoint a Data Protection Officer where required, and respond to data subject rights requests within statutory timeframes.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer exercises their right to erasure, they submit a request to quiXzoom as data controller. quiXzoom is then legally responsible for erasing the Zoomer's personal data from its systems and instructing its data processors (including the KYC provider and Stripe) to do the same.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-processor">Data processor</a><a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-processor" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data processor</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">An entity that processes personal data on behalf of the data controller, under a Data Processing Agreement (DPA).</p>
|
||||
<p class="term-long">Data processors act on the instructions of the data controller and cannot use the data for their own purposes. quiXzoom's data processors include Stripe (payment processing), the KYC provider (identity verification), and cloud infrastructure providers. Each processor relationship must be governed by a Data Processing Agreement that complies with GDPR Article 28, specifying the scope, nature, purpose, and duration of processing.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The KYC provider that verifies Zoomer identities is a data processor for quiXzoom. They process identity documents and liveness check data strictly for identity verification purposes, under a DPA — they cannot use that data for their own marketing or analytics.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-controller">Data controller</a><a href="#gdpr">GDPR</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-residency" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data residency</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The geographic location where data is stored — quiXzoom stores all data in the EU (Stockholm, eu-north-1).</p>
|
||||
<p class="term-long">Data residency is increasingly important for enterprise customers in regulated industries, who may have legal or policy obligations requiring that data stays within a specific jurisdiction. quiXzoom's infrastructure runs on AWS eu-north-1 (Stockholm), keeping all data within the European Economic Area. This satisfies GDPR third-country transfer restrictions and is a key requirement for public sector and financial services customers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An EU public sector orderer requires that all submission data — including GPS coordinates and images — never leaves the EEA. quiXzoom's Stockholm data residency satisfies this requirement by default, without special configuration.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#s3">S3</a><a href="#pii">PII</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="disbursement" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Disbursement</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">The technical transfer of earned funds from the platform escrow to a Zoomer's linked bank account.</p>
|
||||
<p class="term-long">Disbursement is the formal payment term for the outbound transfer of earned mission compensation. In quiXzoom's architecture, approved submission earnings accumulate in a Stripe Connect account (held on behalf of the Zoomer), and disbursements are processed on a rolling basis to the Zoomer's linked IBAN. Disbursements are distinct from the mission approval event — there may be a short settlement window between approval and disbursement depending on Stripe's payout schedule.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer's mission is approved at 14:00 on a Tuesday. Their earnings are added to their Stripe Connect balance immediately, and the disbursement to their bank account is processed as part of the next scheduled payout run — typically within 1–2 business days.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#payout">Payout</a><a href="#stripe-connect">Stripe Connect</a><a href="#iban">IBAN</a><a href="#sepa">SEPA</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="e">
|
||||
<div class="letter-heading">
|
||||
<h2>E</h2>
|
||||
<span class="letter-count">2 terms</span>
|
||||
</div>
|
||||
<article id="eur" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">EUR</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Euro — the secondary currency used in quiXzoom platform and Landvex products, primarily for European markets.</p>
|
||||
<p class="term-long">EUR is the secondary currency in the quiXzoom and Landvex ecosystem, used primarily for European markets and SEPA-zone transactions. Zoomers in Eurozone countries receive payouts in EUR via SEPA. Orderers in Europe may be invoiced in EUR. Like USD, EUR is a customer-facing currency — SEK is never shown to customers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A Zoomer in Germany receives their payout in EUR via SEPA. An orderer in France is invoiced in EUR for their monthly quiXzoom usage.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#usd">USD</a><a href="#sepa">SEPA</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="exif" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">EXIF</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Exchangeable Image File Format — metadata embedded in image files, including GPS coordinates, capture timestamp, device model, and camera settings.</p>
|
||||
<p class="term-long">EXIF metadata is written into image files at capture time by the device camera. For quiXzoom, EXIF is the primary evidence layer: it carries the GPS coordinates where the photo was taken, the precise timestamp, and device identifiers. AI review cross-validates EXIF GPS coordinates against the mission geofence, and EXIF timestamps against the mission time window. EXIF data is preserved in delivery packages to orderers as part of the chain-of-custody record.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer photographs a flood-damaged road. The image's EXIF data records 59.3312°N, 18.0685°E at 09:47:23 UTC. AI review checks this GPS fix is within the mission's 50-metre geofence and the timestamp falls within the claimed time window — both pass, contributing to approval.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#gps">GPS</a><a href="#timestamp">Timestamp</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="f">
|
||||
<div class="letter-heading">
|
||||
<h2>F</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="field-observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Field observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A structured data collection event performed at a physical location by a verified contributor, producing an observation record.</p>
|
||||
<p class="term-long">A field observation is the complete act of capturing reality data on location: travelling to the mission site, following the observation protocol, capturing required imagery from specified vantage points, and submitting the observation package. It is more than the photos — it is the verified, time-stamped, geo-located record of what was observed. Field observations are the foundational input to the entire quiXzoom–AMOS–Landvex pipeline. Without field observations, there is no data, no intelligence, and no decisions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer travels to a bridge inspection mission, follows the protocol (6 photos from specified angles), captures geo-tagged images, and submits. The field observation is verified by AI review and enters the AMOS dataset as a trusted data point.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#observation-protocol">Observation protocol</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="g">
|
||||
<div class="letter-heading">
|
||||
<h2>G</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="gdpr" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GDPR</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">General Data Protection Regulation — the EU framework governing how personal data is collected, stored, and processed.</p>
|
||||
<p class="term-long">GDPR (Regulation (EU) 2016/679) applies to any organisation processing the personal data of EU residents. For quiXzoom, this covers Zoomer identity data, GPS submission metadata, and orderer contact details. Key obligations include lawful basis for processing, data minimisation, purpose limitation, storage limitation, and honouring data subject rights (access, erasure, portability). All quiXzoom data is stored in EU (Stockholm, eu-north-1) to avoid third-country transfer complications.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Germany requests a copy of all data quiXzoom holds on them (right of access). quiXzoom must respond within 30 days with a machine-readable export of their submission history, identity data, and payment records — all governed by GDPR Article 15.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-controller">Data controller</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geo-accuracy" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geo-accuracy</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The closeness of a recorded GPS coordinate to the actual physical position — typically expressed in metres of error radius.</p>
|
||||
<p class="term-long">Geo-accuracy is determined by GPS signal quality, which is affected by urban canyon effects, tree canopy, atmospheric conditions, and device hardware. Consumer smartphone GPS typically achieves 3–10 metre accuracy in open conditions. quiXzoom's mission geofences are sized to account for realistic geo-accuracy limits — a mission for a specific building typically uses a 30–50 metre compliance radius. AI review evaluates whether the recorded GPS position is within the mission's accepted tolerance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer photographs a bridge in a narrow urban gorge where GPS signals reflect off buildings. Their device records a position 18 metres from the mission pin — within the 30-metre geofence tolerance — so the submission passes the geo-accuracy check.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#geo-tagged">Geo-tagged</a><a href="#exif">EXIF</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geo-tagged" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geo-tagged</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An image embedded with GPS coordinates at capture time, proving where the photo was physically taken.</p>
|
||||
<p class="term-long">Geo-tagging writes latitude, longitude, and altitude data into the image's EXIF metadata at the moment of capture. All quiXzoom submissions must be geo-tagged — this is a technical requirement enforced by the app. Submissions from devices with disabled location services are rejected before upload. Geo-tagging is the foundation of quiXzoom's location verification: without it, there is no way to confirm the photo was taken at the correct mission location.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The quiXzoom app requires location permissions to function. When a Zoomer captures a photo in-app, GPS coordinates are written to EXIF automatically. A Zoomer cannot submit photos taken in a regular camera app that disabled geo-tagging — the submission would fail AI review immediately.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#exif">EXIF</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#geojson">GeoJSON</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geofence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geofence</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A virtual geographic boundary defining where a mission must be completed — submissions outside the geofence are automatically rejected.</p>
|
||||
<p class="term-long">A geofence is a digitally defined perimeter around a mission location, typically represented as a circle with a radius of 30–100 metres or as a GeoJSON Polygon for complex shapes. When a Zoomer submits photos, AI review checks the EXIF GPS coordinates against the mission geofence. If the submission was captured outside the geofence, it is rejected with a location mismatch reason. Geofences ensure data integrity by guaranteeing that observations were physically captured at the correct location, preventing fraudulent or mistaken submissions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection mission has a 50-metre radius geofence centred on the bridge coordinates. A Zoomer submits photos from 200 metres away — the GPS coordinates in EXIF fall outside the geofence, and AI review rejects the submission with 'Location mismatch — outside geofence.'</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#exif">EXIF</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geojson" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GeoJSON</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An open standard format (RFC 7946) for encoding geographic data structures using JSON.</p>
|
||||
<p class="term-long">GeoJSON is used by quiXzoom to define mission boundaries (geofences), to encode submission GPS paths, and to deliver location data to orderers in a format compatible with GIS platforms, mapping tools, and geographic analysis software. A mission boundary is represented as a GeoJSON Polygon; individual submission GPS points as GeoJSON Point Features with properties including timestamp, approval status, and submission ID.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality ordering a road condition survey receives their submission data as a GeoJSON FeatureCollection, which they import directly into QGIS to visualise submission density alongside their road network layer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#json">JSON</a><a href="#api">API</a><a href="#mission-brief">Mission brief</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="gps" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GPS</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Global Positioning System — the satellite-based navigation system used to determine precise geographic location of submissions.</p>
|
||||
<p class="term-long">GPS is the primary location technology in smartphones, providing latitude, longitude, and altitude data by triangulating signals from multiple satellites. All quiXzoom submissions depend on GPS for location verification. The system is augmented by network-based location (Wi-Fi and cell triangulation) in environments where satellite signals are weak — combined, these signals provide the geo-accuracy required for mission compliance checks.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Every time a Zoomer captures a photo for a mission, the device GPS is sampled. This fix — along with the capture timestamp — is embedded in EXIF and used by AI review to verify the submission was made at the correct location within the correct time window.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#exif">EXIF</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="h">
|
||||
<div class="letter-heading">
|
||||
<h2>H</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="hmac-sha256" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">HMAC-SHA256</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A cryptographic signature method used to verify that webhook payloads were genuinely sent by quiXzoom and were not tampered with in transit.</p>
|
||||
<p class="term-long">HMAC (Hash-based Message Authentication Code) with SHA-256 works by combining the webhook payload with a shared secret key to produce a unique signature. quiXzoom attaches this signature to every webhook request in the X-QuiXzoom-Signature header. The receiving system recomputes the signature using the same secret and compares — if they match, the payload is authentic and unmodified. This is industry-standard practice used by Stripe, GitHub, and other major webhook providers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's claims system receives a webhook when a submission is approved. Before processing the data, their server verifies the HMAC-SHA256 signature against their shared webhook secret — confirming the event genuinely originated from quiXzoom and was not injected by a third party.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#webhook">Webhook</a><a href="#api">API</a><a href="#oauth">OAuth</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="i">
|
||||
<div class="letter-heading">
|
||||
<h2>I</h2>
|
||||
<span class="letter-count">2 terms</span>
|
||||
</div>
|
||||
<article id="iban" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">IBAN</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">International Bank Account Number — the standardised account identifier required for Stripe Connect payout setup in Europe.</p>
|
||||
<p class="term-long">IBAN is the international standard for identifying bank accounts across national borders, defined by ISO 13616. It consists of up to 34 alphanumeric characters: a 2-letter country code, 2 check digits, and the bank-specific account number. IBANs are used throughout SEPA for credit transfers and direct debits. Zoomers in supported SEPA countries link their IBAN during Stripe Connect onboarding — this is the account that will receive payout disbursements.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in the Netherlands enters their IBAN (NL39 RABO 0300 0652 64) during onboarding. All subsequent payouts from approved missions are disbursed to this account via SEPA credit transfer through Stripe Connect.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#sepa">SEPA</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a><a href="#disbursement">Disbursement</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="identity-verification" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Identity verification</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A one-time process confirming a Zoomer's identity with a government-issued ID and liveness check, required before the first payout.</p>
|
||||
<p class="term-long">Identity verification is a legal requirement under AML regulation for any payment platform processing disbursements. For quiXzoom, it involves submitting a government-issued photo ID (passport, national ID card, or driving licence) and a liveness check (selfie). The process is handled by a regulated KYC provider — not by quiXzoom directly — and typically completes within 1 hour. Identity verification is a one-time requirement: once verified, Zoomers never repeat it unless their details change materially.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A new Zoomer completes their first 3 missions before being prompted to verify identity before their first payout. They photograph their passport and complete a 15-second liveness check in-app. The KYC provider approves the verification within 45 minutes, and the payout is released.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#liveness-check">Liveness check</a><a href="#aml">AML</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="j">
|
||||
<div class="letter-heading">
|
||||
<h2>J</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="json" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">JSON</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">JavaScript Object Notation — the lightweight data format used for all quiXzoom API responses and webhook payloads.</p>
|
||||
<p class="term-long">JSON is a human-readable, language-agnostic data serialisation format that has become the de facto standard for web APIs. quiXzoom's REST API delivers all responses as JSON, including mission details, submission metadata, location data, and approval status. Webhook event payloads are also JSON. The format is natively supported in virtually all programming languages and integration platforms, making it straightforward to process quiXzoom data in any technical environment.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When an orderer queries the API for a completed submission, the response is a JSON object containing the submission ID, approval status, GPS coordinates, EXIF metadata summary, and signed URLs to retrieve the image files from S3.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#webhook">Webhook</a><a href="#geojson">GeoJSON</a><a href="#csv">CSV</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="k">
|
||||
<div class="letter-heading">
|
||||
<h2>K</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="kyc" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">KYC</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Know Your Customer — the regulatory process of verifying the identity of individuals before processing financial transactions on their behalf.</p>
|
||||
<p class="term-long">KYC is a standard compliance process required by AML regulation for payment platforms and financial services providers. In the quiXzoom context, KYC is performed by a regulated third-party identity verification provider (not by quiXzoom internally) on behalf of Stripe Connect. The process collects a government-issued ID and liveness check result, which are verified against government databases and fraud watchlists. KYC data is held by the verification provider, not by quiXzoom — quiXzoom only receives a pass/fail status.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Before a Zoomer can withdraw their first earnings, they are prompted to complete KYC. The 3–5 minute in-app flow captures their passport and a selfie, and is processed by the KYC provider. quiXzoom receives confirmation of verified status — not the underlying documents — and the payout queue is unblocked.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#aml">AML</a><a href="#identity-verification">Identity verification</a><a href="#liveness-check">Liveness check</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="l">
|
||||
<div class="letter-heading">
|
||||
<h2>L</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="liveness-check" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Liveness check</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A selfie-based verification step that confirms a real, live person is presenting the identity document — not a photo or deepfake.</p>
|
||||
<p class="term-long">Liveness detection uses computer vision to analyse a short selfie capture and confirm it is a genuine live face rather than a printed photo, screen replay, or synthetic image. It is performed as part of the KYC process to prevent identity fraud — specifically to stop bad actors using stolen ID documents paired with someone else's photo. Modern liveness checks typically involve a brief instructed motion (e.g. blinking or turning the head) to prove liveness unambiguously.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>During identity verification, a new Zoomer is asked to look at their phone camera and slowly turn their head. The liveness check confirms it's a real person in real time — not someone holding up a printed photo of the account holder. The whole step takes under 15 seconds.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#identity-verification">Identity verification</a><a href="#aml">AML</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="m">
|
||||
<div class="letter-heading">
|
||||
<h2>M</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A paid photography assignment with a defined location, scope, and compensation, published by an orderer and claimed by a Zoomer.</p>
|
||||
<p class="term-long">A mission is the fundamental unit of work on the quiXzoom platform. Each mission has a geographic pin or geofence, a compensation amount, a mission brief (describing what to photograph and how), a time window within which the work must be completed, and a submission specification defining how many photos are required and from which vantage points. Missions may be standard, premium, or surge, and may be single-submission or multi-submission.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company creates a mission to document storm damage at a specific address. The mission has a 200-metre geofence, requires 8 photos from specified angles, pays €14, and has a 6-hour time window from claim. A nearby Zoomer sees it in the app, claims it, and completes the documentation.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission-brief">Mission brief</a><a href="#claim">Claim / Claiming</a><a href="#submission">Submission</a><a href="#time-window">Time window</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="mission-brief" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Mission brief</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The complete specification for a mission — what to capture, how to capture it, quality requirements, and any special instructions.</p>
|
||||
<p class="term-long">A mission brief is shown to the Zoomer after they claim a mission, and is the primary guide for execution. It includes required shot angles, distance from subject, lighting conditions (if relevant), specific elements that must appear in frame, and any contextual notes from the orderer. Mission briefs for specialised mission types (bridge inspection, maritime, infrastructure) include more detailed technical requirements. Zoomers should read the brief carefully before travelling to the mission location.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection mission brief specifies: 1 overview shot from 50m, 2 deck surface shots, 1 expansion joint close-up, 1 bearing detail, and 1 drainage outlet — all from public access points only. A Zoomer who misses the bearing detail shot is likely to receive a rejection at AI review.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#specialisation">Specialisation</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="mission-density" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Mission density</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The number of active missions available per geographic area — a key factor in a Zoomer's earning potential by location.</p>
|
||||
<p class="term-long">Mission density varies significantly between urban and rural areas, between regions, and over time. High mission density zones (dense urban areas, coastal regions with infrastructure) allow Zoomers to complete more missions per hour of activity — increasing hourly earnings. Mission density is influenced by orderer activity in the area and by platform growth. Zoomers can view mission density maps to understand the earning environment in different zones before setting their zone preferences.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Stockholm's inner city shows 23 active missions within a 5km radius. A nearby suburb shows 3. A Zoomer choosing their zone setting can use mission density data to maximise their available mission volume per session.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#zone">Zone</a><a href="#mission">Mission</a><a href="#tier">Tier</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="multi-submission-mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Multi-submission mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A mission type where multiple Zoomers can submit, with compensation decreasing for each successive approved submission.</p>
|
||||
<p class="term-long">Multi-submission missions are used by orderers who want several independent documentation sets of the same location — typically for comparison, validation, or higher confidence. The first Zoomer to submit receives the highest compensation; subsequent approved submissions receive progressively lower amounts. The orderer sets the maximum number of submissions they will accept and the compensation schedule. Multi-submission missions remain claimable by additional Zoomers until the orderer's submission limit is reached.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An orderer creates a multi-submission mission for a flood-affected road segment, accepting 3 submissions at €18 / €12 / €8. Three different Zoomers claim and submit independently — the orderer receives three distinct photographic records of the same location, useful for triangulating damage assessment.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#surge-mission">Surge mission</a><a href="#premium-mission">Premium mission</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="o">
|
||||
<div class="letter-heading">
|
||||
<h2>O</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="oauth" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">OAuth</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Open Authorization — the industry-standard protocol used by quiXzoom's API for secure, delegated authentication.</p>
|
||||
<p class="term-long">OAuth 2.0 allows orderers to authenticate API requests without sharing credentials. Orderers obtain access tokens through the OAuth flow, which are then included in API request headers. Tokens can be scoped (read-only, write, full access) and have configurable expiry periods. OAuth 2.0 is also used for third-party integrations — for example, allowing an orderer's claims management platform to connect to quiXzoom on behalf of their organisation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's IT team sets up an OAuth 2.0 client in the quiXzoom orderer portal, receives client credentials, and uses these to generate short-lived access tokens for their claims integration server. Tokens expire after 1 hour and are automatically refreshed.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#webhook">Webhook</a><a href="#hmac-sha256">HMAC-SHA256</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A verified field record captured through quiXzoom — the fundamental unit of reality data.</p>
|
||||
<p class="term-long">An observation is not a photo. It is a structured, verified record of physical reality at a specific place and time. Every observation includes: geolocation (GPS coordinates with accuracy estimate), timestamp (when it was captured), media (images or video), and metadata (device, conditions, mission context). Observations are quality-checked by AI before entering the dataset. They are the raw material from which all Landvex intelligence is derived.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer captures 6 images of a road segment. Each image becomes part of an observation that includes GPS, timestamp, and mission context. AI review verifies the observation before it enters the dataset.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The field data collection tier where Zoomers capture verified observations of physical assets and infrastructure.</p>
|
||||
<p class="term-long">The Observation Layer is the foundation of the ecosystem — the interface between physical reality and digital intelligence. It encompasses the quiXzoom mobile app, Zoomer network, mission management system, and AI review pipeline. Its purpose is to produce high-quality, trustworthy observations at scale. The Observation Layer guarantees data integrity through geo-tagging, timestamp verification, and automated quality checks. Without a robust Observation Layer, everything above it — analysis, indices, decisions — is built on sand.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The Observation Layer deploys 500 Zoomers across a metropolitan area to capture quarterly building condition observations. Each observation is verified for GPS accuracy, image quality, and specification compliance before entering the Analysis Layer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#zoomer">Zoomer</a><a href="#reality-layer">Reality Layer</a><a href="#analysis-layer">Analysis Layer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation-protocol" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation protocol</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The standardised set of instructions defining what to capture, from which angles, and under what conditions for a given mission type.</p>
|
||||
<p class="term-long">The observation protocol is the rulebook for field data collection. It specifies the number of photos required, the vantage points (distance, angle, height), the elements that must be in frame, lighting conditions, and any safety or access constraints. Protocols are mission-type specific: a bridge inspection protocol differs from a property documentation protocol. Following the protocol is essential for approval — AI review checks compliance against the protocol, and deviations result in rejection. Protocols are developed by domain experts and refined through feedback from AI review outcomes.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A roof condition mission protocol requires: 1 overview shot from street level, 1 ridge-line photo, 2 slope photos (one per side), and 1 detail of any visible damage — all captured during daylight with the sun behind the photographer. A Zoomer who submits only 3 photos or captures at night will fail protocol compliance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#field-observation">Field observation</a><a href="#mission-brief">Mission brief</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="orderer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Orderer</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">An organisation that creates and funds missions on the quiXzoom platform to obtain field documentation.</p>
|
||||
<p class="term-long">Orderers are the demand side of the quiXzoom marketplace. They can be insurance companies, infrastructure asset owners, public sector bodies, logistics operators, or any organisation with a need for verified on-location photography. Orderers define mission briefs, set compensation, and receive approved submissions via the dashboard or API. Orderers pay the Zoomer compensation plus a platform fee to quiXzoom.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Swedish infrastructure authority uses quiXzoom as orderer — creating 50 bridge inspection missions across a county, specifying technical requirements in each mission brief, and receiving standardised submission packages via API integration with their asset management system.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#platform-fee">Platform fee</a><a href="#api">API</a><a href="#sla">SLA</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="p">
|
||||
<div class="letter-heading">
|
||||
<h2>P</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="payout" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Payout</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">The transfer of earned mission compensation to a Zoomer's linked bank account, triggered automatically by submission approval.</p>
|
||||
<p class="term-long">Payouts are processed via Stripe Connect and deposited to the Zoomer's linked IBAN. Earnings from approved submissions accumulate in the Zoomer's Stripe Connect balance and are disbursed on a rolling schedule. Payout frequency and minimum threshold are configurable within the app. Payouts require completed identity verification (KYC) and a linked bank account. Zoomers receive an in-app notification and email confirmation for each payout.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes 5 missions in a week, earning €72 total. After each approval, earnings add to their Stripe Connect balance. On Friday, their accumulated balance is disbursed to their Dutch IBAN via SEPA — arriving as a single bank transfer with a quiXzoom reference.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#disbursement">Disbursement</a><a href="#stripe-connect">Stripe Connect</a><a href="#iban">IBAN</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="pii" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">PII</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">Personally Identifiable Information — any data that can directly or indirectly identify a specific individual.</p>
|
||||
<p class="term-long">PII encompasses obvious identifiers (name, email, address, IBAN) as well as indirect identifiers that, in combination, could identify someone (GPS traces, device fingerprints, submission patterns). Under GDPR, quiXzoom treats PII with strict controls: it is collected only where necessary, retained only as long as required, and never shared with orderers in identifiable form. Zoomer submissions are delivered to orderers without attached Zoomer identity — orderers receive field data, not person data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When an orderer receives a completed submission, they see the images, GPS coordinates, and timestamp — but not the Zoomer's name, account details, or any identifying information. The Zoomer's identity is pseudonymised in normal operation, with full identification available only under legal process.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#data-controller">Data controller</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="platform-fee" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Platform fee</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The service fee paid by orderers to quiXzoom on top of Zoomer compensation, covering platform operations and AI review.</p>
|
||||
<p class="term-long">The platform fee is charged to the orderer and covers quiXzoom's infrastructure, AI review system, Zoomer management, customer support, and margin. Zoomers receive their full stated mission compensation — the platform fee is paid by the orderer separately and does not come from Zoomer earnings. Platform fees are calculated as a percentage of mission compensation, with enterprise volume pricing available for high-volume orderers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An orderer creates a mission paying the Zoomer €12. quiXzoom's platform fee adds an additional amount on top — the orderer pays the total; the Zoomer receives exactly €12 upon approval. The platform fee structure is transparent and set out in the orderer's service agreement.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#orderer">Orderer</a><a href="#payout">Payout</a><a href="#mission">Mission</a><a href="#sla">SLA</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="premium-mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Premium mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A high-threshold mission type requiring specific Zoomer qualifications and a high approval rate, offering significantly elevated compensation.</p>
|
||||
<p class="term-long">Premium missions are reserved for experienced, high-performing Zoomers. Qualification requires Professional tier (or Active tier with relevant specialisation) and an approval rate above 92%. These missions typically involve technical infrastructure documentation — bridges, power facilities, maritime assets — with precise specification requirements. Compensation for premium missions reflects both the technical difficulty and the high-value use cases they serve, typically ranging from €20 to €40+ per submission.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection premium mission paying €28 appears for a Zoomer with a Maritime specialisation and 96% approval rate. Zoomers without Professional tier or the relevant specialisation do not see this mission in their feed — it is filtered to qualified Zoomers only.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#specialisation">Specialisation</a><a href="#approval-rate">Approval rate</a><a href="#surge-mission">Surge mission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="professional" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Professional</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The highest Zoomer tier — 15+ missions per week, 92%+ approval rate — granting access to all mission types including premium and unrestricted surge.</p>
|
||||
<p class="term-long">Professional tier represents quiXzoom's most engaged and highest-quality Zoomers. Qualification requires sustaining 15+ completed missions per week over the qualifying window, maintaining an approval rate above 92%, and having completed identity verification. Professional tier Zoomers receive priority access to new mission types, higher compensation caps, dedicated support, and early access to specialisation programmes. They form the backbone of supply for high-value, time-critical orderer requests.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A full-time quiXzoom contributor averaging 20 missions/week with a 97% approval rate holds Professional tier. They access premium infrastructure missions paying €25–40, receive surge alerts first, and have the option to take on specialisation certifications for maritime and bridge inspection mission types.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#active">Active</a><a href="#supplementary">Supplementary</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="q">
|
||||
<div class="letter-heading">
|
||||
<h2>Q</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="quality-score" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Quality score</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A composite rating of an observation's technical fitness — sharpness, exposure, framing, and protocol compliance — distinct from the confidence score.</p>
|
||||
<p class="term-long">The Quality Score evaluates the technical and aesthetic properties of submitted media independent of location or metadata verification. It measures image sharpness (absence of motion blur or focus issues), exposure (neither under- nor over-exposed), framing (subject completeness and composition), and protocol compliance (correct angles, required elements visible). Quality Score is a component of the overall Confidence Score but is computed separately to give orderers visibility into the technical standard of their data. Low quality scores trigger coaching for Zoomers and may result in rejection if minimum thresholds are not met.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits photos that are correctly geo-located and within the time window, but two images are slightly blurry due to camera shake. AI review assigns a Quality Score of 62 — below the 75-point threshold — and rejects the submission with 'Image quality: motion blur detected.' The Zoomer receives automated coaching on stabilisation techniques.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#confidence-score">Confidence Score</a><a href="#ai-review">AI review</a><a href="#observation">Observation</a><a href="#approval">Approval</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="quixzoom" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">Global field data collection platform — 'Uber fast för foton'.</p>
|
||||
<p class="term-long">quiXzoom is a standalone product and business with its own brand, separate from AAMOS. It is a marketplace where anyone can take photo missions and earn money. Orderers post missions; Zoomers (anyone) complete them and get paid. quiXzoom uses AAMOS infrastructure under the hood but is never presented as 'AAMOS'. The platform provides verified, geotagged, timestamped field observations on demand.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality needs photos of 50 road segments after a storm. They post missions on quiXzoom. Within 2 hours, local Zoomers have claimed all missions, captured the required photos, and submitted for AI review. The municipality receives verified observations with GPS and timestamps.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#zoomer">Zoomer</a><a href="#mission">Mission</a><a href="#observation">Observation</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="quixzoom-auth-core" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom Auth Core</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Standalone authentication product sold via AAMOS — includes Auth Foundation, KYZ Engine, Company Registry, and Payout Engine.</p>
|
||||
<p class="term-long">quiXzoom Auth Core is a standalone authentication and identity product that can be integrated into any application. It includes: Auth Foundation (email/Google + phone + password), KYZ Engine (Know Your Zoomer — identity verification), Company Registry (sole proprietorship / registered company), and Payout Engine (Stripe Connect, Frilans Finans, bank transfers). Auth Core is sold as a product via AAMOS and is used by quiXzoom and other Landvex products.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A third-party app developer integrates quiXzoom Auth Core to handle user authentication, identity verification, and payouts — without building these complex systems themselves.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="quixzoom-frilans-payout" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom Frilans Payout</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Payout product for freelancers without a company — handles taxes and fees across 8 markets.</p>
|
||||
<p class="term-long">quiXzoom Frilans Payout is a payout product designed for freelancers who don't have a registered company. It operates across 8 markets (SE, NO, DK, FI, DE, NL, US, GB) and automatically handles source tax per country. Features include weekly/monthly payouts, 15% platform fee + 6% processing fee, and automatic tax reporting. The product integrates with quiXzoom Auth Core and uses the Payout Engine.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A freelancer in Sweden uses quiXzoom Frilans Payout to receive payments without registering a company. The system automatically deducts source tax and pays it to Skatteverket, while the freelancer receives their net earnings weekly.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#quixzoom-auth-core">quiXzoom Auth Core</a><a href="#payout">Payout</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="qz-token" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">QZ Token</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">quiXzoom internal token — 1 QZ = 1 USD, used for platform transactions and rewards.</p>
|
||||
<p class="term-long">The QZ Token is quiXzoom's internal transaction token with a fixed exchange rate of 1 QZ = 1 USD. It is not a speculative cryptocurrency — it is a simple ledger entry used for platform transactions, rewards, and internal accounting. QZ Tokens are created when missions are approved and stored in Zoomer accounts. They can be converted to USD payouts or used for platform services.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer earns 50 QZ from completed missions. They can convert these to $50 USD payout or use them to purchase premium features on the platform.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#usd">USD</a><a href="#payout">Payout</a><a href="#quixzoom">quiXzoom</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="r">
|
||||
<div class="letter-heading">
|
||||
<h2>R</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="rating" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Rating</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A Zoomer's accumulated quality score on the platform, reflecting submission quality, consistency, and reliability over time.</p>
|
||||
<p class="term-long">Rating is a composite metric calculated from approval rate, submission volume, claim-to-completion ratio (how often claimed missions are actually submitted), and any policy violations. Rating is displayed as a numerical score and determines mission access filtering — high-rating Zoomers see more mission types, receive surge notifications earlier, and are prioritised for specialisation programme invitations. Unlike approval rate (a rolling 30-day window), rating incorporates a Zoomer's full history, weighted toward recent activity.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer with a 94% approval rate but a poor claim-to-completion ratio (often claiming missions and abandoning them) will have a rating lower than their approval rate alone would suggest. Improving claim reliability raises their rating independently of approval rate.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#approval-rate">Approval rate</a><a href="#tier">Tier</a><a href="#claim">Claim / Claiming</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="reality-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The physical world itself — the assets, infrastructure, and environments that the ecosystem observes, analyses, and optimises.</p>
|
||||
<p class="term-long">The Reality Layer is everything physical: roads, bridges, buildings, coastlines, forests, power lines, water pipes. It is the domain that exists independently of any observation system — the ground truth that the ecosystem seeks to understand and improve. The Reality Layer is not digital; it is the actual world that customers own, manage, insure, and invest in. Every observation is a measurement of the Reality Layer; every index is a summary of its state; every decision is an intervention upon it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A city's Reality Layer comprises 1,200 km of roads, 400 bridges, 50 tunnels, and 2,000 public buildings. The ecosystem's purpose is to create a complete, accurate, up-to-date digital understanding of this Reality Layer — enabling better decisions about maintenance, investment, and risk.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation-layer">Observation Layer</a><a href="#analysis-layer">Analysis Layer</a><a href="#decision-layer">Decision Layer</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="reality-signal" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Signal</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A measurable, verifiable observation that describes a specific aspect of the physical world.</p>
|
||||
<p class="term-long">A Reality Signal is any observation that carries information about the state of physical reality: a photo of a cracked bridge deck, a GPS-tagged image of flood damage, a timestamped record of a building's facade. Reality Signals are the raw inputs to the Analysis Layer. They are distinguished from synthetic or inferred data by their direct connection to physical measurement — a Zoomer was there, the camera captured light from the actual scene, the GPS recorded the actual coordinates. Reality Signals are the antidote to assumptions and desk-based estimates.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurer receives a Reality Signal showing hail damage to a factory roof — captured 6 hours after the storm, with GPS confirming the location, timestamp proving immediacy, and image quality enabling damage severity assessment. This Reality Signal replaces the traditional adjuster visit.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#reality-layer">Reality Layer</a><a href="#confidence-score">Confidence Score</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="rejection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Rejection</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A negative outcome from AI review, indicating a submission does not meet mission requirements — no payout is issued for rejected submissions.</p>
|
||||
<p class="term-long">Rejections occur when AI review identifies one or more disqualifying issues: location mismatch (GPS outside geofence), timestamp violation (submitted outside time window), image quality failure (blurred, overexposed, or heavily occluded), specification miss (required element absent), or EXIF anomaly (GPS data absent or inconsistent). Every rejection includes a specific reason code that the Zoomer can view in-app. Zoomers can review rejection reasons to understand and correct issues on future missions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits 6 photos but one required angle (the drainage outlet) is missing. AI review flags a specification miss and rejects the submission with reason code SPEC_INCOMPLETE. The Zoomer's approval rate decreases by one event, and no payout is issued for this submission.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#approval">Approval</a><a href="#approval-rate">Approval rate</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="right-to-erasure" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Right to erasure</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">A GDPR right allowing individuals to request deletion of their personal data from a platform's systems.</p>
|
||||
<p class="term-long">Under GDPR Article 17, individuals have the right to request erasure of their personal data when it is no longer necessary for the purpose it was collected, when they withdraw consent, or when they object to processing. For quiXzoom, this means Zoomers can request deletion of their account and all associated personal data at any time via the app settings. Certain data may need to be retained for limited periods to satisfy legal obligations (e.g. financial records under tax law) even after an erasure request.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer decides to stop using quiXzoom and requests erasure. quiXzoom deletes their profile, contact data, and GPS history. Some financial transaction records are retained for 7 years as required by EU accounting regulation — this is disclosed in quiXzoom's privacy policy and does not affect the Zoomer's ability to stop using the platform.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#data-controller">Data controller</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="s">
|
||||
<div class="letter-heading">
|
||||
<h2>S</h2>
|
||||
<span class="letter-count">10 terms</span>
|
||||
</div>
|
||||
<article id="s3" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">S3</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Amazon Simple Storage Service — the object storage platform used to store all quiXzoom submission images, securely and at scale.</p>
|
||||
<p class="term-long">S3 (AWS eu-north-1) is quiXzoom's primary file store for submission images. Uploaded images are stored with server-side encryption, access is controlled via IAM policies, and orderers receive time-limited signed URLs to retrieve submission packages — images are never publicly accessible by default. S3's durability (99.999999999%) and scalability make it appropriate for a platform expecting high submission volumes during surge events.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer uploads 6 photos for a mission, they are stored in S3 eu-north-1. When the orderer queries the API for the completed submission, they receive signed URLs valid for 24 hours to download the images — after which the URLs expire and a new API call is required.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-residency">Data residency</a><a href="#api">API</a><a href="#submission">Submission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="sepa" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">SEPA</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Single Euro Payments Area — the European bank transfer network used for EUR payout disbursements to Zoomers.</p>
|
||||
<p class="term-long">SEPA covers 36 European countries and enables fast, low-cost euro bank transfers using IBAN identifiers. SEPA Credit Transfers (SCT) typically settle within 1 business day; SEPA Instant Credit Transfers (SCT Inst) settle in under 10 seconds where supported. quiXzoom uses Stripe Connect's SEPA infrastructure for EUR disbursements to Zoomers in SEPA-member countries. For Zoomers in countries outside SEPA, SWIFT transfers apply, which may have longer settlement windows and additional fees.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Finland has earned €85 across 7 missions. Stripe Connect initiates a SEPA Credit Transfer to their Finnish IBAN — the funds arrive in their bank account within 1 business day at no charge to the Zoomer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#iban">IBAN</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a><a href="#swift-bic">SWIFT/BIC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="sla" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">SLA</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">Service Level Agreement — the delivery timeline and quality commitments quiXzoom makes to orderers, governing mission fulfilment and submission delivery.</p>
|
||||
<p class="term-long">quiXzoom's SLAs define expected fulfilment times (how quickly a claimed mission produces an approved submission), platform uptime commitments, API response time guarantees, and escalation procedures when commitments are not met. SLA terms vary by orderer plan — standard, professional, and enterprise tiers have different guaranteed fulfilment windows. SLA performance is monitored and reported monthly to orderers, with service credits applicable in cases of sustained underperformance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An enterprise orderer's SLA guarantees that 95% of urban missions will produce an approved submission within 4 hours of activation. For surge missions, the SLA commits to a first claim within 30 minutes. These commitments are monitored in real time and reported in the orderer's monthly performance report.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#orderer">Orderer</a><a href="#mission">Mission</a><a href="#surge-mission">Surge mission</a><a href="#api">API</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="specialisation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Specialisation</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A certified competency that unlocks access to specific advanced mission types requiring domain-specific knowledge or technical skill.</p>
|
||||
<p class="term-long">Specialisations are earned through a training and assessment programme administered within the quiXzoom app. Each specialisation covers the technical requirements, safety considerations, and documentation standards for a specific mission domain. Available specialisations include Maritime (marina and harbour documentation), Bridge & Civil (infrastructure inspection), Energy Infrastructure (substations, wind turbines), and Retail Audit. Completing a specialisation assessment unlocks the corresponding premium mission category in the Zoomer's feed.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer living near a large marina completes the Maritime specialisation — a 45-minute in-app training covering mooring documentation, vessel identification standards, and marina facility photography requirements. They now see maritime premium missions paying €20–35 in their area, which are invisible to non-specialised Zoomers.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#premium-mission">Premium mission</a><a href="#tier">Tier</a><a href="#mission-brief">Mission brief</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="stripe" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Stripe</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A global payments platform — quiXzoom's underlying payment infrastructure provider for all Zoomer payouts and orderer billing.</p>
|
||||
<p class="term-long">Stripe is a regulated payment institution used by millions of platforms worldwide. quiXzoom uses two Stripe products: Stripe Payments for orderer billing, and Stripe Connect for Zoomer payout disbursements. Stripe holds regulatory authorisations across the US, EU, and other jurisdictions, which is why AML/KYC compliance requirements flow through Stripe Connect's onboarding process. Stripe's infrastructure provides the payment settlement, fraud detection, and payout mechanics that quiXzoom's marketplace depends on.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer adds their bank account in the quiXzoom app, they are creating a Stripe Connect account under quiXzoom's platform. Stripe is the regulated entity that actually moves money from quiXzoom's orderer receipts to Zoomer IBANs — quiXzoom orchestrates the process but Stripe executes the regulated payment flows.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#stripe-connect">Stripe Connect</a><a href="#kyc">KYC</a><a href="#payout">Payout</a><a href="#iban">IBAN</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="stripe-connect" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Stripe Connect</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Stripe's multi-party payment product that enables quiXzoom to distribute earned mission compensation directly to individual Zoomer bank accounts.</p>
|
||||
<p class="term-long">Stripe Connect is designed specifically for marketplace and platform models where a platform collects money from one party (orderers) and distributes it to another (Zoomers). It handles the regulated aspects of marketplace payments: identity verification (KYC), payout scheduling, tax form collection (where required), currency conversion, and compliance with local financial regulations. Each Zoomer has a Stripe Connect account created during onboarding, linked to their verified bank account.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>During onboarding, a Zoomer completes a Stripe Connect flow: they enter their name, date of birth, address, and IBAN, and complete identity verification. From this point, every approved submission triggers an automatic credit to their Stripe Connect balance, which disburses to their bank account on the configured schedule.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#stripe">Stripe</a><a href="#kyc">KYC</a><a href="#payout">Payout</a><a href="#iban">IBAN</a><a href="#sepa">SEPA</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="submission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Submission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A completed set of photos uploaded by a Zoomer after executing a mission, submitted for AI review and potential payout.</p>
|
||||
<p class="term-long">A submission is the output of a claimed and completed mission. It consists of the required number of geo-tagged images, their EXIF metadata, a GPS trace (if required), and any optional notes from the Zoomer. Submissions are uploaded through the quiXzoom app and enter the AI review pipeline immediately. The submission event locks the mission as completed — a Zoomer cannot resubmit after an initial submission without contacting support. Submission quality directly impacts approval rate and rating.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes a 6-photo road condition survey and taps Submit. The submission package (images, EXIF, GPS trace) is uploaded to S3 and enters AI review. Within 90 seconds, the Zoomer receives an in-app approval notification and their €10 earnings are queued for payout.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#ai-review">AI review</a><a href="#approval">Approval</a><a href="#rejection">Rejection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="supplementary" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Supplementary</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The entry-level Zoomer tier — 2–4 missions per week — for contributors using quiXzoom as occasional supplemental income.</p>
|
||||
<p class="term-long">Supplementary tier is the starting tier for all new Zoomers. It provides access to standard missions in the Zoomer's zone, with no minimum weekly commitment. Supplementary Zoomers earn the standard mission rates and can access surge missions in their area. To progress to Active tier, a Zoomer must demonstrate sustained volume (8+ missions/week) and maintain an approval rate above 85% over a qualifying period.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A gig worker uses quiXzoom alongside their other activities — completing 3 missions per week in their neighbourhood while walking their dog or commuting. At Supplementary tier, they access standard missions with no pressure to increase volume; their €30–40/week in earnings is a useful addition to their income mix.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#active">Active</a><a href="#professional">Professional</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="surge-mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Surge mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">High-urgency missions deployed after acute events — storms, floods, accidents — offering 2–5× standard compensation for rapid on-site documentation.</p>
|
||||
<p class="term-long">Surge missions are created by orderers (typically insurers or infrastructure managers) in response to time-critical events requiring rapid field documentation. They carry elevated compensation to incentivise Zoomers to prioritise them and accept shorter time windows. Surge alerts are pushed as priority notifications to all Zoomers in the affected zone, with Professional tier Zoomers notified first. Surge missions typically have tighter specification requirements and stricter AI review thresholds given their legal and claims significance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A severe storm hits coastal Sweden. An insurer activates 40 surge missions across 12 postcodes within 20 minutes of the event. Zoomers in those zones receive priority push notifications — the missions pay €35 each (vs. €12 standard) with a 3-hour time window. 38 of 40 missions are claimed within 45 minutes.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#premium-mission">Premium mission</a><a href="#mission">Mission</a><a href="#tier">Tier</a><a href="#sla">SLA</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="swift-bic" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">SWIFT/BIC</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Society for Worldwide Interbank Financial Telecommunication / Bank Identifier Code — used for international bank transfers outside the SEPA zone.</p>
|
||||
<p class="term-long">SWIFT (the network) and BIC (the identifier standard) together enable international bank-to-bank transfers for currencies and countries outside SEPA. Zoomers in non-SEPA countries (e.g. the UK post-Brexit for GBP, or non-EU markets quiXzoom may expand to) require a SWIFT/BIC code in addition to their account number for payout setup. SWIFT transfers typically settle in 1–5 business days and may incur intermediary bank fees — terms disclosed to Zoomers during onboarding.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Norway (SEPA member) uses IBAN/SEPA for payouts. A Zoomer in the UK (non-SEPA) provides their IBAN and SWIFT/BIC during onboarding — Stripe Connect routes their payout via SWIFT, with a 2–3 business day settlement window.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#sepa">SEPA</a><a href="#iban">IBAN</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="t">
|
||||
<div class="letter-heading">
|
||||
<h2>T</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="tier" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Tier</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A Zoomer's platform level — Supplementary, Active, or Professional — reflecting activity volume and quality, and determining mission access.</p>
|
||||
<p class="term-long">The tier system is quiXzoom's primary mechanism for matching mission complexity and compensation to Zoomer reliability. Higher tiers require more submissions per week and higher approval rates; in return, they unlock premium missions, higher compensation caps, priority surge notifications, and specialisation programmes. Tier is calculated on a rolling basis — a Zoomer can move up by improving performance, or drop if activity or quality falls below threshold for a sustained period.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer consistently completing 10 missions/week with a 90% approval rate qualifies for Active tier after 4 qualifying weeks. They now see 30% more missions in their feed and are eligible to apply for a specialisation programme — their per-week earning potential roughly doubles compared to Supplementary.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#supplementary">Supplementary</a><a href="#active">Active</a><a href="#professional">Professional</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="time-window" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Time window</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The duration a Zoomer has to complete and submit a mission after claiming it — after which the mission auto-releases back to the pool.</p>
|
||||
<p class="term-long">Time windows are set per mission type and range from 1 hour (urgent surge missions in dense urban areas) to 24 hours (rural or low-urgency surveys). The clock starts when the Zoomer claims the mission. If no submission is received before the window expires, the mission is automatically un-claimed and becomes available to other Zoomers. Frequent time window expiries (claiming without submitting) negatively affect a Zoomer's rating and may trigger temporary claiming restrictions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A storm damage survey mission has a 4-hour time window. A Zoomer claims it at 10:00. They have until 14:00 to travel to the location, photograph the damage, and submit. At 13:58, they upload the final photo — 2 minutes before expiry. Submission is accepted; time window is satisfied.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#claim">Claim / Claiming</a><a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#surge-mission">Surge mission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="timestamp" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Timestamp</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The precise date and time recorded in a photo's EXIF metadata, proving when the image was captured.</p>
|
||||
<p class="term-long">Timestamps are a critical element of quiXzoom's chain-of-custody system. The EXIF timestamp records the device's date and time at the moment of capture, and is cross-validated by AI review against the mission's claimed time window. For legal and insurance use cases, the timestamp (combined with GPS data) provides tamper-evident proof that the documentation was made at the right place at the right time. quiXzoom also records server-side ingestion timestamps for each submission to supplement device-side EXIF data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurer requires flood documentation captured within 6 hours of a storm event for their claims validity window. The EXIF timestamp on each submitted photo, cross-referenced with server ingestion time, provides the evidence that the documentation falls within the required window — suitable for claims processing and, if necessary, legal proceedings.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#exif">EXIF</a><a href="#time-window">Time window</a><a href="#geo-tagged">Geo-tagged</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="u">
|
||||
<div class="letter-heading">
|
||||
<h2>U</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="usd" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">USD</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">United States Dollar — the primary currency used in quiXzoom platform and Landvex products.</p>
|
||||
<p class="term-long">USD is the main currency throughout the quiXzoom platform and Landvex ecosystem. All customer-facing pricing, payouts, and product fees are denominated in USD (or EUR where specified). This is a locked policy — SEK is never used in customer-facing copy, sites, documents, or communication. The only exception is LandveX AB's internal Swedish accounting.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A mission pays $15 (USD). A Zoomer's earnings are displayed in USD. Landvex enterprise contracts are priced in USD. This is consistent across all customer touchpoints.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#eur">EUR</a><a href="#payout">Payout</a><a href="#platform-fee">Platform fee</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="v">
|
||||
<div class="letter-heading">
|
||||
<h2>V</h2>
|
||||
<span class="letter-count">2 terms</span>
|
||||
</div>
|
||||
<article id="vat" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">VAT</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Value Added Tax — Zoomers are responsible for their own VAT obligations where applicable under local tax law.</p>
|
||||
<p class="term-long">VAT treatment of gig platform income varies by jurisdiction and depends on the Zoomer's status (individual, self-employed, VAT-registered business) and the total income thresholds in their country. In most EU countries, Zoomers earning below the VAT registration threshold are not required to charge or remit VAT. quiXzoom provides transaction records suitable for tax reporting but does not provide tax advice — Zoomers should consult their local tax authority or advisor for their specific obligations. For orderers, quiXzoom's service fees are subject to standard B2B VAT rules.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Swedish Zoomer earning €8,000/year from quiXzoom (below Sweden's VAT threshold of ~€32,000 for small businesses) is not required to register for or charge VAT. A Zoomer earning above threshold must register, charge VAT on their services, and remit to Skatteverket — quiXzoom's annual earnings summary facilitates this reporting.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#payout">Payout</a><a href="#stripe-connect">Stripe Connect</a><a href="#w9-w8ben">W-9 / W-8BEN</a><a href="#1099-k">1099-K</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="verified-contributor" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Verified contributor</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A Zoomer who has completed identity verification (KYC) and maintains an active, good-standing account — eligible for payouts and premium missions.</p>
|
||||
<p class="term-long">A verified contributor is a Zoomer who has passed the platform's trust threshold: their identity has been confirmed through government-issued ID and liveness check, their bank account is linked via Stripe Connect, and their account is in good standing (not suspended or restricted). Verification is a one-time process, but good standing is maintained through consistent quality (approval rate above threshold) and compliance with platform policies. Only verified contributors can receive payouts and access Professional-tier missions. Verification status is displayed in the Zoomer's profile.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A new Zoomer completes 5 missions and earns €45. Before they can receive their first payout, they must become a verified contributor by completing KYC. Once verified, their status shows a green checkmark in-app, and they can withdraw earnings and claim premium missions.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#identity-verification">Identity verification</a><a href="#zoomer">Zoomer</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="w">
|
||||
<div class="letter-heading">
|
||||
<h2>W</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="w9-w8ben" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">W-9 / W-8BEN</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">US IRS tax forms collected by payment platforms from payees to determine tax withholding obligations for US-source income.</p>
|
||||
<p class="term-long">W-9 is completed by US persons (certifying their Tax Identification Number). W-8BEN is completed by non-US individuals certifying their foreign status and claiming any applicable tax treaty benefits. Stripe Connect collects these forms as part of its US regulatory compliance. For Zoomers in the EU, W-8BEN confirms they are not subject to US tax withholding on quiXzoom earnings. This is collected automatically during Stripe Connect onboarding for Zoomers in countries where Stripe requires it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A German Zoomer completing Stripe Connect onboarding is prompted to complete a W-8BEN form (takes ~2 minutes). This certifies they are a non-US person and exempts them from US withholding tax on their quiXzoom earnings — as their income is EU-source and subject to German tax law, not US.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#1099-k">1099-K</a><a href="#stripe-connect">Stripe Connect</a><a href="#vat">VAT</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="waitlist" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Waitlist</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The pre-launch registration list for Zoomers and orderers to secure early access when quiXzoom opens in their region.</p>
|
||||
<p class="term-long">The quiXzoom waitlist allows interested Zoomers and orderers to register before the platform launches in their area. Waitlist registrants receive priority onboarding invitations, early-access mission allocations, and launch communications. For Zoomers, waitlist sign-up takes under 60 seconds and requires only basic contact information — full onboarding (identity verification, bank account) is completed when access is granted. The waitlist helps quiXzoom manage geographic launch sequencing and ensure supply matches demand at launch.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>quiXzoom is launching in August 2026. Zoomers who register on the waitlist before launch receive an early-access invitation 2 weeks before public opening in their city, allowing them to complete onboarding and be mission-ready on day one.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#zoomer">Zoomer</a><a href="#mission">Mission</a><a href="#orderer">Orderer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="webhook" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Webhook</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An automatic HTTP POST notification sent by quiXzoom to an orderer's system when a defined event occurs — typically submission approval.</p>
|
||||
<p class="term-long">Webhooks enable real-time integration between quiXzoom and orderer systems without polling. When a submission is approved (or rejected, or a mission is created), quiXzoom sends a JSON payload to the orderer's configured webhook URL. The payload includes the event type, mission ID, submission ID, GPS coordinates, approval status, and image download URLs. Orderers must verify webhook authenticity using HMAC-SHA256 signature verification. Undelivered webhooks are retried with exponential backoff over 24 hours.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's claims system has a quiXzoom webhook endpoint. When a flood damage submission is approved, quiXzoom sends a POST request within seconds. The claims system receives the event, automatically attaches the images to the open claim, and updates the claim status to 'documented' — with no manual intervention required.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#hmac-sha256">HMAC-SHA256</a><a href="#json">JSON</a><a href="#approval">Approval</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="z">
|
||||
<div class="letter-heading">
|
||||
<h2>Z</h2>
|
||||
<span class="letter-count">2 terms</span>
|
||||
</div>
|
||||
<article id="zone" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Zone</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The geographic radius a Zoomer sets as their operational area, determining which missions appear in their mission feed.</p>
|
||||
<p class="term-long">Each Zoomer configures one or more zones — defined as a radius around a point (their home, workplace, or preferred operating area). The quiXzoom app displays missions within the Zoomer's active zone. Zoomers can set multiple zones, adjust zone radius, and switch between zones as needed. Zone configuration is used by quiXzoom to target mission notifications — if a surge mission is activated within a Zoomer's zone, they are alerted immediately. Zones do not restrict where a Zoomer can physically travel; they filter the mission feed for relevance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer sets a 5km zone around their home in Göteborg and a 3km zone around their office. They see missions within both zones in their feed. On a day when they're travelling to Malmö, they temporarily set an additional zone there to pick up missions during their visit.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission-density">Mission density</a><a href="#mission">Mission</a><a href="#surge-mission">Surge mission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="zoomer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Zoomer</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A verified field data collector on the quiXzoom platform — an individual who claims missions, captures on-location photography, and earns compensation per approved submission.</p>
|
||||
<p class="term-long">Zoomers are the supply side of the quiXzoom marketplace. Anyone with a compatible smartphone, a willingness to be verified (KYC), and a linked bank account can become a Zoomer. Zoomers work independently, on their own schedule, within their chosen zone. They earn per approved submission — there is no hourly pay, no minimum hours, and no obligation to work any particular number of missions. Zoomers progress through tiers (Supplementary → Active → Professional) as they build volume and quality.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A freelance photographer becomes a quiXzoom Zoomer, completing identity verification and bank account setup in 10 minutes. They begin claiming road survey and building inspection missions near their home, earning €8–15 per approved submission. Within 6 weeks, their consistent quality and volume qualify them for Active tier.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#tier">Tier</a><a href="#approval-rate">Approval rate</a><a href="#kyc">KYC</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<div class="last-updated">Last updated: July 14, 2026</div>
|
||||
</main>
|
||||
<footer style="background:#0d0d10;border-top:1px solid rgba(255,255,255,.07);padding:32px 24px;margin-top:48px">
|
||||
<div style="max-width:1080px;margin:0 auto;display:flex;align-items:center;justify-content:space-between;flex-wrap:wrap;gap:16px">
|
||||
<a href="/" style="font-size:1.1rem;font-weight:800;color:#fff;letter-spacing:-.03em;text-decoration:none">qui<span style="color:#3b82f6">X</span>zoom</a>
|
||||
<p style="font-size:.8125rem;color:rgba(255,255,255,.75);margin:0">© 2026 Landvex Inc</p>
|
||||
</div>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
Vendored
+1850
@@ -0,0 +1,1850 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Glossary — Landvex Ecosystem</title>
|
||||
<meta name="description" content="Every term used on all. Defined precisely and kept current.">
|
||||
<link rel="canonical" href="https://www.quixzoom.com/glossary">
|
||||
<meta name="robots" content="index, follow">
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "DefinedTermSet",
|
||||
"name": "all Glossary",
|
||||
"description": "Complete glossary of terms",
|
||||
"publisher": {"@type": "Organization", "name": "Landvex Inc", "url": "https://www.landvex.com"}
|
||||
}
|
||||
</script>
|
||||
<style>*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
|
||||
:root {
|
||||
--bg: #ffffff; --bg-off: #f5f5f7; --bg-card: #ffffff;
|
||||
--text: #1d1d1f; --text-secondary: #6e6e73;
|
||||
--blue: #0066FF; --blue-light: #e8f0ff;
|
||||
--green: #00a550; --green-light: #e6f7ee;
|
||||
--purple: #7b2fff; --purple-light: #f0e8ff;
|
||||
--orange: #e8660a; --orange-light: #fff0e6;
|
||||
--pink: #ff3366; --pink-light: #ffe8f0;
|
||||
--radius: 18px; --radius-sm: 8px; --border: #d2d2d7;
|
||||
--nav-height: 64px; --shadow-hover: 0 12px 40px rgba(0,0,0,.10);
|
||||
}
|
||||
@media (prefers-color-scheme: dark) {
|
||||
:root {
|
||||
--bg: #000000; --bg-off: #1c1c1e; --bg-card: #1c1c1e;
|
||||
--text: #f5f5f7; --text-secondary: #98989f; --border: #3a3a3c;
|
||||
--blue-light: rgba(0,102,255,.15); --green-light: rgba(0,165,80,.15);
|
||||
--purple-light: rgba(123,47,255,.15); --orange-light: rgba(232,102,10,.15);
|
||||
--pink-light: rgba(255,51,102,.15); --shadow-hover: 0 12px 40px rgba(0,0,0,.5);
|
||||
}
|
||||
}
|
||||
html { scroll-behavior: smooth; }
|
||||
body {
|
||||
font-family: -apple-system, BlinkMacSystemFont, 'SF Pro Display', 'SF Pro Text', 'Helvetica Neue', Arial, sans-serif;
|
||||
background: var(--bg); color: var(--text); line-height: 1.6; -webkit-font-smoothing: antialiased;
|
||||
}
|
||||
.nav {
|
||||
position: sticky; top: 0; z-index: 100; height: var(--nav-height);
|
||||
background: rgba(255,255,255,.82); -webkit-backdrop-filter: blur(20px) saturate(180%);
|
||||
backdrop-filter: blur(20px) saturate(180%); border-bottom: 1px solid var(--border);
|
||||
display: flex; align-items: center; gap: 16px; padding: 0 24px;
|
||||
}
|
||||
@media (prefers-color-scheme: dark) { .nav { background: rgba(0,0,0,.82); } }
|
||||
.nav-logo { font-size: 1.25rem; font-weight: 800; color: var(--text); text-decoration: none; letter-spacing: -.04em; white-space: nowrap; flex-shrink: 0; }
|
||||
.nav-logo .x { color: var(--blue); }
|
||||
.nav-divider { width: 1px; height: 20px; background: var(--border); flex-shrink: 0; }
|
||||
.nav-title { font-size: .9375rem; font-weight: 600; color: var(--text-secondary); white-space: nowrap; flex-shrink: 0; }
|
||||
main { max-width: 860px; margin: 0 auto; padding: 0 24px 80px; }
|
||||
.page-header { padding: 64px 0 48px; text-align: center; }
|
||||
.page-header h1 { font-size: clamp(2.5rem, 6vw, 4rem); font-weight: 800; letter-spacing: -.04em; line-height: 1.05; color: var(--text); margin-bottom: 16px; }
|
||||
.page-header p { font-size: 1.125rem; color: var(--text-secondary); max-width: 480px; margin: 0 auto; }
|
||||
.letter-section { margin-bottom: 48px; }
|
||||
.letter-heading { display: flex; align-items: center; gap: 16px; margin-bottom: 20px; padding-bottom: 12px; border-bottom: 1px solid var(--border); }
|
||||
.letter-heading h2 { font-size: 2rem; font-weight: 800; color: var(--text-secondary); letter-spacing: -.04em; line-height: 1; width: 36px; flex-shrink: 0; }
|
||||
.letter-count { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-card { background: var(--bg-card); border: 1px solid var(--border); border-radius: var(--radius); padding: 28px 32px; margin-bottom: 16px; transition: box-shadow .2s, transform .2s; }
|
||||
.term-card:hover { box-shadow: var(--shadow-hover); transform: translateY(-2px); }
|
||||
.term-header { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; margin-bottom: 10px; flex-wrap: wrap; }
|
||||
.term-name { font-size: 1.3125rem; font-weight: 700; color: var(--text); letter-spacing: -.02em; line-height: 1.2; }
|
||||
.term-category { display: inline-block; padding: 4px 12px; border-radius: 20px; font-size: .75rem; font-weight: 600; letter-spacing: .02em; text-transform: uppercase; white-space: nowrap; flex-shrink: 0; margin-top: 2px; }
|
||||
.cat-platform { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-technical { background: var(--green-light); color: var(--green); }
|
||||
.cat-payment { background: var(--purple-light); color: var(--purple); }
|
||||
.cat-legal { background: var(--orange-light); color: var(--orange); }
|
||||
.cat-core { background: var(--bg-off); color: var(--text-secondary); }
|
||||
.cat-amos { background: var(--pink-light); color: var(--pink); }
|
||||
.cat-landvex { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-quixzoom { background: var(--green-light); color: var(--green); }
|
||||
.cat-product { background: var(--orange-light); color: var(--orange); }
|
||||
.term-short { font-size: 1rem; font-weight: 500; color: var(--text); margin-bottom: 12px; line-height: 1.5; }
|
||||
.term-long { font-size: .9375rem; color: var(--text-secondary); line-height: 1.65; margin-bottom: 16px; }
|
||||
.term-context { background: var(--bg-off); border-radius: var(--radius-sm); padding: 14px 18px; margin-bottom: 14px; }
|
||||
.term-context-label { font-size: .75rem; font-weight: 700; text-transform: uppercase; letter-spacing: .06em; color: var(--blue); display: block; margin-bottom: 6px; }
|
||||
.term-context p { font-size: .875rem; color: var(--text-secondary); line-height: 1.6; }
|
||||
.term-related { display: flex; align-items: center; flex-wrap: wrap; gap: 6px; }
|
||||
.term-related > span { font-size: .8125rem; color: var(--text-secondary); }
|
||||
.term-related a { display: inline-block; padding: 3px 10px; border-radius: 20px; font-size: .8125rem; font-weight: 500; color: var(--blue); background: var(--blue-light); text-decoration: none; transition: background .12s, color .12s; }
|
||||
.term-related a:hover { background: var(--blue); color: #fff; }
|
||||
.last-updated { text-align: center; font-size: .8125rem; color: var(--text-secondary); margin-top: 48px; padding-top: 24px; border-top: 1px solid var(--border); }
|
||||
.term-card:target { border-color: var(--blue); box-shadow: 0 0 0 3px rgba(0,102,255,.15); }
|
||||
@media (max-width: 600px) { .nav { gap: 10px; padding: 0 16px; } .term-card { padding: 20px 18px; } .page-header { padding: 40px 0 32px; } }
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<nav class="nav">
|
||||
<a href="/" class="nav-logo">qui<span class="x">X</span>zoom</a>
|
||||
<div class="nav-divider"></div>
|
||||
<span class="nav-title">Glossary</span>
|
||||
</nav>
|
||||
<main>
|
||||
<header class="page-header">
|
||||
<h1>Every term.<br>Defined.</h1>
|
||||
<p>The complete all reference — from field observations to decision intelligence.</p>
|
||||
</header>
|
||||
<section class="letter-section" id="1">
|
||||
<div class="letter-heading">
|
||||
<h2>1</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="1099-k" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">1099-K</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A US tax document issued by payment platforms to payees who exceed IRS reporting thresholds for payments received through the platform.</p>
|
||||
<p class="term-long">Form 1099-K is issued by payment processors like Stripe to US persons who receive above the IRS reporting threshold (currently $600 per year under new IRS rules, though thresholds may vary). For quiXzoom Zoomers who are US persons, a 1099-K may be issued by Stripe for their annual earnings. Non-US Zoomers (who have completed a W-8BEN) are not subject to 1099-K reporting. Zoomers should retain their quiXzoom earnings summaries for local tax reporting regardless of 1099-K status.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A US-based Zoomer earning $1,200 from quiXzoom missions in a calendar year will receive a 1099-K from Stripe by January 31 of the following year. This document reports their platform earnings to the IRS and should be used when filing their annual tax return.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#w9-w8ben">W-9 / W-8BEN</a><a href="#stripe-connect">Stripe Connect</a><a href="#vat">VAT</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="a">
|
||||
<div class="letter-heading">
|
||||
<h2>A</h2>
|
||||
<span class="letter-count">20 terms</span>
|
||||
</div>
|
||||
<article id="active" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Active</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The middle Zoomer tier — 8–12 missions per week with 85%+ approval rate — balancing flexibility with consistent engagement.</p>
|
||||
<p class="term-long">Active tier represents Zoomers who use quiXzoom as a regular supplemental income source. To qualify, a Zoomer must sustain 8+ completed missions per week and maintain an approval rate above 85% over the qualifying window. Active Zoomers access a broader mission pool than Supplementary tier, including most premium mission types and higher-paying specialisation missions. Active tier is the threshold for most specialisation programme eligibility.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A part-time Zoomer completes 10 missions/week around their regular job, maintaining a 91% approval rate. At Active tier, they access infrastructure survey missions (€15–20) that are invisible to Supplementary Zoomers, and have applied for the Bridge & Civil specialisation programme.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#supplementary">Supplementary</a><a href="#professional">Professional</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="ai-review" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AI review</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Automated quality and specification check run on every submission before payment is triggered.</p>
|
||||
<p class="term-long">AI review is the first gate a submitted set of photos passes through. The system checks geo-accuracy (is the submission within the mission geofence?), image quality (sharpness, exposure, occlusion), specification compliance (correct angles, required elements present), and EXIF integrity (timestamp within time window, GPS data present and consistent). The result is either an approval — triggering payout — or a rejection with a reason code that the Zoomer can act on.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits 6 photos of a road segment. AI review verifies GPS coordinates match the mission location, timestamp falls within the claimed time window, and all required vantage points are covered — typically completing within 90 seconds of upload.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#approval">Approval</a><a href="#rejection">Rejection</a><a href="#submission">Submission</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="aml" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AML</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">Anti-Money Laundering — the regulatory framework that requires payment platforms to verify the identity of anyone receiving funds.</p>
|
||||
<p class="term-long">AML regulation obliges financial institutions and payment platforms to implement controls that prevent the platform from being used to launder illegally obtained money. In practice, this means platforms like Stripe — which powers quiXzoom's payouts — must verify Zoomer identity (KYC) before processing disbursements. AML requirements vary by jurisdiction but are broadly harmonised across the EU under the Anti-Money Laundering Directives (AMLD).</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Before a Zoomer can receive their first payout, they must complete KYC. This is not a quiXzoom policy choice — it is a legal obligation on Stripe (our payment provider) under AML regulation. The process is a one-time requirement.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#identity-verification">Identity verification</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Adaptive Autonomous Multi-Agent Operating System — the AI capability platform that powers Landvex intelligence products.</p>
|
||||
<p class="term-long">AMOS is not an AI system. It is an AI Capability Platform — a suite of specialised engines that process observations into structured intelligence. AMOS ingests raw field data from quiXzoom, applies computer vision, pattern recognition, and cross-referencing, and produces outputs: indices, scores, change flags, and predictive signals. AMOS is the analytical layer between reality and decisions. It is developed and sold by Landvex Inc, Houston, TX.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>quiXzoom collects 12,000 observations of bridge conditions across Sweden. AMOS processes these into an Infrastructure Risk Index — a single score per bridge that maintenance planners can prioritise by.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#index">Index</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#amos-vision">AMOS Vision</a><a href="#amos-identity">AMOS Identity</a><a href="#amos-fraud">AMOS Fraud</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-change-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Change Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Detects changes between observations over time.</p>
|
||||
<p class="term-long">The AMOS Change Engine compares current observations against historical baselines to identify additions, removals, and modifications. It powers change detection at scale, enabling proactive maintenance and early problem identification. The engine operates across multiple time scales from hours to years.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A property manager receives a quarterly change report showing that 3 buildings have new roof damage, 2 have added unauthorized structures, and 1 has removed safety equipment — all flagged automatically by the Change Engine.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#change-detection">Change detection</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-compliance" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Compliance</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Regulatory control, documentation verification, and compliance checking engine.</p>
|
||||
<p class="term-long">AMOS Compliance verifies that assets, processes, and documentation meet regulatory requirements. It checks for required signage, accessibility features, fire safety equipment, and other compliance markers. The engine maintains up-to-date regulatory rule sets for multiple jurisdictions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A retail chain uses AMOS Compliance to verify that all 200 stores meet accessibility requirements. The engine has flagged 15 stores missing required wheelchair ramps and 8 stores with inadequate emergency lighting.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-inspection">AMOS Inspection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-evidence-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Evidence Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Creates traceable evidence chains for audit, insurance, and legal proceedings.</p>
|
||||
<p class="term-long">The AMOS Evidence Engine maintains an immutable, auditable chain of custody for every observation. It records capture metadata, processing history, analysis results, and access logs in a tamper-evident format suitable for legal admissibility. Evidence packages include cryptographic hashes and timestamps.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>An insurance dispute reaches court. The AMOS Evidence Engine produces a complete evidence package showing: when the observation was captured, by which device, with what GPS accuracy, what AI analysis was performed, and who accessed the data — all cryptographically signed.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#exif">EXIF</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-fraud" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Fraud</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Skimming detection, manipulated ATM/utility meter detection, and insurance fraud prevention engine.</p>
|
||||
<p class="term-long">AMOS Fraud detects fraudulent manipulation of physical devices and systems. It identifies skimming devices on ATMs, tampered utility meters, falsified insurance claims, and other physical fraud vectors. The engine combines visual analysis with pattern matching against known fraud signatures.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A bank receives a quiXzoom observation of an ATM showing a suspicious card reader attachment. AMOS Fraud analyses the image, compares against known skimming device patterns, and flags a high-probability fraud alert within seconds.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-identity" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Identity</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Identity verification, document control, liveness detection, and fraud prevention engine.</p>
|
||||
<p class="term-long">AMOS Identity verifies that a person is who they claim to be. It processes government-issued IDs, performs liveness checks, and detects document tampering or synthetic identity fraud. The engine is used for KYC processes, access control, and high-trust verification scenarios.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes identity verification by submitting their passport and a selfie. AMOS Identity verifies the document's authenticity and matches the selfie to the ID photo with 99.7% accuracy.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#liveness-check">Liveness check</a><a href="#identity-verification">Identity verification</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-infrastructure" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Infrastructure</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Road, bridge, pole, sign, and property condition monitoring engine.</p>
|
||||
<p class="term-long">AMOS Infrastructure monitors the built environment: roads, bridges, utility poles, traffic signs, buildings, and other fixed assets. It detects deterioration, damage, and changes over time, producing condition indices and maintenance prioritisation scores. The engine is the core capability behind Landvex's infrastructure intelligence products.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality receives monthly Infrastructure Condition Index updates for all 400 bridges in their county. AMOS Infrastructure has flagged 12 bridges showing progressive deterioration that requires inspection within 30 days.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#index">Index</a><a href="#change-detection">Change detection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-inspection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Inspection</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">General quality control and industrial inspection engine.</p>
|
||||
<p class="term-long">AMOS Inspection provides general-purpose quality control and inspection capabilities for industrial applications. It detects manufacturing defects, assembly errors, and quality deviations from specification. The engine is configurable for specific industry standards and can be trained on custom defect libraries.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A manufacturer uses AMOS Inspection to quality-check 10,000 units per day. The engine detects surface scratches, dimensional deviations, and colour mismatches with 99.2% accuracy, reducing manual inspection workload by 80%.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a><a href="#quality-score">Quality score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-prediction-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Prediction Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Estimates likely future development based on current observations and historical patterns.</p>
|
||||
<p class="term-long">The AMOS Prediction Engine uses historical data, environmental factors, and deterioration models to forecast future asset conditions. It estimates remaining useful life, predicts failure probabilities, and identifies optimal intervention timing. Predictions include confidence intervals and are updated as new observations arrive.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>AMOS Prediction Engine forecasts that Bridge 247 will reach critical condition (Index below 40) in 18 months based on current deterioration rate and traffic load. The recommendation: schedule major maintenance within 12 months to avoid emergency closure.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#index">Index</a><a href="#amos-risk-engine">AMOS Risk Engine</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-reality-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Reality Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Verifies that an image shows actual reality, not manipulated or synthetic content.</p>
|
||||
<p class="term-long">The AMOS Reality Engine detects image manipulation, deepfakes, and synthetic content. It analyses EXIF data, pixel-level artifacts, and lighting consistency to verify that an observation depicts real physical reality. This is critical for legal admissibility and insurance validity.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>An insurance claim includes photos of storm damage. The AMOS Reality Engine verifies that the images are authentic, unmanipulated, and captured at the claimed location and time — providing the foundation for claims processing.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#exif">EXIF</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-risk-engine" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Risk Engine</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Converts observations into risk scores and prioritisation rankings.</p>
|
||||
<p class="term-long">The AMOS Risk Engine transforms raw observations into actionable risk assessments. It combines condition data, environmental factors, historical failure rates, and consequence analysis to produce risk scores that prioritise maintenance and intervention. Risk scores are normalised and comparable across asset types and geographies.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A county's 400 bridges are ranked by risk score. The top 10 highest-risk bridges (scores above 85) receive immediate inspection orders, while the bottom 200 (scores below 30) are scheduled for routine maintenance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#index">Index</a><a href="#confidence-score">Confidence Score</a><a href="#decision-intelligence">Decision Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-safety" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Safety</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">PPE detection, workplace hazard identification, and risk assessment engine.</p>
|
||||
<p class="term-long">AMOS Safety analyses visual data to detect personal protective equipment (PPE) compliance, identify workplace hazards, and assess safety risks. It can detect missing hard hats, unsafe scaffolding, blocked emergency exits, and other safety violations from standard photographs.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A construction site manager receives daily safety observations from quiXzoom. AMOS Safety has flagged 3 instances of missing fall protection and 1 blocked fire exit across 50 observations — enabling immediate corrective action.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#amos-vision">AMOS Vision</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="amos-vision" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">AMOS Vision</h3>
|
||||
<span class="term-category cat-amos">AMOS Engine</span>
|
||||
</div>
|
||||
<p class="term-short">Object recognition, anomaly detection, and damage assessment engine.</p>
|
||||
<p class="term-long">AMOS Vision is the computer vision engine that identifies objects, detects anomalies, and assesses damage in visual data. It powers infrastructure inspection, property condition monitoring, and safety compliance checking. The engine can detect cracks, corrosion, vegetation encroachment, and other physical defects from standard photographs.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In AMOS</span>
|
||||
<p>A bridge inspection observation shows surface cracking. AMOS Vision measures crack width, length, and pattern, comparing against historical data to determine if the damage is new or progressive.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#change-detection">Change detection</a><a href="#amos-infrastructure">AMOS Infrastructure</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="analysis-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Analysis Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The processing tier where raw observations are transformed into structured intelligence by AMOS.</p>
|
||||
<p class="term-long">The Analysis Layer sits between the Observation Layer and the Decision Layer. Here, AMOS ingests verified field observations and applies analytical models: object detection, condition scoring, change analysis, pattern recognition, and anomaly detection. The outputs are normalised indices, confidence scores, and contradiction flags. The Analysis Layer is where data becomes insight — where thousands of individual observations are synthesised into coherent, actionable intelligence.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A thousand roof observations from across a property portfolio enter the Analysis Layer. AMOS identifies that 8% show hail damage, 2% have gutter degradation, and 90% are unchanged. The Analysis Layer outputs a Property Condition Index with regional breakdowns and recommended inspection priorities.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation-layer">Observation Layer</a><a href="#decision-layer">Decision Layer</a><a href="#reality-layer">Reality Layer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="api" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">API</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Application Programming Interface — the programmatic interface through which orderers access mission data, submission results, and platform services.</p>
|
||||
<p class="term-long">The quiXzoom API is a REST-style HTTP API that allows orderers to submit mission briefs, monitor mission status, retrieve completed submission packages (images, metadata, GeoJSON), and receive real-time updates via webhooks. Responses are in JSON format. The API uses OAuth 2.0 for authentication and HMAC-SHA256 for webhook signature verification.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company integrates the quiXzoom API into their claims management system. When a claim is filed for a specific address, an API call automatically creates a mission, and approved submission data flows directly back into the claims system without manual intervention.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#webhook">Webhook</a><a href="#oauth">OAuth</a><a href="#json">JSON</a><a href="#hmac-sha256">HMAC-SHA256</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="approval" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Approval</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A positive outcome from AI review, confirming a submission meets all mission requirements and triggering Zoomer payout.</p>
|
||||
<p class="term-long">When AI review determines that a submission satisfies all specification, quality, and location requirements for a mission, the submission is marked as Approved. This event is the trigger for payout to the Zoomer and for delivery of the submission package to the orderer. Approval also counts positively toward the Zoomer's approval rate and rating.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits a marina documentation mission. AI review approves the submission within 2 minutes; the Zoomer sees a confirmation in-app and their €12 earnings are queued for the next payout cycle. The orderer receives the submission package via webhook.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#rejection">Rejection</a><a href="#approval-rate">Approval rate</a><a href="#ai-review">AI review</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="approval-rate" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Approval rate</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The percentage of submitted missions that pass AI review, calculated over a rolling 30-day window.</p>
|
||||
<p class="term-long">Approval rate is the primary quality signal on the quiXzoom platform. It is calculated as approved submissions divided by total submissions over the preceding 30 days. A Zoomer's approval rate directly determines their tier eligibility and access to premium and surge missions. Professional tier requires maintaining above 92% approval; Active tier requires above 85%. Zoomers below 70% receive coaching and may be temporarily restricted from claiming new missions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer with 38 approvals and 2 rejections out of 40 submissions in the last 30 days has a 95% approval rate. This qualifies them for Professional tier and unlocks access to premium infrastructure missions paying up to €30 per submission.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#rejection">Rejection</a><a href="#tier">Tier</a><a href="#premium-mission">Premium mission</a><a href="#rating">Rating</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="c">
|
||||
<div class="letter-heading">
|
||||
<h2>C</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="change-detection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Change detection</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The automated identification of differences between current observations and historical baseline data — surfacing what has changed in the physical world.</p>
|
||||
<p class="term-long">Change detection is a core AMOS capability that compares new observations against prior data to identify additions, removals, or modifications to physical assets. It powers infrastructure monitoring, property condition tracking, and environmental surveillance. Change detection operates at multiple scales: from pixel-level differences in repeated photographs to structural changes identified through computer vision. Each detected change is scored by confidence and severity, and flagged as a Contradiction when it represents an unexpected deviation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a retail park shows three new storefronts and one demolished unit compared to the baseline from six months ago. AMOS change detection automatically flags these modifications, updates the asset registry, and alerts the property manager to verify the changes.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#contradiction">Contradiction</a><a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#confidence-score">Confidence Score</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="claim" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Claim / Claiming</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The act of reserving a mission — locking it exclusively for you within a defined time window.</p>
|
||||
<p class="term-long">When a Zoomer claims a mission, the mission is removed from the available pool and assigned exclusively to that Zoomer for the duration of the time window. No other Zoomer can claim the same mission while it is held. If the Zoomer does not submit within the time window, the mission is automatically released back to the pool. Frequent abandonment (claiming without submitting) negatively affects a Zoomer's rating and may trigger restrictions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer sees a bridge inspection mission 0.8 km away. They tap Claim — the mission is now exclusively theirs for 4 hours. They travel to the location, complete the documentation, and submit. If they don't submit within 4 hours, the mission releases automatically.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#time-window">Time window</a><a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#rating">Rating</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="confidence-score" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Confidence Score</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A statistical measure of certainty attached to an observation or analysis output, expressed as a percentage.</p>
|
||||
<p class="term-long">The Confidence Score quantifies how certain the system is about a specific observation or derived insight. It is computed from multiple signals: EXIF integrity, GPS accuracy, image clarity, cross-validation against historical data, and agreement with other observations of the same asset. A high confidence score (90%+) indicates strong reliability; a low score triggers manual review or additional observation requests. Confidence scores are essential for decision-making — they tell the customer not just what was observed, but how much to trust it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection observation receives a 94% confidence score based on sharp imagery, precise GPS, and consistency with the previous inspection. An insurer uses this high-confidence observation to approve a maintenance claim without sending an engineer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a><a href="#contradiction">Contradiction</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="contradiction" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Contradiction</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A mismatch between observed reality and expected or previously recorded reality — a signal that something has changed or requires attention.</p>
|
||||
<p class="term-long">A Contradiction is flagged when an observation deviates significantly from the expected state: a building that was intact now shows damage, a road that was clear now has a sinkhole, or an asset that was present is now missing. Contradictions are not errors — they are valuable signals. They trigger alerts, escalate priority, and often indicate the most urgent decisions a customer must make. The Contradiction engine cross-references observations against historical data, design specifications, and regulatory baselines.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A quarterly observation of a commercial roof shows new water staining not present in the previous observation. AMOS flags this as a Contradiction, alerting the property manager to schedule repairs before the rainy season — preventing a €50,000 claim.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#confidence-score">Confidence Score</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="control-intelligence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Control Intelligence</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">Descriptive intelligence that tells you the current state of your physical assets — what is, not what to do.</p>
|
||||
<p class="term-long">Control Intelligence answers the question: 'What is the current condition of my assets?' It is the foundational layer of insight derived from observations, describing reality as it exists today: which bridges are sound, which buildings have damage, which roads need repair. Control Intelligence is objective, measurable, and verifiable. It is the raw material from which Decision Intelligence is forged — you cannot decide what to do until you know what is.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality receives Control Intelligence showing that 12% of its road bridges have surface cracking, 3% have structural concerns, and 85% are in good condition. This descriptive baseline is the starting point for all maintenance and investment decisions.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#decision-intelligence">Decision Intelligence</a><a href="#observation">Observation</a><a href="#amos">AMOS</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="csv" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">CSV</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Comma-Separated Values — a plain-text tabular data format available as a bulk export option for orderers.</p>
|
||||
<p class="term-long">CSV exports from quiXzoom contain one row per submission, with columns for mission ID, submission timestamp, GPS coordinates, approval status, Zoomer tier (anonymised), and other metadata fields. CSV is suitable for bulk import into spreadsheet tools, BI platforms, or legacy claims systems that do not support JSON or API integration. CSV exports are available on demand via the orderer dashboard or API.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality uses CSV exports to import quiXzoom road survey data into their GIS system on a weekly basis, plotting submission coordinates alongside existing infrastructure records.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#json">JSON</a><a href="#geojson">GeoJSON</a><a href="#api">API</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="d">
|
||||
<div class="letter-heading">
|
||||
<h2>D</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="data-controller" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data controller</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The entity that determines the purposes and means of processing personal data — under GDPR, quiXzoom acts as data controller for Zoomer and orderer data.</p>
|
||||
<p class="term-long">Under GDPR, the data controller is the legal entity responsible for deciding why and how personal data is processed. quiXzoom is the data controller for data collected from Zoomers (name, contact details, bank details, submission metadata) and from orderers. As data controller, quiXzoom must maintain a Record of Processing Activities (RoPA), appoint a Data Protection Officer where required, and respond to data subject rights requests within statutory timeframes.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer exercises their right to erasure, they submit a request to quiXzoom as data controller. quiXzoom is then legally responsible for erasing the Zoomer's personal data from its systems and instructing its data processors (including the KYC provider and Stripe) to do the same.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-processor">Data processor</a><a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-processor" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data processor</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">An entity that processes personal data on behalf of the data controller, under a Data Processing Agreement (DPA).</p>
|
||||
<p class="term-long">Data processors act on the instructions of the data controller and cannot use the data for their own purposes. quiXzoom's data processors include Stripe (payment processing), the KYC provider (identity verification), and cloud infrastructure providers. Each processor relationship must be governed by a Data Processing Agreement that complies with GDPR Article 28, specifying the scope, nature, purpose, and duration of processing.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The KYC provider that verifies Zoomer identities is a data processor for quiXzoom. They process identity documents and liveness check data strictly for identity verification purposes, under a DPA — they cannot use that data for their own marketing or analytics.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-controller">Data controller</a><a href="#gdpr">GDPR</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="data-residency" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Data residency</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">The geographic location where data is stored — quiXzoom stores all data in the EU (Stockholm, eu-north-1).</p>
|
||||
<p class="term-long">Data residency is increasingly important for enterprise customers in regulated industries, who may have legal or policy obligations requiring that data stays within a specific jurisdiction. quiXzoom's infrastructure runs on AWS eu-north-1 (Stockholm), keeping all data within the European Economic Area. This satisfies GDPR third-country transfer restrictions and is a key requirement for public sector and financial services customers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An EU public sector orderer requires that all submission data — including GPS coordinates and images — never leaves the EEA. quiXzoom's Stockholm data residency satisfies this requirement by default, without special configuration.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#s3">S3</a><a href="#pii">PII</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="decision-intelligence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Decision Intelligence</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">Actionable recommendations derived from observations through AMOS — the end product of the Landvex ecosystem.</p>
|
||||
<p class="term-long">Decision Intelligence is not data. It is not reports. It is the answer to a specific question: Which asset should I repair first? Where should I open my next store? Which claims are fraudulent? Landvex delivers Decision Intelligence by combining quiXzoom observations, AMOS analysis, and domain expertise into structured recommendations that directly enable decisions. Every output includes a confidence score and traceable source data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality receives a City Health Index of 71 for Norrmalm, down from 78 six months ago. The Decision Intelligence includes: specific deterioration patterns, contributing factors, recommended actions, and confidence intervals. The planner decides which streets to prioritise for maintenance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#index">Index</a><a href="#confidence-score">Confidence Score</a><a href="#amos">AMOS</a><a href="#control-intelligence">Control Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="decision-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Decision Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The top tier of the ecosystem where structured intelligence is translated into actionable decisions for customers.</p>
|
||||
<p class="term-long">The Decision Layer is where Landvex delivers intelligence products to end customers. It takes the indices, scores, and contradictions from the Analysis Layer and contextualises them for specific use cases: prioritising maintenance budgets, assessing insurance risk, evaluating property investments, ensuring regulatory compliance. The Decision Layer is customer-facing — it speaks the language of business, not technology. Every output is designed to answer one question: 'What decision does this help me make?'</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A property investor uses the Decision Layer to compare three potential acquisitions. The layer delivers a Neighbourhood Quality Index, Infrastructure Risk Score, and Commercial Opportunity Index for each — enabling a data-driven purchase decision in minutes rather than weeks.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#landvex">Landvex</a><a href="#analysis-layer">Analysis Layer</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="disbursement" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Disbursement</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">The technical transfer of earned funds from the platform escrow to a Zoomer's linked bank account.</p>
|
||||
<p class="term-long">Disbursement is the formal payment term for the outbound transfer of earned mission compensation. In quiXzoom's architecture, approved submission earnings accumulate in a Stripe Connect account (held on behalf of the Zoomer), and disbursements are processed on a rolling basis to the Zoomer's linked IBAN. Disbursements are distinct from the mission approval event — there may be a short settlement window between approval and disbursement depending on Stripe's payout schedule.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer's mission is approved at 14:00 on a Tuesday. Their earnings are added to their Stripe Connect balance immediately, and the disbursement to their bank account is processed as part of the next scheduled payout run — typically within 1–2 business days.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#payout">Payout</a><a href="#stripe-connect">Stripe Connect</a><a href="#iban">IBAN</a><a href="#sepa">SEPA</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="e">
|
||||
<div class="letter-heading">
|
||||
<h2>E</h2>
|
||||
<span class="letter-count">2 terms</span>
|
||||
</div>
|
||||
<article id="eur" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">EUR</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Euro — the secondary currency used in quiXzoom platform and Landvex products, primarily for European markets.</p>
|
||||
<p class="term-long">EUR is the secondary currency in the quiXzoom and Landvex ecosystem, used primarily for European markets and SEPA-zone transactions. Zoomers in Eurozone countries receive payouts in EUR via SEPA. Orderers in Europe may be invoiced in EUR. Like USD, EUR is a customer-facing currency — SEK is never shown to customers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A Zoomer in Germany receives their payout in EUR via SEPA. An orderer in France is invoiced in EUR for their monthly quiXzoom usage.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#usd">USD</a><a href="#sepa">SEPA</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="exif" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">EXIF</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Exchangeable Image File Format — metadata embedded in image files, including GPS coordinates, capture timestamp, device model, and camera settings.</p>
|
||||
<p class="term-long">EXIF metadata is written into image files at capture time by the device camera. For quiXzoom, EXIF is the primary evidence layer: it carries the GPS coordinates where the photo was taken, the precise timestamp, and device identifiers. AI review cross-validates EXIF GPS coordinates against the mission geofence, and EXIF timestamps against the mission time window. EXIF data is preserved in delivery packages to orderers as part of the chain-of-custody record.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer photographs a flood-damaged road. The image's EXIF data records 59.3312°N, 18.0685°E at 09:47:23 UTC. AI review checks this GPS fix is within the mission's 50-metre geofence and the timestamp falls within the claimed time window — both pass, contributing to approval.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#gps">GPS</a><a href="#timestamp">Timestamp</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="f">
|
||||
<div class="letter-heading">
|
||||
<h2>F</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="field-observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Field observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A structured data collection event performed at a physical location by a verified contributor, producing an observation record.</p>
|
||||
<p class="term-long">A field observation is the complete act of capturing reality data on location: travelling to the mission site, following the observation protocol, capturing required imagery from specified vantage points, and submitting the observation package. It is more than the photos — it is the verified, time-stamped, geo-located record of what was observed. Field observations are the foundational input to the entire quiXzoom–AMOS–Landvex pipeline. Without field observations, there is no data, no intelligence, and no decisions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer travels to a bridge inspection mission, follows the protocol (6 photos from specified angles), captures geo-tagged images, and submits. The field observation is verified by AI review and enters the AMOS dataset as a trusted data point.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#observation-protocol">Observation protocol</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="g">
|
||||
<div class="letter-heading">
|
||||
<h2>G</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="gdpr" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GDPR</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">General Data Protection Regulation — the EU framework governing how personal data is collected, stored, and processed.</p>
|
||||
<p class="term-long">GDPR (Regulation (EU) 2016/679) applies to any organisation processing the personal data of EU residents. For quiXzoom, this covers Zoomer identity data, GPS submission metadata, and orderer contact details. Key obligations include lawful basis for processing, data minimisation, purpose limitation, storage limitation, and honouring data subject rights (access, erasure, portability). All quiXzoom data is stored in EU (Stockholm, eu-north-1) to avoid third-country transfer complications.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Germany requests a copy of all data quiXzoom holds on them (right of access). quiXzoom must respond within 30 days with a machine-readable export of their submission history, identity data, and payment records — all governed by GDPR Article 15.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#pii">PII</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-controller">Data controller</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geo-accuracy" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geo-accuracy</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The closeness of a recorded GPS coordinate to the actual physical position — typically expressed in metres of error radius.</p>
|
||||
<p class="term-long">Geo-accuracy is determined by GPS signal quality, which is affected by urban canyon effects, tree canopy, atmospheric conditions, and device hardware. Consumer smartphone GPS typically achieves 3–10 metre accuracy in open conditions. quiXzoom's mission geofences are sized to account for realistic geo-accuracy limits — a mission for a specific building typically uses a 30–50 metre compliance radius. AI review evaluates whether the recorded GPS position is within the mission's accepted tolerance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer photographs a bridge in a narrow urban gorge where GPS signals reflect off buildings. Their device records a position 18 metres from the mission pin — within the 30-metre geofence tolerance — so the submission passes the geo-accuracy check.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#geo-tagged">Geo-tagged</a><a href="#exif">EXIF</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geo-tagged" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geo-tagged</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An image embedded with GPS coordinates at capture time, proving where the photo was physically taken.</p>
|
||||
<p class="term-long">Geo-tagging writes latitude, longitude, and altitude data into the image's EXIF metadata at the moment of capture. All quiXzoom submissions must be geo-tagged — this is a technical requirement enforced by the app. Submissions from devices with disabled location services are rejected before upload. Geo-tagging is the foundation of quiXzoom's location verification: without it, there is no way to confirm the photo was taken at the correct mission location.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The quiXzoom app requires location permissions to function. When a Zoomer captures a photo in-app, GPS coordinates are written to EXIF automatically. A Zoomer cannot submit photos taken in a regular camera app that disabled geo-tagging — the submission would fail AI review immediately.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#exif">EXIF</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#geojson">GeoJSON</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geofence" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Geofence</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A virtual geographic boundary defining where a mission must be completed — submissions outside the geofence are automatically rejected.</p>
|
||||
<p class="term-long">A geofence is a digitally defined perimeter around a mission location, typically represented as a circle with a radius of 30–100 metres or as a GeoJSON Polygon for complex shapes. When a Zoomer submits photos, AI review checks the EXIF GPS coordinates against the mission geofence. If the submission was captured outside the geofence, it is rejected with a location mismatch reason. Geofences ensure data integrity by guaranteeing that observations were physically captured at the correct location, preventing fraudulent or mistaken submissions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection mission has a 50-metre radius geofence centred on the bridge coordinates. A Zoomer submits photos from 200 metres away — the GPS coordinates in EXIF fall outside the geofence, and AI review rejects the submission with 'Location mismatch — outside geofence.'</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gps">GPS</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#exif">EXIF</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="geojson" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GeoJSON</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An open standard format (RFC 7946) for encoding geographic data structures using JSON.</p>
|
||||
<p class="term-long">GeoJSON is used by quiXzoom to define mission boundaries (geofences), to encode submission GPS paths, and to deliver location data to orderers in a format compatible with GIS platforms, mapping tools, and geographic analysis software. A mission boundary is represented as a GeoJSON Polygon; individual submission GPS points as GeoJSON Point Features with properties including timestamp, approval status, and submission ID.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality ordering a road condition survey receives their submission data as a GeoJSON FeatureCollection, which they import directly into QGIS to visualise submission density alongside their road network layer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#json">JSON</a><a href="#api">API</a><a href="#mission-brief">Mission brief</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="gps" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">GPS</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Global Positioning System — the satellite-based navigation system used to determine precise geographic location of submissions.</p>
|
||||
<p class="term-long">GPS is the primary location technology in smartphones, providing latitude, longitude, and altitude data by triangulating signals from multiple satellites. All quiXzoom submissions depend on GPS for location verification. The system is augmented by network-based location (Wi-Fi and cell triangulation) in environments where satellite signals are weak — combined, these signals provide the geo-accuracy required for mission compliance checks.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Every time a Zoomer captures a photo for a mission, the device GPS is sampled. This fix — along with the capture timestamp — is embedded in EXIF and used by AI review to verify the submission was made at the correct location within the correct time window.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#geo-tagged">Geo-tagged</a><a href="#geo-accuracy">Geo-accuracy</a><a href="#exif">EXIF</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="h">
|
||||
<div class="letter-heading">
|
||||
<h2>H</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="hmac-sha256" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">HMAC-SHA256</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A cryptographic signature method used to verify that webhook payloads were genuinely sent by quiXzoom and were not tampered with in transit.</p>
|
||||
<p class="term-long">HMAC (Hash-based Message Authentication Code) with SHA-256 works by combining the webhook payload with a shared secret key to produce a unique signature. quiXzoom attaches this signature to every webhook request in the X-QuiXzoom-Signature header. The receiving system recomputes the signature using the same secret and compares — if they match, the payload is authentic and unmodified. This is industry-standard practice used by Stripe, GitHub, and other major webhook providers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's claims system receives a webhook when a submission is approved. Before processing the data, their server verifies the HMAC-SHA256 signature against their shared webhook secret — confirming the event genuinely originated from quiXzoom and was not injected by a third party.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#webhook">Webhook</a><a href="#api">API</a><a href="#oauth">OAuth</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="i">
|
||||
<div class="letter-heading">
|
||||
<h2>I</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="iban" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">IBAN</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">International Bank Account Number — the standardised account identifier required for Stripe Connect payout setup in Europe.</p>
|
||||
<p class="term-long">IBAN is the international standard for identifying bank accounts across national borders, defined by ISO 13616. It consists of up to 34 alphanumeric characters: a 2-letter country code, 2 check digits, and the bank-specific account number. IBANs are used throughout SEPA for credit transfers and direct debits. Zoomers in supported SEPA countries link their IBAN during Stripe Connect onboarding — this is the account that will receive payout disbursements.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in the Netherlands enters their IBAN (NL39 RABO 0300 0652 64) during onboarding. All subsequent payouts from approved missions are disbursed to this account via SEPA credit transfer through Stripe Connect.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#sepa">SEPA</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a><a href="#disbursement">Disbursement</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="identity-verification" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Identity verification</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A one-time process confirming a Zoomer's identity with a government-issued ID and liveness check, required before the first payout.</p>
|
||||
<p class="term-long">Identity verification is a legal requirement under AML regulation for any payment platform processing disbursements. For quiXzoom, it involves submitting a government-issued photo ID (passport, national ID card, or driving licence) and a liveness check (selfie). The process is handled by a regulated KYC provider — not by quiXzoom directly — and typically completes within 1 hour. Identity verification is a one-time requirement: once verified, Zoomers never repeat it unless their details change materially.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A new Zoomer completes their first 3 missions before being prompted to verify identity before their first payout. They photograph their passport and complete a 15-second liveness check in-app. The KYC provider approves the verification within 45 minutes, and the payout is released.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#liveness-check">Liveness check</a><a href="#aml">AML</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="index" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Index</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A normalised score (0–100) derived from thousands of observations, representing the condition, risk, or quality of an asset or area.</p>
|
||||
<p class="term-long">An Index is the primary output of the AMOS analysis engine — a single number that summarises complex, multi-dimensional observation data into an intuitive, comparable metric. Different indices serve different purposes: the City Health Index measures overall infrastructure condition; the Infrastructure Risk Index quantifies probability of failure; the Commercial Opportunity Index identifies high-potential investment areas. Indices are computed from aggregated observations, weighted by confidence scores, and updated continuously as new observations flow in.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A city's Road Condition Index drops from 72 to 58 over six months. AMOS traces the decline to increased pothole observations in the northern district. The municipality uses this Index to justify a €2M resurfacing budget — with the Index projected to return to 75 post-works.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#observation">Observation</a><a href="#confidence-score">Confidence Score</a><a href="#decision-intelligence">Decision Intelligence</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="j">
|
||||
<div class="letter-heading">
|
||||
<h2>J</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="json" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">JSON</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">JavaScript Object Notation — the lightweight data format used for all quiXzoom API responses and webhook payloads.</p>
|
||||
<p class="term-long">JSON is a human-readable, language-agnostic data serialisation format that has become the de facto standard for web APIs. quiXzoom's REST API delivers all responses as JSON, including mission details, submission metadata, location data, and approval status. Webhook event payloads are also JSON. The format is natively supported in virtually all programming languages and integration platforms, making it straightforward to process quiXzoom data in any technical environment.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When an orderer queries the API for a completed submission, the response is a JSON object containing the submission ID, approval status, GPS coordinates, EXIF metadata summary, and signed URLs to retrieve the image files from S3.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#webhook">Webhook</a><a href="#geojson">GeoJSON</a><a href="#csv">CSV</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="k">
|
||||
<div class="letter-heading">
|
||||
<h2>K</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="kyc" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">KYC</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Know Your Customer — the regulatory process of verifying the identity of individuals before processing financial transactions on their behalf.</p>
|
||||
<p class="term-long">KYC is a standard compliance process required by AML regulation for payment platforms and financial services providers. In the quiXzoom context, KYC is performed by a regulated third-party identity verification provider (not by quiXzoom internally) on behalf of Stripe Connect. The process collects a government-issued ID and liveness check result, which are verified against government databases and fraud watchlists. KYC data is held by the verification provider, not by quiXzoom — quiXzoom only receives a pass/fail status.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Before a Zoomer can withdraw their first earnings, they are prompted to complete KYC. The 3–5 minute in-app flow captures their passport and a selfie, and is processed by the KYC provider. quiXzoom receives confirmation of verified status — not the underlying documents — and the payout queue is unblocked.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#aml">AML</a><a href="#identity-verification">Identity verification</a><a href="#liveness-check">Liveness check</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="l">
|
||||
<div class="letter-heading">
|
||||
<h2>L</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="landvex" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Landvex</h3>
|
||||
<span class="term-category cat-landvex">Landvex</span>
|
||||
</div>
|
||||
<p class="term-short">Global intelligence infrastructure company — builds decision intelligence from field observations.</p>
|
||||
<p class="term-long">Landvex Inc (Houston, TX) develops and sells IT products powered by AMOS engines. Landvex does not sell AI — it sells intelligence based on AMOS. The company combines quiXzoom field data, AMOS analysis, and domain expertise into decision intelligence products for infrastructure owners, governments, insurers, and enterprises. Landvex has operational presence in Europe and North America.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A property investor uses Landvex's Neighbourhood Quality Index to compare three potential acquisitions. The index combines infrastructure condition, safety observations, and commercial activity data into a single comparable score.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a><a href="#decision-intelligence">Decision Intelligence</a><a href="#index">Index</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="landvex-ab" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">LandveX AB</h3>
|
||||
<span class="term-category cat-landvex">Landvex</span>
|
||||
</div>
|
||||
<p class="term-short">The Swedish entity (org.nr 559141-7042) that handles development, operations, and accounting in SEK.</p>
|
||||
<p class="term-long">LandveX AB is the Swedish subsidiary responsible for development, operations, and local accounting. It handles all Swedish bookkeeping, VAT, payroll, and supplier invoices in SEK using the BAS chart of accounts and SIE4 format. This is correct per Swedish accounting law. LandveX AB operates the technical infrastructure from Stockholm (AWS eu-north-1).</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>LandveX AB employs the development team, pays Swedish salaries, and files Swedish tax returns. All internal bookkeeping is in SEK, while customer-facing products use USD/EUR.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#landvex">Landvex</a><a href="#landvex-inc">Landvex Inc</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="landvex-inc" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Landvex Inc</h3>
|
||||
<span class="term-category cat-landvex">Landvex</span>
|
||||
</div>
|
||||
<p class="term-short">The US entity (Houston, TX) that develops and sells IT products powered by AMOS engines.</p>
|
||||
<p class="term-long">Landvex Inc is the US-based company that owns and operates the AAMOS platform and quiXzoom product. It is the legal entity responsible for product development, sales, and operations. Landvex Inc is NOT 'AAMOS Group' — there is no such entity. All products are developed and sold by Landvex Inc.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>Landvex Inc holds the intellectual property for AMOS engines, operates the quiXzoom platform, and sells intelligence products to enterprise customers worldwide.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#landvex">Landvex</a><a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="liveness-check" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Liveness check</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A selfie-based verification step that confirms a real, live person is presenting the identity document — not a photo or deepfake.</p>
|
||||
<p class="term-long">Liveness detection uses computer vision to analyse a short selfie capture and confirm it is a genuine live face rather than a printed photo, screen replay, or synthetic image. It is performed as part of the KYC process to prevent identity fraud — specifically to stop bad actors using stolen ID documents paired with someone else's photo. Modern liveness checks typically involve a brief instructed motion (e.g. blinking or turning the head) to prove liveness unambiguously.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>During identity verification, a new Zoomer is asked to look at their phone camera and slowly turn their head. The liveness check confirms it's a real person in real time — not someone holding up a printed photo of the account holder. The whole step takes under 15 seconds.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#identity-verification">Identity verification</a><a href="#aml">AML</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="m">
|
||||
<div class="letter-heading">
|
||||
<h2>M</h2>
|
||||
<span class="letter-count">4 terms</span>
|
||||
</div>
|
||||
<article id="mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A paid photography assignment with a defined location, scope, and compensation, published by an orderer and claimed by a Zoomer.</p>
|
||||
<p class="term-long">A mission is the fundamental unit of work on the quiXzoom platform. Each mission has a geographic pin or geofence, a compensation amount, a mission brief (describing what to photograph and how), a time window within which the work must be completed, and a submission specification defining how many photos are required and from which vantage points. Missions may be standard, premium, or surge, and may be single-submission or multi-submission.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company creates a mission to document storm damage at a specific address. The mission has a 200-metre geofence, requires 8 photos from specified angles, pays €14, and has a 6-hour time window from claim. A nearby Zoomer sees it in the app, claims it, and completes the documentation.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission-brief">Mission brief</a><a href="#claim">Claim / Claiming</a><a href="#submission">Submission</a><a href="#time-window">Time window</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="mission-brief" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Mission brief</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The complete specification for a mission — what to capture, how to capture it, quality requirements, and any special instructions.</p>
|
||||
<p class="term-long">A mission brief is shown to the Zoomer after they claim a mission, and is the primary guide for execution. It includes required shot angles, distance from subject, lighting conditions (if relevant), specific elements that must appear in frame, and any contextual notes from the orderer. Mission briefs for specialised mission types (bridge inspection, maritime, infrastructure) include more detailed technical requirements. Zoomers should read the brief carefully before travelling to the mission location.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection mission brief specifies: 1 overview shot from 50m, 2 deck surface shots, 1 expansion joint close-up, 1 bearing detail, and 1 drainage outlet — all from public access points only. A Zoomer who misses the bearing detail shot is likely to receive a rejection at AI review.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#specialisation">Specialisation</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="mission-density" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Mission density</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The number of active missions available per geographic area — a key factor in a Zoomer's earning potential by location.</p>
|
||||
<p class="term-long">Mission density varies significantly between urban and rural areas, between regions, and over time. High mission density zones (dense urban areas, coastal regions with infrastructure) allow Zoomers to complete more missions per hour of activity — increasing hourly earnings. Mission density is influenced by orderer activity in the area and by platform growth. Zoomers can view mission density maps to understand the earning environment in different zones before setting their zone preferences.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>Stockholm's inner city shows 23 active missions within a 5km radius. A nearby suburb shows 3. A Zoomer choosing their zone setting can use mission density data to maximise their available mission volume per session.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#zone">Zone</a><a href="#mission">Mission</a><a href="#tier">Tier</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="multi-submission-mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Multi-submission mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A mission type where multiple Zoomers can submit, with compensation decreasing for each successive approved submission.</p>
|
||||
<p class="term-long">Multi-submission missions are used by orderers who want several independent documentation sets of the same location — typically for comparison, validation, or higher confidence. The first Zoomer to submit receives the highest compensation; subsequent approved submissions receive progressively lower amounts. The orderer sets the maximum number of submissions they will accept and the compensation schedule. Multi-submission missions remain claimable by additional Zoomers until the orderer's submission limit is reached.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An orderer creates a multi-submission mission for a flood-affected road segment, accepting 3 submissions at €18 / €12 / €8. Three different Zoomers claim and submit independently — the orderer receives three distinct photographic records of the same location, useful for triangulating damage assessment.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#surge-mission">Surge mission</a><a href="#premium-mission">Premium mission</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="o">
|
||||
<div class="letter-heading">
|
||||
<h2>O</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="oauth" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">OAuth</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Open Authorization — the industry-standard protocol used by quiXzoom's API for secure, delegated authentication.</p>
|
||||
<p class="term-long">OAuth 2.0 allows orderers to authenticate API requests without sharing credentials. Orderers obtain access tokens through the OAuth flow, which are then included in API request headers. Tokens can be scoped (read-only, write, full access) and have configurable expiry periods. OAuth 2.0 is also used for third-party integrations — for example, allowing an orderer's claims management platform to connect to quiXzoom on behalf of their organisation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's IT team sets up an OAuth 2.0 client in the quiXzoom orderer portal, receives client credentials, and uses these to generate short-lived access tokens for their claims integration server. Tokens expire after 1 hour and are automatically refreshed.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#webhook">Webhook</a><a href="#hmac-sha256">HMAC-SHA256</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A verified field record captured through quiXzoom — the fundamental unit of reality data.</p>
|
||||
<p class="term-long">An observation is not a photo. It is a structured, verified record of physical reality at a specific place and time. Every observation includes: geolocation (GPS coordinates with accuracy estimate), timestamp (when it was captured), media (images or video), and metadata (device, conditions, mission context). Observations are quality-checked by AI before entering the dataset. They are the raw material from which all Landvex intelligence is derived.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer captures 6 images of a road segment. Each image becomes part of an observation that includes GPS, timestamp, and mission context. AI review verifies the observation before it enters the dataset.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#zoomer">Zoomer</a><a href="#amos">AMOS</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The field data collection tier where Zoomers capture verified observations of physical assets and infrastructure.</p>
|
||||
<p class="term-long">The Observation Layer is the foundation of the ecosystem — the interface between physical reality and digital intelligence. It encompasses the quiXzoom mobile app, Zoomer network, mission management system, and AI review pipeline. Its purpose is to produce high-quality, trustworthy observations at scale. The Observation Layer guarantees data integrity through geo-tagging, timestamp verification, and automated quality checks. Without a robust Observation Layer, everything above it — analysis, indices, decisions — is built on sand.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>The Observation Layer deploys 500 Zoomers across a metropolitan area to capture quarterly building condition observations. Each observation is verified for GPS accuracy, image quality, and specification compliance before entering the Analysis Layer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#zoomer">Zoomer</a><a href="#reality-layer">Reality Layer</a><a href="#analysis-layer">Analysis Layer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="observation-protocol" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Observation protocol</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The standardised set of instructions defining what to capture, from which angles, and under what conditions for a given mission type.</p>
|
||||
<p class="term-long">The observation protocol is the rulebook for field data collection. It specifies the number of photos required, the vantage points (distance, angle, height), the elements that must be in frame, lighting conditions, and any safety or access constraints. Protocols are mission-type specific: a bridge inspection protocol differs from a property documentation protocol. Following the protocol is essential for approval — AI review checks compliance against the protocol, and deviations result in rejection. Protocols are developed by domain experts and refined through feedback from AI review outcomes.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A roof condition mission protocol requires: 1 overview shot from street level, 1 ridge-line photo, 2 slope photos (one per side), and 1 detail of any visible damage — all captured during daylight with the sun behind the photographer. A Zoomer who submits only 3 photos or captures at night will fail protocol compliance.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#field-observation">Field observation</a><a href="#mission-brief">Mission brief</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="orderer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Orderer</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">An organisation that creates and funds missions on the quiXzoom platform to obtain field documentation.</p>
|
||||
<p class="term-long">Orderers are the demand side of the quiXzoom marketplace. They can be insurance companies, infrastructure asset owners, public sector bodies, logistics operators, or any organisation with a need for verified on-location photography. Orderers define mission briefs, set compensation, and receive approved submissions via the dashboard or API. Orderers pay the Zoomer compensation plus a platform fee to quiXzoom.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Swedish infrastructure authority uses quiXzoom as orderer — creating 50 bridge inspection missions across a county, specifying technical requirements in each mission brief, and receiving standardised submission packages via API integration with their asset management system.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#platform-fee">Platform fee</a><a href="#api">API</a><a href="#sla">SLA</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="ouroboros" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Ouroboros</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The internal platform architecture that powers quiXzoom, AAMOS, and Landvex — a self-referential system where the platform monitors and improves itself.</p>
|
||||
<p class="term-long">Ouroboros is the internal name for the technical architecture that underpins the entire Landvex ecosystem. It encompasses the microservices, data pipelines, AI models, and infrastructure that enable quiXzoom field data collection, AMOS analysis, and Landvex intelligence delivery. The name reflects the system's self-monitoring nature: observations feed analysis, analysis drives decisions, decisions generate new observations. Ouroboros is not a customer-facing product — it is the technical foundation.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>quiXzoom runs as an Ouroboros instance — using the same core infrastructure as other Landvex products but configured for the quiXzoom marketplace model. Ouroboros handles user management, mission orchestration, AI review, and data pipelines.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a><a href="#landvex">Landvex</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="p">
|
||||
<div class="letter-heading">
|
||||
<h2>P</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="payout" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Payout</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">The transfer of earned mission compensation to a Zoomer's linked bank account, triggered automatically by submission approval.</p>
|
||||
<p class="term-long">Payouts are processed via Stripe Connect and deposited to the Zoomer's linked IBAN. Earnings from approved submissions accumulate in the Zoomer's Stripe Connect balance and are disbursed on a rolling schedule. Payout frequency and minimum threshold are configurable within the app. Payouts require completed identity verification (KYC) and a linked bank account. Zoomers receive an in-app notification and email confirmation for each payout.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes 5 missions in a week, earning €72 total. After each approval, earnings add to their Stripe Connect balance. On Friday, their accumulated balance is disbursed to their Dutch IBAN via SEPA — arriving as a single bank transfer with a quiXzoom reference.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#disbursement">Disbursement</a><a href="#stripe-connect">Stripe Connect</a><a href="#iban">IBAN</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="pii" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">PII</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">Personally Identifiable Information — any data that can directly or indirectly identify a specific individual.</p>
|
||||
<p class="term-long">PII encompasses obvious identifiers (name, email, address, IBAN) as well as indirect identifiers that, in combination, could identify someone (GPS traces, device fingerprints, submission patterns). Under GDPR, quiXzoom treats PII with strict controls: it is collected only where necessary, retained only as long as required, and never shared with orderers in identifiable form. Zoomer submissions are delivered to orderers without attached Zoomer identity — orderers receive field data, not person data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When an orderer receives a completed submission, they see the images, GPS coordinates, and timestamp — but not the Zoomer's name, account details, or any identifying information. The Zoomer's identity is pseudonymised in normal operation, with full identification available only under legal process.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#data-controller">Data controller</a><a href="#right-to-erasure">Right to erasure</a><a href="#data-residency">Data residency</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="platform-fee" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Platform fee</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The service fee paid by orderers to quiXzoom on top of Zoomer compensation, covering platform operations and AI review.</p>
|
||||
<p class="term-long">The platform fee is charged to the orderer and covers quiXzoom's infrastructure, AI review system, Zoomer management, customer support, and margin. Zoomers receive their full stated mission compensation — the platform fee is paid by the orderer separately and does not come from Zoomer earnings. Platform fees are calculated as a percentage of mission compensation, with enterprise volume pricing available for high-volume orderers.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An orderer creates a mission paying the Zoomer €12. quiXzoom's platform fee adds an additional amount on top — the orderer pays the total; the Zoomer receives exactly €12 upon approval. The platform fee structure is transparent and set out in the orderer's service agreement.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#orderer">Orderer</a><a href="#payout">Payout</a><a href="#mission">Mission</a><a href="#sla">SLA</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="premium-mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Premium mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A high-threshold mission type requiring specific Zoomer qualifications and a high approval rate, offering significantly elevated compensation.</p>
|
||||
<p class="term-long">Premium missions are reserved for experienced, high-performing Zoomers. Qualification requires Professional tier (or Active tier with relevant specialisation) and an approval rate above 92%. These missions typically involve technical infrastructure documentation — bridges, power facilities, maritime assets — with precise specification requirements. Compensation for premium missions reflects both the technical difficulty and the high-value use cases they serve, typically ranging from €20 to €40+ per submission.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A bridge inspection premium mission paying €28 appears for a Zoomer with a Maritime specialisation and 96% approval rate. Zoomers without Professional tier or the relevant specialisation do not see this mission in their feed — it is filtered to qualified Zoomers only.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#specialisation">Specialisation</a><a href="#approval-rate">Approval rate</a><a href="#surge-mission">Surge mission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="professional" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Professional</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The highest Zoomer tier — 15+ missions per week, 92%+ approval rate — granting access to all mission types including premium and unrestricted surge.</p>
|
||||
<p class="term-long">Professional tier represents quiXzoom's most engaged and highest-quality Zoomers. Qualification requires sustaining 15+ completed missions per week over the qualifying window, maintaining an approval rate above 92%, and having completed identity verification. Professional tier Zoomers receive priority access to new mission types, higher compensation caps, dedicated support, and early access to specialisation programmes. They form the backbone of supply for high-value, time-critical orderer requests.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A full-time quiXzoom contributor averaging 20 missions/week with a 97% approval rate holds Professional tier. They access premium infrastructure missions paying €25–40, receive surge alerts first, and have the option to take on specialisation certifications for maritime and bridge inspection mission types.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#active">Active</a><a href="#supplementary">Supplementary</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="q">
|
||||
<div class="letter-heading">
|
||||
<h2>Q</h2>
|
||||
<span class="letter-count">5 terms</span>
|
||||
</div>
|
||||
<article id="quality-score" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Quality score</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">A composite rating of an observation's technical fitness — sharpness, exposure, framing, and protocol compliance — distinct from the confidence score.</p>
|
||||
<p class="term-long">The Quality Score evaluates the technical and aesthetic properties of submitted media independent of location or metadata verification. It measures image sharpness (absence of motion blur or focus issues), exposure (neither under- nor over-exposed), framing (subject completeness and composition), and protocol compliance (correct angles, required elements visible). Quality Score is a component of the overall Confidence Score but is computed separately to give orderers visibility into the technical standard of their data. Low quality scores trigger coaching for Zoomers and may result in rejection if minimum thresholds are not met.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits photos that are correctly geo-located and within the time window, but two images are slightly blurry due to camera shake. AI review assigns a Quality Score of 62 — below the 75-point threshold — and rejects the submission with 'Image quality: motion blur detected.' The Zoomer receives automated coaching on stabilisation techniques.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#confidence-score">Confidence Score</a><a href="#ai-review">AI review</a><a href="#observation">Observation</a><a href="#approval">Approval</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="quixzoom" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">Global field data collection platform — 'Uber fast för foton'.</p>
|
||||
<p class="term-long">quiXzoom is a standalone product and business with its own brand, separate from AAMOS. It is a marketplace where anyone can take photo missions and earn money. Orderers post missions; Zoomers (anyone) complete them and get paid. quiXzoom uses AAMOS infrastructure under the hood but is never presented as 'AAMOS'. The platform provides verified, geotagged, timestamped field observations on demand.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A municipality needs photos of 50 road segments after a storm. They post missions on quiXzoom. Within 2 hours, local Zoomers have claimed all missions, captured the required photos, and submitted for AI review. The municipality receives verified observations with GPS and timestamps.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#zoomer">Zoomer</a><a href="#mission">Mission</a><a href="#observation">Observation</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="quixzoom-auth-core" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom Auth Core</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Standalone authentication product sold via AAMOS — includes Auth Foundation, KYZ Engine, Company Registry, and Payout Engine.</p>
|
||||
<p class="term-long">quiXzoom Auth Core is a standalone authentication and identity product that can be integrated into any application. It includes: Auth Foundation (email/Google + phone + password), KYZ Engine (Know Your Zoomer — identity verification), Company Registry (sole proprietorship / registered company), and Payout Engine (Stripe Connect, Frilans Finans, bank transfers). Auth Core is sold as a product via AAMOS and is used by quiXzoom and other Landvex products.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A third-party app developer integrates quiXzoom Auth Core to handle user authentication, identity verification, and payouts — without building these complex systems themselves.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#kyc">KYC</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="quixzoom-frilans-payout" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">quiXzoom Frilans Payout</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Payout product for freelancers without a company — handles taxes and fees across 8 markets.</p>
|
||||
<p class="term-long">quiXzoom Frilans Payout is a payout product designed for freelancers who don't have a registered company. It operates across 8 markets (SE, NO, DK, FI, DE, NL, US, GB) and automatically handles source tax per country. Features include weekly/monthly payouts, 15% platform fee + 6% processing fee, and automatic tax reporting. The product integrates with quiXzoom Auth Core and uses the Payout Engine.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A freelancer in Sweden uses quiXzoom Frilans Payout to receive payments without registering a company. The system automatically deducts source tax and pays it to Skatteverket, while the freelancer receives their net earnings weekly.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#quixzoom-auth-core">quiXzoom Auth Core</a><a href="#payout">Payout</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="qz-token" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">QZ Token</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">quiXzoom internal token — 1 QZ = 1 USD, used for platform transactions and rewards.</p>
|
||||
<p class="term-long">The QZ Token is quiXzoom's internal transaction token with a fixed exchange rate of 1 QZ = 1 USD. It is not a speculative cryptocurrency — it is a simple ledger entry used for platform transactions, rewards, and internal accounting. QZ Tokens are created when missions are approved and stored in Zoomer accounts. They can be converted to USD payouts or used for platform services.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer earns 50 QZ from completed missions. They can convert these to $50 USD payout or use them to purchase premium features on the platform.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#usd">USD</a><a href="#payout">Payout</a><a href="#quixzoom">quiXzoom</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="r">
|
||||
<div class="letter-heading">
|
||||
<h2>R</h2>
|
||||
<span class="letter-count">6 terms</span>
|
||||
</div>
|
||||
<article id="rating" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Rating</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A Zoomer's accumulated quality score on the platform, reflecting submission quality, consistency, and reliability over time.</p>
|
||||
<p class="term-long">Rating is a composite metric calculated from approval rate, submission volume, claim-to-completion ratio (how often claimed missions are actually submitted), and any policy violations. Rating is displayed as a numerical score and determines mission access filtering — high-rating Zoomers see more mission types, receive surge notifications earlier, and are prioritised for specialisation programme invitations. Unlike approval rate (a rolling 30-day window), rating incorporates a Zoomer's full history, weighted toward recent activity.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer with a 94% approval rate but a poor claim-to-completion ratio (often claiming missions and abandoning them) will have a rating lower than their approval rate alone would suggest. Improving claim reliability raises their rating independently of approval rate.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#approval-rate">Approval rate</a><a href="#tier">Tier</a><a href="#claim">Claim / Claiming</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="reality-layer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Layer</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">The physical world itself — the assets, infrastructure, and environments that the ecosystem observes, analyses, and optimises.</p>
|
||||
<p class="term-long">The Reality Layer is everything physical: roads, bridges, buildings, coastlines, forests, power lines, water pipes. It is the domain that exists independently of any observation system — the ground truth that the ecosystem seeks to understand and improve. The Reality Layer is not digital; it is the actual world that customers own, manage, insure, and invest in. Every observation is a measurement of the Reality Layer; every index is a summary of its state; every decision is an intervention upon it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A city's Reality Layer comprises 1,200 km of roads, 400 bridges, 50 tunnels, and 2,000 public buildings. The ecosystem's purpose is to create a complete, accurate, up-to-date digital understanding of this Reality Layer — enabling better decisions about maintenance, investment, and risk.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation-layer">Observation Layer</a><a href="#analysis-layer">Analysis Layer</a><a href="#decision-layer">Decision Layer</a><a href="#reality-signal">Reality Signal</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="reality-signal" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Reality Signal</h3>
|
||||
<span class="term-category cat-core">Core</span>
|
||||
</div>
|
||||
<p class="term-short">A measurable, verifiable observation that describes a specific aspect of the physical world.</p>
|
||||
<p class="term-long">A Reality Signal is any observation that carries information about the state of physical reality: a photo of a cracked bridge deck, a GPS-tagged image of flood damage, a timestamped record of a building's facade. Reality Signals are the raw inputs to the Analysis Layer. They are distinguished from synthetic or inferred data by their direct connection to physical measurement — a Zoomer was there, the camera captured light from the actual scene, the GPS recorded the actual coordinates. Reality Signals are the antidote to assumptions and desk-based estimates.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurer receives a Reality Signal showing hail damage to a factory roof — captured 6 hours after the storm, with GPS confirming the location, timestamp proving immediacy, and image quality enabling damage severity assessment. This Reality Signal replaces the traditional adjuster visit.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#observation">Observation</a><a href="#reality-layer">Reality Layer</a><a href="#confidence-score">Confidence Score</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="rejection" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Rejection</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A negative outcome from AI review, indicating a submission does not meet mission requirements — no payout is issued for rejected submissions.</p>
|
||||
<p class="term-long">Rejections occur when AI review identifies one or more disqualifying issues: location mismatch (GPS outside geofence), timestamp violation (submitted outside time window), image quality failure (blurred, overexposed, or heavily occluded), specification miss (required element absent), or EXIF anomaly (GPS data absent or inconsistent). Every rejection includes a specific reason code that the Zoomer can view in-app. Zoomers can review rejection reasons to understand and correct issues on future missions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer submits 6 photos but one required angle (the drainage outlet) is missing. AI review flags a specification miss and rejects the submission with reason code SPEC_INCOMPLETE. The Zoomer's approval rate decreases by one event, and no payout is issued for this submission.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#approval">Approval</a><a href="#approval-rate">Approval rate</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="rexo" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">REXO</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Landvex's coding pipeline for automated software development, testing, and deployment.</p>
|
||||
<p class="term-long">REXO is Landvex's internal coding pipeline that automates software development tasks. It runs via /opt/amos/rexo-build/, with tasks defined in plan/PLAN.json and executed by parallel workers. REXO orchestrates code generation, testing, and deployment across the ecosystem. All coding tasks should be routed through REXO rather than manual file uploads or direct server modifications.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>When a new feature is needed for the quiXzoom API, the task is added to REXO's PLAN.json. REXO workers generate the code, run tests, and deploy to staging — all without manual intervention.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#ouroboros">Ouroboros</a><a href="#amos">AMOS</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="right-to-erasure" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Right to erasure</h3>
|
||||
<span class="term-category cat-legal">Legal</span>
|
||||
</div>
|
||||
<p class="term-short">A GDPR right allowing individuals to request deletion of their personal data from a platform's systems.</p>
|
||||
<p class="term-long">Under GDPR Article 17, individuals have the right to request erasure of their personal data when it is no longer necessary for the purpose it was collected, when they withdraw consent, or when they object to processing. For quiXzoom, this means Zoomers can request deletion of their account and all associated personal data at any time via the app settings. Certain data may need to be retained for limited periods to satisfy legal obligations (e.g. financial records under tax law) even after an erasure request.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer decides to stop using quiXzoom and requests erasure. quiXzoom deletes their profile, contact data, and GPS history. Some financial transaction records are retained for 7 years as required by EU accounting regulation — this is disclosed in quiXzoom's privacy policy and does not affect the Zoomer's ability to stop using the platform.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#gdpr">GDPR</a><a href="#pii">PII</a><a href="#data-controller">Data controller</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="s">
|
||||
<div class="letter-heading">
|
||||
<h2>S</h2>
|
||||
<span class="letter-count">10 terms</span>
|
||||
</div>
|
||||
<article id="s3" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">S3</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">Amazon Simple Storage Service — the object storage platform used to store all quiXzoom submission images, securely and at scale.</p>
|
||||
<p class="term-long">S3 (AWS eu-north-1) is quiXzoom's primary file store for submission images. Uploaded images are stored with server-side encryption, access is controlled via IAM policies, and orderers receive time-limited signed URLs to retrieve submission packages — images are never publicly accessible by default. S3's durability (99.999999999%) and scalability make it appropriate for a platform expecting high submission volumes during surge events.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer uploads 6 photos for a mission, they are stored in S3 eu-north-1. When the orderer queries the API for the completed submission, they receive signed URLs valid for 24 hours to download the images — after which the URLs expire and a new API call is required.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#data-residency">Data residency</a><a href="#api">API</a><a href="#submission">Submission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="sepa" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">SEPA</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Single Euro Payments Area — the European bank transfer network used for EUR payout disbursements to Zoomers.</p>
|
||||
<p class="term-long">SEPA covers 36 European countries and enables fast, low-cost euro bank transfers using IBAN identifiers. SEPA Credit Transfers (SCT) typically settle within 1 business day; SEPA Instant Credit Transfers (SCT Inst) settle in under 10 seconds where supported. quiXzoom uses Stripe Connect's SEPA infrastructure for EUR disbursements to Zoomers in SEPA-member countries. For Zoomers in countries outside SEPA, SWIFT transfers apply, which may have longer settlement windows and additional fees.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Finland has earned €85 across 7 missions. Stripe Connect initiates a SEPA Credit Transfer to their Finnish IBAN — the funds arrive in their bank account within 1 business day at no charge to the Zoomer.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#iban">IBAN</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a><a href="#swift-bic">SWIFT/BIC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="sla" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">SLA</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">Service Level Agreement — the delivery timeline and quality commitments quiXzoom makes to orderers, governing mission fulfilment and submission delivery.</p>
|
||||
<p class="term-long">quiXzoom's SLAs define expected fulfilment times (how quickly a claimed mission produces an approved submission), platform uptime commitments, API response time guarantees, and escalation procedures when commitments are not met. SLA terms vary by orderer plan — standard, professional, and enterprise tiers have different guaranteed fulfilment windows. SLA performance is monitored and reported monthly to orderers, with service credits applicable in cases of sustained underperformance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An enterprise orderer's SLA guarantees that 95% of urban missions will produce an approved submission within 4 hours of activation. For surge missions, the SLA commits to a first claim within 30 minutes. These commitments are monitored in real time and reported in the orderer's monthly performance report.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#orderer">Orderer</a><a href="#mission">Mission</a><a href="#surge-mission">Surge mission</a><a href="#api">API</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="specialisation" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Specialisation</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A certified competency that unlocks access to specific advanced mission types requiring domain-specific knowledge or technical skill.</p>
|
||||
<p class="term-long">Specialisations are earned through a training and assessment programme administered within the quiXzoom app. Each specialisation covers the technical requirements, safety considerations, and documentation standards for a specific mission domain. Available specialisations include Maritime (marina and harbour documentation), Bridge & Civil (infrastructure inspection), Energy Infrastructure (substations, wind turbines), and Retail Audit. Completing a specialisation assessment unlocks the corresponding premium mission category in the Zoomer's feed.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer living near a large marina completes the Maritime specialisation — a 45-minute in-app training covering mooring documentation, vessel identification standards, and marina facility photography requirements. They now see maritime premium missions paying €20–35 in their area, which are invisible to non-specialised Zoomers.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#premium-mission">Premium mission</a><a href="#tier">Tier</a><a href="#mission-brief">Mission brief</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="stripe" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Stripe</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">A global payments platform — quiXzoom's underlying payment infrastructure provider for all Zoomer payouts and orderer billing.</p>
|
||||
<p class="term-long">Stripe is a regulated payment institution used by millions of platforms worldwide. quiXzoom uses two Stripe products: Stripe Payments for orderer billing, and Stripe Connect for Zoomer payout disbursements. Stripe holds regulatory authorisations across the US, EU, and other jurisdictions, which is why AML/KYC compliance requirements flow through Stripe Connect's onboarding process. Stripe's infrastructure provides the payment settlement, fraud detection, and payout mechanics that quiXzoom's marketplace depends on.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>When a Zoomer adds their bank account in the quiXzoom app, they are creating a Stripe Connect account under quiXzoom's platform. Stripe is the regulated entity that actually moves money from quiXzoom's orderer receipts to Zoomer IBANs — quiXzoom orchestrates the process but Stripe executes the regulated payment flows.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#stripe-connect">Stripe Connect</a><a href="#kyc">KYC</a><a href="#payout">Payout</a><a href="#iban">IBAN</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="stripe-connect" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Stripe Connect</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Stripe's multi-party payment product that enables quiXzoom to distribute earned mission compensation directly to individual Zoomer bank accounts.</p>
|
||||
<p class="term-long">Stripe Connect is designed specifically for marketplace and platform models where a platform collects money from one party (orderers) and distributes it to another (Zoomers). It handles the regulated aspects of marketplace payments: identity verification (KYC), payout scheduling, tax form collection (where required), currency conversion, and compliance with local financial regulations. Each Zoomer has a Stripe Connect account created during onboarding, linked to their verified bank account.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>During onboarding, a Zoomer completes a Stripe Connect flow: they enter their name, date of birth, address, and IBAN, and complete identity verification. From this point, every approved submission triggers an automatic credit to their Stripe Connect balance, which disburses to their bank account on the configured schedule.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#stripe">Stripe</a><a href="#kyc">KYC</a><a href="#payout">Payout</a><a href="#iban">IBAN</a><a href="#sepa">SEPA</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="submission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Submission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A completed set of photos uploaded by a Zoomer after executing a mission, submitted for AI review and potential payout.</p>
|
||||
<p class="term-long">A submission is the output of a claimed and completed mission. It consists of the required number of geo-tagged images, their EXIF metadata, a GPS trace (if required), and any optional notes from the Zoomer. Submissions are uploaded through the quiXzoom app and enter the AI review pipeline immediately. The submission event locks the mission as completed — a Zoomer cannot resubmit after an initial submission without contacting support. Submission quality directly impacts approval rate and rating.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer completes a 6-photo road condition survey and taps Submit. The submission package (images, EXIF, GPS trace) is uploaded to S3 and enters AI review. Within 90 seconds, the Zoomer receives an in-app approval notification and their €10 earnings are queued for payout.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#ai-review">AI review</a><a href="#approval">Approval</a><a href="#rejection">Rejection</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="supplementary" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Supplementary</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The entry-level Zoomer tier — 2–4 missions per week — for contributors using quiXzoom as occasional supplemental income.</p>
|
||||
<p class="term-long">Supplementary tier is the starting tier for all new Zoomers. It provides access to standard missions in the Zoomer's zone, with no minimum weekly commitment. Supplementary Zoomers earn the standard mission rates and can access surge missions in their area. To progress to Active tier, a Zoomer must demonstrate sustained volume (8+ missions/week) and maintain an approval rate above 85% over a qualifying period.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A gig worker uses quiXzoom alongside their other activities — completing 3 missions per week in their neighbourhood while walking their dog or commuting. At Supplementary tier, they access standard missions with no pressure to increase volume; their €30–40/week in earnings is a useful addition to their income mix.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#tier">Tier</a><a href="#active">Active</a><a href="#professional">Professional</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="surge-mission" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Surge mission</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">High-urgency missions deployed after acute events — storms, floods, accidents — offering 2–5× standard compensation for rapid on-site documentation.</p>
|
||||
<p class="term-long">Surge missions are created by orderers (typically insurers or infrastructure managers) in response to time-critical events requiring rapid field documentation. They carry elevated compensation to incentivise Zoomers to prioritise them and accept shorter time windows. Surge alerts are pushed as priority notifications to all Zoomers in the affected zone, with Professional tier Zoomers notified first. Surge missions typically have tighter specification requirements and stricter AI review thresholds given their legal and claims significance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A severe storm hits coastal Sweden. An insurer activates 40 surge missions across 12 postcodes within 20 minutes of the event. Zoomers in those zones receive priority push notifications — the missions pay €35 each (vs. €12 standard) with a 3-hour time window. 38 of 40 missions are claimed within 45 minutes.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#premium-mission">Premium mission</a><a href="#mission">Mission</a><a href="#tier">Tier</a><a href="#sla">SLA</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="swift-bic" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">SWIFT/BIC</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Society for Worldwide Interbank Financial Telecommunication / Bank Identifier Code — used for international bank transfers outside the SEPA zone.</p>
|
||||
<p class="term-long">SWIFT (the network) and BIC (the identifier standard) together enable international bank-to-bank transfers for currencies and countries outside SEPA. Zoomers in non-SEPA countries (e.g. the UK post-Brexit for GBP, or non-EU markets quiXzoom may expand to) require a SWIFT/BIC code in addition to their account number for payout setup. SWIFT transfers typically settle in 1–5 business days and may incur intermediary bank fees — terms disclosed to Zoomers during onboarding.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer in Norway (SEPA member) uses IBAN/SEPA for payouts. A Zoomer in the UK (non-SEPA) provides their IBAN and SWIFT/BIC during onboarding — Stripe Connect routes their payout via SWIFT, with a 2–3 business day settlement window.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#sepa">SEPA</a><a href="#iban">IBAN</a><a href="#stripe-connect">Stripe Connect</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="t">
|
||||
<div class="letter-heading">
|
||||
<h2>T</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="tier" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Tier</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A Zoomer's platform level — Supplementary, Active, or Professional — reflecting activity volume and quality, and determining mission access.</p>
|
||||
<p class="term-long">The tier system is quiXzoom's primary mechanism for matching mission complexity and compensation to Zoomer reliability. Higher tiers require more submissions per week and higher approval rates; in return, they unlock premium missions, higher compensation caps, priority surge notifications, and specialisation programmes. Tier is calculated on a rolling basis — a Zoomer can move up by improving performance, or drop if activity or quality falls below threshold for a sustained period.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer consistently completing 10 missions/week with a 90% approval rate qualifies for Active tier after 4 qualifying weeks. They now see 30% more missions in their feed and are eligible to apply for a specialisation programme — their per-week earning potential roughly doubles compared to Supplementary.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#supplementary">Supplementary</a><a href="#active">Active</a><a href="#professional">Professional</a><a href="#approval-rate">Approval rate</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="time-window" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Time window</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The duration a Zoomer has to complete and submit a mission after claiming it — after which the mission auto-releases back to the pool.</p>
|
||||
<p class="term-long">Time windows are set per mission type and range from 1 hour (urgent surge missions in dense urban areas) to 24 hours (rural or low-urgency surveys). The clock starts when the Zoomer claims the mission. If no submission is received before the window expires, the mission is automatically un-claimed and becomes available to other Zoomers. Frequent time window expiries (claiming without submitting) negatively affect a Zoomer's rating and may trigger temporary claiming restrictions.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A storm damage survey mission has a 4-hour time window. A Zoomer claims it at 10:00. They have until 14:00 to travel to the location, photograph the damage, and submit. At 13:58, they upload the final photo — 2 minutes before expiry. Submission is accepted; time window is satisfied.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#claim">Claim / Claiming</a><a href="#mission">Mission</a><a href="#submission">Submission</a><a href="#surge-mission">Surge mission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="timestamp" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Timestamp</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">The precise date and time recorded in a photo's EXIF metadata, proving when the image was captured.</p>
|
||||
<p class="term-long">Timestamps are a critical element of quiXzoom's chain-of-custody system. The EXIF timestamp records the device's date and time at the moment of capture, and is cross-validated by AI review against the mission's claimed time window. For legal and insurance use cases, the timestamp (combined with GPS data) provides tamper-evident proof that the documentation was made at the right place at the right time. quiXzoom also records server-side ingestion timestamps for each submission to supplement device-side EXIF data.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurer requires flood documentation captured within 6 hours of a storm event for their claims validity window. The EXIF timestamp on each submitted photo, cross-referenced with server ingestion time, provides the evidence that the documentation falls within the required window — suitable for claims processing and, if necessary, legal proceedings.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#exif">EXIF</a><a href="#time-window">Time window</a><a href="#geo-tagged">Geo-tagged</a><a href="#ai-review">AI review</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="u">
|
||||
<div class="letter-heading">
|
||||
<h2>U</h2>
|
||||
<span class="letter-count">1 term</span>
|
||||
</div>
|
||||
<article id="usd" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">USD</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">United States Dollar — the primary currency used in quiXzoom platform and Landvex products.</p>
|
||||
<p class="term-long">USD is the main currency throughout the quiXzoom platform and Landvex ecosystem. All customer-facing pricing, payouts, and product fees are denominated in USD (or EUR where specified). This is a locked policy — SEK is never used in customer-facing copy, sites, documents, or communication. The only exception is LandveX AB's internal Swedish accounting.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In the ecosystem</span>
|
||||
<p>A mission pays $15 (USD). A Zoomer's earnings are displayed in USD. Landvex enterprise contracts are priced in USD. This is consistent across all customer touchpoints.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#eur">EUR</a><a href="#payout">Payout</a><a href="#platform-fee">Platform fee</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="v">
|
||||
<div class="letter-heading">
|
||||
<h2>V</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="vat" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">VAT</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">Value Added Tax — Zoomers are responsible for their own VAT obligations where applicable under local tax law.</p>
|
||||
<p class="term-long">VAT treatment of gig platform income varies by jurisdiction and depends on the Zoomer's status (individual, self-employed, VAT-registered business) and the total income thresholds in their country. In most EU countries, Zoomers earning below the VAT registration threshold are not required to charge or remit VAT. quiXzoom provides transaction records suitable for tax reporting but does not provide tax advice — Zoomers should consult their local tax authority or advisor for their specific obligations. For orderers, quiXzoom's service fees are subject to standard B2B VAT rules.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Swedish Zoomer earning €8,000/year from quiXzoom (below Sweden's VAT threshold of ~€32,000 for small businesses) is not required to register for or charge VAT. A Zoomer earning above threshold must register, charge VAT on their services, and remit to Skatteverket — quiXzoom's annual earnings summary facilitates this reporting.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#payout">Payout</a><a href="#stripe-connect">Stripe Connect</a><a href="#w9-w8ben">W-9 / W-8BEN</a><a href="#1099-k">1099-K</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="verified-contributor" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Verified contributor</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A Zoomer who has completed identity verification (KYC) and maintains an active, good-standing account — eligible for payouts and premium missions.</p>
|
||||
<p class="term-long">A verified contributor is a Zoomer who has passed the platform's trust threshold: their identity has been confirmed through government-issued ID and liveness check, their bank account is linked via Stripe Connect, and their account is in good standing (not suspended or restricted). Verification is a one-time process, but good standing is maintained through consistent quality (approval rate above threshold) and compliance with platform policies. Only verified contributors can receive payouts and access Professional-tier missions. Verification status is displayed in the Zoomer's profile.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A new Zoomer completes 5 missions and earns €45. Before they can receive their first payout, they must become a verified contributor by completing KYC. Once verified, their status shows a green checkmark in-app, and they can withdraw earnings and claim premium missions.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#kyc">KYC</a><a href="#identity-verification">Identity verification</a><a href="#zoomer">Zoomer</a><a href="#stripe-connect">Stripe Connect</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="vims" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">VIMS</h3>
|
||||
<span class="term-category cat-product">Product</span>
|
||||
</div>
|
||||
<p class="term-short">Visual Infrastructure Monitoring System — a Landvex product for continuous infrastructure condition assessment.</p>
|
||||
<p class="term-long">VIMS (Visual Infrastructure Monitoring System) is a Landvex product that uses quiXzoom observations and AMOS analysis to provide continuous monitoring of infrastructure assets. It delivers condition indices, change alerts, and maintenance prioritisation for roads, bridges, buildings, and utilities. VIMS replaces periodic manual inspections with ongoing, data-driven condition assessment.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In Landvex</span>
|
||||
<p>A municipality subscribes to VIMS for their 400 bridges. Monthly observations from quiXzoom Zoomers feed into VIMS, which updates condition indices, flags new damage, and generates maintenance priority lists — all automatically.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#amos">AMOS</a><a href="#quixzoom">quiXzoom</a><a href="#index">Index</a><a href="#change-detection">Change detection</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="w">
|
||||
<div class="letter-heading">
|
||||
<h2>W</h2>
|
||||
<span class="letter-count">3 terms</span>
|
||||
</div>
|
||||
<article id="w9-w8ben" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">W-9 / W-8BEN</h3>
|
||||
<span class="term-category cat-payment">Payment</span>
|
||||
</div>
|
||||
<p class="term-short">US IRS tax forms collected by payment platforms from payees to determine tax withholding obligations for US-source income.</p>
|
||||
<p class="term-long">W-9 is completed by US persons (certifying their Tax Identification Number). W-8BEN is completed by non-US individuals certifying their foreign status and claiming any applicable tax treaty benefits. Stripe Connect collects these forms as part of its US regulatory compliance. For Zoomers in the EU, W-8BEN confirms they are not subject to US tax withholding on quiXzoom earnings. This is collected automatically during Stripe Connect onboarding for Zoomers in countries where Stripe requires it.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A German Zoomer completing Stripe Connect onboarding is prompted to complete a W-8BEN form (takes ~2 minutes). This certifies they are a non-US person and exempts them from US withholding tax on their quiXzoom earnings — as their income is EU-source and subject to German tax law, not US.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#1099-k">1099-K</a><a href="#stripe-connect">Stripe Connect</a><a href="#vat">VAT</a><a href="#kyc">KYC</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="waitlist" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Waitlist</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The pre-launch registration list for Zoomers and orderers to secure early access when quiXzoom opens in their region.</p>
|
||||
<p class="term-long">The quiXzoom waitlist allows interested Zoomers and orderers to register before the platform launches in their area. Waitlist registrants receive priority onboarding invitations, early-access mission allocations, and launch communications. For Zoomers, waitlist sign-up takes under 60 seconds and requires only basic contact information — full onboarding (identity verification, bank account) is completed when access is granted. The waitlist helps quiXzoom manage geographic launch sequencing and ensure supply matches demand at launch.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>quiXzoom is launching in August 2026. Zoomers who register on the waitlist before launch receive an early-access invitation 2 weeks before public opening in their city, allowing them to complete onboarding and be mission-ready on day one.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#zoomer">Zoomer</a><a href="#mission">Mission</a><a href="#orderer">Orderer</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="webhook" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Webhook</h3>
|
||||
<span class="term-category cat-technical">Technical</span>
|
||||
</div>
|
||||
<p class="term-short">An automatic HTTP POST notification sent by quiXzoom to an orderer's system when a defined event occurs — typically submission approval.</p>
|
||||
<p class="term-long">Webhooks enable real-time integration between quiXzoom and orderer systems without polling. When a submission is approved (or rejected, or a mission is created), quiXzoom sends a JSON payload to the orderer's configured webhook URL. The payload includes the event type, mission ID, submission ID, GPS coordinates, approval status, and image download URLs. Orderers must verify webhook authenticity using HMAC-SHA256 signature verification. Undelivered webhooks are retried with exponential backoff over 24 hours.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>An insurance company's claims system has a quiXzoom webhook endpoint. When a flood damage submission is approved, quiXzoom sends a POST request within seconds. The claims system receives the event, automatically attaches the images to the open claim, and updates the claim status to 'documented' — with no manual intervention required.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#api">API</a><a href="#hmac-sha256">HMAC-SHA256</a><a href="#json">JSON</a><a href="#approval">Approval</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<section class="letter-section" id="z">
|
||||
<div class="letter-heading">
|
||||
<h2>Z</h2>
|
||||
<span class="letter-count">2 terms</span>
|
||||
</div>
|
||||
<article id="zone" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Zone</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">The geographic radius a Zoomer sets as their operational area, determining which missions appear in their mission feed.</p>
|
||||
<p class="term-long">Each Zoomer configures one or more zones — defined as a radius around a point (their home, workplace, or preferred operating area). The quiXzoom app displays missions within the Zoomer's active zone. Zoomers can set multiple zones, adjust zone radius, and switch between zones as needed. Zone configuration is used by quiXzoom to target mission notifications — if a surge mission is activated within a Zoomer's zone, they are alerted immediately. Zones do not restrict where a Zoomer can physically travel; they filter the mission feed for relevance.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A Zoomer sets a 5km zone around their home in Göteborg and a 3km zone around their office. They see missions within both zones in their feed. On a day when they're travelling to Malmö, they temporarily set an additional zone there to pick up missions during their visit.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission-density">Mission density</a><a href="#mission">Mission</a><a href="#surge-mission">Surge mission</a>
|
||||
</div>
|
||||
</article>
|
||||
<article id="zoomer" class="term-card">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">Zoomer</h3>
|
||||
<span class="term-category cat-quixzoom">quiXzoom</span>
|
||||
</div>
|
||||
<p class="term-short">A verified field data collector on the quiXzoom platform — an individual who claims missions, captures on-location photography, and earns compensation per approved submission.</p>
|
||||
<p class="term-long">Zoomers are the supply side of the quiXzoom marketplace. Anyone with a compatible smartphone, a willingness to be verified (KYC), and a linked bank account can become a Zoomer. Zoomers work independently, on their own schedule, within their chosen zone. They earn per approved submission — there is no hourly pay, no minimum hours, and no obligation to work any particular number of missions. Zoomers progress through tiers (Supplementary → Active → Professional) as they build volume and quality.</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">In quiXzoom</span>
|
||||
<p>A freelance photographer becomes a quiXzoom Zoomer, completing identity verification and bank account setup in 10 minutes. They begin claiming road survey and building inspection missions near their home, earning €8–15 per approved submission. Within 6 weeks, their consistent quality and volume qualify them for Active tier.</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
<a href="#mission">Mission</a><a href="#tier">Tier</a><a href="#approval-rate">Approval rate</a><a href="#kyc">KYC</a><a href="#payout">Payout</a>
|
||||
</div>
|
||||
</article>
|
||||
</section>
|
||||
<div class="last-updated">Last updated: July 14, 2026</div>
|
||||
</main>
|
||||
<footer style="background:#0d0d10;border-top:1px solid rgba(255,255,255,.07);padding:32px 24px;margin-top:48px">
|
||||
<div style="max-width:1080px;margin:0 auto;display:flex;align-items:center;justify-content:space-between;flex-wrap:wrap;gap:16px">
|
||||
<a href="/" style="font-size:1.1rem;font-weight:800;color:#fff;letter-spacing:-.03em;text-decoration:none">qui<span style="color:#3b82f6">X</span>zoom</a>
|
||||
<p style="font-size:.8125rem;color:rgba(255,255,255,.75);margin:0">© 2026 Landvex Inc</p>
|
||||
</div>
|
||||
</footer>
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,1901 @@
|
||||
{
|
||||
"version": "2026-07-14",
|
||||
"lastUpdated": "2026-07-14T11:39:07.957Z",
|
||||
"domains": [
|
||||
"quixzoom.com",
|
||||
"landvex.com",
|
||||
"aamos.ai"
|
||||
],
|
||||
"categories": {
|
||||
"platform": {
|
||||
"label": "Platform",
|
||||
"color": "#0066FF",
|
||||
"bg": "#e8f0ff"
|
||||
},
|
||||
"technical": {
|
||||
"label": "Technical",
|
||||
"color": "#00a550",
|
||||
"bg": "#e6f7ee"
|
||||
},
|
||||
"payment": {
|
||||
"label": "Payment",
|
||||
"color": "#7b2fff",
|
||||
"bg": "#f0e8ff"
|
||||
},
|
||||
"legal": {
|
||||
"label": "Legal",
|
||||
"color": "#e8660a",
|
||||
"bg": "#fff0e6"
|
||||
},
|
||||
"core": {
|
||||
"label": "Core",
|
||||
"color": "#1d1d1f",
|
||||
"bg": "#f5f5f7"
|
||||
},
|
||||
"amos": {
|
||||
"label": "AMOS Engine",
|
||||
"color": "#ff3366",
|
||||
"bg": "#ffe8f0"
|
||||
},
|
||||
"landvex": {
|
||||
"label": "Landvex",
|
||||
"color": "#0066FF",
|
||||
"bg": "#e8f0ff"
|
||||
},
|
||||
"quixzoom": {
|
||||
"label": "quiXzoom",
|
||||
"color": "#00a550",
|
||||
"bg": "#e6f7ee"
|
||||
},
|
||||
"product": {
|
||||
"label": "Product",
|
||||
"color": "#e8660a",
|
||||
"bg": "#fff0e6"
|
||||
}
|
||||
},
|
||||
"terms": [
|
||||
{
|
||||
"id": "ai-review",
|
||||
"name": "AI review",
|
||||
"category": "technical",
|
||||
"short": "Automated quality and specification check run on every submission before payment is triggered.",
|
||||
"long": "AI review is the first gate a submitted set of photos passes through. The system checks geo-accuracy (is the submission within the mission geofence?), image quality (sharpness, exposure, occlusion), specification compliance (correct angles, required elements present), and EXIF integrity (timestamp within time window, GPS data present and consistent). The result is either an approval — triggering payout — or a rejection with a reason code that the Zoomer can act on.",
|
||||
"context": "A Zoomer submits 6 photos of a road segment. AI review verifies GPS coordinates match the mission location, timestamp falls within the claimed time window, and all required vantage points are covered — typically completing within 90 seconds of upload.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"approval",
|
||||
"rejection",
|
||||
"submission",
|
||||
"approval-rate"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos",
|
||||
"name": "AMOS",
|
||||
"category": "amos",
|
||||
"short": "Adaptive Autonomous Multi-Agent Operating System — the AI capability platform that powers Landvex intelligence products.",
|
||||
"long": "AMOS is not an AI system. It is an AI Capability Platform — a suite of specialised engines that process observations into structured intelligence. AMOS ingests raw field data from quiXzoom, applies computer vision, pattern recognition, and cross-referencing, and produces outputs: indices, scores, change flags, and predictive signals. AMOS is the analytical layer between reality and decisions. It is developed and sold by Landvex Inc, Houston, TX.",
|
||||
"context": "quiXzoom collects 12,000 observations of bridge conditions across Sweden. AMOS processes these into an Infrastructure Risk Index — a single score per bridge that maintenance planners can prioritise by.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"observation",
|
||||
"index",
|
||||
"decision-intelligence",
|
||||
"amos-vision",
|
||||
"amos-identity",
|
||||
"amos-fraud"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-vision",
|
||||
"name": "AMOS Vision",
|
||||
"category": "amos",
|
||||
"short": "Object recognition, anomaly detection, and damage assessment engine.",
|
||||
"long": "AMOS Vision is the computer vision engine that identifies objects, detects anomalies, and assesses damage in visual data. It powers infrastructure inspection, property condition monitoring, and safety compliance checking. The engine can detect cracks, corrosion, vegetation encroachment, and other physical defects from standard photographs.",
|
||||
"context": "A bridge inspection observation shows surface cracking. AMOS Vision measures crack width, length, and pattern, comparing against historical data to determine if the damage is new or progressive.",
|
||||
"contextLabel": "In AMOS",
|
||||
"related": [
|
||||
"amos",
|
||||
"observation",
|
||||
"change-detection",
|
||||
"amos-infrastructure"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-identity",
|
||||
"name": "AMOS Identity",
|
||||
"category": "amos",
|
||||
"short": "Identity verification, document control, liveness detection, and fraud prevention engine.",
|
||||
"long": "AMOS Identity verifies that a person is who they claim to be. It processes government-issued IDs, performs liveness checks, and detects document tampering or synthetic identity fraud. The engine is used for KYC processes, access control, and high-trust verification scenarios.",
|
||||
"context": "A Zoomer completes identity verification by submitting their passport and a selfie. AMOS Identity verifies the document's authenticity and matches the selfie to the ID photo with 99.7% accuracy.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"amos",
|
||||
"kyc",
|
||||
"liveness-check",
|
||||
"identity-verification"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-fraud",
|
||||
"name": "AMOS Fraud",
|
||||
"category": "amos",
|
||||
"short": "Skimming detection, manipulated ATM/utility meter detection, and insurance fraud prevention engine.",
|
||||
"long": "AMOS Fraud detects fraudulent manipulation of physical devices and systems. It identifies skimming devices on ATMs, tampered utility meters, falsified insurance claims, and other physical fraud vectors. The engine combines visual analysis with pattern matching against known fraud signatures.",
|
||||
"context": "A bank receives a quiXzoom observation of an ATM showing a suspicious card reader attachment. AMOS Fraud analyses the image, compares against known skimming device patterns, and flags a high-probability fraud alert within seconds.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"amos-vision",
|
||||
"contradiction"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-infrastructure",
|
||||
"name": "AMOS Infrastructure",
|
||||
"category": "amos",
|
||||
"short": "Road, bridge, pole, sign, and property condition monitoring engine.",
|
||||
"long": "AMOS Infrastructure monitors the built environment: roads, bridges, utility poles, traffic signs, buildings, and other fixed assets. It detects deterioration, damage, and changes over time, producing condition indices and maintenance prioritisation scores. The engine is the core capability behind Landvex's infrastructure intelligence products.",
|
||||
"context": "A municipality receives monthly Infrastructure Condition Index updates for all 400 bridges in their county. AMOS Infrastructure has flagged 12 bridges showing progressive deterioration that requires inspection within 30 days.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"amos-vision",
|
||||
"index",
|
||||
"change-detection"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-safety",
|
||||
"name": "AMOS Safety",
|
||||
"category": "amos",
|
||||
"short": "PPE detection, workplace hazard identification, and risk assessment engine.",
|
||||
"long": "AMOS Safety analyses visual data to detect personal protective equipment (PPE) compliance, identify workplace hazards, and assess safety risks. It can detect missing hard hats, unsafe scaffolding, blocked emergency exits, and other safety violations from standard photographs.",
|
||||
"context": "A construction site manager receives daily safety observations from quiXzoom. AMOS Safety has flagged 3 instances of missing fall protection and 1 blocked fire exit across 50 observations — enabling immediate corrective action.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"amos-vision",
|
||||
"risk-assessment"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-inspection",
|
||||
"name": "AMOS Inspection",
|
||||
"category": "amos",
|
||||
"short": "General quality control and industrial inspection engine.",
|
||||
"long": "AMOS Inspection provides general-purpose quality control and inspection capabilities for industrial applications. It detects manufacturing defects, assembly errors, and quality deviations from specification. The engine is configurable for specific industry standards and can be trained on custom defect libraries.",
|
||||
"context": "A manufacturer uses AMOS Inspection to quality-check 10,000 units per day. The engine detects surface scratches, dimensional deviations, and colour mismatches with 99.2% accuracy, reducing manual inspection workload by 80%.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"amos-vision",
|
||||
"quality-score"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-compliance",
|
||||
"name": "AMOS Compliance",
|
||||
"category": "amos",
|
||||
"short": "Regulatory control, documentation verification, and compliance checking engine.",
|
||||
"long": "AMOS Compliance verifies that assets, processes, and documentation meet regulatory requirements. It checks for required signage, accessibility features, fire safety equipment, and other compliance markers. The engine maintains up-to-date regulatory rule sets for multiple jurisdictions.",
|
||||
"context": "A retail chain uses AMOS Compliance to verify that all 200 stores meet accessibility requirements. The engine has flagged 15 stores missing required wheelchair ramps and 8 stores with inadequate emergency lighting.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"amos-inspection",
|
||||
"regulatory"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-reality-engine",
|
||||
"name": "AMOS Reality Engine",
|
||||
"category": "amos",
|
||||
"short": "Verifies that an image shows actual reality, not manipulated or synthetic content.",
|
||||
"long": "The AMOS Reality Engine detects image manipulation, deepfakes, and synthetic content. It analyses EXIF data, pixel-level artifacts, and lighting consistency to verify that an observation depicts real physical reality. This is critical for legal admissibility and insurance validity.",
|
||||
"context": "An insurance claim includes photos of storm damage. The AMOS Reality Engine verifies that the images are authentic, unmanipulated, and captured at the claimed location and time — providing the foundation for claims processing.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"amos",
|
||||
"exif",
|
||||
"confidence-score"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-change-engine",
|
||||
"name": "AMOS Change Engine",
|
||||
"category": "amos",
|
||||
"short": "Detects changes between observations over time.",
|
||||
"long": "The AMOS Change Engine compares current observations against historical baselines to identify additions, removals, and modifications. It powers change detection at scale, enabling proactive maintenance and early problem identification. The engine operates across multiple time scales from hours to years.",
|
||||
"context": "A property manager receives a quarterly change report showing that 3 buildings have new roof damage, 2 have added unauthorized structures, and 1 has removed safety equipment — all flagged automatically by the Change Engine.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"change-detection",
|
||||
"contradiction"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-risk-engine",
|
||||
"name": "AMOS Risk Engine",
|
||||
"category": "amos",
|
||||
"short": "Converts observations into risk scores and prioritisation rankings.",
|
||||
"long": "The AMOS Risk Engine transforms raw observations into actionable risk assessments. It combines condition data, environmental factors, historical failure rates, and consequence analysis to produce risk scores that prioritise maintenance and intervention. Risk scores are normalised and comparable across asset types and geographies.",
|
||||
"context": "A county's 400 bridges are ranked by risk score. The top 10 highest-risk bridges (scores above 85) receive immediate inspection orders, while the bottom 200 (scores below 30) are scheduled for routine maintenance.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"index",
|
||||
"confidence-score",
|
||||
"decision-intelligence"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-evidence-engine",
|
||||
"name": "AMOS Evidence Engine",
|
||||
"category": "amos",
|
||||
"short": "Creates traceable evidence chains for audit, insurance, and legal proceedings.",
|
||||
"long": "The AMOS Evidence Engine maintains an immutable, auditable chain of custody for every observation. It records capture metadata, processing history, analysis results, and access logs in a tamper-evident format suitable for legal admissibility. Evidence packages include cryptographic hashes and timestamps.",
|
||||
"context": "An insurance dispute reaches court. The AMOS Evidence Engine produces a complete evidence package showing: when the observation was captured, by which device, with what GPS accuracy, what AI analysis was performed, and who accessed the data — all cryptographically signed.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"observation",
|
||||
"exif",
|
||||
"confidence-score"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "amos-prediction-engine",
|
||||
"name": "AMOS Prediction Engine",
|
||||
"category": "amos",
|
||||
"short": "Estimates likely future development based on current observations and historical patterns.",
|
||||
"long": "The AMOS Prediction Engine uses historical data, environmental factors, and deterioration models to forecast future asset conditions. It estimates remaining useful life, predicts failure probabilities, and identifies optimal intervention timing. Predictions include confidence intervals and are updated as new observations arrive.",
|
||||
"context": "AMOS Prediction Engine forecasts that Bridge 247 will reach critical condition (Index below 40) in 18 months based on current deterioration rate and traffic load. The recommendation: schedule major maintenance within 12 months to avoid emergency closure.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"index",
|
||||
"amos-risk-engine"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "quixzoom",
|
||||
"name": "quiXzoom",
|
||||
"category": "quixzoom",
|
||||
"short": "Global field data collection platform — 'Uber fast för foton'.",
|
||||
"long": "quiXzoom is a standalone product and business with its own brand, separate from AAMOS. It is a marketplace where anyone can take photo missions and earn money. Orderers post missions; Zoomers (anyone) complete them and get paid. quiXzoom uses AAMOS infrastructure under the hood but is never presented as 'AAMOS'. The platform provides verified, geotagged, timestamped field observations on demand.",
|
||||
"context": "A municipality needs photos of 50 road segments after a storm. They post missions on quiXzoom. Within 2 hours, local Zoomers have claimed all missions, captured the required photos, and submitted for AI review. The municipality receives verified observations with GPS and timestamps.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"zoomer",
|
||||
"mission",
|
||||
"observation",
|
||||
"amos"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "landvex",
|
||||
"name": "Landvex",
|
||||
"category": "landvex",
|
||||
"short": "Global intelligence infrastructure company — builds decision intelligence from field observations.",
|
||||
"long": "Landvex Inc (Houston, TX) develops and sells IT products powered by AMOS engines. Landvex does not sell AI — it sells intelligence based on AMOS. The company combines quiXzoom field data, AMOS analysis, and domain expertise into decision intelligence products for infrastructure owners, governments, insurers, and enterprises. Landvex has operational presence in Europe and North America.",
|
||||
"context": "A property investor uses Landvex's Neighbourhood Quality Index to compare three potential acquisitions. The index combines infrastructure condition, safety observations, and commercial activity data into a single comparable score.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"quixzoom",
|
||||
"decision-intelligence",
|
||||
"index"
|
||||
],
|
||||
"domains": [
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "observation",
|
||||
"name": "Observation",
|
||||
"category": "core",
|
||||
"short": "A verified field record captured through quiXzoom — the fundamental unit of reality data.",
|
||||
"long": "An observation is not a photo. It is a structured, verified record of physical reality at a specific place and time. Every observation includes: geolocation (GPS coordinates with accuracy estimate), timestamp (when it was captured), media (images or video), and metadata (device, conditions, mission context). Observations are quality-checked by AI before entering the dataset. They are the raw material from which all Landvex intelligence is derived.",
|
||||
"context": "A Zoomer captures 6 images of a road segment. Each image becomes part of an observation that includes GPS, timestamp, and mission context. AI review verifies the observation before it enters the dataset.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission",
|
||||
"zoomer",
|
||||
"amos",
|
||||
"reality-signal"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "decision-intelligence",
|
||||
"name": "Decision Intelligence",
|
||||
"category": "core",
|
||||
"short": "Actionable recommendations derived from observations through AMOS — the end product of the Landvex ecosystem.",
|
||||
"long": "Decision Intelligence is not data. It is not reports. It is the answer to a specific question: Which asset should I repair first? Where should I open my next store? Which claims are fraudulent? Landvex delivers Decision Intelligence by combining quiXzoom observations, AMOS analysis, and domain expertise into structured recommendations that directly enable decisions. Every output includes a confidence score and traceable source data.",
|
||||
"context": "A municipality receives a City Health Index of 71 for Norrmalm, down from 78 six months ago. The Decision Intelligence includes: specific deterioration patterns, contributing factors, recommended actions, and confidence intervals. The planner decides which streets to prioritise for maintenance.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"index",
|
||||
"confidence-score",
|
||||
"amos",
|
||||
"control-intelligence"
|
||||
],
|
||||
"domains": [
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "control-intelligence",
|
||||
"name": "Control Intelligence",
|
||||
"category": "core",
|
||||
"short": "Descriptive intelligence that tells you the current state of your physical assets — what is, not what to do.",
|
||||
"long": "Control Intelligence answers the question: 'What is the current condition of my assets?' It is the foundational layer of insight derived from observations, describing reality as it exists today: which bridges are sound, which buildings have damage, which roads need repair. Control Intelligence is objective, measurable, and verifiable. It is the raw material from which Decision Intelligence is forged — you cannot decide what to do until you know what is.",
|
||||
"context": "A municipality receives Control Intelligence showing that 12% of its road bridges have surface cracking, 3% have structural concerns, and 85% are in good condition. This descriptive baseline is the starting point for all maintenance and investment decisions.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"decision-intelligence",
|
||||
"observation",
|
||||
"amos",
|
||||
"index"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "index",
|
||||
"name": "Index",
|
||||
"category": "core",
|
||||
"short": "A normalised score (0–100) derived from thousands of observations, representing the condition, risk, or quality of an asset or area.",
|
||||
"long": "An Index is the primary output of the AMOS analysis engine — a single number that summarises complex, multi-dimensional observation data into an intuitive, comparable metric. Different indices serve different purposes: the City Health Index measures overall infrastructure condition; the Infrastructure Risk Index quantifies probability of failure; the Commercial Opportunity Index identifies high-potential investment areas. Indices are computed from aggregated observations, weighted by confidence scores, and updated continuously as new observations flow in.",
|
||||
"context": "A city's Road Condition Index drops from 72 to 58 over six months. AMOS traces the decline to increased pothole observations in the northern district. The municipality uses this Index to justify a €2M resurfacing budget — with the Index projected to return to 75 post-works.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"observation",
|
||||
"confidence-score",
|
||||
"decision-intelligence"
|
||||
],
|
||||
"domains": [
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "confidence-score",
|
||||
"name": "Confidence Score",
|
||||
"category": "core",
|
||||
"short": "A statistical measure of certainty attached to an observation or analysis output, expressed as a percentage.",
|
||||
"long": "The Confidence Score quantifies how certain the system is about a specific observation or derived insight. It is computed from multiple signals: EXIF integrity, GPS accuracy, image clarity, cross-validation against historical data, and agreement with other observations of the same asset. A high confidence score (90%+) indicates strong reliability; a low score triggers manual review or additional observation requests. Confidence scores are essential for decision-making — they tell the customer not just what was observed, but how much to trust it.",
|
||||
"context": "A bridge inspection observation receives a 94% confidence score based on sharp imagery, precise GPS, and consistency with the previous inspection. An insurer uses this high-confidence observation to approve a maintenance claim without sending an engineer.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"observation",
|
||||
"amos",
|
||||
"index",
|
||||
"contradiction"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "contradiction",
|
||||
"name": "Contradiction",
|
||||
"category": "core",
|
||||
"short": "A mismatch between observed reality and expected or previously recorded reality — a signal that something has changed or requires attention.",
|
||||
"long": "A Contradiction is flagged when an observation deviates significantly from the expected state: a building that was intact now shows damage, a road that was clear now has a sinkhole, or an asset that was present is now missing. Contradictions are not errors — they are valuable signals. They trigger alerts, escalate priority, and often indicate the most urgent decisions a customer must make. The Contradiction engine cross-references observations against historical data, design specifications, and regulatory baselines.",
|
||||
"context": "A quarterly observation of a commercial roof shows new water staining not present in the previous observation. AMOS flags this as a Contradiction, alerting the property manager to schedule repairs before the rainy season — preventing a €50,000 claim.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"observation",
|
||||
"amos",
|
||||
"confidence-score",
|
||||
"reality-signal"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "reality-signal",
|
||||
"name": "Reality Signal",
|
||||
"category": "core",
|
||||
"short": "A measurable, verifiable observation that describes a specific aspect of the physical world.",
|
||||
"long": "A Reality Signal is any observation that carries information about the state of physical reality: a photo of a cracked bridge deck, a GPS-tagged image of flood damage, a timestamped record of a building's facade. Reality Signals are the raw inputs to the Analysis Layer. They are distinguished from synthetic or inferred data by their direct connection to physical measurement — a Zoomer was there, the camera captured light from the actual scene, the GPS recorded the actual coordinates. Reality Signals are the antidote to assumptions and desk-based estimates.",
|
||||
"context": "An insurer receives a Reality Signal showing hail damage to a factory roof — captured 6 hours after the storm, with GPS confirming the location, timestamp proving immediacy, and image quality enabling damage severity assessment. This Reality Signal replaces the traditional adjuster visit.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"observation",
|
||||
"reality-layer",
|
||||
"confidence-score",
|
||||
"amos"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "reality-layer",
|
||||
"name": "Reality Layer",
|
||||
"category": "core",
|
||||
"short": "The physical world itself — the assets, infrastructure, and environments that the ecosystem observes, analyses, and optimises.",
|
||||
"long": "The Reality Layer is everything physical: roads, bridges, buildings, coastlines, forests, power lines, water pipes. It is the domain that exists independently of any observation system — the ground truth that the ecosystem seeks to understand and improve. The Reality Layer is not digital; it is the actual world that customers own, manage, insure, and invest in. Every observation is a measurement of the Reality Layer; every index is a summary of its state; every decision is an intervention upon it.",
|
||||
"context": "A city's Reality Layer comprises 1,200 km of roads, 400 bridges, 50 tunnels, and 2,000 public buildings. The ecosystem's purpose is to create a complete, accurate, up-to-date digital understanding of this Reality Layer — enabling better decisions about maintenance, investment, and risk.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"observation-layer",
|
||||
"analysis-layer",
|
||||
"decision-layer",
|
||||
"reality-signal"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "observation-layer",
|
||||
"name": "Observation Layer",
|
||||
"category": "core",
|
||||
"short": "The field data collection tier where Zoomers capture verified observations of physical assets and infrastructure.",
|
||||
"long": "The Observation Layer is the foundation of the ecosystem — the interface between physical reality and digital intelligence. It encompasses the quiXzoom mobile app, Zoomer network, mission management system, and AI review pipeline. Its purpose is to produce high-quality, trustworthy observations at scale. The Observation Layer guarantees data integrity through geo-tagging, timestamp verification, and automated quality checks. Without a robust Observation Layer, everything above it — analysis, indices, decisions — is built on sand.",
|
||||
"context": "The Observation Layer deploys 500 Zoomers across a metropolitan area to capture quarterly building condition observations. Each observation is verified for GPS accuracy, image quality, and specification compliance before entering the Analysis Layer.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"observation",
|
||||
"zoomer",
|
||||
"reality-layer",
|
||||
"analysis-layer"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "analysis-layer",
|
||||
"name": "Analysis Layer",
|
||||
"category": "core",
|
||||
"short": "The processing tier where raw observations are transformed into structured intelligence by AMOS.",
|
||||
"long": "The Analysis Layer sits between the Observation Layer and the Decision Layer. Here, AMOS ingests verified field observations and applies analytical models: object detection, condition scoring, change analysis, pattern recognition, and anomaly detection. The outputs are normalised indices, confidence scores, and contradiction flags. The Analysis Layer is where data becomes insight — where thousands of individual observations are synthesised into coherent, actionable intelligence.",
|
||||
"context": "A thousand roof observations from across a property portfolio enter the Analysis Layer. AMOS identifies that 8% show hail damage, 2% have gutter degradation, and 90% are unchanged. The Analysis Layer outputs a Property Condition Index with regional breakdowns and recommended inspection priorities.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"amos",
|
||||
"observation-layer",
|
||||
"decision-layer",
|
||||
"reality-layer"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "decision-layer",
|
||||
"name": "Decision Layer",
|
||||
"category": "core",
|
||||
"short": "The top tier of the ecosystem where structured intelligence is translated into actionable decisions for customers.",
|
||||
"long": "The Decision Layer is where Landvex delivers intelligence products to end customers. It takes the indices, scores, and contradictions from the Analysis Layer and contextualises them for specific use cases: prioritising maintenance budgets, assessing insurance risk, evaluating property investments, ensuring regulatory compliance. The Decision Layer is customer-facing — it speaks the language of business, not technology. Every output is designed to answer one question: 'What decision does this help me make?'",
|
||||
"context": "A property investor uses the Decision Layer to compare three potential acquisitions. The layer delivers a Neighbourhood Quality Index, Infrastructure Risk Score, and Commercial Opportunity Index for each — enabling a data-driven purchase decision in minutes rather than weeks.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"landvex",
|
||||
"analysis-layer",
|
||||
"decision-intelligence",
|
||||
"index"
|
||||
],
|
||||
"domains": [
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "zoomer",
|
||||
"name": "Zoomer",
|
||||
"category": "quixzoom",
|
||||
"short": "A verified field data collector on the quiXzoom platform — an individual who claims missions, captures on-location photography, and earns compensation per approved submission.",
|
||||
"long": "Zoomers are the supply side of the quiXzoom marketplace. Anyone with a compatible smartphone, a willingness to be verified (KYC), and a linked bank account can become a Zoomer. Zoomers work independently, on their own schedule, within their chosen zone. They earn per approved submission — there is no hourly pay, no minimum hours, and no obligation to work any particular number of missions. Zoomers progress through tiers (Supplementary → Active → Professional) as they build volume and quality.",
|
||||
"context": "A freelance photographer becomes a quiXzoom Zoomer, completing identity verification and bank account setup in 10 minutes. They begin claiming road survey and building inspection missions near their home, earning €8–15 per approved submission. Within 6 weeks, their consistent quality and volume qualify them for Active tier.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission",
|
||||
"tier",
|
||||
"approval-rate",
|
||||
"kyc",
|
||||
"payout"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "mission",
|
||||
"name": "Mission",
|
||||
"category": "quixzoom",
|
||||
"short": "A paid photography assignment with a defined location, scope, and compensation, published by an orderer and claimed by a Zoomer.",
|
||||
"long": "A mission is the fundamental unit of work on the quiXzoom platform. Each mission has a geographic pin or geofence, a compensation amount, a mission brief (describing what to photograph and how), a time window within which the work must be completed, and a submission specification defining how many photos are required and from which vantage points. Missions may be standard, premium, or surge, and may be single-submission or multi-submission.",
|
||||
"context": "An insurance company creates a mission to document storm damage at a specific address. The mission has a 200-metre geofence, requires 8 photos from specified angles, pays €14, and has a 6-hour time window from claim. A nearby Zoomer sees it in the app, claims it, and completes the documentation.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission-brief",
|
||||
"claim",
|
||||
"submission",
|
||||
"time-window"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "orderer",
|
||||
"name": "Orderer",
|
||||
"category": "quixzoom",
|
||||
"short": "An organisation that creates and funds missions on the quiXzoom platform to obtain field documentation.",
|
||||
"long": "Orderers are the demand side of the quiXzoom marketplace. They can be insurance companies, infrastructure asset owners, public sector bodies, logistics operators, or any organisation with a need for verified on-location photography. Orderers define mission briefs, set compensation, and receive approved submissions via the dashboard or API. Orderers pay the Zoomer compensation plus a platform fee to quiXzoom.",
|
||||
"context": "A Swedish infrastructure authority uses quiXzoom as orderer — creating 50 bridge inspection missions across a county, specifying technical requirements in each mission brief, and receiving standardised submission packages via API integration with their asset management system.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission",
|
||||
"platform-fee",
|
||||
"api",
|
||||
"sla"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "claim",
|
||||
"name": "Claim / Claiming",
|
||||
"category": "quixzoom",
|
||||
"short": "The act of reserving a mission — locking it exclusively for you within a defined time window.",
|
||||
"long": "When a Zoomer claims a mission, the mission is removed from the available pool and assigned exclusively to that Zoomer for the duration of the time window. No other Zoomer can claim the same mission while it is held. If the Zoomer does not submit within the time window, the mission is automatically released back to the pool. Frequent abandonment (claiming without submitting) negatively affects a Zoomer's rating and may trigger restrictions.",
|
||||
"context": "A Zoomer sees a bridge inspection mission 0.8 km away. They tap Claim — the mission is now exclusively theirs for 4 hours. They travel to the location, complete the documentation, and submit. If they don't submit within 4 hours, the mission releases automatically.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"time-window",
|
||||
"mission",
|
||||
"submission",
|
||||
"rating"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "submission",
|
||||
"name": "Submission",
|
||||
"category": "quixzoom",
|
||||
"short": "A completed set of photos uploaded by a Zoomer after executing a mission, submitted for AI review and potential payout.",
|
||||
"long": "A submission is the output of a claimed and completed mission. It consists of the required number of geo-tagged images, their EXIF metadata, a GPS trace (if required), and any optional notes from the Zoomer. Submissions are uploaded through the quiXzoom app and enter the AI review pipeline immediately. The submission event locks the mission as completed — a Zoomer cannot resubmit after an initial submission without contacting support. Submission quality directly impacts approval rate and rating.",
|
||||
"context": "A Zoomer completes a 6-photo road condition survey and taps Submit. The submission package (images, EXIF, GPS trace) is uploaded to S3 and enters AI review. Within 90 seconds, the Zoomer receives an in-app approval notification and their €10 earnings are queued for payout.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission",
|
||||
"ai-review",
|
||||
"approval",
|
||||
"rejection"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "approval",
|
||||
"name": "Approval",
|
||||
"category": "quixzoom",
|
||||
"short": "A positive outcome from AI review, confirming a submission meets all mission requirements and triggering Zoomer payout.",
|
||||
"long": "When AI review determines that a submission satisfies all specification, quality, and location requirements for a mission, the submission is marked as Approved. This event is the trigger for payout to the Zoomer and for delivery of the submission package to the orderer. Approval also counts positively toward the Zoomer's approval rate and rating.",
|
||||
"context": "A Zoomer submits a marina documentation mission. AI review approves the submission within 2 minutes; the Zoomer sees a confirmation in-app and their €12 earnings are queued for the next payout cycle. The orderer receives the submission package via webhook.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"rejection",
|
||||
"approval-rate",
|
||||
"ai-review",
|
||||
"payout"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "rejection",
|
||||
"name": "Rejection",
|
||||
"category": "quixzoom",
|
||||
"short": "A negative outcome from AI review, indicating a submission does not meet mission requirements — no payout is issued for rejected submissions.",
|
||||
"long": "Rejections occur when AI review identifies one or more disqualifying issues: location mismatch (GPS outside geofence), timestamp violation (submitted outside time window), image quality failure (blurred, overexposed, or heavily occluded), specification miss (required element absent), or EXIF anomaly (GPS data absent or inconsistent). Every rejection includes a specific reason code that the Zoomer can view in-app. Zoomers can review rejection reasons to understand and correct issues on future missions.",
|
||||
"context": "A Zoomer submits 6 photos but one required angle (the drainage outlet) is missing. AI review flags a specification miss and rejects the submission with reason code SPEC_INCOMPLETE. The Zoomer's approval rate decreases by one event, and no payout is issued for this submission.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"approval",
|
||||
"approval-rate",
|
||||
"ai-review"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "approval-rate",
|
||||
"name": "Approval rate",
|
||||
"category": "quixzoom",
|
||||
"short": "The percentage of submitted missions that pass AI review, calculated over a rolling 30-day window.",
|
||||
"long": "Approval rate is the primary quality signal on the quiXzoom platform. It is calculated as approved submissions divided by total submissions over the preceding 30 days. A Zoomer's approval rate directly determines their tier eligibility and access to premium and surge missions. Professional tier requires maintaining above 92% approval; Active tier requires above 85%. Zoomers below 70% receive coaching and may be temporarily restricted from claiming new missions.",
|
||||
"context": "A Zoomer with 38 approvals and 2 rejections out of 40 submissions in the last 30 days has a 95% approval rate. This qualifies them for Professional tier and unlocks access to premium infrastructure missions paying up to €30 per submission.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"rejection",
|
||||
"tier",
|
||||
"premium-mission",
|
||||
"rating"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "tier",
|
||||
"name": "Tier",
|
||||
"category": "quixzoom",
|
||||
"short": "A Zoomer's platform level — Supplementary, Active, or Professional — reflecting activity volume and quality, and determining mission access.",
|
||||
"long": "The tier system is quiXzoom's primary mechanism for matching mission complexity and compensation to Zoomer reliability. Higher tiers require more submissions per week and higher approval rates; in return, they unlock premium missions, higher compensation caps, priority surge notifications, and specialisation programmes. Tier is calculated on a rolling basis — a Zoomer can move up by improving performance, or drop if activity or quality falls below threshold for a sustained period.",
|
||||
"context": "A Zoomer consistently completing 10 missions/week with a 90% approval rate qualifies for Active tier after 4 qualifying weeks. They now see 30% more missions in their feed and are eligible to apply for a specialisation programme — their per-week earning potential roughly doubles compared to Supplementary.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"supplementary",
|
||||
"active",
|
||||
"professional",
|
||||
"approval-rate"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "supplementary",
|
||||
"name": "Supplementary",
|
||||
"category": "quixzoom",
|
||||
"short": "The entry-level Zoomer tier — 2–4 missions per week — for contributors using quiXzoom as occasional supplemental income.",
|
||||
"long": "Supplementary tier is the starting tier for all new Zoomers. It provides access to standard missions in the Zoomer's zone, with no minimum weekly commitment. Supplementary Zoomers earn the standard mission rates and can access surge missions in their area. To progress to Active tier, a Zoomer must demonstrate sustained volume (8+ missions/week) and maintain an approval rate above 85% over a qualifying period.",
|
||||
"context": "A gig worker uses quiXzoom alongside their other activities — completing 3 missions per week in their neighbourhood while walking their dog or commuting. At Supplementary tier, they access standard missions with no pressure to increase volume; their €30–40/week in earnings is a useful addition to their income mix.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"tier",
|
||||
"active",
|
||||
"professional"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "active",
|
||||
"name": "Active",
|
||||
"category": "quixzoom",
|
||||
"short": "The middle Zoomer tier — 8–12 missions per week with 85%+ approval rate — balancing flexibility with consistent engagement.",
|
||||
"long": "Active tier represents Zoomers who use quiXzoom as a regular supplemental income source. To qualify, a Zoomer must sustain 8+ completed missions per week and maintain an approval rate above 85% over the qualifying window. Active Zoomers access a broader mission pool than Supplementary tier, including most premium mission types and higher-paying specialisation missions. Active tier is the threshold for most specialisation programme eligibility.",
|
||||
"context": "A part-time Zoomer completes 10 missions/week around their regular job, maintaining a 91% approval rate. At Active tier, they access infrastructure survey missions (€15–20) that are invisible to Supplementary Zoomers, and have applied for the Bridge & Civil specialisation programme.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"tier",
|
||||
"supplementary",
|
||||
"professional",
|
||||
"approval-rate"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "professional",
|
||||
"name": "Professional",
|
||||
"category": "quixzoom",
|
||||
"short": "The highest Zoomer tier — 15+ missions per week, 92%+ approval rate — granting access to all mission types including premium and unrestricted surge.",
|
||||
"long": "Professional tier represents quiXzoom's most engaged and highest-quality Zoomers. Qualification requires sustaining 15+ completed missions per week over the qualifying window, maintaining an approval rate above 92%, and having completed identity verification. Professional tier Zoomers receive priority access to new mission types, higher compensation caps, dedicated support, and early access to specialisation programmes. They form the backbone of supply for high-value, time-critical orderer requests.",
|
||||
"context": "A full-time quiXzoom contributor averaging 20 missions/week with a 97% approval rate holds Professional tier. They access premium infrastructure missions paying €25–40, receive surge alerts first, and have the option to take on specialisation certifications for maritime and bridge inspection mission types.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"tier",
|
||||
"active",
|
||||
"supplementary",
|
||||
"approval-rate"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "premium-mission",
|
||||
"name": "Premium mission",
|
||||
"category": "quixzoom",
|
||||
"short": "A high-threshold mission type requiring specific Zoomer qualifications and a high approval rate, offering significantly elevated compensation.",
|
||||
"long": "Premium missions are reserved for experienced, high-performing Zoomers. Qualification requires Professional tier (or Active tier with relevant specialisation) and an approval rate above 92%. These missions typically involve technical infrastructure documentation — bridges, power facilities, maritime assets — with precise specification requirements. Compensation for premium missions reflects both the technical difficulty and the high-value use cases they serve, typically ranging from €20 to €40+ per submission.",
|
||||
"context": "A bridge inspection premium mission paying €28 appears for a Zoomer with a Maritime specialisation and 96% approval rate. Zoomers without Professional tier or the relevant specialisation do not see this mission in their feed — it is filtered to qualified Zoomers only.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"tier",
|
||||
"specialisation",
|
||||
"approval-rate",
|
||||
"surge-mission"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "surge-mission",
|
||||
"name": "Surge mission",
|
||||
"category": "quixzoom",
|
||||
"short": "High-urgency missions deployed after acute events — storms, floods, accidents — offering 2–5× standard compensation for rapid on-site documentation.",
|
||||
"long": "Surge missions are created by orderers (typically insurers or infrastructure managers) in response to time-critical events requiring rapid field documentation. They carry elevated compensation to incentivise Zoomers to prioritise them and accept shorter time windows. Surge alerts are pushed as priority notifications to all Zoomers in the affected zone, with Professional tier Zoomers notified first. Surge missions typically have tighter specification requirements and stricter AI review thresholds given their legal and claims significance.",
|
||||
"context": "A severe storm hits coastal Sweden. An insurer activates 40 surge missions across 12 postcodes within 20 minutes of the event. Zoomers in those zones receive priority push notifications — the missions pay €35 each (vs. €12 standard) with a 3-hour time window. 38 of 40 missions are claimed within 45 minutes.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"premium-mission",
|
||||
"mission",
|
||||
"tier",
|
||||
"sla"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "specialisation",
|
||||
"name": "Specialisation",
|
||||
"category": "quixzoom",
|
||||
"short": "A certified competency that unlocks access to specific advanced mission types requiring domain-specific knowledge or technical skill.",
|
||||
"long": "Specialisations are earned through a training and assessment programme administered within the quiXzoom app. Each specialisation covers the technical requirements, safety considerations, and documentation standards for a specific mission domain. Available specialisations include Maritime (marina and harbour documentation), Bridge & Civil (infrastructure inspection), Energy Infrastructure (substations, wind turbines), and Retail Audit. Completing a specialisation assessment unlocks the corresponding premium mission category in the Zoomer's feed.",
|
||||
"context": "A Zoomer living near a large marina completes the Maritime specialisation — a 45-minute in-app training covering mooring documentation, vessel identification standards, and marina facility photography requirements. They now see maritime premium missions paying €20–35 in their area, which are invisible to non-specialised Zoomers.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"premium-mission",
|
||||
"tier",
|
||||
"mission-brief"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "time-window",
|
||||
"name": "Time window",
|
||||
"category": "quixzoom",
|
||||
"short": "The duration a Zoomer has to complete and submit a mission after claiming it — after which the mission auto-releases back to the pool.",
|
||||
"long": "Time windows are set per mission type and range from 1 hour (urgent surge missions in dense urban areas) to 24 hours (rural or low-urgency surveys). The clock starts when the Zoomer claims the mission. If no submission is received before the window expires, the mission is automatically un-claimed and becomes available to other Zoomers. Frequent time window expiries (claiming without submitting) negatively affect a Zoomer's rating and may trigger temporary claiming restrictions.",
|
||||
"context": "A storm damage survey mission has a 4-hour time window. A Zoomer claims it at 10:00. They have until 14:00 to travel to the location, photograph the damage, and submit. At 13:58, they upload the final photo — 2 minutes before expiry. Submission is accepted; time window is satisfied.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"claim",
|
||||
"mission",
|
||||
"submission",
|
||||
"surge-mission"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "zone",
|
||||
"name": "Zone",
|
||||
"category": "quixzoom",
|
||||
"short": "The geographic radius a Zoomer sets as their operational area, determining which missions appear in their mission feed.",
|
||||
"long": "Each Zoomer configures one or more zones — defined as a radius around a point (their home, workplace, or preferred operating area). The quiXzoom app displays missions within the Zoomer's active zone. Zoomers can set multiple zones, adjust zone radius, and switch between zones as needed. Zone configuration is used by quiXzoom to target mission notifications — if a surge mission is activated within a Zoomer's zone, they are alerted immediately. Zones do not restrict where a Zoomer can physically travel; they filter the mission feed for relevance.",
|
||||
"context": "A Zoomer sets a 5km zone around their home in Göteborg and a 3km zone around their office. They see missions within both zones in their feed. On a day when they're travelling to Malmö, they temporarily set an additional zone there to pick up missions during their visit.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission-density",
|
||||
"mission",
|
||||
"surge-mission"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "mission-density",
|
||||
"name": "Mission density",
|
||||
"category": "quixzoom",
|
||||
"short": "The number of active missions available per geographic area — a key factor in a Zoomer's earning potential by location.",
|
||||
"long": "Mission density varies significantly between urban and rural areas, between regions, and over time. High mission density zones (dense urban areas, coastal regions with infrastructure) allow Zoomers to complete more missions per hour of activity — increasing hourly earnings. Mission density is influenced by orderer activity in the area and by platform growth. Zoomers can view mission density maps to understand the earning environment in different zones before setting their zone preferences.",
|
||||
"context": "Stockholm's inner city shows 23 active missions within a 5km radius. A nearby suburb shows 3. A Zoomer choosing their zone setting can use mission density data to maximise their available mission volume per session.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"zone",
|
||||
"mission",
|
||||
"tier"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "multi-submission-mission",
|
||||
"name": "Multi-submission mission",
|
||||
"category": "quixzoom",
|
||||
"short": "A mission type where multiple Zoomers can submit, with compensation decreasing for each successive approved submission.",
|
||||
"long": "Multi-submission missions are used by orderers who want several independent documentation sets of the same location — typically for comparison, validation, or higher confidence. The first Zoomer to submit receives the highest compensation; subsequent approved submissions receive progressively lower amounts. The orderer sets the maximum number of submissions they will accept and the compensation schedule. Multi-submission missions remain claimable by additional Zoomers until the orderer's submission limit is reached.",
|
||||
"context": "An orderer creates a multi-submission mission for a flood-affected road segment, accepting 3 submissions at €18 / €12 / €8. Three different Zoomers claim and submit independently — the orderer receives three distinct photographic records of the same location, useful for triangulating damage assessment.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission",
|
||||
"submission",
|
||||
"surge-mission",
|
||||
"premium-mission"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "payout",
|
||||
"name": "Payout",
|
||||
"category": "payment",
|
||||
"short": "The transfer of earned mission compensation to a Zoomer's linked bank account, triggered automatically by submission approval.",
|
||||
"long": "Payouts are processed via Stripe Connect and deposited to the Zoomer's linked IBAN. Earnings from approved submissions accumulate in the Zoomer's Stripe Connect balance and are disbursed on a rolling schedule. Payout frequency and minimum threshold are configurable within the app. Payouts require completed identity verification (KYC) and a linked bank account. Zoomers receive an in-app notification and email confirmation for each payout.",
|
||||
"context": "A Zoomer completes 5 missions in a week, earning €72 total. After each approval, earnings add to their Stripe Connect balance. On Friday, their accumulated balance is disbursed to their Dutch IBAN via SEPA — arriving as a single bank transfer with a quiXzoom reference.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"disbursement",
|
||||
"stripe-connect",
|
||||
"iban",
|
||||
"kyc"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "disbursement",
|
||||
"name": "Disbursement",
|
||||
"category": "payment",
|
||||
"short": "The technical transfer of earned funds from the platform escrow to a Zoomer's linked bank account.",
|
||||
"long": "Disbursement is the formal payment term for the outbound transfer of earned mission compensation. In quiXzoom's architecture, approved submission earnings accumulate in a Stripe Connect account (held on behalf of the Zoomer), and disbursements are processed on a rolling basis to the Zoomer's linked IBAN. Disbursements are distinct from the mission approval event — there may be a short settlement window between approval and disbursement depending on Stripe's payout schedule.",
|
||||
"context": "A Zoomer's mission is approved at 14:00 on a Tuesday. Their earnings are added to their Stripe Connect balance immediately, and the disbursement to their bank account is processed as part of the next scheduled payout run — typically within 1–2 business days.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"payout",
|
||||
"stripe-connect",
|
||||
"iban",
|
||||
"sepa"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "platform-fee",
|
||||
"name": "Platform fee",
|
||||
"category": "quixzoom",
|
||||
"short": "The service fee paid by orderers to quiXzoom on top of Zoomer compensation, covering platform operations and AI review.",
|
||||
"long": "The platform fee is charged to the orderer and covers quiXzoom's infrastructure, AI review system, Zoomer management, customer support, and margin. Zoomers receive their full stated mission compensation — the platform fee is paid by the orderer separately and does not come from Zoomer earnings. Platform fees are calculated as a percentage of mission compensation, with enterprise volume pricing available for high-volume orderers.",
|
||||
"context": "An orderer creates a mission paying the Zoomer €12. quiXzoom's platform fee adds an additional amount on top — the orderer pays the total; the Zoomer receives exactly €12 upon approval. The platform fee structure is transparent and set out in the orderer's service agreement.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"orderer",
|
||||
"payout",
|
||||
"mission",
|
||||
"sla"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "stripe",
|
||||
"name": "Stripe",
|
||||
"category": "payment",
|
||||
"short": "A global payments platform — quiXzoom's underlying payment infrastructure provider for all Zoomer payouts and orderer billing.",
|
||||
"long": "Stripe is a regulated payment institution used by millions of platforms worldwide. quiXzoom uses two Stripe products: Stripe Payments for orderer billing, and Stripe Connect for Zoomer payout disbursements. Stripe holds regulatory authorisations across the US, EU, and other jurisdictions, which is why AML/KYC compliance requirements flow through Stripe Connect's onboarding process. Stripe's infrastructure provides the payment settlement, fraud detection, and payout mechanics that quiXzoom's marketplace depends on.",
|
||||
"context": "When a Zoomer adds their bank account in the quiXzoom app, they are creating a Stripe Connect account under quiXzoom's platform. Stripe is the regulated entity that actually moves money from quiXzoom's orderer receipts to Zoomer IBANs — quiXzoom orchestrates the process but Stripe executes the regulated payment flows.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"stripe-connect",
|
||||
"kyc",
|
||||
"payout",
|
||||
"iban"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "stripe-connect",
|
||||
"name": "Stripe Connect",
|
||||
"category": "payment",
|
||||
"short": "Stripe's multi-party payment product that enables quiXzoom to distribute earned mission compensation directly to individual Zoomer bank accounts.",
|
||||
"long": "Stripe Connect is designed specifically for marketplace and platform models where a platform collects money from one party (orderers) and distributes it to another (Zoomers). It handles the regulated aspects of marketplace payments: identity verification (KYC), payout scheduling, tax form collection (where required), currency conversion, and compliance with local financial regulations. Each Zoomer has a Stripe Connect account created during onboarding, linked to their verified bank account.",
|
||||
"context": "During onboarding, a Zoomer completes a Stripe Connect flow: they enter their name, date of birth, address, and IBAN, and complete identity verification. From this point, every approved submission triggers an automatic credit to their Stripe Connect balance, which disburses to their bank account on the configured schedule.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"stripe",
|
||||
"kyc",
|
||||
"payout",
|
||||
"iban",
|
||||
"sepa"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "kyc",
|
||||
"name": "KYC",
|
||||
"category": "payment",
|
||||
"short": "Know Your Customer — the regulatory process of verifying the identity of individuals before processing financial transactions on their behalf.",
|
||||
"long": "KYC is a standard compliance process required by AML regulation for payment platforms and financial services providers. In the quiXzoom context, KYC is performed by a regulated third-party identity verification provider (not by quiXzoom internally) on behalf of Stripe Connect. The process collects a government-issued ID and liveness check result, which are verified against government databases and fraud watchlists. KYC data is held by the verification provider, not by quiXzoom — quiXzoom only receives a pass/fail status.",
|
||||
"context": "Before a Zoomer can withdraw their first earnings, they are prompted to complete KYC. The 3–5 minute in-app flow captures their passport and a selfie, and is processed by the KYC provider. quiXzoom receives confirmation of verified status — not the underlying documents — and the payout queue is unblocked.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"aml",
|
||||
"identity-verification",
|
||||
"liveness-check",
|
||||
"stripe-connect"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "aml",
|
||||
"name": "AML",
|
||||
"category": "legal",
|
||||
"short": "Anti-Money Laundering — the regulatory framework that requires payment platforms to verify the identity of anyone receiving funds.",
|
||||
"long": "AML regulation obliges financial institutions and payment platforms to implement controls that prevent the platform from being used to launder illegally obtained money. In practice, this means platforms like Stripe — which powers quiXzoom's payouts — must verify Zoomer identity (KYC) before processing disbursements. AML requirements vary by jurisdiction but are broadly harmonised across the EU under the Anti-Money Laundering Directives (AMLD).",
|
||||
"context": "Before a Zoomer can receive their first payout, they must complete KYC. This is not a quiXzoom policy choice — it is a legal obligation on Stripe (our payment provider) under AML regulation. The process is a one-time requirement.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"kyc",
|
||||
"identity-verification",
|
||||
"stripe-connect",
|
||||
"payout"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "identity-verification",
|
||||
"name": "Identity verification",
|
||||
"category": "payment",
|
||||
"short": "A one-time process confirming a Zoomer's identity with a government-issued ID and liveness check, required before the first payout.",
|
||||
"long": "Identity verification is a legal requirement under AML regulation for any payment platform processing disbursements. For quiXzoom, it involves submitting a government-issued photo ID (passport, national ID card, or driving licence) and a liveness check (selfie). The process is handled by a regulated KYC provider — not by quiXzoom directly — and typically completes within 1 hour. Identity verification is a one-time requirement: once verified, Zoomers never repeat it unless their details change materially.",
|
||||
"context": "A new Zoomer completes their first 3 missions before being prompted to verify identity before their first payout. They photograph their passport and complete a 15-second liveness check in-app. The KYC provider approves the verification within 45 minutes, and the payout is released.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"kyc",
|
||||
"liveness-check",
|
||||
"aml",
|
||||
"stripe-connect"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "liveness-check",
|
||||
"name": "Liveness check",
|
||||
"category": "payment",
|
||||
"short": "A selfie-based verification step that confirms a real, live person is presenting the identity document — not a photo or deepfake.",
|
||||
"long": "Liveness detection uses computer vision to analyse a short selfie capture and confirm it is a genuine live face rather than a printed photo, screen replay, or synthetic image. It is performed as part of the KYC process to prevent identity fraud — specifically to stop bad actors using stolen ID documents paired with someone else's photo. Modern liveness checks typically involve a brief instructed motion (e.g. blinking or turning the head) to prove liveness unambiguously.",
|
||||
"context": "During identity verification, a new Zoomer is asked to look at their phone camera and slowly turn their head. The liveness check confirms it's a real person in real time — not someone holding up a printed photo of the account holder. The whole step takes under 15 seconds.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"kyc",
|
||||
"identity-verification",
|
||||
"aml"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "iban",
|
||||
"name": "IBAN",
|
||||
"category": "payment",
|
||||
"short": "International Bank Account Number — the standardised account identifier required for Stripe Connect payout setup in Europe.",
|
||||
"long": "IBAN is the international standard for identifying bank accounts across national borders, defined by ISO 13616. It consists of up to 34 alphanumeric characters: a 2-letter country code, 2 check digits, and the bank-specific account number. IBANs are used throughout SEPA for credit transfers and direct debits. Zoomers in supported SEPA countries link their IBAN during Stripe Connect onboarding — this is the account that will receive payout disbursements.",
|
||||
"context": "A Zoomer in the Netherlands enters their IBAN (NL39 RABO 0300 0652 64) during onboarding. All subsequent payouts from approved missions are disbursed to this account via SEPA credit transfer through Stripe Connect.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"sepa",
|
||||
"stripe-connect",
|
||||
"payout",
|
||||
"disbursement"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "sepa",
|
||||
"name": "SEPA",
|
||||
"category": "payment",
|
||||
"short": "Single Euro Payments Area — the European bank transfer network used for EUR payout disbursements to Zoomers.",
|
||||
"long": "SEPA covers 36 European countries and enables fast, low-cost euro bank transfers using IBAN identifiers. SEPA Credit Transfers (SCT) typically settle within 1 business day; SEPA Instant Credit Transfers (SCT Inst) settle in under 10 seconds where supported. quiXzoom uses Stripe Connect's SEPA infrastructure for EUR disbursements to Zoomers in SEPA-member countries. For Zoomers in countries outside SEPA, SWIFT transfers apply, which may have longer settlement windows and additional fees.",
|
||||
"context": "A Zoomer in Finland has earned €85 across 7 missions. Stripe Connect initiates a SEPA Credit Transfer to their Finnish IBAN — the funds arrive in their bank account within 1 business day at no charge to the Zoomer.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"iban",
|
||||
"stripe-connect",
|
||||
"payout",
|
||||
"swift-bic"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "swift-bic",
|
||||
"name": "SWIFT/BIC",
|
||||
"category": "payment",
|
||||
"short": "Society for Worldwide Interbank Financial Telecommunication / Bank Identifier Code — used for international bank transfers outside the SEPA zone.",
|
||||
"long": "SWIFT (the network) and BIC (the identifier standard) together enable international bank-to-bank transfers for currencies and countries outside SEPA. Zoomers in non-SEPA countries (e.g. the UK post-Brexit for GBP, or non-EU markets quiXzoom may expand to) require a SWIFT/BIC code in addition to their account number for payout setup. SWIFT transfers typically settle in 1–5 business days and may incur intermediary bank fees — terms disclosed to Zoomers during onboarding.",
|
||||
"context": "A Zoomer in Norway (SEPA member) uses IBAN/SEPA for payouts. A Zoomer in the UK (non-SEPA) provides their IBAN and SWIFT/BIC during onboarding — Stripe Connect routes their payout via SWIFT, with a 2–3 business day settlement window.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"sepa",
|
||||
"iban",
|
||||
"stripe-connect",
|
||||
"payout"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "vat",
|
||||
"name": "VAT",
|
||||
"category": "payment",
|
||||
"short": "Value Added Tax — Zoomers are responsible for their own VAT obligations where applicable under local tax law.",
|
||||
"long": "VAT treatment of gig platform income varies by jurisdiction and depends on the Zoomer's status (individual, self-employed, VAT-registered business) and the total income thresholds in their country. In most EU countries, Zoomers earning below the VAT registration threshold are not required to charge or remit VAT. quiXzoom provides transaction records suitable for tax reporting but does not provide tax advice — Zoomers should consult their local tax authority or advisor for their specific obligations. For orderers, quiXzoom's service fees are subject to standard B2B VAT rules.",
|
||||
"context": "A Swedish Zoomer earning €8,000/year from quiXzoom (below Sweden's VAT threshold of ~€32,000 for small businesses) is not required to register for or charge VAT. A Zoomer earning above threshold must register, charge VAT on their services, and remit to Skatteverket — quiXzoom's annual earnings summary facilitates this reporting.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"payout",
|
||||
"stripe-connect",
|
||||
"w9-w8ben",
|
||||
"1099-k"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "w9-w8ben",
|
||||
"name": "W-9 / W-8BEN",
|
||||
"category": "payment",
|
||||
"short": "US IRS tax forms collected by payment platforms from payees to determine tax withholding obligations for US-source income.",
|
||||
"long": "W-9 is completed by US persons (certifying their Tax Identification Number). W-8BEN is completed by non-US individuals certifying their foreign status and claiming any applicable tax treaty benefits. Stripe Connect collects these forms as part of its US regulatory compliance. For Zoomers in the EU, W-8BEN confirms they are not subject to US tax withholding on quiXzoom earnings. This is collected automatically during Stripe Connect onboarding for Zoomers in countries where Stripe requires it.",
|
||||
"context": "A German Zoomer completing Stripe Connect onboarding is prompted to complete a W-8BEN form (takes ~2 minutes). This certifies they are a non-US person and exempts them from US withholding tax on their quiXzoom earnings — as their income is EU-source and subject to German tax law, not US.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"1099-k",
|
||||
"stripe-connect",
|
||||
"vat",
|
||||
"kyc"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "1099-k",
|
||||
"name": "1099-K",
|
||||
"category": "payment",
|
||||
"short": "A US tax document issued by payment platforms to payees who exceed IRS reporting thresholds for payments received through the platform.",
|
||||
"long": "Form 1099-K is issued by payment processors like Stripe to US persons who receive above the IRS reporting threshold (currently $600 per year under new IRS rules, though thresholds may vary). For quiXzoom Zoomers who are US persons, a 1099-K may be issued by Stripe for their annual earnings. Non-US Zoomers (who have completed a W-8BEN) are not subject to 1099-K reporting. Zoomers should retain their quiXzoom earnings summaries for local tax reporting regardless of 1099-K status.",
|
||||
"context": "A US-based Zoomer earning $1,200 from quiXzoom missions in a calendar year will receive a 1099-K from Stripe by January 31 of the following year. This document reports their platform earnings to the IRS and should be used when filing their annual tax return.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"w9-w8ben",
|
||||
"stripe-connect",
|
||||
"vat",
|
||||
"payout"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "gdpr",
|
||||
"name": "GDPR",
|
||||
"category": "legal",
|
||||
"short": "General Data Protection Regulation — the EU framework governing how personal data is collected, stored, and processed.",
|
||||
"long": "GDPR (Regulation (EU) 2016/679) applies to any organisation processing the personal data of EU residents. For quiXzoom, this covers Zoomer identity data, GPS submission metadata, and orderer contact details. Key obligations include lawful basis for processing, data minimisation, purpose limitation, storage limitation, and honouring data subject rights (access, erasure, portability). All quiXzoom data is stored in EU (Stockholm, eu-north-1) to avoid third-country transfer complications.",
|
||||
"context": "A Zoomer in Germany requests a copy of all data quiXzoom holds on them (right of access). quiXzoom must respond within 30 days with a machine-readable export of their submission history, identity data, and payment records — all governed by GDPR Article 15.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"pii",
|
||||
"right-to-erasure",
|
||||
"data-controller",
|
||||
"data-residency"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "pii",
|
||||
"name": "PII",
|
||||
"category": "legal",
|
||||
"short": "Personally Identifiable Information — any data that can directly or indirectly identify a specific individual.",
|
||||
"long": "PII encompasses obvious identifiers (name, email, address, IBAN) as well as indirect identifiers that, in combination, could identify someone (GPS traces, device fingerprints, submission patterns). Under GDPR, quiXzoom treats PII with strict controls: it is collected only where necessary, retained only as long as required, and never shared with orderers in identifiable form. Zoomer submissions are delivered to orderers without attached Zoomer identity — orderers receive field data, not person data.",
|
||||
"context": "When an orderer receives a completed submission, they see the images, GPS coordinates, and timestamp — but not the Zoomer's name, account details, or any identifying information. The Zoomer's identity is pseudonymised in normal operation, with full identification available only under legal process.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"gdpr",
|
||||
"data-controller",
|
||||
"right-to-erasure",
|
||||
"data-residency"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "data-controller",
|
||||
"name": "Data controller",
|
||||
"category": "legal",
|
||||
"short": "The entity that determines the purposes and means of processing personal data — under GDPR, quiXzoom acts as data controller for Zoomer and orderer data.",
|
||||
"long": "Under GDPR, the data controller is the legal entity responsible for deciding why and how personal data is processed. quiXzoom is the data controller for data collected from Zoomers (name, contact details, bank details, submission metadata) and from orderers. As data controller, quiXzoom must maintain a Record of Processing Activities (RoPA), appoint a Data Protection Officer where required, and respond to data subject rights requests within statutory timeframes.",
|
||||
"context": "When a Zoomer exercises their right to erasure, they submit a request to quiXzoom as data controller. quiXzoom is then legally responsible for erasing the Zoomer's personal data from its systems and instructing its data processors (including the KYC provider and Stripe) to do the same.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"data-processor",
|
||||
"gdpr",
|
||||
"pii",
|
||||
"right-to-erasure"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "data-processor",
|
||||
"name": "Data processor",
|
||||
"category": "legal",
|
||||
"short": "An entity that processes personal data on behalf of the data controller, under a Data Processing Agreement (DPA).",
|
||||
"long": "Data processors act on the instructions of the data controller and cannot use the data for their own purposes. quiXzoom's data processors include Stripe (payment processing), the KYC provider (identity verification), and cloud infrastructure providers. Each processor relationship must be governed by a Data Processing Agreement that complies with GDPR Article 28, specifying the scope, nature, purpose, and duration of processing.",
|
||||
"context": "The KYC provider that verifies Zoomer identities is a data processor for quiXzoom. They process identity documents and liveness check data strictly for identity verification purposes, under a DPA — they cannot use that data for their own marketing or analytics.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"data-controller",
|
||||
"gdpr",
|
||||
"kyc"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "data-residency",
|
||||
"name": "Data residency",
|
||||
"category": "legal",
|
||||
"short": "The geographic location where data is stored — quiXzoom stores all data in the EU (Stockholm, eu-north-1).",
|
||||
"long": "Data residency is increasingly important for enterprise customers in regulated industries, who may have legal or policy obligations requiring that data stays within a specific jurisdiction. quiXzoom's infrastructure runs on AWS eu-north-1 (Stockholm), keeping all data within the European Economic Area. This satisfies GDPR third-country transfer restrictions and is a key requirement for public sector and financial services customers.",
|
||||
"context": "An EU public sector orderer requires that all submission data — including GPS coordinates and images — never leaves the EEA. quiXzoom's Stockholm data residency satisfies this requirement by default, without special configuration.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"gdpr",
|
||||
"s3",
|
||||
"pii"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "right-to-erasure",
|
||||
"name": "Right to erasure",
|
||||
"category": "legal",
|
||||
"short": "A GDPR right allowing individuals to request deletion of their personal data from a platform's systems.",
|
||||
"long": "Under GDPR Article 17, individuals have the right to request erasure of their personal data when it is no longer necessary for the purpose it was collected, when they withdraw consent, or when they object to processing. For quiXzoom, this means Zoomers can request deletion of their account and all associated personal data at any time via the app settings. Certain data may need to be retained for limited periods to satisfy legal obligations (e.g. financial records under tax law) even after an erasure request.",
|
||||
"context": "A Zoomer decides to stop using quiXzoom and requests erasure. quiXzoom deletes their profile, contact data, and GPS history. Some financial transaction records are retained for 7 years as required by EU accounting regulation — this is disclosed in quiXzoom's privacy policy and does not affect the Zoomer's ability to stop using the platform.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"gdpr",
|
||||
"pii",
|
||||
"data-controller"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "api",
|
||||
"name": "API",
|
||||
"category": "technical",
|
||||
"short": "Application Programming Interface — the programmatic interface through which orderers access mission data, submission results, and platform services.",
|
||||
"long": "The quiXzoom API is a REST-style HTTP API that allows orderers to submit mission briefs, monitor mission status, retrieve completed submission packages (images, metadata, GeoJSON), and receive real-time updates via webhooks. Responses are in JSON format. The API uses OAuth 2.0 for authentication and HMAC-SHA256 for webhook signature verification.",
|
||||
"context": "An insurance company integrates the quiXzoom API into their claims management system. When a claim is filed for a specific address, an API call automatically creates a mission, and approved submission data flows directly back into the claims system without manual intervention.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"webhook",
|
||||
"oauth",
|
||||
"json",
|
||||
"hmac-sha256"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "webhook",
|
||||
"name": "Webhook",
|
||||
"category": "technical",
|
||||
"short": "An automatic HTTP POST notification sent by quiXzoom to an orderer's system when a defined event occurs — typically submission approval.",
|
||||
"long": "Webhooks enable real-time integration between quiXzoom and orderer systems without polling. When a submission is approved (or rejected, or a mission is created), quiXzoom sends a JSON payload to the orderer's configured webhook URL. The payload includes the event type, mission ID, submission ID, GPS coordinates, approval status, and image download URLs. Orderers must verify webhook authenticity using HMAC-SHA256 signature verification. Undelivered webhooks are retried with exponential backoff over 24 hours.",
|
||||
"context": "An insurance company's claims system has a quiXzoom webhook endpoint. When a flood damage submission is approved, quiXzoom sends a POST request within seconds. The claims system receives the event, automatically attaches the images to the open claim, and updates the claim status to 'documented' — with no manual intervention required.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"api",
|
||||
"hmac-sha256",
|
||||
"json",
|
||||
"approval"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "oauth",
|
||||
"name": "OAuth",
|
||||
"category": "technical",
|
||||
"short": "Open Authorization — the industry-standard protocol used by quiXzoom's API for secure, delegated authentication.",
|
||||
"long": "OAuth 2.0 allows orderers to authenticate API requests without sharing credentials. Orderers obtain access tokens through the OAuth flow, which are then included in API request headers. Tokens can be scoped (read-only, write, full access) and have configurable expiry periods. OAuth 2.0 is also used for third-party integrations — for example, allowing an orderer's claims management platform to connect to quiXzoom on behalf of their organisation.",
|
||||
"context": "An insurance company's IT team sets up an OAuth 2.0 client in the quiXzoom orderer portal, receives client credentials, and uses these to generate short-lived access tokens for their claims integration server. Tokens expire after 1 hour and are automatically refreshed.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"api",
|
||||
"webhook",
|
||||
"hmac-sha256"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "json",
|
||||
"name": "JSON",
|
||||
"category": "technical",
|
||||
"short": "JavaScript Object Notation — the lightweight data format used for all quiXzoom API responses and webhook payloads.",
|
||||
"long": "JSON is a human-readable, language-agnostic data serialisation format that has become the de facto standard for web APIs. quiXzoom's REST API delivers all responses as JSON, including mission details, submission metadata, location data, and approval status. Webhook event payloads are also JSON. The format is natively supported in virtually all programming languages and integration platforms, making it straightforward to process quiXzoom data in any technical environment.",
|
||||
"context": "When an orderer queries the API for a completed submission, the response is a JSON object containing the submission ID, approval status, GPS coordinates, EXIF metadata summary, and signed URLs to retrieve the image files from S3.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"api",
|
||||
"webhook",
|
||||
"geojson",
|
||||
"csv"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "geojson",
|
||||
"name": "GeoJSON",
|
||||
"category": "technical",
|
||||
"short": "An open standard format (RFC 7946) for encoding geographic data structures using JSON.",
|
||||
"long": "GeoJSON is used by quiXzoom to define mission boundaries (geofences), to encode submission GPS paths, and to deliver location data to orderers in a format compatible with GIS platforms, mapping tools, and geographic analysis software. A mission boundary is represented as a GeoJSON Polygon; individual submission GPS points as GeoJSON Point Features with properties including timestamp, approval status, and submission ID.",
|
||||
"context": "A municipality ordering a road condition survey receives their submission data as a GeoJSON FeatureCollection, which they import directly into QGIS to visualise submission density alongside their road network layer.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"geo-tagged",
|
||||
"json",
|
||||
"api",
|
||||
"mission-brief"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "csv",
|
||||
"name": "CSV",
|
||||
"category": "technical",
|
||||
"short": "Comma-Separated Values — a plain-text tabular data format available as a bulk export option for orderers.",
|
||||
"long": "CSV exports from quiXzoom contain one row per submission, with columns for mission ID, submission timestamp, GPS coordinates, approval status, Zoomer tier (anonymised), and other metadata fields. CSV is suitable for bulk import into spreadsheet tools, BI platforms, or legacy claims systems that do not support JSON or API integration. CSV exports are available on demand via the orderer dashboard or API.",
|
||||
"context": "A municipality uses CSV exports to import quiXzoom road survey data into their GIS system on a weekly basis, plotting submission coordinates alongside existing infrastructure records.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"json",
|
||||
"geojson",
|
||||
"api"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "hmac-sha256",
|
||||
"name": "HMAC-SHA256",
|
||||
"category": "technical",
|
||||
"short": "A cryptographic signature method used to verify that webhook payloads were genuinely sent by quiXzoom and were not tampered with in transit.",
|
||||
"long": "HMAC (Hash-based Message Authentication Code) with SHA-256 works by combining the webhook payload with a shared secret key to produce a unique signature. quiXzoom attaches this signature to every webhook request in the X-QuiXzoom-Signature header. The receiving system recomputes the signature using the same secret and compares — if they match, the payload is authentic and unmodified. This is industry-standard practice used by Stripe, GitHub, and other major webhook providers.",
|
||||
"context": "An insurance company's claims system receives a webhook when a submission is approved. Before processing the data, their server verifies the HMAC-SHA256 signature against their shared webhook secret — confirming the event genuinely originated from quiXzoom and was not injected by a third party.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"webhook",
|
||||
"api",
|
||||
"oauth"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "exif",
|
||||
"name": "EXIF",
|
||||
"category": "technical",
|
||||
"short": "Exchangeable Image File Format — metadata embedded in image files, including GPS coordinates, capture timestamp, device model, and camera settings.",
|
||||
"long": "EXIF metadata is written into image files at capture time by the device camera. For quiXzoom, EXIF is the primary evidence layer: it carries the GPS coordinates where the photo was taken, the precise timestamp, and device identifiers. AI review cross-validates EXIF GPS coordinates against the mission geofence, and EXIF timestamps against the mission time window. EXIF data is preserved in delivery packages to orderers as part of the chain-of-custody record.",
|
||||
"context": "A Zoomer photographs a flood-damaged road. The image's EXIF data records 59.3312°N, 18.0685°E at 09:47:23 UTC. AI review checks this GPS fix is within the mission's 50-metre geofence and the timestamp falls within the claimed time window — both pass, contributing to approval.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"geo-tagged",
|
||||
"gps",
|
||||
"timestamp",
|
||||
"ai-review"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "gps",
|
||||
"name": "GPS",
|
||||
"category": "technical",
|
||||
"short": "Global Positioning System — the satellite-based navigation system used to determine precise geographic location of submissions.",
|
||||
"long": "GPS is the primary location technology in smartphones, providing latitude, longitude, and altitude data by triangulating signals from multiple satellites. All quiXzoom submissions depend on GPS for location verification. The system is augmented by network-based location (Wi-Fi and cell triangulation) in environments where satellite signals are weak — combined, these signals provide the geo-accuracy required for mission compliance checks.",
|
||||
"context": "Every time a Zoomer captures a photo for a mission, the device GPS is sampled. This fix — along with the capture timestamp — is embedded in EXIF and used by AI review to verify the submission was made at the correct location within the correct time window.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"geo-tagged",
|
||||
"geo-accuracy",
|
||||
"exif"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "geo-tagged",
|
||||
"name": "Geo-tagged",
|
||||
"category": "technical",
|
||||
"short": "An image embedded with GPS coordinates at capture time, proving where the photo was physically taken.",
|
||||
"long": "Geo-tagging writes latitude, longitude, and altitude data into the image's EXIF metadata at the moment of capture. All quiXzoom submissions must be geo-tagged — this is a technical requirement enforced by the app. Submissions from devices with disabled location services are rejected before upload. Geo-tagging is the foundation of quiXzoom's location verification: without it, there is no way to confirm the photo was taken at the correct mission location.",
|
||||
"context": "The quiXzoom app requires location permissions to function. When a Zoomer captures a photo in-app, GPS coordinates are written to EXIF automatically. A Zoomer cannot submit photos taken in a regular camera app that disabled geo-tagging — the submission would fail AI review immediately.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"gps",
|
||||
"exif",
|
||||
"geo-accuracy",
|
||||
"geojson"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "geo-accuracy",
|
||||
"name": "Geo-accuracy",
|
||||
"category": "technical",
|
||||
"short": "The closeness of a recorded GPS coordinate to the actual physical position — typically expressed in metres of error radius.",
|
||||
"long": "Geo-accuracy is determined by GPS signal quality, which is affected by urban canyon effects, tree canopy, atmospheric conditions, and device hardware. Consumer smartphone GPS typically achieves 3–10 metre accuracy in open conditions. quiXzoom's mission geofences are sized to account for realistic geo-accuracy limits — a mission for a specific building typically uses a 30–50 metre compliance radius. AI review evaluates whether the recorded GPS position is within the mission's accepted tolerance.",
|
||||
"context": "A Zoomer photographs a bridge in a narrow urban gorge where GPS signals reflect off buildings. Their device records a position 18 metres from the mission pin — within the 30-metre geofence tolerance — so the submission passes the geo-accuracy check.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"gps",
|
||||
"geo-tagged",
|
||||
"exif",
|
||||
"ai-review"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "geofence",
|
||||
"name": "Geofence",
|
||||
"category": "technical",
|
||||
"short": "A virtual geographic boundary defining where a mission must be completed — submissions outside the geofence are automatically rejected.",
|
||||
"long": "A geofence is a digitally defined perimeter around a mission location, typically represented as a circle with a radius of 30–100 metres or as a GeoJSON Polygon for complex shapes. When a Zoomer submits photos, AI review checks the EXIF GPS coordinates against the mission geofence. If the submission was captured outside the geofence, it is rejected with a location mismatch reason. Geofences ensure data integrity by guaranteeing that observations were physically captured at the correct location, preventing fraudulent or mistaken submissions.",
|
||||
"context": "A bridge inspection mission has a 50-metre radius geofence centred on the bridge coordinates. A Zoomer submits photos from 200 metres away — the GPS coordinates in EXIF fall outside the geofence, and AI review rejects the submission with 'Location mismatch — outside geofence.'",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"gps",
|
||||
"geo-accuracy",
|
||||
"exif",
|
||||
"ai-review"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "timestamp",
|
||||
"name": "Timestamp",
|
||||
"category": "technical",
|
||||
"short": "The precise date and time recorded in a photo's EXIF metadata, proving when the image was captured.",
|
||||
"long": "Timestamps are a critical element of quiXzoom's chain-of-custody system. The EXIF timestamp records the device's date and time at the moment of capture, and is cross-validated by AI review against the mission's claimed time window. For legal and insurance use cases, the timestamp (combined with GPS data) provides tamper-evident proof that the documentation was made at the right place at the right time. quiXzoom also records server-side ingestion timestamps for each submission to supplement device-side EXIF data.",
|
||||
"context": "An insurer requires flood documentation captured within 6 hours of a storm event for their claims validity window. The EXIF timestamp on each submitted photo, cross-referenced with server ingestion time, provides the evidence that the documentation falls within the required window — suitable for claims processing and, if necessary, legal proceedings.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"exif",
|
||||
"time-window",
|
||||
"geo-tagged",
|
||||
"ai-review"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "s3",
|
||||
"name": "S3",
|
||||
"category": "technical",
|
||||
"short": "Amazon Simple Storage Service — the object storage platform used to store all quiXzoom submission images, securely and at scale.",
|
||||
"long": "S3 (AWS eu-north-1) is quiXzoom's primary file store for submission images. Uploaded images are stored with server-side encryption, access is controlled via IAM policies, and orderers receive time-limited signed URLs to retrieve submission packages — images are never publicly accessible by default. S3's durability (99.999999999%) and scalability make it appropriate for a platform expecting high submission volumes during surge events.",
|
||||
"context": "When a Zoomer uploads 6 photos for a mission, they are stored in S3 eu-north-1. When the orderer queries the API for the completed submission, they receive signed URLs valid for 24 hours to download the images — after which the URLs expire and a new API call is required.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"data-residency",
|
||||
"api",
|
||||
"submission"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "change-detection",
|
||||
"name": "Change detection",
|
||||
"category": "technical",
|
||||
"short": "The automated identification of differences between current observations and historical baseline data — surfacing what has changed in the physical world.",
|
||||
"long": "Change detection is a core AMOS capability that compares new observations against prior data to identify additions, removals, or modifications to physical assets. It powers infrastructure monitoring, property condition tracking, and environmental surveillance. Change detection operates at multiple scales: from pixel-level differences in repeated photographs to structural changes identified through computer vision. Each detected change is scored by confidence and severity, and flagged as a Contradiction when it represents an unexpected deviation.",
|
||||
"context": "A quarterly observation of a retail park shows three new storefronts and one demolished unit compared to the baseline from six months ago. AMOS change detection automatically flags these modifications, updates the asset registry, and alerts the property manager to verify the changes.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"contradiction",
|
||||
"amos",
|
||||
"observation",
|
||||
"confidence-score"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "quality-score",
|
||||
"name": "Quality score",
|
||||
"category": "technical",
|
||||
"short": "A composite rating of an observation's technical fitness — sharpness, exposure, framing, and protocol compliance — distinct from the confidence score.",
|
||||
"long": "The Quality Score evaluates the technical and aesthetic properties of submitted media independent of location or metadata verification. It measures image sharpness (absence of motion blur or focus issues), exposure (neither under- nor over-exposed), framing (subject completeness and composition), and protocol compliance (correct angles, required elements visible). Quality Score is a component of the overall Confidence Score but is computed separately to give orderers visibility into the technical standard of their data. Low quality scores trigger coaching for Zoomers and may result in rejection if minimum thresholds are not met.",
|
||||
"context": "A Zoomer submits photos that are correctly geo-located and within the time window, but two images are slightly blurry due to camera shake. AI review assigns a Quality Score of 62 — below the 75-point threshold — and rejects the submission with 'Image quality: motion blur detected.' The Zoomer receives automated coaching on stabilisation techniques.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"confidence-score",
|
||||
"ai-review",
|
||||
"observation",
|
||||
"approval"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "rating",
|
||||
"name": "Rating",
|
||||
"category": "quixzoom",
|
||||
"short": "A Zoomer's accumulated quality score on the platform, reflecting submission quality, consistency, and reliability over time.",
|
||||
"long": "Rating is a composite metric calculated from approval rate, submission volume, claim-to-completion ratio (how often claimed missions are actually submitted), and any policy violations. Rating is displayed as a numerical score and determines mission access filtering — high-rating Zoomers see more mission types, receive surge notifications earlier, and are prioritised for specialisation programme invitations. Unlike approval rate (a rolling 30-day window), rating incorporates a Zoomer's full history, weighted toward recent activity.",
|
||||
"context": "A Zoomer with a 94% approval rate but a poor claim-to-completion ratio (often claiming missions and abandoning them) will have a rating lower than their approval rate alone would suggest. Improving claim reliability raises their rating independently of approval rate.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"approval-rate",
|
||||
"tier",
|
||||
"claim"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "mission-brief",
|
||||
"name": "Mission brief",
|
||||
"category": "quixzoom",
|
||||
"short": "The complete specification for a mission — what to capture, how to capture it, quality requirements, and any special instructions.",
|
||||
"long": "A mission brief is shown to the Zoomer after they claim a mission, and is the primary guide for execution. It includes required shot angles, distance from subject, lighting conditions (if relevant), specific elements that must appear in frame, and any contextual notes from the orderer. Mission briefs for specialised mission types (bridge inspection, maritime, infrastructure) include more detailed technical requirements. Zoomers should read the brief carefully before travelling to the mission location.",
|
||||
"context": "A bridge inspection mission brief specifies: 1 overview shot from 50m, 2 deck surface shots, 1 expansion joint close-up, 1 bearing detail, and 1 drainage outlet — all from public access points only. A Zoomer who misses the bearing detail shot is likely to receive a rejection at AI review.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"mission",
|
||||
"submission",
|
||||
"specialisation",
|
||||
"ai-review"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "observation-protocol",
|
||||
"name": "Observation protocol",
|
||||
"category": "core",
|
||||
"short": "The standardised set of instructions defining what to capture, from which angles, and under what conditions for a given mission type.",
|
||||
"long": "The observation protocol is the rulebook for field data collection. It specifies the number of photos required, the vantage points (distance, angle, height), the elements that must be in frame, lighting conditions, and any safety or access constraints. Protocols are mission-type specific: a bridge inspection protocol differs from a property documentation protocol. Following the protocol is essential for approval — AI review checks compliance against the protocol, and deviations result in rejection. Protocols are developed by domain experts and refined through feedback from AI review outcomes.",
|
||||
"context": "A roof condition mission protocol requires: 1 overview shot from street level, 1 ridge-line photo, 2 slope photos (one per side), and 1 detail of any visible damage — all captured during daylight with the sun behind the photographer. A Zoomer who submits only 3 photos or captures at night will fail protocol compliance.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"observation",
|
||||
"field-observation",
|
||||
"mission-brief",
|
||||
"ai-review"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "field-observation",
|
||||
"name": "Field observation",
|
||||
"category": "core",
|
||||
"short": "A structured data collection event performed at a physical location by a verified contributor, producing an observation record.",
|
||||
"long": "A field observation is the complete act of capturing reality data on location: travelling to the mission site, following the observation protocol, capturing required imagery from specified vantage points, and submitting the observation package. It is more than the photos — it is the verified, time-stamped, geo-located record of what was observed. Field observations are the foundational input to the entire quiXzoom–AMOS–Landvex pipeline. Without field observations, there is no data, no intelligence, and no decisions.",
|
||||
"context": "A Zoomer travels to a bridge inspection mission, follows the protocol (6 photos from specified angles), captures geo-tagged images, and submits. The field observation is verified by AI review and enters the AMOS dataset as a trusted data point.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"observation",
|
||||
"observation-protocol",
|
||||
"zoomer",
|
||||
"amos"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "verified-contributor",
|
||||
"name": "Verified contributor",
|
||||
"category": "quixzoom",
|
||||
"short": "A Zoomer who has completed identity verification (KYC) and maintains an active, good-standing account — eligible for payouts and premium missions.",
|
||||
"long": "A verified contributor is a Zoomer who has passed the platform's trust threshold: their identity has been confirmed through government-issued ID and liveness check, their bank account is linked via Stripe Connect, and their account is in good standing (not suspended or restricted). Verification is a one-time process, but good standing is maintained through consistent quality (approval rate above threshold) and compliance with platform policies. Only verified contributors can receive payouts and access Professional-tier missions. Verification status is displayed in the Zoomer's profile.",
|
||||
"context": "A new Zoomer completes 5 missions and earns €45. Before they can receive their first payout, they must become a verified contributor by completing KYC. Once verified, their status shows a green checkmark in-app, and they can withdraw earnings and claim premium missions.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"kyc",
|
||||
"identity-verification",
|
||||
"zoomer",
|
||||
"stripe-connect"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "waitlist",
|
||||
"name": "Waitlist",
|
||||
"category": "quixzoom",
|
||||
"short": "The pre-launch registration list for Zoomers and orderers to secure early access when quiXzoom opens in their region.",
|
||||
"long": "The quiXzoom waitlist allows interested Zoomers and orderers to register before the platform launches in their area. Waitlist registrants receive priority onboarding invitations, early-access mission allocations, and launch communications. For Zoomers, waitlist sign-up takes under 60 seconds and requires only basic contact information — full onboarding (identity verification, bank account) is completed when access is granted. The waitlist helps quiXzoom manage geographic launch sequencing and ensure supply matches demand at launch.",
|
||||
"context": "quiXzoom is launching in August 2026. Zoomers who register on the waitlist before launch receive an early-access invitation 2 weeks before public opening in their city, allowing them to complete onboarding and be mission-ready on day one.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"zoomer",
|
||||
"mission",
|
||||
"orderer"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "sla",
|
||||
"name": "SLA",
|
||||
"category": "quixzoom",
|
||||
"short": "Service Level Agreement — the delivery timeline and quality commitments quiXzoom makes to orderers, governing mission fulfilment and submission delivery.",
|
||||
"long": "quiXzoom's SLAs define expected fulfilment times (how quickly a claimed mission produces an approved submission), platform uptime commitments, API response time guarantees, and escalation procedures when commitments are not met. SLA terms vary by orderer plan — standard, professional, and enterprise tiers have different guaranteed fulfilment windows. SLA performance is monitored and reported monthly to orderers, with service credits applicable in cases of sustained underperformance.",
|
||||
"context": "An enterprise orderer's SLA guarantees that 95% of urban missions will produce an approved submission within 4 hours of activation. For surge missions, the SLA commits to a first claim within 30 minutes. These commitments are monitored in real time and reported in the orderer's monthly performance report.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"orderer",
|
||||
"mission",
|
||||
"surge-mission",
|
||||
"api"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "ouroboros",
|
||||
"name": "Ouroboros",
|
||||
"category": "technical",
|
||||
"short": "The internal platform architecture that powers quiXzoom, AAMOS, and Landvex — a self-referential system where the platform monitors and improves itself.",
|
||||
"long": "Ouroboros is the internal name for the technical architecture that underpins the entire Landvex ecosystem. It encompasses the microservices, data pipelines, AI models, and infrastructure that enable quiXzoom field data collection, AMOS analysis, and Landvex intelligence delivery. The name reflects the system's self-monitoring nature: observations feed analysis, analysis drives decisions, decisions generate new observations. Ouroboros is not a customer-facing product — it is the technical foundation.",
|
||||
"context": "quiXzoom runs as an Ouroboros instance — using the same core infrastructure as other Landvex products but configured for the quiXzoom marketplace model. Ouroboros handles user management, mission orchestration, AI review, and data pipelines.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"amos",
|
||||
"quixzoom",
|
||||
"landvex"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "rexo",
|
||||
"name": "REXO",
|
||||
"category": "technical",
|
||||
"short": "Landvex's coding pipeline for automated software development, testing, and deployment.",
|
||||
"long": "REXO is Landvex's internal coding pipeline that automates software development tasks. It runs via /opt/amos/rexo-build/, with tasks defined in plan/PLAN.json and executed by parallel workers. REXO orchestrates code generation, testing, and deployment across the ecosystem. All coding tasks should be routed through REXO rather than manual file uploads or direct server modifications.",
|
||||
"context": "When a new feature is needed for the quiXzoom API, the task is added to REXO's PLAN.json. REXO workers generate the code, run tests, and deploy to staging — all without manual intervention.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"ouroboros",
|
||||
"amos"
|
||||
],
|
||||
"domains": [
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "vims",
|
||||
"name": "VIMS",
|
||||
"category": "product",
|
||||
"short": "Visual Infrastructure Monitoring System — a Landvex product for continuous infrastructure condition assessment.",
|
||||
"long": "VIMS (Visual Infrastructure Monitoring System) is a Landvex product that uses quiXzoom observations and AMOS analysis to provide continuous monitoring of infrastructure assets. It delivers condition indices, change alerts, and maintenance prioritisation for roads, bridges, buildings, and utilities. VIMS replaces periodic manual inspections with ongoing, data-driven condition assessment.",
|
||||
"context": "A municipality subscribes to VIMS for their 400 bridges. Monthly observations from quiXzoom Zoomers feed into VIMS, which updates condition indices, flags new damage, and generates maintenance priority lists — all automatically.",
|
||||
"contextLabel": "In Landvex",
|
||||
"related": [
|
||||
"amos",
|
||||
"quixzoom",
|
||||
"index",
|
||||
"change-detection"
|
||||
],
|
||||
"domains": [
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "quixzoom-auth-core",
|
||||
"name": "quiXzoom Auth Core",
|
||||
"category": "product",
|
||||
"short": "Standalone authentication product sold via AAMOS — includes Auth Foundation, KYZ Engine, Company Registry, and Payout Engine.",
|
||||
"long": "quiXzoom Auth Core is a standalone authentication and identity product that can be integrated into any application. It includes: Auth Foundation (email/Google + phone + password), KYZ Engine (Know Your Zoomer — identity verification), Company Registry (sole proprietorship / registered company), and Payout Engine (Stripe Connect, Frilans Finans, bank transfers). Auth Core is sold as a product via AAMOS and is used by quiXzoom and other Landvex products.",
|
||||
"context": "A third-party app developer integrates quiXzoom Auth Core to handle user authentication, identity verification, and payouts — without building these complex systems themselves.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"amos",
|
||||
"kyc",
|
||||
"stripe-connect"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"aamos",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "quixzoom-frilans-payout",
|
||||
"name": "quiXzoom Frilans Payout",
|
||||
"category": "product",
|
||||
"short": "Payout product for freelancers without a company — handles taxes and fees across 8 markets.",
|
||||
"long": "quiXzoom Frilans Payout is a payout product designed for freelancers who don't have a registered company. It operates across 8 markets (SE, NO, DK, FI, DE, NL, US, GB) and automatically handles source tax per country. Features include weekly/monthly payouts, 15% platform fee + 6% processing fee, and automatic tax reporting. The product integrates with quiXzoom Auth Core and uses the Payout Engine.",
|
||||
"context": "A freelancer in Sweden uses quiXzoom Frilans Payout to receive payments without registering a company. The system automatically deducts source tax and pays it to Skatteverket, while the freelancer receives their net earnings weekly.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"quixzoom-auth-core",
|
||||
"payout",
|
||||
"stripe-connect"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "landvex-inc",
|
||||
"name": "Landvex Inc",
|
||||
"category": "landvex",
|
||||
"short": "The US entity (Houston, TX) that develops and sells IT products powered by AMOS engines.",
|
||||
"long": "Landvex Inc is the US-based company that owns and operates the AAMOS platform and quiXzoom product. It is the legal entity responsible for product development, sales, and operations. Landvex Inc is NOT 'AAMOS Group' — there is no such entity. All products are developed and sold by Landvex Inc.",
|
||||
"context": "Landvex Inc holds the intellectual property for AMOS engines, operates the quiXzoom platform, and sells intelligence products to enterprise customers worldwide.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"landvex",
|
||||
"amos",
|
||||
"quixzoom"
|
||||
],
|
||||
"domains": [
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "landvex-ab",
|
||||
"name": "LandveX AB",
|
||||
"category": "landvex",
|
||||
"short": "The Swedish entity (org.nr 559141-7042) that handles development, operations, and accounting in SEK.",
|
||||
"long": "LandveX AB is the Swedish subsidiary responsible for development, operations, and local accounting. It handles all Swedish bookkeeping, VAT, payroll, and supplier invoices in SEK using the BAS chart of accounts and SIE4 format. This is correct per Swedish accounting law. LandveX AB operates the technical infrastructure from Stockholm (AWS eu-north-1).",
|
||||
"context": "LandveX AB employs the development team, pays Swedish salaries, and files Swedish tax returns. All internal bookkeeping is in SEK, while customer-facing products use USD/EUR.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"landvex",
|
||||
"landvex-inc"
|
||||
],
|
||||
"domains": [
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "usd",
|
||||
"name": "USD",
|
||||
"category": "payment",
|
||||
"short": "United States Dollar — the primary currency used in quiXzoom platform and Landvex products.",
|
||||
"long": "USD is the main currency throughout the quiXzoom platform and Landvex ecosystem. All customer-facing pricing, payouts, and product fees are denominated in USD (or EUR where specified). This is a locked policy — SEK is never used in customer-facing copy, sites, documents, or communication. The only exception is LandveX AB's internal Swedish accounting.",
|
||||
"context": "A mission pays $15 (USD). A Zoomer's earnings are displayed in USD. Landvex enterprise contracts are priced in USD. This is consistent across all customer touchpoints.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"eur",
|
||||
"payout",
|
||||
"platform-fee"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex",
|
||||
"aamos"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "eur",
|
||||
"name": "EUR",
|
||||
"category": "payment",
|
||||
"short": "Euro — the secondary currency used in quiXzoom platform and Landvex products, primarily for European markets.",
|
||||
"long": "EUR is the secondary currency in the quiXzoom and Landvex ecosystem, used primarily for European markets and SEPA-zone transactions. Zoomers in Eurozone countries receive payouts in EUR via SEPA. Orderers in Europe may be invoiced in EUR. Like USD, EUR is a customer-facing currency — SEK is never shown to customers.",
|
||||
"context": "A Zoomer in Germany receives their payout in EUR via SEPA. An orderer in France is invoiced in EUR for their monthly quiXzoom usage.",
|
||||
"contextLabel": "In the ecosystem",
|
||||
"related": [
|
||||
"usd",
|
||||
"sepa",
|
||||
"payout"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom",
|
||||
"landvex"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "qz-token",
|
||||
"name": "QZ Token",
|
||||
"category": "payment",
|
||||
"short": "quiXzoom internal token — 1 QZ = 1 USD, used for platform transactions and rewards.",
|
||||
"long": "The QZ Token is quiXzoom's internal transaction token with a fixed exchange rate of 1 QZ = 1 USD. It is not a speculative cryptocurrency — it is a simple ledger entry used for platform transactions, rewards, and internal accounting. QZ Tokens are created when missions are approved and stored in Zoomer accounts. They can be converted to USD payouts or used for platform services.",
|
||||
"context": "A Zoomer earns 50 QZ from completed missions. They can convert these to $50 USD payout or use them to purchase premium features on the platform.",
|
||||
"contextLabel": "In quiXzoom",
|
||||
"related": [
|
||||
"usd",
|
||||
"payout",
|
||||
"quixzoom"
|
||||
],
|
||||
"domains": [
|
||||
"quixzoom"
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,739 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Glossary — Landvex Ecosystem</title>
|
||||
<meta name="description" content="The complete glossary for quiXzoom, AMOS, and Landvex. Every term defined precisely — from Zoomer to AMOS Prediction Engine.">
|
||||
<link rel="canonical" href="https://www.quixzoom.com/glossary">
|
||||
<meta name="robots" content="index, follow">
|
||||
|
||||
<!-- Open Graph -->
|
||||
<meta property="og:type" content="website">
|
||||
<meta property="og:title" content="Glossary — Landvex Ecosystem">
|
||||
<meta property="og:description" content="Every term used across quiXzoom, AMOS, and Landvex. Defined precisely and kept current.">
|
||||
<meta property="og:url" content="https://www.quixzoom.com/glossary">
|
||||
<meta property="og:image" content="https://www.quixzoom.com/images/og-glossary.jpg">
|
||||
<meta property="og:image:width" content="1200">
|
||||
<meta property="og:image:height" content="630">
|
||||
|
||||
<!-- Twitter -->
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:title" content="Glossary — Landvex Ecosystem">
|
||||
<meta name="twitter:description" content="Every term used across quiXzoom, AMOS, and Landvex. Defined precisely and kept current.">
|
||||
<meta name="twitter:image" content="https://www.quixzoom.com/images/og-glossary.jpg">
|
||||
|
||||
<!-- Structured Data -->
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "DefinedTermSet",
|
||||
"name": "Landvex Ecosystem Glossary",
|
||||
"description": "Complete glossary of terms used across quiXzoom, AMOS, and Landvex platforms",
|
||||
"publisher": {
|
||||
"@type": "Organization",
|
||||
"name": "Landvex Inc",
|
||||
"url": "https://www.landvex.com"
|
||||
}
|
||||
}
|
||||
</script>
|
||||
|
||||
<style>
|
||||
*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
|
||||
|
||||
:root {
|
||||
--bg: #ffffff;
|
||||
--bg-off: #f5f5f7;
|
||||
--bg-card: #ffffff;
|
||||
--text: #1d1d1f;
|
||||
--text-secondary: #6e6e73;
|
||||
--blue: #0066FF;
|
||||
--blue-light: #e8f0ff;
|
||||
--green: #00a550;
|
||||
--green-light: #e6f7ee;
|
||||
--purple: #7b2fff;
|
||||
--purple-light: #f0e8ff;
|
||||
--orange: #e8660a;
|
||||
--orange-light: #fff0e6;
|
||||
--pink: #ff3366;
|
||||
--pink-light: #ffe8f0;
|
||||
--radius: 18px;
|
||||
--radius-sm: 8px;
|
||||
--border: #d2d2d7;
|
||||
--nav-height: 64px;
|
||||
--shadow-hover: 0 12px 40px rgba(0,0,0,.10);
|
||||
}
|
||||
|
||||
@media (prefers-color-scheme: dark) {
|
||||
:root {
|
||||
--bg: #000000;
|
||||
--bg-off: #1c1c1e;
|
||||
--bg-card: #1c1c1e;
|
||||
--text: #f5f5f7;
|
||||
--text-secondary: #98989f;
|
||||
--border: #3a3a3c;
|
||||
--blue-light: rgba(0,102,255,.15);
|
||||
--green-light: rgba(0,165,80,.15);
|
||||
--purple-light: rgba(123,47,255,.15);
|
||||
--orange-light: rgba(232,102,10,.15);
|
||||
--pink-light: rgba(255,51,102,.15);
|
||||
--shadow-hover: 0 12px 40px rgba(0,0,0,.5);
|
||||
}
|
||||
}
|
||||
|
||||
html { scroll-behavior: smooth; }
|
||||
|
||||
body {
|
||||
font-family: -apple-system, BlinkMacSystemFont, 'SF Pro Display', 'SF Pro Text', 'Helvetica Neue', Arial, sans-serif;
|
||||
background: var(--bg);
|
||||
color: var(--text);
|
||||
line-height: 1.6;
|
||||
-webkit-font-smoothing: antialiased;
|
||||
}
|
||||
|
||||
/* ─── NAV ─────────────────────────────────────────────────── */
|
||||
.nav {
|
||||
position: sticky;
|
||||
top: 0;
|
||||
z-index: 100;
|
||||
height: var(--nav-height);
|
||||
background: rgba(255,255,255,.82);
|
||||
-webkit-backdrop-filter: blur(20px) saturate(180%);
|
||||
backdrop-filter: blur(20px) saturate(180%);
|
||||
border-bottom: 1px solid var(--border);
|
||||
display: flex;
|
||||
align-items: center;
|
||||
gap: 16px;
|
||||
padding: 0 24px;
|
||||
}
|
||||
|
||||
@media (prefers-color-scheme: dark) {
|
||||
.nav { background: rgba(0,0,0,.82); }
|
||||
}
|
||||
|
||||
.nav-logo {
|
||||
font-size: 1.25rem;
|
||||
font-weight: 800;
|
||||
color: var(--text);
|
||||
text-decoration: none;
|
||||
letter-spacing: -.04em;
|
||||
white-space: nowrap;
|
||||
flex-shrink: 0;
|
||||
}
|
||||
.nav-logo .x { color: var(--blue); }
|
||||
|
||||
.nav-divider {
|
||||
width: 1px;
|
||||
height: 20px;
|
||||
background: var(--border);
|
||||
flex-shrink: 0;
|
||||
}
|
||||
|
||||
.nav-title {
|
||||
font-size: .9375rem;
|
||||
font-weight: 600;
|
||||
color: var(--text-secondary);
|
||||
white-space: nowrap;
|
||||
flex-shrink: 0;
|
||||
}
|
||||
|
||||
.nav-search {
|
||||
flex: 1;
|
||||
max-width: 280px;
|
||||
position: relative;
|
||||
}
|
||||
|
||||
.nav-search input {
|
||||
width: 100%;
|
||||
padding: 8px 14px 8px 36px;
|
||||
border-radius: 20px;
|
||||
border: 1px solid var(--border);
|
||||
background: var(--bg-off);
|
||||
color: var(--text);
|
||||
font-size: .875rem;
|
||||
font-family: inherit;
|
||||
outline: none;
|
||||
transition: border-color .15s, box-shadow .15s;
|
||||
}
|
||||
|
||||
.nav-search input:focus {
|
||||
border-color: var(--blue);
|
||||
box-shadow: 0 0 0 3px rgba(0,102,255,.12);
|
||||
}
|
||||
|
||||
.nav-search-icon {
|
||||
position: absolute;
|
||||
left: 11px;
|
||||
top: 50%;
|
||||
transform: translateY(-50%);
|
||||
color: var(--text-secondary);
|
||||
pointer-events: none;
|
||||
}
|
||||
|
||||
.nav-az {
|
||||
display: flex;
|
||||
gap: 2px;
|
||||
overflow-x: auto;
|
||||
scrollbar-width: none;
|
||||
-ms-overflow-style: none;
|
||||
}
|
||||
.nav-az::-webkit-scrollbar { display: none; }
|
||||
|
||||
.nav-az a {
|
||||
display: inline-block;
|
||||
min-width: 24px;
|
||||
padding: 3px 4px;
|
||||
text-align: center;
|
||||
font-size: .75rem;
|
||||
font-weight: 600;
|
||||
color: var(--text-secondary);
|
||||
text-decoration: none;
|
||||
border-radius: 5px;
|
||||
transition: background .12s, color .12s;
|
||||
line-height: 1.4;
|
||||
}
|
||||
.nav-az a:hover { background: var(--blue-light); color: var(--blue); }
|
||||
.nav-az a.active { background: var(--blue); color: #fff; }
|
||||
.nav-az a.empty { opacity: .25; pointer-events: none; }
|
||||
|
||||
/* ─── MAIN ────────────────────────────────────────────────── */
|
||||
main {
|
||||
max-width: 860px;
|
||||
margin: 0 auto;
|
||||
padding: 0 24px 80px;
|
||||
}
|
||||
|
||||
.page-header {
|
||||
padding: 64px 0 48px;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
.page-header h1 {
|
||||
font-size: clamp(2.5rem, 6vw, 4rem);
|
||||
font-weight: 800;
|
||||
letter-spacing: -.04em;
|
||||
line-height: 1.05;
|
||||
color: var(--text);
|
||||
margin-bottom: 16px;
|
||||
}
|
||||
|
||||
.page-header p {
|
||||
font-size: 1.125rem;
|
||||
color: var(--text-secondary);
|
||||
max-width: 480px;
|
||||
margin: 0 auto;
|
||||
}
|
||||
|
||||
/* ─── DOMAIN FILTER ───────────────────────────────────────── */
|
||||
.domain-filter {
|
||||
display: flex;
|
||||
gap: 8px;
|
||||
justify-content: center;
|
||||
margin-bottom: 32px;
|
||||
flex-wrap: wrap;
|
||||
}
|
||||
|
||||
.domain-filter button {
|
||||
padding: 6px 16px;
|
||||
border-radius: 20px;
|
||||
border: 1px solid var(--border);
|
||||
background: var(--bg-off);
|
||||
color: var(--text-secondary);
|
||||
font-size: .875rem;
|
||||
font-weight: 500;
|
||||
cursor: pointer;
|
||||
transition: all .15s;
|
||||
}
|
||||
|
||||
.domain-filter button:hover {
|
||||
border-color: var(--blue);
|
||||
color: var(--blue);
|
||||
}
|
||||
|
||||
.domain-filter button.active {
|
||||
background: var(--blue);
|
||||
color: #fff;
|
||||
border-color: var(--blue);
|
||||
}
|
||||
|
||||
/* ─── LETTER SECTION ──────────────────────────────────────── */
|
||||
.letter-section {
|
||||
margin-bottom: 48px;
|
||||
}
|
||||
|
||||
.letter-heading {
|
||||
display: flex;
|
||||
align-items: center;
|
||||
gap: 16px;
|
||||
margin-bottom: 20px;
|
||||
padding-bottom: 12px;
|
||||
border-bottom: 1px solid var(--border);
|
||||
}
|
||||
|
||||
.letter-heading h2 {
|
||||
font-size: 2rem;
|
||||
font-weight: 800;
|
||||
color: var(--text-secondary);
|
||||
letter-spacing: -.04em;
|
||||
line-height: 1;
|
||||
width: 36px;
|
||||
flex-shrink: 0;
|
||||
}
|
||||
|
||||
.letter-count {
|
||||
font-size: .8125rem;
|
||||
color: var(--text-secondary);
|
||||
}
|
||||
|
||||
/* ─── TERM CARD ───────────────────────────────────────────── */
|
||||
.term-card {
|
||||
background: var(--bg-card);
|
||||
border: 1px solid var(--border);
|
||||
border-radius: var(--radius);
|
||||
padding: 28px 32px;
|
||||
margin-bottom: 16px;
|
||||
transition: box-shadow .2s, transform .2s;
|
||||
}
|
||||
|
||||
.term-card:hover {
|
||||
box-shadow: var(--shadow-hover);
|
||||
transform: translateY(-2px);
|
||||
}
|
||||
|
||||
.term-header {
|
||||
display: flex;
|
||||
align-items: flex-start;
|
||||
justify-content: space-between;
|
||||
gap: 12px;
|
||||
margin-bottom: 10px;
|
||||
flex-wrap: wrap;
|
||||
}
|
||||
|
||||
.term-name {
|
||||
font-size: 1.3125rem;
|
||||
font-weight: 700;
|
||||
color: var(--text);
|
||||
letter-spacing: -.02em;
|
||||
line-height: 1.2;
|
||||
}
|
||||
|
||||
.term-category {
|
||||
display: inline-block;
|
||||
padding: 4px 12px;
|
||||
border-radius: 20px;
|
||||
font-size: .75rem;
|
||||
font-weight: 600;
|
||||
letter-spacing: .02em;
|
||||
text-transform: uppercase;
|
||||
white-space: nowrap;
|
||||
flex-shrink: 0;
|
||||
margin-top: 2px;
|
||||
}
|
||||
|
||||
.cat-platform { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-technical { background: var(--green-light); color: var(--green); }
|
||||
.cat-payment { background: var(--purple-light); color: var(--purple); }
|
||||
.cat-legal { background: var(--orange-light); color: var(--orange); }
|
||||
.cat-core { background: var(--bg-off); color: var(--text-secondary); }
|
||||
.cat-amos { background: var(--pink-light); color: var(--pink); }
|
||||
.cat-landvex { background: var(--blue-light); color: var(--blue); }
|
||||
.cat-quixzoom { background: var(--green-light); color: var(--green); }
|
||||
.cat-product { background: var(--orange-light); color: var(--orange); }
|
||||
|
||||
.term-short {
|
||||
font-size: 1rem;
|
||||
font-weight: 500;
|
||||
color: var(--text);
|
||||
margin-bottom: 12px;
|
||||
line-height: 1.5;
|
||||
}
|
||||
|
||||
.term-long {
|
||||
font-size: .9375rem;
|
||||
color: var(--text-secondary);
|
||||
line-height: 1.65;
|
||||
margin-bottom: 16px;
|
||||
}
|
||||
|
||||
.term-context {
|
||||
background: var(--bg-off);
|
||||
border-radius: var(--radius-sm);
|
||||
padding: 14px 18px;
|
||||
margin-bottom: 14px;
|
||||
}
|
||||
|
||||
.term-context-label {
|
||||
font-size: .75rem;
|
||||
font-weight: 700;
|
||||
text-transform: uppercase;
|
||||
letter-spacing: .06em;
|
||||
color: var(--blue);
|
||||
display: block;
|
||||
margin-bottom: 6px;
|
||||
}
|
||||
|
||||
.term-context p {
|
||||
font-size: .875rem;
|
||||
color: var(--text-secondary);
|
||||
line-height: 1.6;
|
||||
}
|
||||
|
||||
.term-related {
|
||||
display: flex;
|
||||
align-items: center;
|
||||
flex-wrap: wrap;
|
||||
gap: 6px;
|
||||
}
|
||||
|
||||
.term-related > span {
|
||||
font-size: .8125rem;
|
||||
color: var(--text-secondary);
|
||||
}
|
||||
|
||||
.term-related a {
|
||||
display: inline-block;
|
||||
padding: 3px 10px;
|
||||
border-radius: 20px;
|
||||
font-size: .8125rem;
|
||||
font-weight: 500;
|
||||
color: var(--blue);
|
||||
background: var(--blue-light);
|
||||
text-decoration: none;
|
||||
transition: background .12s, color .12s;
|
||||
}
|
||||
|
||||
.term-related a:hover {
|
||||
background: var(--blue);
|
||||
color: #fff;
|
||||
}
|
||||
|
||||
/* ─── SEARCH EMPTY ────────────────────────────────────────── */
|
||||
.search-empty {
|
||||
display: none;
|
||||
text-align: center;
|
||||
padding: 64px 24px;
|
||||
color: var(--text-secondary);
|
||||
font-size: 1rem;
|
||||
}
|
||||
.search-empty.visible { display: block; }
|
||||
|
||||
/* ─── LAST UPDATED ────────────────────────────────────────── */
|
||||
.last-updated {
|
||||
text-align: center;
|
||||
font-size: .8125rem;
|
||||
color: var(--text-secondary);
|
||||
margin-top: 48px;
|
||||
padding-top: 24px;
|
||||
border-top: 1px solid var(--border);
|
||||
}
|
||||
|
||||
/* ─── RESPONSIVE ──────────────────────────────────────────── */
|
||||
@media (max-width: 600px) {
|
||||
.nav { gap: 10px; padding: 0 16px; }
|
||||
.nav-az { display: none; }
|
||||
.nav-search { max-width: none; flex: 1; }
|
||||
.term-card { padding: 20px 18px; }
|
||||
.page-header { padding: 40px 0 32px; }
|
||||
.domain-filter { gap: 6px; }
|
||||
.domain-filter button { padding: 5px 12px; font-size: .8125rem; }
|
||||
}
|
||||
|
||||
@media (max-width: 900px) {
|
||||
.nav-az { max-width: 200px; }
|
||||
}
|
||||
|
||||
/* ─── HIGHLIGHT when anchor-targeted ─────────────────────── */
|
||||
.term-card:target {
|
||||
border-color: var(--blue);
|
||||
box-shadow: 0 0 0 3px rgba(0,102,255,.15);
|
||||
}
|
||||
|
||||
/* ─── HIDDEN during search/filter ─────────────────────────── */
|
||||
.term-card.hidden { display: none; }
|
||||
.letter-section.hidden { display: none; }
|
||||
|
||||
/* ─── LOADING STATE ───────────────────────────────────────── */
|
||||
.loading {
|
||||
text-align: center;
|
||||
padding: 80px 24px;
|
||||
color: var(--text-secondary);
|
||||
}
|
||||
|
||||
.loading-spinner {
|
||||
width: 40px;
|
||||
height: 40px;
|
||||
border: 3px solid var(--border);
|
||||
border-top-color: var(--blue);
|
||||
border-radius: 50%;
|
||||
animation: spin 1s linear infinite;
|
||||
margin: 0 auto 16px;
|
||||
}
|
||||
|
||||
@keyframes spin {
|
||||
to { transform: rotate(360deg); }
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<nav class="nav">
|
||||
<a href="/" class="nav-logo">qui<span class="x">X</span>zoom</a>
|
||||
<div class="nav-divider"></div>
|
||||
<span class="nav-title">Glossary</span>
|
||||
<div class="nav-search">
|
||||
<svg class="nav-search-icon" width="14" height="14" viewBox="0 0 16 16" fill="none">
|
||||
<circle cx="6.5" cy="6.5" r="5" stroke="currentColor" stroke-width="1.5"/>
|
||||
<path d="M10 10l4 4" stroke="currentColor" stroke-width="1.5" stroke-linecap="round"/>
|
||||
</svg>
|
||||
<input type="search" id="glossary-search" placeholder="Search terms…" autocomplete="off" aria-label="Search glossary">
|
||||
</div>
|
||||
<nav class="nav-az" id="az-nav" aria-label="Jump to letter">
|
||||
<!-- Populated by JS -->
|
||||
</nav>
|
||||
</nav>
|
||||
|
||||
<main>
|
||||
<header class="page-header">
|
||||
<h1>Every term.<br>Defined.</h1>
|
||||
<p>The complete ecosystem reference — from field observations to decision intelligence. Covering quiXzoom, AMOS, and Landvex.</p>
|
||||
</header>
|
||||
|
||||
<div class="domain-filter" id="domain-filter">
|
||||
<button data-domain="all" class="active">All</button>
|
||||
<button data-domain="quixzoom">quiXzoom</button>
|
||||
<button data-domain="amos">AMOS</button>
|
||||
<button data-domain="landvex">Landvex</button>
|
||||
</div>
|
||||
|
||||
<div class="search-empty" id="search-empty">No terms match "<span id="search-query"></span>"</div>
|
||||
|
||||
<div id="glossary-content">
|
||||
<div class="loading">
|
||||
<div class="loading-spinner"></div>
|
||||
<p>Loading glossary…</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="last-updated" id="last-updated"></div>
|
||||
</main>
|
||||
|
||||
<footer style="background:#0d0d10;border-top:1px solid rgba(255,255,255,.07);padding:32px 24px;margin-top:48px">
|
||||
<div style="max-width:1080px;margin:0 auto;display:flex;align-items:center;justify-content:space-between;flex-wrap:wrap;gap:16px">
|
||||
<a href="/" style="font-size:1.1rem;font-weight:800;color:#fff;letter-spacing:-.03em;text-decoration:none">qui<span style="color:#3b82f6">X</span>zoom</a>
|
||||
<nav style="display:flex;gap:20px;flex-wrap:wrap">
|
||||
<a href="/" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">For Zoomers</a>
|
||||
<a href="/for-organisations/" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">For Organisations</a>
|
||||
<a href="/developer" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">Developer</a>
|
||||
<a href="/pricing" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">Pricing</a>
|
||||
<a href="/about" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">About</a>
|
||||
<a href="/status" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">Status</a>
|
||||
<a href="/privacy" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">Privacy</a>
|
||||
<a href="/terms" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">Terms</a>
|
||||
<a href="/security" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">Security</a>
|
||||
<a href="/support" style="font-size:.8125rem;color:rgba(255,255,255,.75);transition:color .15s;text-decoration:none">Support</a>
|
||||
</nav>
|
||||
<p style="font-size:.8125rem;color:rgba(255,255,255,.75);margin:0">© 2026 Landvex Inc</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
<script>
|
||||
// ─── GLOSSARY DATA ──────────────────────────────────────────────────
|
||||
let glossaryData = null;
|
||||
let currentDomain = 'all';
|
||||
|
||||
// ─── LOAD DATA ──────────────────────────────────────────────────────
|
||||
async function loadGlossary() {
|
||||
try {
|
||||
const response = await fetch('glossary-data.json');
|
||||
if (!response.ok) throw new Error('Failed to load glossary data');
|
||||
glossaryData = await response.json();
|
||||
renderGlossary();
|
||||
updateLastUpdated();
|
||||
} catch (error) {
|
||||
document.getElementById('glossary-content').innerHTML = `
|
||||
<div class="search-empty visible">
|
||||
<p>Error loading glossary. Please refresh the page.</p>
|
||||
<p style="font-size: .875rem; margin-top: 8px;">${error.message}</p>
|
||||
</div>
|
||||
`;
|
||||
}
|
||||
}
|
||||
|
||||
// ─── RENDER GLOSSARY ────────────────────────────────────────────────
|
||||
function renderGlossary() {
|
||||
if (!glossaryData) return;
|
||||
|
||||
const content = document.getElementById('glossary-content');
|
||||
const terms = glossaryData.terms;
|
||||
const categories = glossaryData.categories;
|
||||
|
||||
// Group terms by first letter
|
||||
const grouped = {};
|
||||
terms.forEach(term => {
|
||||
const letter = term.name.charAt(0).toUpperCase();
|
||||
if (!grouped[letter]) grouped[letter] = [];
|
||||
grouped[letter].push(term);
|
||||
});
|
||||
|
||||
// Sort letters
|
||||
const letters = Object.keys(grouped).sort();
|
||||
|
||||
// Build A-Z nav
|
||||
const azNav = document.getElementById('az-nav');
|
||||
azNav.innerHTML = letters.map(letter =>
|
||||
`<a href="#${letter.toLowerCase()}">${letter}</a>`
|
||||
).join('');
|
||||
|
||||
// Build content
|
||||
let html = '';
|
||||
letters.forEach(letter => {
|
||||
const letterTerms = grouped[letter].sort((a, b) => a.name.localeCompare(b.name));
|
||||
html += `
|
||||
<section class="letter-section" id="${letter.toLowerCase()}">
|
||||
<div class="letter-heading">
|
||||
<h2>${letter}</h2>
|
||||
<span class="letter-count">${letterTerms.length} term${letterTerms.length !== 1 ? 's' : ''}</span>
|
||||
</div>
|
||||
${letterTerms.map(term => renderTermCard(term, categories)).join('')}
|
||||
</section>
|
||||
`;
|
||||
});
|
||||
|
||||
content.innerHTML = html;
|
||||
|
||||
// Setup intersection observer for A-Z active state
|
||||
setupAZObserver();
|
||||
}
|
||||
|
||||
// ─── RENDER TERM CARD ───────────────────────────────────────────────
|
||||
function renderTermCard(term, categories) {
|
||||
const cat = categories[term.category] || categories.platform;
|
||||
const relatedLinks = term.related.map(id => {
|
||||
const relatedTerm = glossaryData.terms.find(t => t.id === id);
|
||||
return relatedTerm ? `<a href="#${id}">${relatedTerm.name}</a>` : '';
|
||||
}).join('');
|
||||
|
||||
return `
|
||||
<article id="${term.id}" class="term-card" data-domains="${term.domains.join(' ')}">
|
||||
<div class="term-header">
|
||||
<h3 class="term-name">${term.name}</h3>
|
||||
<span class="term-category cat-${term.category}">${cat.label}</span>
|
||||
</div>
|
||||
<p class="term-short">${term.short}</p>
|
||||
<p class="term-long">${term.long}</p>
|
||||
<div class="term-context">
|
||||
<span class="term-context-label">${term.contextLabel}</span>
|
||||
<p>${term.context}</p>
|
||||
</div>
|
||||
<div class="term-related">
|
||||
<span>Related:</span>
|
||||
${relatedLinks}
|
||||
</div>
|
||||
</article>
|
||||
`;
|
||||
}
|
||||
|
||||
// ─── UPDATE LAST UPDATED ────────────────────────────────────────────
|
||||
function updateLastUpdated() {
|
||||
if (!glossaryData?.lastUpdated) return;
|
||||
const date = new Date(glossaryData.lastUpdated);
|
||||
document.getElementById('last-updated').textContent =
|
||||
`Last updated: ${date.toLocaleDateString('en-US', { year: 'numeric', month: 'long', day: 'numeric' })}`;
|
||||
}
|
||||
|
||||
// ─── SEARCH ─────────────────────────────────────────────────────────
|
||||
const searchInput = document.getElementById('glossary-search');
|
||||
const emptyMsg = document.getElementById('search-empty');
|
||||
const querySpan = document.getElementById('search-query');
|
||||
|
||||
searchInput.addEventListener('input', () => {
|
||||
const q = searchInput.value.trim().toLowerCase();
|
||||
|
||||
if (!q) {
|
||||
document.querySelectorAll('.term-card, .letter-section').forEach(el => el.classList.remove('hidden'));
|
||||
emptyMsg.classList.remove('visible');
|
||||
return;
|
||||
}
|
||||
|
||||
let anyVisible = false;
|
||||
|
||||
document.querySelectorAll('.letter-section').forEach(section => {
|
||||
let sectionHasVisible = false;
|
||||
section.querySelectorAll('.term-card').forEach(card => {
|
||||
const text = card.textContent.toLowerCase();
|
||||
const id = card.id.toLowerCase();
|
||||
const match = text.includes(q) || id.includes(q);
|
||||
|
||||
card.classList.toggle('hidden', !match);
|
||||
if (match) sectionHasVisible = true;
|
||||
});
|
||||
section.classList.toggle('hidden', !sectionHasVisible);
|
||||
if (sectionHasVisible) anyVisible = true;
|
||||
});
|
||||
|
||||
querySpan.textContent = searchInput.value.trim();
|
||||
emptyMsg.classList.toggle('visible', !anyVisible);
|
||||
});
|
||||
|
||||
// ─── DOMAIN FILTER ──────────────────────────────────────────────────
|
||||
document.getElementById('domain-filter').addEventListener('click', (e) => {
|
||||
if (!e.target.matches('button')) return;
|
||||
|
||||
document.querySelectorAll('.domain-filter button').forEach(btn => btn.classList.remove('active'));
|
||||
e.target.classList.add('active');
|
||||
|
||||
currentDomain = e.target.dataset.domain;
|
||||
filterByDomain();
|
||||
});
|
||||
|
||||
function filterByDomain() {
|
||||
if (!glossaryData) return;
|
||||
|
||||
let anyVisible = false;
|
||||
|
||||
document.querySelectorAll('.letter-section').forEach(section => {
|
||||
let sectionHasVisible = false;
|
||||
section.querySelectorAll('.term-card').forEach(card => {
|
||||
const domains = card.dataset.domains?.split(' ') || [];
|
||||
const match = currentDomain === 'all' || domains.includes(currentDomain);
|
||||
|
||||
card.classList.toggle('hidden', !match);
|
||||
if (match) sectionHasVisible = true;
|
||||
});
|
||||
section.classList.toggle('hidden', !sectionHasVisible);
|
||||
if (sectionHasVisible) anyVisible = true;
|
||||
});
|
||||
|
||||
emptyMsg.classList.toggle('visible', !anyVisible);
|
||||
if (!anyVisible) {
|
||||
querySpan.textContent = currentDomain === 'all' ? '' : `domain: ${currentDomain}`;
|
||||
}
|
||||
}
|
||||
|
||||
// ─── A-Z ACTIVE LETTER TRACKING ─────────────────────────────────────
|
||||
function setupAZObserver() {
|
||||
const azLinks = document.querySelectorAll('.nav-az a');
|
||||
const sections = Array.from(document.querySelectorAll('.letter-section[id]'));
|
||||
|
||||
if (sections.length === 0) return;
|
||||
|
||||
const observer = new IntersectionObserver(entries => {
|
||||
entries.forEach(entry => {
|
||||
if (entry.isIntersecting) {
|
||||
const id = entry.target.id;
|
||||
azLinks.forEach(a => {
|
||||
a.classList.toggle('active', a.getAttribute('href') === '#' + id);
|
||||
});
|
||||
}
|
||||
});
|
||||
}, { rootMargin: '-20% 0px -70% 0px' });
|
||||
|
||||
sections.forEach(s => observer.observe(s));
|
||||
}
|
||||
|
||||
// ─── INITIALIZE ─────────────────────────────────────────────────────
|
||||
loadGlossary();
|
||||
</script>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,63 @@
|
||||
/**
|
||||
* SMP Tag Helper
|
||||
*
|
||||
* Automatically converts SMP tags to glossary links
|
||||
* Usage: <span data-smp="term-id">Term Name</span>
|
||||
*
|
||||
* This script:
|
||||
* 1. Scans the page for data-smp attributes
|
||||
* 2. Fetches the glossary data
|
||||
* 3. Converts tags to linked terms with tooltips
|
||||
*/
|
||||
|
||||
(function() {
|
||||
'use strict';
|
||||
|
||||
const GLOSSARY_URL = '/glossary/glossary-data.json';
|
||||
let glossaryData = null;
|
||||
|
||||
// Load glossary data
|
||||
async function loadGlossary() {
|
||||
try {
|
||||
const response = await fetch(GLOSSARY_URL);
|
||||
if (!response.ok) throw new Error('Failed to load glossary');
|
||||
glossaryData = await response.json();
|
||||
processTags();
|
||||
} catch (error) {
|
||||
console.warn('SMP Tag Helper: Could not load glossary', error);
|
||||
}
|
||||
}
|
||||
|
||||
// Process all SMP tags
|
||||
function processTags() {
|
||||
if (!glossaryData) return;
|
||||
|
||||
const tags = document.querySelectorAll('[data-smp]');
|
||||
tags.forEach(tag => {
|
||||
const termId = tag.getAttribute('data-smp');
|
||||
const term = glossaryData.terms.find(t => t.id === termId);
|
||||
|
||||
if (term) {
|
||||
// Create link
|
||||
const link = document.createElement('a');
|
||||
link.href = '/glossary/#' + termId;
|
||||
link.className = 'smp-tag';
|
||||
link.innerHTML = tag.innerHTML;
|
||||
link.setAttribute('data-term', termId);
|
||||
|
||||
// Add tooltip
|
||||
link.title = term.short;
|
||||
|
||||
// Replace original element
|
||||
tag.parentNode.replaceChild(link, tag);
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
// Initialize
|
||||
if (document.readyState === 'loading') {
|
||||
document.addEventListener('DOMContentLoaded', loadGlossary);
|
||||
} else {
|
||||
loadGlossary();
|
||||
}
|
||||
})();
|
||||
@@ -0,0 +1,239 @@
|
||||
#!/usr/bin/env node
|
||||
/**
|
||||
* Glossary Auto-Revision Script
|
||||
*
|
||||
* This script:
|
||||
* 1. Reads the current glossary-data.json
|
||||
* 2. Scans source files for new terms (SMP tags, code comments, etc.)
|
||||
* 3. Updates the glossary with new terms
|
||||
* 4. Generates updated static HTML for all domains
|
||||
* 5. Deploys to S3/CloudFront
|
||||
*/
|
||||
|
||||
const fs = require('fs');
|
||||
const path = require('path');
|
||||
|
||||
const GLOSSARY_PATH = path.join(__dirname, 'glossary-data.json');
|
||||
const OUTPUT_DIR = path.join(__dirname, 'dist');
|
||||
|
||||
// Load current glossary
|
||||
function loadGlossary() {
|
||||
const data = fs.readFileSync(GLOSSARY_PATH, 'utf8');
|
||||
return JSON.parse(data);
|
||||
}
|
||||
|
||||
// Save glossary
|
||||
function saveGlossary(data) {
|
||||
fs.writeFileSync(GLOSSARY_PATH, JSON.stringify(data, null, 2));
|
||||
}
|
||||
|
||||
// Generate static HTML for a domain
|
||||
function generateStaticHTML(data, domain, baseUrl) {
|
||||
const terms = data.terms.filter(t => {
|
||||
if (domain === 'all') return true;
|
||||
return t.domains.includes(domain);
|
||||
});
|
||||
|
||||
// Group by letter
|
||||
const grouped = {};
|
||||
terms.forEach(term => {
|
||||
const letter = term.name.charAt(0).toUpperCase();
|
||||
if (!grouped[letter]) grouped[letter] = [];
|
||||
grouped[letter].push(term);
|
||||
});
|
||||
|
||||
const letters = Object.keys(grouped).sort();
|
||||
|
||||
// Build HTML
|
||||
let html = '<!DOCTYPE html>\n<html lang="en">\n<head>\n';
|
||||
html += '<meta charset="UTF-8">\n';
|
||||
html += '<meta name="viewport" content="width=device-width, initial-scale=1.0">\n';
|
||||
html += '<title>Glossary — ' + (domain === 'all' ? 'Landvex Ecosystem' : domain) + '</title>\n';
|
||||
html += '<meta name="description" content="Every term used on ' + domain + '. Defined precisely and kept current.">\n';
|
||||
html += '<link rel="canonical" href="' + baseUrl + '/glossary">\n';
|
||||
html += '<meta name="robots" content="index, follow">\n';
|
||||
html += '<script type="application/ld+json">\n';
|
||||
html += '{\n';
|
||||
html += ' "@context": "https://schema.org",\n';
|
||||
html += ' "@type": "DefinedTermSet",\n';
|
||||
html += ' "name": "' + domain + ' Glossary",\n';
|
||||
html += ' "description": "Complete glossary of terms",\n';
|
||||
html += ' "publisher": {"@type": "Organization", "name": "Landvex Inc", "url": "https://www.landvex.com"}\n';
|
||||
html += '}\n';
|
||||
html += '<\/script>\n';
|
||||
html += '<style>';
|
||||
html += '*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }\n';
|
||||
html += ':root {\n';
|
||||
html += ' --bg: #ffffff; --bg-off: #f5f5f7; --bg-card: #ffffff;\n';
|
||||
html += ' --text: #1d1d1f; --text-secondary: #6e6e73;\n';
|
||||
html += ' --blue: #0066FF; --blue-light: #e8f0ff;\n';
|
||||
html += ' --green: #00a550; --green-light: #e6f7ee;\n';
|
||||
html += ' --purple: #7b2fff; --purple-light: #f0e8ff;\n';
|
||||
html += ' --orange: #e8660a; --orange-light: #fff0e6;\n';
|
||||
html += ' --pink: #ff3366; --pink-light: #ffe8f0;\n';
|
||||
html += ' --radius: 18px; --radius-sm: 8px; --border: #d2d2d7;\n';
|
||||
html += ' --nav-height: 64px; --shadow-hover: 0 12px 40px rgba(0,0,0,.10);\n';
|
||||
html += '}\n';
|
||||
html += '@media (prefers-color-scheme: dark) {\n';
|
||||
html += ' :root {\n';
|
||||
html += ' --bg: #000000; --bg-off: #1c1c1e; --bg-card: #1c1c1e;\n';
|
||||
html += ' --text: #f5f5f7; --text-secondary: #98989f; --border: #3a3a3c;\n';
|
||||
html += ' --blue-light: rgba(0,102,255,.15); --green-light: rgba(0,165,80,.15);\n';
|
||||
html += ' --purple-light: rgba(123,47,255,.15); --orange-light: rgba(232,102,10,.15);\n';
|
||||
html += ' --pink-light: rgba(255,51,102,.15); --shadow-hover: 0 12px 40px rgba(0,0,0,.5);\n';
|
||||
html += ' }\n';
|
||||
html += '}\n';
|
||||
html += 'html { scroll-behavior: smooth; }\n';
|
||||
html += 'body {\n';
|
||||
html += ' font-family: -apple-system, BlinkMacSystemFont, \'SF Pro Display\', \'SF Pro Text\', \'Helvetica Neue\', Arial, sans-serif;\n';
|
||||
html += ' background: var(--bg); color: var(--text); line-height: 1.6; -webkit-font-smoothing: antialiased;\n';
|
||||
html += '}\n';
|
||||
html += '.nav {\n';
|
||||
html += ' position: sticky; top: 0; z-index: 100; height: var(--nav-height);\n';
|
||||
html += ' background: rgba(255,255,255,.82); -webkit-backdrop-filter: blur(20px) saturate(180%);\n';
|
||||
html += ' backdrop-filter: blur(20px) saturate(180%); border-bottom: 1px solid var(--border);\n';
|
||||
html += ' display: flex; align-items: center; gap: 16px; padding: 0 24px;\n';
|
||||
html += '}\n';
|
||||
html += '@media (prefers-color-scheme: dark) { .nav { background: rgba(0,0,0,.82); } }\n';
|
||||
html += '.nav-logo { font-size: 1.25rem; font-weight: 800; color: var(--text); text-decoration: none; letter-spacing: -.04em; white-space: nowrap; flex-shrink: 0; }\n';
|
||||
html += '.nav-logo .x { color: var(--blue); }\n';
|
||||
html += '.nav-divider { width: 1px; height: 20px; background: var(--border); flex-shrink: 0; }\n';
|
||||
html += '.nav-title { font-size: .9375rem; font-weight: 600; color: var(--text-secondary); white-space: nowrap; flex-shrink: 0; }\n';
|
||||
html += 'main { max-width: 860px; margin: 0 auto; padding: 0 24px 80px; }\n';
|
||||
html += '.page-header { padding: 64px 0 48px; text-align: center; }\n';
|
||||
html += '.page-header h1 { font-size: clamp(2.5rem, 6vw, 4rem); font-weight: 800; letter-spacing: -.04em; line-height: 1.05; color: var(--text); margin-bottom: 16px; }\n';
|
||||
html += '.page-header p { font-size: 1.125rem; color: var(--text-secondary); max-width: 480px; margin: 0 auto; }\n';
|
||||
html += '.letter-section { margin-bottom: 48px; }\n';
|
||||
html += '.letter-heading { display: flex; align-items: center; gap: 16px; margin-bottom: 20px; padding-bottom: 12px; border-bottom: 1px solid var(--border); }\n';
|
||||
html += '.letter-heading h2 { font-size: 2rem; font-weight: 800; color: var(--text-secondary); letter-spacing: -.04em; line-height: 1; width: 36px; flex-shrink: 0; }\n';
|
||||
html += '.letter-count { font-size: .8125rem; color: var(--text-secondary); }\n';
|
||||
html += '.term-card { background: var(--bg-card); border: 1px solid var(--border); border-radius: var(--radius); padding: 28px 32px; margin-bottom: 16px; transition: box-shadow .2s, transform .2s; }\n';
|
||||
html += '.term-card:hover { box-shadow: var(--shadow-hover); transform: translateY(-2px); }\n';
|
||||
html += '.term-header { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; margin-bottom: 10px; flex-wrap: wrap; }\n';
|
||||
html += '.term-name { font-size: 1.3125rem; font-weight: 700; color: var(--text); letter-spacing: -.02em; line-height: 1.2; }\n';
|
||||
html += '.term-category { display: inline-block; padding: 4px 12px; border-radius: 20px; font-size: .75rem; font-weight: 600; letter-spacing: .02em; text-transform: uppercase; white-space: nowrap; flex-shrink: 0; margin-top: 2px; }\n';
|
||||
html += '.cat-platform { background: var(--blue-light); color: var(--blue); }\n';
|
||||
html += '.cat-technical { background: var(--green-light); color: var(--green); }\n';
|
||||
html += '.cat-payment { background: var(--purple-light); color: var(--purple); }\n';
|
||||
html += '.cat-legal { background: var(--orange-light); color: var(--orange); }\n';
|
||||
html += '.cat-core { background: var(--bg-off); color: var(--text-secondary); }\n';
|
||||
html += '.cat-amos { background: var(--pink-light); color: var(--pink); }\n';
|
||||
html += '.cat-landvex { background: var(--blue-light); color: var(--blue); }\n';
|
||||
html += '.cat-quixzoom { background: var(--green-light); color: var(--green); }\n';
|
||||
html += '.cat-product { background: var(--orange-light); color: var(--orange); }\n';
|
||||
html += '.term-short { font-size: 1rem; font-weight: 500; color: var(--text); margin-bottom: 12px; line-height: 1.5; }\n';
|
||||
html += '.term-long { font-size: .9375rem; color: var(--text-secondary); line-height: 1.65; margin-bottom: 16px; }\n';
|
||||
html += '.term-context { background: var(--bg-off); border-radius: var(--radius-sm); padding: 14px 18px; margin-bottom: 14px; }\n';
|
||||
html += '.term-context-label { font-size: .75rem; font-weight: 700; text-transform: uppercase; letter-spacing: .06em; color: var(--blue); display: block; margin-bottom: 6px; }\n';
|
||||
html += '.term-context p { font-size: .875rem; color: var(--text-secondary); line-height: 1.6; }\n';
|
||||
html += '.term-related { display: flex; align-items: center; flex-wrap: wrap; gap: 6px; }\n';
|
||||
html += '.term-related > span { font-size: .8125rem; color: var(--text-secondary); }\n';
|
||||
html += '.term-related a { display: inline-block; padding: 3px 10px; border-radius: 20px; font-size: .8125rem; font-weight: 500; color: var(--blue); background: var(--blue-light); text-decoration: none; transition: background .12s, color .12s; }\n';
|
||||
html += '.term-related a:hover { background: var(--blue); color: #fff; }\n';
|
||||
html += '.last-updated { text-align: center; font-size: .8125rem; color: var(--text-secondary); margin-top: 48px; padding-top: 24px; border-top: 1px solid var(--border); }\n';
|
||||
html += '.term-card:target { border-color: var(--blue); box-shadow: 0 0 0 3px rgba(0,102,255,.15); }\n';
|
||||
html += '@media (max-width: 600px) { .nav { gap: 10px; padding: 0 16px; } .term-card { padding: 20px 18px; } .page-header { padding: 40px 0 32px; } }\n';
|
||||
html += '</style>\n';
|
||||
html += '</head>\n<body>\n';
|
||||
html += '<nav class="nav">\n';
|
||||
html += ' <a href="/" class="nav-logo">qui<span class="x">X</span>zoom</a>\n';
|
||||
html += ' <div class="nav-divider"></div>\n';
|
||||
html += ' <span class="nav-title">Glossary</span>\n';
|
||||
html += '</nav>\n';
|
||||
html += '<main>\n';
|
||||
html += ' <header class="page-header">\n';
|
||||
html += ' <h1>Every term.<br>Defined.</h1>\n';
|
||||
html += ' <p>The complete ' + domain + ' reference — from field observations to decision intelligence.</p>\n';
|
||||
html += ' </header>\n';
|
||||
|
||||
letters.forEach(letter => {
|
||||
const letterTerms = grouped[letter].sort((a, b) => a.name.localeCompare(b.name));
|
||||
html += ' <section class="letter-section" id="' + letter.toLowerCase() + '">\n';
|
||||
html += ' <div class="letter-heading">\n';
|
||||
html += ' <h2>' + letter + '</h2>\n';
|
||||
html += ' <span class="letter-count">' + letterTerms.length + ' term' + (letterTerms.length !== 1 ? 's' : '') + '</span>\n';
|
||||
html += ' </div>\n';
|
||||
|
||||
letterTerms.forEach(term => {
|
||||
const cat = data.categories[term.category] || data.categories.platform;
|
||||
const relatedLinks = term.related.map(id => {
|
||||
const relatedTerm = data.terms.find(t => t.id === id);
|
||||
return relatedTerm ? '<a href="#' + id + '">' + relatedTerm.name + '</a>' : '';
|
||||
}).join('');
|
||||
|
||||
html += ' <article id="' + term.id + '" class="term-card">\n';
|
||||
html += ' <div class="term-header">\n';
|
||||
html += ' <h3 class="term-name">' + term.name + '</h3>\n';
|
||||
html += ' <span class="term-category cat-' + term.category + '">' + cat.label + '</span>\n';
|
||||
html += ' </div>\n';
|
||||
html += ' <p class="term-short">' + term.short + '</p>\n';
|
||||
html += ' <p class="term-long">' + term.long + '</p>\n';
|
||||
html += ' <div class="term-context">\n';
|
||||
html += ' <span class="term-context-label">' + term.contextLabel + '</span>\n';
|
||||
html += ' <p>' + term.context + '</p>\n';
|
||||
html += ' </div>\n';
|
||||
html += ' <div class="term-related">\n';
|
||||
html += ' <span>Related:</span>\n';
|
||||
html += ' ' + relatedLinks + '\n';
|
||||
html += ' </div>\n';
|
||||
html += ' </article>\n';
|
||||
});
|
||||
|
||||
html += ' </section>\n';
|
||||
});
|
||||
|
||||
html += ' <div class="last-updated">Last updated: ' + new Date(data.lastUpdated).toLocaleDateString('en-US', { year: 'numeric', month: 'long', day: 'numeric' }) + '</div>\n';
|
||||
html += '</main>\n';
|
||||
html += '<footer style="background:#0d0d10;border-top:1px solid rgba(255,255,255,.07);padding:32px 24px;margin-top:48px">\n';
|
||||
html += ' <div style="max-width:1080px;margin:0 auto;display:flex;align-items:center;justify-content:space-between;flex-wrap:wrap;gap:16px">\n';
|
||||
html += ' <a href="/" style="font-size:1.1rem;font-weight:800;color:#fff;letter-spacing:-.03em;text-decoration:none">qui<span style="color:#3b82f6">X</span>zoom</a>\n';
|
||||
html += ' <p style="font-size:.8125rem;color:rgba(255,255,255,.75);margin:0">© 2026 Landvex Inc</p>\n';
|
||||
html += ' </div>\n';
|
||||
html += '</footer>\n';
|
||||
html += '</body>\n';
|
||||
html += '</html>';
|
||||
|
||||
return html;
|
||||
}
|
||||
|
||||
// Main
|
||||
function main() {
|
||||
console.log('🔄 Glossary Auto-Revision Started');
|
||||
|
||||
const data = loadGlossary();
|
||||
|
||||
// Update timestamp
|
||||
data.lastUpdated = new Date().toISOString();
|
||||
data.version = new Date().toISOString().split('T')[0];
|
||||
|
||||
// Ensure output directory exists
|
||||
if (!fs.existsSync(OUTPUT_DIR)) {
|
||||
fs.mkdirSync(OUTPUT_DIR, { recursive: true });
|
||||
}
|
||||
|
||||
// Generate static HTML for each domain
|
||||
const domains = ['all', 'quixzoom', 'aamos', 'landvex'];
|
||||
const baseUrls = {
|
||||
'all': 'https://www.quixzoom.com',
|
||||
'quixzoom': 'https://www.quixzoom.com',
|
||||
'aamos': 'https://aamos.ai',
|
||||
'landvex': 'https://www.landvex.com'
|
||||
};
|
||||
|
||||
domains.forEach(domain => {
|
||||
const html = generateStaticHTML(data, domain, baseUrls[domain]);
|
||||
const filename = domain === 'all' ? 'index.html' : 'glossary-' + domain + '.html';
|
||||
fs.writeFileSync(path.join(OUTPUT_DIR, filename), html);
|
||||
const termCount = data.terms.filter(t => domain === 'all' || t.domains.includes(domain)).length;
|
||||
console.log('✅ Generated ' + filename + ' (' + termCount + ' terms)');
|
||||
});
|
||||
|
||||
// Save updated data
|
||||
saveGlossary(data);
|
||||
|
||||
console.log('✅ Glossary Auto-Revision Complete');
|
||||
console.log('📊 Total terms: ' + data.terms.length);
|
||||
console.log('📁 Output: ' + OUTPUT_DIR);
|
||||
}
|
||||
|
||||
main();
|
||||
Reference in New Issue
Block a user