Bounties Guide

Understanding HQ-Funded Missions vs. Client-Funded Contracts

Within the Verified Reality (VRA) ecosystem, a Bounty serves as the master contract framework for a specific field capture assignment. Rather than an employment opportunity, a bounty represents an unassigned commercial brief that populates on terminal Radars for autonomous selection by independent contractors .

While all incoming data payloads move through the same underlying system pipeline, the specific funding source dictates the payment structure, intellectual property (IP) allocations, and downstream marketplace lifecycle behaviors. The network identifies the bounty classification programmatically via backend database schemas, ensuring automated execution across all pipelines.

RELEASING ASSIGNMENTS TO THE FIELD

The lifecycle of an unassigned asset brief moves through a clear programmatic sequence: Completion, then Closed Vetting Queue, then HQ Veto/Clearance Gate, then the 72-Hour Dark Window, and finally Open Exchange Live Cascade.

When a bounty master contract is formally authorized and transitions into the dispatched state, the platform's background distribution framework populates the active radar matrix. At this precise millisecond, the field contractor's fixed milestone settlement fee is permanently locked and stamped onto the assignment data container according to the specific tracking model (Internal or Client-Funded) .

The system dynamically applies automated Head-Start Windows based on objective performance data filters:

•  

  The Open Bounty Pool: Standard high-entropy assignments require a Credential 2 (C2) validation status or higher, displaying openly to the regional network pool .

•  

  The 60-Minute Tip Monopoly: For verified field intelligence submitted via the Pro Portal, the system grants the originating terminal an exclusive 60-minute head start, blinding the coordinates from nearby competitors to allow the developer to secure their field position .

OWNERSHIP, BALANCES, AND ROYALTIES

Once a digital data container is finalized in the field, it is securely transmitted to our ingestion servers. The platform generates an independent metadata record—the JSON Evaluation Blob—to catalog environmental traits without altering the immutably sealed file binary . Downstream transaction routing and royalty splits are strictly determined by the funding source track.

Track 1: HQ-Funded Internal Intel Bounties

•  

  Overview: Internal Bounties represent data collection paths where platform HQ funds the capture upfront as a corporate asset investment . HQ maintains ownership of the resulting data container and coordinates the long-tail licensing distribution pipeline across the open marketplace.

•  

  The Advance Against Royalties Model: The upfront fee displayed on the Radar represents an Advance Against Royalties. HQ calculates an Estimated Market Value based on local data density, and the field contractor receives 100% of this stated advance immediately upon successful server ingestion.

•  

  The Axel Vetting Safetynet: Payloads are scanned automatically by the read-only triage engine (Axel) for environmental integrity . Technical tracking flags do not invalidate the contractor's payout; the fixed milestone advance is guaranteed for successful execution of the physical field protocols .

•  

  Ongoing Residual Structure: Because the upfront payout functions as a capital advance, the field contractor retains a permanent 5,000 Basis Point (50.0%) equity stake within the IP Royalty Ledger . Every time a media outlet or AI training laboratory licenses that unique Master VRA Asset ID, 50% of the gross transactional yield settles directly to the contractor's ledger vault in perpetuity. HQ recovers its initial advance strictly out of its own half-share of future marketplace sales.

•  

  Data Ingestion Path: These missions originate from automated network sweeps, newsroom editorial demands, and verified operator tips . Upon successful ingestion, files move to the pending review queue for validation before initializing the 72-hour Newsload exclusivity countdown.

Track 2: Client-Funded Bounties (B2B Lead-Gen Pipeline)

•  

  Overview: For these bounties, an external business entity allocates upfront capital to secure specific localized data parameters. Bizbio Inc. acts strictly as a neutral technology infrastructure facilitator and common-carrier clearinghouse, managing the automated dispatch matching matrix. HQ does not deploy corporate capital to underwrite the capture.

•  

  The Subcontractor Milestone Fee Model: The independent contractor receives a flat, fixed Subcontractor Milestone Fee representing 50% of the total gross value allocated by the client brief .

•  

  Work-for-Hire Constraints: Compensation is delivered strictly as a one-time settlement for the extraction and ingestion of the physical data container. Symmetrically mapped to the financial ledger rules, client-funded assignments carry exactly 0 Basis Points in backend royalties; the contractor retains no tailing interest or downstream tracking parameters within the IP Royalty Ledger.

• Content Control, Sovereign Windows, and Automated Cascading: The funding client secures exclusive data utility and broadcast rights over the Truth Packet for exactly seventy-two (72) consecutive hours from the moment Platform HQ grants administrative clearance and initializes the storefront status of an embargoed preview.

• System-Enforced Technical Lifecycle Paths: To protect platform liquidity and prevent clients from locking up data assets indefinitely by ghosting the platform, the interface removes all manual "opt-out" toggles from the client dashboard. The client must select between two distinct technical lifecycle paths before the 72-hour countdown expires:

  • Automated Storefront Cascading: If the client takes no administrative action before the 72-hour countdown expires, the database state machine executes an automated technical bypass. The verified container automatically cascades live onto the open, non-exclusive VRA Exchange marketplace storefront for general B2B commercial licensing, subject to a 20% platform notary fee.

  •  

    Sovereign Exclusive Buyout: At any point during the active 72-hour window, the client retains an absolute Right of First Refusal to pay the premium checkout fee and execute a permanent Tier 3 Sovereign Exclusive License . This upgrades the data container's ledger parameters, removing it from the public staging deck and routing it into an absolute, permanent private lockout status forever.

CORE STATUS LIFECYCLE SUMMARY

• HQ Staff Review Required (pending_approval database state): Ingestion payload locked. Axel and Stella execute read-only automated triage scanning for privacy and branding vectors .

• 72h Sovereign Window Active (EMBARGOED_PREVIEW database state): Administrative clearance granted and the 72-hour countdown initializes. Public non-exclusive checkouts are blocked during this phase. Track 1 assigns exclusivity to the Client, while Track 2 assigns it to Newsload .

• Live on Open Exchange (OPEN_CO_OP database state): Exclusivity window lapsed without a buyout. The file container flips to an exchange-discoverable status for public B2B data licensing and syndication checkouts.

• System Enclave Hold (HASH_MISMATCH_QUARANTINE database state): Mathematical validation failure. This state occurs if a hardware clock or file byte-range tampering is registered at ingestion, freezing all payout tracking indefinitely.