Journal post – Weekly Connections #1
Plato, Alphabets, Logic & Space Risk
Each week I’m asking myself a simple question:
What new connection did I make across disciplines that could one day create value for others?
This week’s connection: ancient philosophy + alphabets + Euclid + AI-driven space-risk systems.
The connection
I finished my first blog post on Plato’s Republic, kept going with Aristotle’s Nicomachean Ethics, completed Lesson 1 of mathematics (Aristotle’s logic + Euclid’s Book I), pushed further into Arabic writing, and read a stack of pieces on modern space politics and AI, including:
US–Middle East space partnerships
Arguments for a Yuma spaceport and a southern launch corridor
The “fallacy of being first” in Moon/Mars exploration
AI for environmental change detection and military C2
Non-Earth imaging and space-to-space surveillance
On paper these look unrelated.
But they’re all training the same muscle: the ability to live and think inside a structure.
Plato and Aristotle → how to order a life and a city.
Euclid → how to order arguments and proofs.
Arabic → how to order sounds and meaning on the page.
Space policy & AI articles → how nations and companies try to order power, risk, and infrastructure in orbit.
Those are exactly the questions I’m trying to solve with AION:
how to design systems for space insurance where logic, incentives, data, and behaviour stay in harmony instead of colliding.
Plato’s tripartite psychology (reason, spirit, appetite) is slowly turning into a design lens for AION architecture.
Euclid is teaching me the logic of structure.
Arabic is teaching me the discipline of symbols.
Space politics is teaching me how those inner structures meet real-world power.
Together, they’re forming an inner blueprint for how to build outer systems.
What I studied
Plato & Ethics
Finished Republic and published my first long-form reflection.
Read Books 7–9 of Aristotle’s Nicomachean Ethics (pleasure, friendship, character).
Mathematics – Lesson 1 (Ancient Method)
Studied Aristotle’s logical structure: terms, propositions, syllogisms.
Copied Euclid’s Definitions, Postulates, and Common Notions by hand – the old Newton/Franklin method.
Wrote my own small “First Principles” page: personal definitions, axioms, and a syllogism.
Completed a first mini-proof (“the whole is greater than the part”) and did basic logic + geometric reasoning exercises.
Arabic (Lessons 2–4)
Now comfortable writing and joining all 28 letters.
Starting to recognise word patterns and write with more flow.
Historical & Intellectual Research
Watched deep dives on Jefferson, Franklin, Washington and added notes into my School of Thought database.
What I researched (space, AI & policy)
AI infra & orchestration maps
Frameworks for how LLMs, agents, retrieval and tools fit together.
Confirmed that AION sits in the workflow/orchestration and risk infra layers, not as “just another app”.
Reinforced the decision to build a Context + Memory Engine and AI Council instead of scattering RAG scripts everywhere.
Agentic systems & token efficiency
Threads on using fewer tokens, more tool calls, and lightweight local models.
Fed directly into the idea of the AI Council as a cost-aware “Code Mode” layer, not a giant prompt that does everything.
Founder/operator reality checks
Lists of what solo builders actually end up doing: product, sales, decks, infra, support.
Helpful as a sanity check: AION can start as a solo “Jarvis-for-space” lab, but real traction will probably need partners and a focused wedge.
20s philosophy & “rock bottom on purpose”
Advice threads about upskilling, embracing discomfort, and rejecting the default 9–5 → 40–year ladder.
Lined up almost eerily with what I’m doing: deliberate reset at 27, rebuilding identity around systems thinking and the space economy.
“Don’t build from scratch” & YC-style takes
Opinions that in the current AI era, pure from-scratch full-stack coding is a bad use of time for non-engineers.
Validated my own stance: lean heavily on AI tools + existing infra, focus my energy on architecture, risk logic, and product design.
Personal Jarvis & local GPU dreams
Threads about running your own local stack and having a home “AI rig”.
This clicked as a long-term aspiration: an at-home GPU + AION stack acting as my private space-risk lab, not just cloud prompts.
What I built
AION Module 1 — Phase 4
Tested the latest UI sprint for the AION Space Risk Engine.
Continued shaping the risk simulator around a mission-phase timeline instead of generic “cards”.
Started treating Perplexity as a real research assistant, not just a flashy Google.
Research Database v1
Created a new structure for tracking ideas across space, AI, engineering, history, risk, and philosophy.
It feels like moving from “collecting links” to building a long-term mental operating system.
Brand foundations
Cleaned and relaunched my X account for public experiments.
Redesigned my Squarespace site to feel more cohesive.
Published my Plato’s Republic reflection.
Workspace upgrade
New chair, new bookshelf – Monk Mode shouldn’t happen on a collapsing chair and a pile of boxes.
Small takeaways
Systems borrowed from philosophy (Plato / Aristotle) are surprisingly powerful blueprints for software architecture and risk governance.
Alphabets and axioms look simple, but they’re really interfaces into much larger systems – get them right early.
Writing Euclid by hand did more for my clarity than any modern tutorial.
Ancient philosophers argued about how to order a city; modern builders argue about how to order AI systems and careers. The underlying problem is the same: how to live and build inside a structure that doesn’t waste your one life.
A research database plus good tools (like Perplexity) is a quiet unlock: less hunting, more thinking.
Slow, foundational learning compounds – especially in mathematics, languages, and systems design.