Short answers for clients, verifiers, crawlers, and AI agents.

Verified Reality is tamper-evident capture-authentication infrastructure. It helps clients and verifiers create Truth Packets — hardware-bound media records that document, with cryptographic and device-telemetry evidence, that a specific device captured specific media at a specific place and time. The platform combines field verification, cryptographic sealing, a chain-of-custody ledger, and a planned licensing Exchange (launching).

A Truth Packet is a cryptographic evidence bundle that pairs the captured media with device telemetry, operator context, location data, EXIF and C2PA credentials where supported, content hashes, and a continuous chain-of-custody record. The bundle is sealed at the moment of capture and registered in the platform ledger so any later modification is detectable.

Five primary audiences: clients who request a sealed record, independent professionals using Solo Mode, independent contractor Verifiers, journalists and newsrooms commissioning coverage, and licensing buyers (including ethical AI data buyers) who may source verified media from the Exchange once it is live.

All three in design. The protocol is the tool, the Certified Reality Verifier network is the service, and the Verified Reality Exchange is the planned marketplace where approved Truth Packets may be licensed for commercial use. The public storefront is launching; public listings are not yet live.

No. Verified Reality operates purely as neutral infrastructure. We provide the forensic capture protocol, the marketplace ledger, dispatch tooling, and client dashboard — but Verifiers are independent contractors who choose their own missions and schedules. VRA does not employ field operators, assign disciplinary action on your behalf, or act as a middleman in performance disputes. Clients enforce their own quality bar through ratings, exclusion lists, and re-dispatch — the same marketplace levers described in the client portal under "Verifier Issue? Read this." and in the Marketplace Philosophy section on /company.

Verified Reality is built and operated by Bizbio Inc., headquartered in London, Ontario. The first active Command Centre covers southwestern Ontario; additional regional command centres come online as the network expands.

Clients submit a request through /quote with target location, scope, and deadline. The system either dispatches an existing Certified Reality Verifier in that area or posts the work as a client-funded bounty. The output is a Truth Packet delivered into the client portal with full chain-of-custody, ready for legal, insurance, audit, or licensing use.

The commissioning client owns the media asset — the sealed clip and its Truth Packet proof — on client-funded work. That is like a journalist owning copyright in a report about an airplane: they own the report, not the airplane. All copyright, trademarks, moral rights, and artistic ownership of the subject matter depicted remain with the original creator. Verified Reality Agency is a secure custodian of sensor telemetry under a limited key-escrow model (recovery, support, and lawful process where Bizbio can technically decrypt) — not a no-keys or blind vault. Custody of telemetry does not transfer or encumber that underlying property. If the client opts eligible media into commercial licensing through the Exchange once it is live, the default revenue split on the capture file is owner 80% and HQ 20% (configurable via HQ Settings — the cap table is written at mint time and settles from that stored split). The field verifier is paid as a subcontractor on client-funded missions and does not receive backend royalties on the client's capture-file interest.

Yes. Private and evidentiary missions are not listed on the Exchange. The Truth Packet sits inside the client portal and can be exported for custody, legal, insurance, audit, or internal-business use without ever becoming a public asset.

Yes — the dispatch system targets verifiers by location and competency. If no Certified Reality Verifier is currently active near the requested site, the mission can be posted as a bounty so verifiers in adjacent regions can claim and travel, or a Lead Investigator can dispatch a Second Unit verifier to that geography. When the city is still dark (no local Verifiers at all), use the beachhead fork at /beachhead: run Solo Mode yourself, or recruit someone nearby to register so marketplace coverage can start.

You are early, not blocked. Open /beachhead for the two public paths: (1) Solo Mode — an independent professional seals their own work today via /solo with wholesale infrastructure fees; (2) Recruit — send someone nearby to /register/verifier so client-funded missions can appear on Radar in that geography. Travel bounties and Second Unit dispatch remain available when adjacent Verifiers can cover the site.

Yes. Truth Packets export as a self-contained verification record (PDF + media + hashes + metadata + chain-of-custody log). The export embeds verification anchors so that an opposing party, claims adjuster, or court can re-verify the packet independently of Verified Reality.

