Skip to content

Aura by OmniConflux

Network governance and privacy isolation

How Aura by OmniConflux handles earnings, advertiser vetting, on-device isolation, and consent. Aura runs today for approved closed beta accounts.

The money loop: a sponsored card under the Confluence ring, its strand of light splitting at a glass prism into the network and a wallet

Closed beta network

Aura by OmniConflux runs today for approved closed beta accounts. The governance policies, isolation rules, and ledger rules described on this page are the rules the closed beta runs under. Points and earnings can pay your OmniConflux seat or fund ad credit. Payout by ACH to your bank is planned and is not available yet.

Privacy Isolation

On-device classification

Context classification runs locally with a fixed topic taxonomy. Source code, repository contents, file paths, and prompts are never sent for ad matching.

  • Only coarse topic tags, and at most one short summary built from those tags, leave the machine.
  • Classification runs on-device during active sessions.
  • Humanness and input cadence scores are computed on-device, without sending keystrokes or diffs.
  • No persistent remote profiles and no cross-site tracking.

Demand Quality

Advertiser vetting and disclosure

Demand comes from direct campaigns and developer tool affiliate programs. Every advertiser and creative is reviewed before it can run.

  • Creatives are one short line of text, an optional icon and one link, with no code, scripts, or tracking.
  • Each advertiser and creative is reviewed against the Aura advertising policies before it runs.
  • Every placement is labeled Sponsored first, then its pricing tag: CPM view, PPC click or CPS sale.
  • Auctions have short timeouts so they never slow your tools.

Accounting and Integrity

Verifiable yield and ledger

A view only earns credit after continuous focused visibility (10 continuous seconds of focused visibility), so advertisers pay for real human attention.

  • Qualified views require continuous focused visibility and an on-device humanness check.
  • Headless server, CI, and datacenter traffic is filtered out.
  • The earnings ledger is append-only, and your wallet shows recent ledger entries.
  • Member share: 50 percent of what your ads earn.
  • Daily caps per account on credited views and clicks and their gross earnings: 2,000 credited views, 50 credited clicks or $24 gross a day. Sales are exempt and stay pending until settled.

Placement Integrity

Display surface rules

Aura keeps sponsorships apart from your tools. A sponsored entry must never get in your way or change what an agent does. Advertisers and creatives are reviewed against the advertising policies before they run.

  • Idle status line

    Shows a short contextual line only when the terminal or dashboard is idle. Never over errors, system alerts, or resource limits.

  • Task completion summary

    Appears below a completed agent summary, framed apart from agent output so a sponsored tool is never mistaken for a model suggestion.

  • Dedicated surfaces only

    Runs only on OmniConflux desktop, CLI, and console surfaces. Never injected into other applications, client libraries, or headless worker nodes.

Frequently asked questions

Does enabling Aura expose proprietary source code to advertisers?

No. Aura never sends source code, file contents, environment variables, or agent prompts for matching. An on-device classifier assigns broad topic tags, and only those tags, or at most one short summary built from those tags, are used for matching.

How are advertisers vetted?

Every advertiser and creative is reviewed against the Aura advertising policies before it runs. Creatives are one short line of text, an optional icon and one link, with no code, scripts, or tracking, and every placement is labeled Sponsored first, then its pricing tag.

Where do sponsored messages appear within the platform?

Sponsored items appear only in set OmniConflux slots, such as idle status lines and completed task summaries. They are labeled and stay out of terminal output and background work.

When and how are host earnings calculated and distributed?

Qualified views are checked against continuous focused visibility thresholds and credited to the ledger. The member share is 50 percent of what the ad earns, with daily caps on views, clicks and their gross earnings of 2,000 credited views, 50 credited clicks or $24 gross a day. Sales are exempt from the caps and stay pending until settled. Points and earnings can pay your OmniConflux seat or fund ad credit. Payout by ACH to your bank is planned and is not available yet, and earnings are never promised.