AuraAI · Mycelium Protocol · Apache 2.0

The engineer, no longer deployed
but still present

AI's next stop isn't a smarter model — it's getting the model into every real context. The people who did that were called FDEs: Palantir's 2010 coinage for institutionalized grunt work — you had to get inside the customer to see the real jam.

We think the role outlasts the name. It's the ANE — AI Native Engineer: not deployed, but fluent in what AI can and cannot do, turning pain into product for individuals, small orgs, and cities.

This repository is their workbench.

FIG. A

Not deployed, but present

He stands outside the client's building — his feet never cross the threshold. But his hands reach in through the window and turn the gears. The thing inside moves because of him.

A figure stands outside a building and reaches through the window to turn the gears inside
01 / The Premise

When the cost of productivity
approaches the price of electricity,
what's left for you to do?

This forecast has no rigorous scientific proof behind it. It grew out of personal observation and the feedback of many sources. But it determines everything about how this repository is designed.

First, what won't disappear: the person frying dough sticks, the bakery, all of service work. Eating bread is far less efficient than an injection of nutrients — yet most people will never take the shot. Because humans carry ingrained habits and emotional needs, and it is precisely those things that make you a person. Give them up, and the human flavor goes with them.

— On what cannot be replaced

What does get restructured is commercially driven work — the roles that exist purely in pursuit of extreme efficiency. There, we believe only three roles retain core value. And they are not mutually exclusive; they stack: an ANE may also be an Innovator, and may also be a YouTuber.

FIG. B

One person, three ways to live

The Expresser speaks into the megaphone — the things only a person can say. The Innovator carries a lantern into the fog and leaves a path behind for others. The Builder kneels down and fixes the wobbly stool that hurts someone every day.

Three figures: one with a megaphone, one carrying a lantern into fog, one fixing a stool with a wrench
02 / The Map

Demand side · Three roles · The ANE work loop

On the left, who needs to become AI native. In the middle, who they should go find. On the right, how that person actually works. The band along the bottom is what we provide.

A · DEMAND SIDE / WHO NEEDS AI NATIVE 👤 Individual → Sin90 Information → Action → Connection → Communication → ⟲ back to Information Life · learning · social · work 🏢 Community / SMB → Cos72 Knowledge base ⟵ sediment ⟵ org workflow Org brain = LLM API + self-trained LoRA Connectors / Sensors (agents of all kinds) Can't afford an FDE — so be your own? 🏙 City → CityOS Inter-org collaboration · resource pooling Becomes an agent; draws talent seeks B · THREE ROLES / WHO CAN HELP Expresser KOL / blogger / honest voices Innovator Thinker · explorer · pathfinder Builder = ANE · AI Native Engineer Not deployed, but present The three stack · no hard borders method C · SUPPLY SIDE / THE ANE WORK LOOP Existing AI Arch · domain · limits New capability Rewrap · compose New resources Enterprise / org context Deep dialogue Pain point Only repeated talks find it With org workflow Solution Iterated continuously Generalize Abstracted into product feeds the library Product flows back · serving individuals / orgs / cities → they truly become AI native FOUNDATION · WHAT THIS REPO PROVIDES SELF-FDE WORKBENCH — open methodology · tooling · digital public goods Sin90 (individual OS) · Cos72 (org OS) · CityOS · one-click multi-platform publishing · pain-point matchmaking · model selection / LoRA / memory supports · all open source, Apache 2.0
Fig.1 — Self-FDE WorkBench overview hand sketch → structured · 2026-07-12
FIG. C

The ANE flywheel

The map above, in plain words: pull the bent nail out of the client's floor (the pain point), forge it into a usable tool (the product), drop it in the toolbox — which is now fuller, so the next nail comes out easier.

A circular loop: pulling a bent red nail from the ground, an anvil, a wrench, and a full toolbox
Original hand-drawn sketch
Fig.0 — the original sketch (hover to see it as drawn)
Origin

It all started on one notebook page

The diagram above didn't come out of a template. It's the structured version of this handwritten page — left side: the three constituencies and their operating systems; right side: the ANE work loop and the three roles.

Every sentence spoken while explaining this page was archived verbatim. Views will change, but how we thought at the time is worth keeping.

Read the blueprint →
03 / Digital public goods

Three operating systems

Individuals, small organizations, cities. Three constituencies, three Apache 2.0 open systems. They are not products. They are digital public goods.

System For Core Status
Sin90 Individuals Built around the growth loop — Information → Action → Connection → Communication — to raise ordinary people's digital wellbeing Designing
Cos72 Communities / small orgs / businesses Knowledge base + org workflow + org brain (LLM API + self-trained LoRA) + connectors In progress
CityOS Cities Inter-org collaboration and resource pooling — the city itself becomes an agent, drawing capital and talent across borders Long term
Explore the three systems →
04 / Join

Ten years ago, every industry had to go online.
Now, every industry has to go AI.

This is not a prediction; it's a settled fact sitting in plain view. AuraAI, as an organization that gathers ANEs, keeps accumulating and exchanging what it learns — so that more people can become Expressers, Innovators and Builders.