Aura by OmniConflux
Network Governance and Privacy Isolation
How Aura by OmniConflux is designed to handle earnings, advertiser vetting, on-device isolation, and consent. Aura is planned, not live.
Aura by OmniConflux is not yet live. The governance policies, auction design, isolation rules, and ledger rules described on this page reflect the network design specifications. Network applications and payouts will open after corporate formation and public launch.
On-Device Classification
Context classification is designed to run locally with a fixed topic taxonomy. Source code, repository contents, file paths, and prompts are designed never to leave your machine.
- •Only coarse topic tags, and at most a one-line synthetic summary, are designed to leave the machine.
- •Classification is planned to run on-device during active sessions.
- •Humanness and input cadence scores are designed to be computed on-device, without sending keystrokes or diffs.
- •No persistent remote profiles and no cross-site tracking in the design.
Explicit User Consent
In the Aura design, the network is opt-in and off by default. You decide whether it runs at all.
- •Off by default until you opt in.
- •One toggle turns the whole network off.
- •An inspector shows exactly which tags leave the machine.
- •Planned: per-slot toggles and a per-category advertiser block list.
Advertiser Vetting & Disclosure
Demand is planned to come from direct campaigns and developer tool affiliate programs. Every advertiser and creative is designed to be reviewed before it can run.
- •Creatives are text only: one short line and one link, with no code, scripts, or tracking.
- •Each advertiser and creative is to be reviewed against the Aura advertising policies before it runs.
- •Every placement is designed to be labeled Sponsored.
- •Auctions are designed with short timeouts so they never slow your tools.
Verifiable Yield & Ledger
In the design, a view only earns credit after continuous focused visibility (such as 5 to 10 seconds of focused window time), so advertisers pay for real human attention.
- •Qualified views are designed to require continuous focused visibility and an on-device humanness check.
- •Designed to filter out headless server, CI, and datacenter traffic.
- •Planned local and central ledgers you can inspect.
- •Host revenue share: announced at launch.
Placement Integrity
Display Surface Rules
Aura is designed to keep sponsorships apart from your tools. A sponsored entry must never get in your way or change what an agent does. Advertisers and creatives will be reviewed against the advertising policies before they run.
Idle Status Line
Designed to show a short contextual line only when the terminal or dashboard is idle. Never over errors, system alerts, or resource limits.
Task Completion Summary
Designed to appear below a completed agent summary, framed apart from agent output so a sponsored tool is never mistaken for a model suggestion.
Dedicated Surfaces Only
Planned only for 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. In the design, source code, file contents, environment variables, and agent prompts stay on your machine. An on-device classifier assigns broad topic tags, and only those tags, or at most a one-line synthetic summary, are used for matching.
How are advertisers vetted?
Every advertiser and creative is designed to be reviewed against the Aura advertising policies before it runs. Creatives are text only, with no code, scripts, or tracking, and every placement is designed to be labeled Sponsored.
Where do sponsored messages appear within the platform?
In the design, sponsored items appear only in set OmniConflux slots, such as idle status lines and completed task summaries. They are labeled and never interfere with terminal output or background work.
When and how are host earnings calculated and distributed?
Under the network design, qualified views are checked against continuous focused visibility thresholds and credited to a ledger. Payout details, minimum balances, and the host revenue share will be announced at launch.