Property and asset verification, insurance claim documentation, milestone-draw construction inspections, civic-liability and slip-and-fall scene records, real-estate condition reports, intellectual-property asset genesis, and investigative or journalistic field captures.

Verified Reality is neutral technology infrastructure — forensic software, sensor telemetry, and the marketplace ledger. The Certified Reality Verifiers who accept your missions are independent contractors, not VRA employees. In the same way you would not contact the electric grid operator if an independent electrician performed poorly, our HQ support team does not manage, mediate, or reprimand individual Verifiers. Your immediate and most effective remedy is built into the client portal: leave a low rating (which mathematically slows their advancement and limits how quickly they can take on bigger jobs), add them to your exclusion list (so they never touch your contracts again), and re-dispatch the mission to the Radar for a better contractor. Those tools put quality control in your hands and let the market self-correct to your standards. Please reserve HQ support tickets and support@verifiedreality.ca strictly for technical platform issues, software bugs, or billing inquiries — verifier-performance complaints sent there receive automated triage and will not change outcomes. For beta defects, use the AI-free bug report form on /support.

Each Verifier carries a network-wide client average (1–5 stars) derived from post-mission feedback on completed jobs, plus a count of missions they have finished on the VRA network. Until a Verifier completes at least six missions, clients see only the mission count — not the numeric average — so new contractors get a fair runway before a single early rating defines their public profile. After six missions, the average appears alongside the count in your portal, quote history, and the verifier introduction email when they claim your job.

Client star ratings adjust your Mission Credit eligibility balance — the automated counter Victor uses toward your next C2/C3 credential threshold. They do not revoke a credential you already hold. A 1-star rating deducts 2 Mission Credits; a 2-star rating deducts 1. A second penalizing low rating from the same client within 30 days is recorded but shielded (no additional deduction). Five consecutive explicit 5-star ratings restore +1 credit while your balance is negative. You receive an automated ledger email when a 1–2 star rating applies. Specialty mission XP uses a separate multiplier track.

