Aweb system graph.

Position

Aweb is the parent operating layer. The systems are domain tests around it.

GEX, Veritas, Nina, and Leony are not separate mythology. They are public surfaces around one operating question: can Aweb turn a mission into bounded work through tools, provider routing, memory, evaluation, artifacts, and receipts?

The system graph makes the relationship explicit. Aweb is the parent layer. Each subsystem gives the operating model a domain where the claim boundary has to be different.

Systems

Each surface needs its own proof standard.

GEX touches markets, so the boundary must avoid financial advice and performance claims. Veritas touches forecasting, so the boundary must avoid betting promises and fake certainty. Nina touches commerce operations, so the boundary must avoid unverified revenue claims. Leony touches creative workflows, so the boundary must avoid fake persona or platform-reach claims.

This is why the graph matters. Aweb can share operating primitives across all of them, but the public claim cannot be copied blindly from one domain to another.

• Aweb: Governed agentic orchestration platform. Boundary: Describe Aweb as a public product and operating layer without claiming fake autonomy, fake funding, or private customer proof.
• GEX: Options and market-structure intelligence. Boundary: No financial advice, trading signals, profit claims, account-performance claims, or betting-style guarantees.
• Veritas: Prediction-market and probability intelligence. Boundary: No betting advice, guaranteed predictions, outcome promises, or financial-performance claims.
• Nina: Commerce and digital-product operations. Boundary: No revenue claims, customer claims, platform dominance claims, or unverified commerce performance claims.
• Leony: Media, persona, and creative distribution. Boundary: No fake celebrity/persona claims, no unverified platform reach claims, and no hidden provider-spend claims.

Aweb

The common layer is missions, tools, memory, evaluation, and receipts.

The interesting part is not that the systems have names. The interesting part is that they can share an operating posture: mission before motion, tools under rules, receipts before belief, and a human operator who remains responsible.

Aweb is where that posture becomes reusable. The subsystem pages make the graph public. The studies explain the operating model. The conversation page gives people a public-safe way to ask what is real, what is still becoming sharper, and what should not be claimed.

Boundary

This graph is public identity architecture, not a private system map.

This page does not expose private services, internal routes, customer data, API keys, databases, or private operational logs. It only maps public pages, public system names, public URLs, and public-safe claim boundaries.

The public purpose is discoverability and clarity: Daniel Wahnich, Aweb, GEX, Veritas, Nina, and Leony should be connected as one work graph without collapsing their domains into vague AI branding.