diff --git a/.replit b/.replit index cdaaa961..56884198 100644 --- a/.replit +++ b/.replit @@ -62,7 +62,7 @@ localPort = 40437 externalPort = 3001 [[ports]] -localPort = 46043 +localPort = 45017 externalPort = 3002 [deployment] diff --git a/client/App.tsx b/client/App.tsx index 2a19b4f6..1e1405a5 100644 --- a/client/App.tsx +++ b/client/App.tsx @@ -138,6 +138,7 @@ import ClientSettings from "./pages/hub/ClientSettings"; import Space1Welcome from "./pages/internal-docs/Space1Welcome"; import Space1AxiomModel from "./pages/internal-docs/Space1AxiomModel"; import Space1FindYourRole from "./pages/internal-docs/Space1FindYourRole"; +import Space1OwnershipFlows from "./pages/internal-docs/Space1OwnershipFlows"; import Space2CodeOfConduct from "./pages/internal-docs/Space2CodeOfConduct"; import Space2Communication from "./pages/internal-docs/Space2Communication"; import Space2MeetingCadence from "./pages/internal-docs/Space2MeetingCadence"; @@ -729,6 +730,10 @@ const App = () => ( path="/internal-docs/find-your-role" element={} /> + } + /> } diff --git a/client/pages/internal-docs/Space1OwnershipFlows.tsx b/client/pages/internal-docs/Space1OwnershipFlows.tsx new file mode 100644 index 00000000..d07b6724 --- /dev/null +++ b/client/pages/internal-docs/Space1OwnershipFlows.tsx @@ -0,0 +1,265 @@ +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 +

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
RouteDestinationLegal EntityAction
/foundation/*aethex.foundationNon-Profit (Guardian)Redirect
/gameforge/*aethex.foundation/gameforgeNon-Profit (Program)Redirect
/labs/*aethex.studioFor-Profit (Skunkworks)Redirect
/nexus/*aethex.devFor-Profit (Monetization)Local
/corp/*aethex.devFor-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. +

+
+
+ + ); +}