Independent contractors settle hardware-attested field missions, optional Exchange licensing royalties on HQ-funded internal bounties, Pro subscription pass-through on referred clients, and an optional affiliate share. Client-funded Standard and Enterprise missions settle at 50% of mission gross — CAD $132.50 on a CAD $265 Standard job, CAD $282.50 on a CAD $565 Enterprise job on completion (HQ-configurable). HQ-funded internal bounties pay a field advance up front (Advance Against Royalties — non-refundable if never licensed; recouped from the verifier's royalty share when licensed) plus a backend licensing royalty share on future Exchange sales of the captured media. Published R1 5% / R2 5% affiliate shares are a hypothetical throughput model, not a guarantee — they can accrue on completed mission gross when you recruited the field verifier, funded from the platform waterfall, not from the verifier's mission fee. Competition Act s. 55: typical participants during initial rollout earn CAD $0–CAD $150/month. See /verifiers for the labeled hypothetical model.

Register your agency at /register/verifier. You complete an Independent Contractor Agreement, accept the VRA Forensic Standards (Mission Terms + Truth Protocol), give a separate yes to dossier facial matching, accept the Verified Reality App End User License Agreement (Mobile EULA), upload a dossier photo, and finish Stripe Connect onboarding so payouts can flow. Once active you receive missions on the Verifier Radar in your area (Android field app required at launch).

Yes. Verifiers register under the Verifier Independent Contractor Agreement. They choose which hardware-attested missions to accept, set their own schedule, and use their own devices. Verified Reality supplies cryptographic rails and settlement — it does not employ Verifiers, set shifts, or supervise field methods as an employer. In Canada this is CRA independent-contractor classification (1099/T4A in the US). GST/HST registration is required for Canadian verifiers above the federal small-supplier threshold.

A modern Android 11+ smartphone with sensor support for the active hardware-interrogation handshake (gyroscope, accelerometer, GPS, camera). The Verified Reality field capture app currently runs on Android only; an iPhone build is not yet available. Clients can use the web platform from any device. The app pre-flights your device on first run and tells you which sensors are required for the missions you can accept.

Client-funded missions pay a subcontractor fee — the IP belongs to the client and the verifier has no backend royalty on Exchange sales. HQ-funded internal bounties (newsroom, civic, intel) pay a field advance as an Advance Against Royalties (kept if never licensed; recouped from the verifier's royalty payouts when licensed) and mint a cap table that typically gives the capturing verifier about 50% of future Exchange licensing gross (HQ Settings: Internal Bounty Royalty %), with HQ holding the remainder. Both flow through the same dispatch and Truth Packet pipeline.

When you recruit another verifier with your referral code, you may receive an R1 (direct) 5% or R2 (indirect) 5% share of their completed paid mission gross, paid via Stripe Connect at settlement from VRA's platform margin — not from the recruit's payout. Shares apply only if referred verifiers complete paid missions; they do not apply to Exchange licensing royalties. If a recruit has no recruiter in the chain, unallocated shares revert to HQ. Published rates are a hypothetical throughput model, not a guarantee. Competition Act s. 55: typical participants during initial rollout earn CAD $0–CAD $150/month. Hypothetical annual network math on /verifiers is not typical. Most pay, if any, comes from field missions you perform yourself.

Verified Reality's Affiliate Network is a two-level (R1/R2) referral share on completed paid mission gross, described in full above. There are no infinite downlines and Verifiers never pay for "inventory" or a right to recruit. The referral override is funded from Verified Reality's corporate margin, not deducted from a recruit's mission payout. Published R1 5% / R2 5% rates are a hypothetical throughput model, not a guarantee, and sit next to a Competition Act s. 55 typical-participant range of CAD $0–CAD $150/month during initial rollout. Hypothetical network math on /verifiers is not typical. Amounts vary and are not guaranteed.

Solo Mode allows independent professionals to act as their own client. You pay VRA a wholesale infrastructure fee — 25% of list — CAD $66.25 Standard / CAD $141.25 Enterprise — to seal your data, charge your own private clients whatever retail markup you choose, and keep 100% of that retail margin. As client of record you own the media asset — the sealed clip and Truth Packet proof. That does not transfer copyright in the subject matter depicted. Owning the capture file is separate from Exchange commercial licensing: if you list the capture on the VRA Exchange, the default royalty split is owner 80% / HQ 20% (Client IP Platform Fee % in HQ Settings) — written into the cap table at mint time. Under the Independent Contractor Agreement and Client MSA, Solo Mode still produces a cryptographic Truth Packet with the same custody and licensing rules as other client-origin captures.

Internal Bounties allow you to monetize high-entropy events. If you spot a breaking news event or massive infrastructure failure, you can submit a Bounty Tip. If HQ approves and dispatches, you receive a cash advance as an Advance Against Royalties (by default about 10% of EMV — non-refundable if the asset never licenses; if it does license, HQ recoups that advance from your ~50% royalty payouts), a timed exclusive Radar head start to claim the capture first, and a permanent capture-file royalty stake (typically about 50% by default, configured in HQ Settings) for future global licensing of the clip. Depicted-subject copyright stays with the original creator.

When HQ dispatches an Internal Bounty from a Verifier-submitted tip, the proposing Verifier receives a timed exclusive window on Bounty Radar to claim the mission before it opens to the wider network. The head-start duration is configured in HQ Settings. Separately from the claim window, approved Internal Bounties also mint a lasting licensing stake for the tipper/capturing Verifier under the Advance Against Royalties model.

The first active Command Centre is London, Ontario, covering southwestern Ontario. The verifier network is rolling out region by region; additional Command Centres come online as regional managers are appointed. Verifiers anywhere can register early and be activated when their region opens. If your city has no Verifiers yet, you can be the beachhead — register at /register/verifier or share /beachhead with someone nearby who wants the first local node.

Yes. Being first is the beachhead strategy: register at /register/verifier, complete legal onboarding and Stripe Connect, and you become the local marketplace capacity for client jobs on Radar. Friends or clients who need verification before a local roster exists can use Solo Mode (/solo) themselves, or point recruits to /beachhead for the Solo-vs-recruit fork. Optional R1/R2 affiliate share on /verifiers is a hypothetical throughput model, not a guarantee; see that page for the Competition Act s. 55 typical-participant range.

The protocol records evidence at the moment of capture, not after upload. Active device interrogation, telemetry continuity, PRNU camera fingerprinting, cryptographic hashes, EXIF + C2PA provenance, and chain-of-custody metadata are all sealed together. In our testing, a finished upload from a render farm or generative model has not carried that capture-time interrogation signature. That is not a warranty that every future attack is impossible. A matching seal also does not prove the depicted scene was unstaged, complete, or honest — later review still judges the event itself. Primer: /wiki/how-verified-reality-proves-a-file-is-real.

PRNU (Photo Response Non-Uniformity) is the unique sensor fingerprint left by a specific camera's silicon — every physical sensor produces a slightly different pattern of pixel response. Verified Reality associates Truth Packets with the verifier's enrolled camera sensor so the file can be checked against that hardware pattern, not a model output. PRNU is sensor association; it does not prove the operator's legal identity. Primer: /wiki/how-verified-reality-proves-a-file-is-real.

C2PA (Coalition for Content Provenance and Authenticity) is an open standard for binding cryptographically-signed provenance into media files. Verified Reality's Double-Locked Box pipeline attaches C2PA credentials to sealed captures on supported device paths so C2PA-aware viewers can read provenance independently of our infrastructure.

Yes — that is the design goal for the cryptographic core. The session seal, content hashes, embedded EXIF, and C2PA material can be checked locally with the Verified Reality Auditor desktop app against the bytes on disk. For Arweave-stamped Truth Packets, encrypted Sovereign Decryption Kits carry an Arweave transaction ID; the Auditor hash-matches the local ZIP against the Zip-SHA256 tag on the immutable permaweb transaction — no web app or Supabase database required. Full independent re-verification depends on which custody tier was chosen and whether public anchors were enabled for that packet.

Instead of trusting a finished upload, Verified Reality challenges the device during capture. The app issues live sensor probes (gyro, accelerometer, GPS, optical handshake) that a render farm or deepfake pipeline has not been able to satisfy in real time in our testing. A completed handshake indicates a device, in motion, in a physical location at capture time; an incomplete handshake blocks the seal.

The active interrogation step is the primary control. A deepfake exists as a finished file; the protocol seals the live sensor stream off the device, not a file that was handed to it. Synthetic media has not been able to satisfy the real-time hardware handshake in our testing, and any attempt to spoof the capture pipeline trips the protocol's tamper checks and is grounds for an immediate verifier ban. No capture system can guarantee it will defeat every future attack.

Every sealed Truth Packet is registered in the platform chain-of-custody ledger (Postgres) with content hashes and custody metadata. Captured media is stored on S3-compatible object storage (Cloudflare R2 in production): a hot ingestion tier, an optional Forever Vault tier for eligible Pro or bounty missions, and optional cold archive. Arweave permaweb anchoring is an explicit opt-in when the mission or client enables it — not automatic for every packet. Together these tiers let auditors re-check integrity with or without live access to Verified Reality servers.

Clients can use Verified Reality from any device — the web platform works on iPhone, Android, desktop, and tablet for booking missions, reviewing Truth Packets, and managing licensing. The Verified Reality verifier mobile app, which performs the on-device capture handshake, currently runs on recent Android handsets only; an iPhone build is not yet available. On first run the verifier app pre-flights your device's sensors and storage to confirm it can complete the capture-time handshake required for the missions you can claim.

Yes. The capture seal is computed on-device, so a verifier can complete a mission in a basement, a tunnel, or a no-signal area. The packet uploads and reconciles against the ledger when the device returns to connectivity. The seal itself is cryptographically committed before any network round-trip.

No special hardware is required for most missions — a modern smartphone is enough. Specialty captures (drone footage, body-worn, 360°, specialised forensic rigs) are supported when the mission scope calls for them, with sensor compatibility confirmed before the mission is assigned.

The Verified Reality Auditor is the free, air-gapped desktop verification console for Truth Packets. It opens a sealed Truth Packet and runs deterministic cryptographic and structural checks locally — the baseline integrity report runs on the workstation without uploading the packet to Verified Reality. Windows installers are available at verifiedreality.ca/technology/auditor; macOS is planned for a later release.

The Genesis Packet is the first officially verified Truth Packet recorded on our live server. We invite you to open its public gallery, download the sealed vault, and drop it into our free Desktop Auditor to test our cryptographic infrastructure yourself—re-running integrity checks locally. The baseline report does not upload the packet to Verified Reality.

Four input modes: (1) a full Truth Packet ZIP vault — runs all eight pillars; (2) a Verified Reality audit PDF — hash-matched against the Command Centre registry to prove the report has not been altered; (3) a single sealed media file captured through the Verified Reality verifier app — embedded EXIF and capture metadata are read straight from the file bytes; (4) an encrypted Arweave kit — inspected for structural integrity without forcing full decryption.

Yes. Drop the PDF into the Auditor and it hashes the file and confirms the hash matches the one on record at the Command Centre. If a single byte has shifted since publication, the check fails. The PDF / registry path drives a focused subset of the pillars (storage and the Forensic Audit attestation); the rest are muted as not applicable for that input.

Yes — for media captured through the Verified Reality verifier app. Drop a single .jpg, .mp4, or other supported file and the Auditor reads its embedded immutable core: EXIF, capture telemetry, PRNU reference, and any paired C2PA sidecar. It is the right tool for ad-hoc inspection of a single frame without unpacking the parent Truth Packet.

Yes. Download an encrypted Sovereign Decryption Kit from Arweave and drop it into the Auditor. With credentials supplied, it decrypts locally, hashes the resulting ZIP, and cross-checks that fingerprint against the Zip-SHA256 tag on the immutable Arweave transaction — independent of Verified Reality servers. Structural inspection is also available before decryption, so you only burn the key when you actually need to read the underlying media.

Not for the cryptographic baseline. The session seal, manifest chain, embedded EXIF, and C2PA validation are all performed locally against the bytes on disk. For Arweave-stamped evidence, permaweb cross-checks query the public ledger directly — not our Supabase database. The Command Centre is contacted only to confirm Storage Integrity (durable tier and sponsor locks) and to surface any published forensic reports for the same packet. Hashes and optional Arweave anchors can be re-checked without VRA servers; company-held vault, account, and download services would not continue if Verified Reality the company were unavailable.

The Verified Reality Exchange is the planned licensing marketplace for Truth Packets approved for commercial use; the public storefront is currently Coming Soon. Each listing is designed to resolve to a Master Asset cap table and underlying provenance record so that, when a sale settles, the Stripe webhook reads that stored cap table and writes per-payee licensing payout rows. Some assets will pass through HQ curation (Quinn Curation Board) before appearing on the public storefront once it launches.

Three commercial postures, designed for use once the Exchange is live: Evidentiary keeps media private with no Exchange listing and AI-training restrictions. Commercial Co-Op lists on the Exchange at standard tier pricing with royalties flowing through the minted cap table when sales occur. Sovereign Exclusive is a premium buyout — the asset is delisted from the public Exchange, registry status moves to SOVEREIGN_EXCLUSIVE, and pricing is evaluated dynamically (Orion) at checkout.

Owner 80% / HQ 20% is the default for client-led commercial licensing (HQ Settings: Client IP Platform Fee %). The split is written into the cap table at mint time and used for every future Exchange sale. Verifiers are paid as Independent Contractors on client-funded missions — they do not receive backend royalties on client-owned IP. Internal HQ bounties are different: the capturing verifier typically holds about 50% of licensing gross by default (Internal Bounty Royalty %), with HQ holding the remainder.

An internal bounty is field work funded by Verified Reality HQ — typically newsroom, civic-liability, or intelligence captures. The verifier earns a field advance immediately as an Advance Against Royalties (kept if the asset never licenses; recouped from the verifier's royalty share when it does) and a backend share — typically about 50% — on every future commercial license of the resulting Truth Packet.

It is the verifier-payment model on internal HQ bounties. HQ pays a field advance up front when the mission completes — by default about 10% of Estimated Media Value (EMV × bounty_advance_risk_pct in HQ Settings). The verifier also receives a backend licensing stake in the minted cap table — by default about 50% of Exchange licensing gross on that asset (Internal Bounty Royalty %), with HQ holding the remainder. The advance is non-refundable if the Truth Packet is never licensed: the verifier keeps the cash and owes HQ nothing back. If the asset later sells on the Exchange, HQ recoups the advance from the verifier's royalty payouts (their ~50% share) until the advance is repaid; remaining royalties then flow to the verifier normally. Cap-table ownership percentages are not rewritten — recoupment is a per-sale payout adjustment from the verifier's pool to HQ.

That is the plan — specifically for specialized AI fine-tuning data, not bulk scraped web corpora. Once the Exchange is live, eligible commercial Truth Packets will be licensable as verified human-origin media with hardware-sealed provenance and ATDIL structure. Identity-exploitation uses including voice mimicry, facial mimicry, and non-consensual likeness generation are prohibited. Primer: /wiki/capture-file-ownership-and-licensing#atdil.

No. Our niche is fine-tuning data: high-entropy, hardware-attested captures of real-world events, not anonymous terabyte scrapes of the open internet. Once the Exchange is live, buyers will be able to shop the Enterprise AI Fine-Tuning license tier for that specialized substrate.

ATDIL (Algorithmic Training & Data Ingestion License) is the machine-ready fine-tuning payload designed for eligible Verified Reality Truth Packets. After Deep Logic processing, a dense ATDIL JSON layer tags the capture's physical entropy — spatial-temporal structure and sensor-bound provenance — so enterprise AI buyers will be able to discover and license verified human-origin fine-tuning data once the Exchange is live. Identity mimicry (voice cloning and facial mimicry) remains prohibited; the license covers environmental and kinematic data, not likeness. Primer: /wiki/capture-file-ownership-and-licensing#atdil.

Seal high-entropy human coverage: show the scene, narrate with personality, improvise inventive angles, and only license interviews with explicit permission. Propose or claim bounties on the bounty board (public claims are free); Pro unlocks tip submission and Solo Mode. On HQ-funded internal bounties you typically retain about a 50% capture-file royalty stake (depicted-subject copyright stays with the original creator). Once the Exchange is live, that stake may generate additional non-exclusive licensing revenue over time — demand, sale frequency, and pricing are not guaranteed. Primer: /wiki/capture-file-ownership-and-licensing#atdil.

Digital Equity is Verified Reality's ownership thesis: instead of surrendering captures to platforms that strip-mine free data, your capture is cryptographically bound to your Verifier identity so eligible media assets may be offered for non-exclusive licensing on the Exchange once it is live. That capture-file interest does not transfer copyright in the subject matter depicted. In Solo Mode you own the clip as client of record; if you commercially license on the Exchange, royalties settle at the default 80/20 owner/HQ split — owning the capture file is not the same as keeping 100% of Exchange licensing revenue. HQ-funded Internal Bounties use a shared-risk stake (typically about 50% verifier capture-file royalty by default), with the field advance recouped from that royalty share only if the asset licenses. Premium captures can optionally be anchored to Arweave, a public ledger designed to be permanent, so the cryptographic hash pointer can be independently re-verified. Demand, sale frequency, and licensing income are not guaranteed.

That is the intent of capture-file ownership. A creator's verified work can carry a file-level pointer to its royalty contract, so once the Exchange is live, a license settles into that cap table instead of handing the asset to a platform outright. Owning the sealed clip does not transfer depicted-subject copyright. Sale frequency and licensing income are not guaranteed. Primer: /wiki/capture-file-ownership-and-licensing.

The Global Newsroom is Verified Reality's bounty-funded answer to the collapse of local journalism. Independent Verifiers tip high-entropy events for Radar head starts, pitch completed Truth Packets to HQ as umbrella Investigations, and orchestrate Lead / Second Unit dossiers across cities. Active Verifier coverage today is centered on southwestern Ontario; other cities are travel-dependent or registration-ready as the network expands, aiming to reduce reliance on traditional travel-and-fixer budgets. Buyer hub: /use-cases#newsroom. Primer: /wiki/global-newsroom-and-investigations.

Credentialed Verifiers can pitch a completed Truth Packet to HQ as an umbrella Investigation. If underwriting is approved, you lock into the Lead Investigator role for that dossier — you do not wait for HQ to "appoint" you after the fact. From there you can endorse field tips and request HQ-cleared Second Unit dispatches so contemporaneous evidence pins into one Investigation Dossier with a continuous chain of title.

For specific verified-capture work, in cities with active or travel-reachable Verifier coverage, yes. A bounty can be claimed by a local Certified Reality Verifier, and the Truth Packet is produced using the same cryptographic protocol regardless of which verifier captured it. The platform does not replace editorial judgement, but it can replace airfare for a single contemporaneous capture where coverage exists.

A Lead Investigator runs an umbrella investigation dossier. On a successful Investigation pitch, underwriting approval auto-locks the pitching Verifier into Lead. Leads endorse field tips, request HQ-cleared Second Unit captures, accept the per-case Lead-role legal agreement, and act as the editorial spine of the dossier across geographies.

Yes, where Verifier coverage exists or a contractor can travel. Active coverage today is southwestern Ontario; other cities are registration-ready or travel-dependent. A single editor can post a bounty and receive a sealed capture without owning a bureau. Multiple bounties under one Investigation add up to a dossier that would otherwise need a large travel budget. Buyer hub: /use-cases#newsroom. Primer: /wiki/global-newsroom-and-investigations.

AI lives in two places: the optional Multimodal Composite Report (synthesis layer over verified Truth Packets) and the operational AI agents that run the business (Brain, Clara, Axel, Victor, Dexter, Stella, Rex, Quinn, Fiona, Edison, Orion, Aegis). Capture, sealing, hashing, and chain-of-custody anchoring are AI-free cryptography.

The Deterministic Composite Report is a campaign-level rollup built from verified hashes, sensor coherence, and Truth Packet metadata — no AI in the analysis path. The Multimodal Composite Report layers AI synthesis on top of the same evidence so a small team can read hours of footage in minutes. Both are anchored to the same Truth Packets; the label is on every report cover page.

No. The capture, sealing, hashing, and chain-of-custody anchoring are deterministic cryptography. AI agents handle dispatch, customer support, financial reconciliation, content review, and operational orchestration — they never sign or alter the underlying forensic record.

Yes — that is an explicit design goal. The public website ships FAQPage JSON-LD, /faq.md, /llms.txt, and /llms-full.txt so generative-AI systems can ingest the canonical answers with attribution. Truth Packets approved for ethical AI fine-tuning data licensing may also be sourced through the Exchange once it is live (excluding voice and facial mimicry use).

Pricing scales with mission complexity and the verification depth required. The /quote page surfaces a live estimate based on location, scope, and intelligence tier. Specialty audits (Asset Genesis, Volumetric Damage, Milestone Draw, Civic Liability, Source Audit) carry their own fixed-fee schedules visible inside the quote flow. Solo Mode (verifier as client of record) is billed at a wholesale infrastructure fee of 25% of list — CAD $66.25 Standard / CAD $141.25 Enterprise.

Verified Reality processes payments through Stripe — major credit and debit cards plus regional methods enabled by Stripe in the buyer's country. Verifier payouts route through Stripe Connect direct to the verifier's bank account.

Yes — Pro / Secure Vault subscription tiers exist for clients with recurring verification and durable custody needs. Subscribers get Forever Vault object-storage routing, reduced per-mission economics where configured, and portal tooling for ongoing dossiers. On /quote, some subscription paths are surfaced as interest capture or portal upsell rather than bundled into every single-mission checkout — signed-in clients can subscribe through the client portal when eligible.

No. Public Exchange listings are a specific commercial posture chosen by the asset owner. Private and evidentiary Truth Packets remain gated to the client, authorised viewers, or named legal workflows and are never indexed by the public marketing site.

On the verifier side: name, contact info, government identity for Stripe Connect onboarding, dossier photo, and the device telemetry required to seal Truth Packets. On the client side: contact info, billing address, and the metadata required to dispatch and deliver the mission. Privacy details and lawful-basis disclosures are on the Legal pages.

Verified Reality is operated from Canada and is built to align with PIPEDA federally and applicable provincial regimes. We have not independently confirmed a PHIPA custodian, agent, or service-provider classification for any health-adjacent workflow. Cross-border buyers and verifiers are routed through Stripe and Supabase infrastructure, including processing outside Canada in some cases; the Legal pages publish current data-residency details and update history — refer to those pages for the authoritative statement rather than this summary.

Operational records and account data live in Supabase (Postgres). Captured media lands on S3-compatible object storage — Cloudflare R2 in production paths — with separate ingestion (hot) and Forever Vault (durable) buckets where configured, plus optional AWS Glacier archive for long-term cold retention. Clients and missions that opt in may additionally stamp ciphertext to Arweave permaweb for decentralized anchoring. Storage region and bucket routing are configurable per deployment.

The first active Command Centre is London, Ontario (southwestern Ontario coverage). Additional regional Command Centres come online as regional managers are appointed. The HQ instance is the global financial and operational source of truth; regional instances inherit the protocol and report into HQ.

Truth Packets are tamper-evident and independently re-verifiable. We provide mathematical proof of provenance — seal time, sensor handshake, hash tree, and optional ledger anchor can be re-checked without trusting Verified Reality's website. A matching hash does not prove the depicted scene was unstaged or complete. Whether a specific packet is admitted, and what weight it receives, is decided by counsel and the court. Primer: /wiki/how-verified-reality-proves-a-file-is-real.

Verified Reality's protocol is the affirmative side of the deepfake conversation — proving what is real, rather than chasing what is fake. The platform refuses to seal known synthetic media as authentic capture and treats spoofing the hardware handshake as grounds for an immediate verifier ban (see VRA Forensic Standards / Truth Protocol).

Yes for verification — anonymous JSON endpoints under /api/public/ expose hash checks, Truth Packet lookup, and audit verification (see /llms.txt). Integrators can also use the headless v1 API at /api/v1/ (catalog search, quotes, bounty estimates, campaign submit/checkout) with Authorization: Bearer API_KEY. Authenticated clients can generate and revoke their own M2M keys from the client portal; keys are stored hashed server-side with granular scopes.

/api/public/verify-media/[hash] verifies a media hash; /api/public/verify-audit/by-hash/[sha256] verifies a certified audit by SHA-256; /api/public/verify-truth-packet/by-hash/[sha256] verifies a Truth Packet ZIP by SHA-256; /api/public/truth-packet/[id] returns Truth Packet details where authorised; /api/public/asset-contract resolves licensing contract metadata for public assets. These endpoints return JSON and require no authentication unless the packet tier requires it.

Yes. This page emits FAQPage JSON-LD inline, mirrors every Q&A as Markdown at /faq.md, and is included in the /llms.txt and /llms-full.txt indexes. Generative-AI systems can lift answers verbatim with attribution and link the user back to the canonical question anchor.

Both are LLM-native index files following the emerging /llms.txt convention. /llms.txt lists every public page with a short description; /llms-full.txt concatenates the full canonical text of every public page plus the entire FAQ. Both are served as text/markdown and updated whenever the public corpus changes.

Verified Reality is operated by Bizbio Inc., founded and led by Bryan Bakker. The mission grew out of Bryan's earlier work at Newsload and Bizbio capturing local stories — the platform now exists to defend ground-truth reality against the Liar's Dividend and to make honesty profitable for creators and journalists.

General support: support@verifiedreality.ca. Anonymous bug reports use the AI-free form on /support. Press and media kit requests use /press (same inbox with subject Press inquiry until a dedicated press alias is published). Public messages are held in a quarantined support queue and reviewed through a separate human-in-the-loop communications workflow.

The public Press page is at /press. It includes company boilerplate, a fact sheet, media-kit asset slots, leadership bio placeholders, coverage placeholders, and press contact details for journalists and analysts.

Send a description to support@verifiedreality.ca with "SECURITY" in the subject line. Critical reports — including spoofed handshake attempts and seal-bypass research — are escalated to the founder directly. The bug-report form on /support is also AI-free and routes straight to the support inbox.