import InternalDocsLayout from "./InternalDocsLayout"; import { Download, Monitor, FlaskConical, Briefcase, GraduationCap, ArrowRight } from "lucide-react"; export default function Space1OwnershipFlows() { return (

This document illustrates how the Axiom Model manifests in real user journeys and internal operations. Understanding these flows is critical for maintaining legal entity separation while delivering a seamless user experience.

The Core Principle

Foundation Owns

The Mission - Programs, curriculum, community governance

Corp Owns

The Tool - Software, infrastructure, engineering

User Journey Examples

Example 1: User Downloads GameForge Studio

User visits aethex.dev/downloads Stays on Corp domain
  • • Download button links to Corp-hosted binaries (GitHub releases or Corp CDN)
  • • The .exe is signed with Corp's code signing certificate
  • • User opens app → sees "GameForge Studio" branding (Foundation name, Corp-built tool)

Why: Users are downloading Corp-built software. The Corp owns the codebase and infrastructure.

Example 2: User Accesses GameForge Dashboard

User clicks "GameForge" on aethex.dev Redirect to aethex.foundation/gameforge
  • • User sees Foundation branding, curriculum, mentorship info
  • • URL bar shows aethex.foundation
  • • The Foundation domain reinforces this is a non-profit educational program

Why: The Foundation owns the GameForge program. Users must see the Foundation URL to trust the non-profit mission.

Example 3: User Browses Labs Research

User clicks "Labs" on aethex.dev Redirect to aethex.studio
  • • User sees proprietary R&D, experimental projects
  • • The separate domain signals this is the Corp's Skunkworks division
  • • Security-sensitive work with PII scrubbing and code monitoring

Why: Labs is proprietary Corp R&D. The separate domain protects IP and client confidentiality.

Example 4: User Books a Consulting Call

User visits aethex.dev/corp/schedule-consultation Stays on aethex.dev
  • • No redirect - this is the For-Profit's revenue-generating service
  • • Appropriately hosted on the commercial domain
  • • Client contracts, billing, and service delivery happen here

Why: Corp services generate revenue. The commercial domain is appropriate for for-profit activities.

Internal Operations Example

Example 5: Service Contract Flow (GameForge Studio .EXE)

The Foundation needs the GameForge Studio desktop application to deliver its educational program. Here's how the ownership and development flow works:

1️⃣

Foundation Requests

Foundation needs software to execute the GameForge Plan (KND-001)

2️⃣

Corp Builds

LABS team develops GameForge Studio .EXE as Custom Software Development

3️⃣

License/Donate

Corp licenses software to Foundation (nominal fee or in-kind Service Donation)

Why This Structure?

  • Funding: The Corp has revenue (from EdTech/Consulting) to pay engineers. Non-profits can't fund app development.
  • Security: Corp owns the codebase, enabling the LABS BOT to monitor for proprietary leaks and PII scrubbing.
  • Tax Efficiency: Corp can write off donated development hours as a charitable contribution.

Routing Summary Table

Route Destination Legal Entity Action
/foundation/* aethex.foundation Non-Profit (Guardian) Redirect
/gameforge/* aethex.foundation/gameforge Non-Profit (Program) Redirect
/labs/* aethex.studio For-Profit (Skunkworks) Redirect
/nexus/* aethex.dev For-Profit (Monetization) Local
/corp/* aethex.dev For-Profit (Services) Local

Key Takeaway

The URL bar is the user's window into our legal structure. When they see aethex.foundation, they know they're interacting with the non-profit Guardian. When they see aethex.dev, they know they're on the commercial platform. This transparency builds trust and ensures legal compliance.

); }