Skip to content

The Claude Masterclass

Grow a body, not a bot.

Most people ask AI to build them something. This class teaches the way XLNC actually works: give the intelligence your world first, let it design its own instructions, and grow a living system one organ at a time.

You have walked the body. Now learn how a body is grown.

The big picture

Work is changing hands.

For all of history, work meant people. To do more, you hired more. That rule is breaking. The most valuable systems now run on workers that are not human — and the people who see this early will build differently from everyone else.

ERA ONE

GOODS & SERVICES

You sold what you could make or do. Value came from output — and output was capped by hours and hands.

Make & sell

ERA TWO

NETWORK EFFECT

You sold access to a network. Value came from who else was already there, and it grew as the network grew.

Connect & scale

ERA THREE

THE AGENTIC ECONOMY

You deploy workers that think and act. Value comes from what your system does on its own, day and night, while you sleep.

Deploy & grow

This third era is the one being born right now. Its unit of work is the AI worker.

An AI worker is an intelligence given one job, your context, and clear limits. You tell it who you are, what you want, and what it must never do. Then it senses, decides, acts, and reports — in plain language, at any hour, for a fraction of what a person costs. One worker is useful. The shift is what happens when you have many.

The analyst

Reads markets, news, and data around the clock and reports what changed and what it means.

The writer

Turns your notes and your voice into the newsletter, the lesson, the answer — drafted for you to approve.

The concierge

Answers questions in plain language, day and night, so no one waits and nothing is missed.

The guard

Watches a system without blinking, testing its own walls and raising a hand the moment something is wrong.

The scribe

Files every decision and lesson into one memory, so the system never forgets what it learned.

Here is the move most people miss. A pile of workers is not a company. What turns many workers into something that lives is how you arrange them — each one an organ, placed where it belongs, serving one function, feeding the others. Deployed through a body, workers stop being tools you operate and become a system that works on its own.

That is what this class teaches you to grow. Not a bot. A body.

Why this matters to you

The mission is clear. The doing is where it breaks.

Most people know what they are here to do. What stops them is not the vision. It is that one person cannot hold all the work a real mission asks for. A body is how you carry it.

The wall

Doing it all, alone

You are the analyst, the builder, the writer, the support desk, and the guard — all at once. The work never sleeps, but you must. What you know lives in your head, so when you rest, everything stops. You react after the fact, because no one person can watch everything. And every new tool is one more login to manage.

The body

Carried by many hands

A body gives you organs that each take one job and never tire. They work while you sleep. Their memory outlives any single day, so nothing walks out the door. Their senses watch what you cannot, and warn you first. One system replaces the tangle of tools. And a conscience is built in, so you keep control and your values stay in the design.

The mission does not get smaller. You get larger. That is the whole idea.

The path

What you walk away with

This is not a lecture you watch. It is a build you do. By the end you will have grown a working organ of your own — and you will understand the way of building that grows the rest.

The leverage of a team

The output of a desk of specialists — without a payroll, and without waiting.

Your time back

The repetition moves to the organs. You move up to judgment — the part only you can do.

A system that compounds

Every organ you add makes the next one faster to grow. The tenth is easier than the first.

Ownership, not dependence

You are not renting someone else's bot. You are growing something that is yours, on ground you control.

Here is the path, top to bottom.

First, why a body beats a bot — the nine organs every living system needs. Then the method: the two keys that separate people who command AI from people who grow it. Then the workshop, where you build one real organ with your own hands, step by step. And finally the mirror, where you see the same body already running, at full scale, inside XLNC — because everything taught here is something we do for our members every day.

Start where every body starts: with why it must be a body at all.

Fundamentals

Why a body

A machine does tasks. A body keeps you alive. When you build with AI one prompt at a time, you get tasks. When you build organs that sense, act, remember, defend, and repair, you get something that works while you sleep.

An illustration of a human body with the skeleton visible inside a soft blue outline, marked with nine glowing organ points.

An illustration. Tap an organ to read it.

The heart

The human at the center. Everything else exists to serve it.

Without a defined center, a system optimizes for nothing.

Replaces: mission statements nobody reads.

The heart

The human at the center. Everything else exists to serve it.

Without a defined center, a system optimizes for nothing.

Replaces: mission statements nobody reads.

The senses

Analysts that read markets, news, and data around the clock.

A blind project reacts after the fact; a seeing one moves first.

Replaces: the research you never have time to do.

The hands

The engines that act: trading, publishing, deploying.

Insight without action is a diary.

Replaces: the repetitive execution work of a whole desk.

The immune system

A full security team: watching, penetration-testing its own walls, never standing down.

Everything valuable is tested daily by people you will never see.

Replaces: hoping nothing happens.

The memory

A scribe that files every decision, lesson, and mistake into one ledger.

A system that cannot forget does not repeat its losses.

Replaces: the knowledge that walks out the door when a person leaves.

The healer

Self-healing: systems that notice their own breakage and repair it.

Uptime you do not have to buy with night shifts.

Replaces: the 3am phone call.

The mouth

One voice on many surfaces: digests, answers, teaching.

A body that cannot speak cannot serve.

Replaces: the newsletter you keep meaning to write.

The conscience

Governance: what AI may do alone, what it must propose, what it never touches.

Autonomy is only safe inside a gate.

Replaces: blind trust in automation.

The spirit

Harmony designed in: people, nature, spirit — measured, not asserted.

A body that takes more than it returns dies.

Replaces: values as decoration.

The tools

The tools, plainly

The thinking room

Claude Cowork

This is where you never write code. You give Claude your world: your files, your goals, your rules. You think together. Everything downstream is only as good as what happens here.

The building hands

Claude Code

This is where the build happens. It writes the files, tests them, and deploys them. It is brilliant and it is literal: it builds exactly what it is told. Which is why the thinking room comes first.

And Claude is not the only mind. Different models have different strengths and different prices. A fast cheap model can watch a price feed all day; the strongest mind should make the judgment calls. Masters do not use one model for everything — they route the right mind to the right task. You will play with this below.

Claude, Claude Cowork, and Claude Code are products of Anthropic. This page stands on Cloudflare Pages. Independent tools, respectfully used; no endorsement implied.

The method

Sim's two keys

Key one

Context before command.

Never open with "build me X." First give the intelligence everything: who you are, what already exists, what you value, what done looks like. Ten minutes of context saves ten hours of wrong building.

Key two

Ask it how it would ask itself.

Once it holds your world, ask it to write the instructions it would want to receive. Then hand those instructions to a fresh session of the builder. Ideation and execution are two sittings, two minds. The brief is the bridge.

Try it. Pick a project. Add the five kinds of context, one at a time, and watch a one-line ask become a brief worth building from.

What most people type

What the master hands over

Brief quality0/5

This brief was written by the intelligence itself. Your job was the context.

What most people type

Build me a market dashboard.

I write a small market letter and I am not a programmer, so everything must be explained in plain language.

I already track twelve assets in a spreadsheet, and my readers already visit my website.

My rules: never invent a number, show missing data as missing, and nothing goes public without my approval.

Done looks like one page I open each morning: prices, the day's change, and two plain sentences on what moved.

Before you build, write the brief you would want to receive for this, and ask me what is still unclear.

What the master hands over

Brief quality5/5

Who this is for

Owner: a non-technical writer publishing for everyday readers. Every label and note on screen in plain language. No jargon, no unexplained terms.

What already exists

Reuse the existing twelve-asset list exactly as it stands. Do not add tickers the owner did not ask for. The page must fit the existing website.

The rules

Missing data renders as "no data", never as a guess. Nothing publishes without explicit approval. No numbers without a named source.

What done looks like

One morning page: prices, daily change, two plain sentences on what moved. Loads fast on a phone. The owner can update the asset list without help.

How to proceed

Confirm understanding before building. List open questions first. Build the smallest version that satisfies done, then verify it honestly.

This brief was written by the intelligence itself. Your job was the context.

The operating system

Your operating system

The constitution

A CLAUDE.md every session reads first — your rules, standing. Written once, loaded always, so you never re-explain what you value.

The ledger

Decisions filed as they happen. Why something was built, what was tried, what failed. The reasoning survives even when the chat does not.

The vault

Memory that outlives every session. Lessons, preferences, and hard-won context, carried into every future conversation.

The skills

Recipes that make the tenth build faster than the first. A good way of doing a thing, written down once, reused forever.

Governance

GREENActs alone — reversible
AMBERProposes — you approve
REDNever without you

Verification

Never trust the first output. Test it, attack it, make it show its sources. Trust is earned per build, not assumed.

Honest-empty

A number you do not have is shown empty, never invented. An honest gap beats a confident guess, every time.

This is the difference between using AI and having an operating system. The OS is what makes every session smarter than the last.

The pipeline

From idea to organ

01

IDEA

Name the organ and why it deserves to exist.

You

02

CONTEXT

Pour your world into the thinking room.

Cowork

03

SELF-BRIEF

Ask it to write the instructions it would want to receive.

Cowork

04

BUILD

Hand the brief to the builder. Approve the plan, not just the result.

Claude Code

05

VERIFY

Test it, feed it nothing, attack it.

You

06

DEPLOY

Put it on free ground with a live URL.

Claude Code

07

REMEMBER

File the build log in your ledger.

Cowork

08

GOVERN

Set what it may do alone, propose, or never touch.

You

This is the map. Now we walk it for real.

The workshop

Build one organ, end to end

Fundamentals done. Now we build — together, step by step. You are going to grow your first organ: a market analyst. The same organ, generalized, that writes what this community reads every day. Every step below has a block you can copy. Do this once and you will never see software the same way.

1

Open the thinking room.

Open Claude (Cowork mode). Do not ask for anything yet. Paste the Context Brief below, filled in with your own answers. You are introducing yourself, not ordering.

K1 — Context Brief template
CONTEXT BRIEF

WHO I AM
I am [name]. I am [what you do]. I am not a programmer. Explain everything
to me in plain language and never assume I know technical terms.

WHAT I AM BUILDING TOWARD
[Two or three sentences on the bigger goal, not the first task.]

WHAT ALREADY EXISTS
[List anything real: a website, a spreadsheet, an audience, a routine you
do by hand today. If nothing exists yet, say so honestly.]

MY VALUES AND HARD RULES
- Never invent a number. If data is missing, show it as missing.
- Never touch or move money.
- Nothing irreversible without asking me first.
- [Add your own.]

WHAT DONE LOOKS LIKE
[One paragraph. What would make you say "this works" one week from now?]

WHAT YOU SHOULD NEVER DO
[Anything off-limits: topics, actions, tones.]

Do not build anything yet. First, confirm what you understood, and tell me
what is unclear.
2

Let it ask you.

Now send this single line and answer everything it asks. The questions it asks are the gaps in your context.

K2 — The interview line
Before we design anything: ask me every question you need answered to
understand my world fully. Ask them one at a time.
3

Ask it how it would ask itself.

This is the move that changes everything. Send this, then read the brief it writes. Correct anything wrong — this is the moment you steer.

K3 — The ask-itself prompt
You now hold my full context. Write the complete build brief you would want
to receive to build this perfectly. Include: your assumptions, the exact
structure of what will be built, the steps in order, what to verify at the
end, and the questions to ask me before starting. Write it as instructions
to a fresh instance of yourself that has none of this context. Do not start
building. The brief is the deliverable.
4

Hand the brief to the builder.

Make a new empty folder. Put one file in it, CLAUDE.md, with the constitution below. Open Claude Code in that folder and paste the brief from step 3. Ask it to show you its plan before it builds. Approve the plan, not just the result.

K4 — CLAUDE.md constitution skeleton
# CLAUDE.md - my constitution

I am not a programmer. Explain every change in plain language.

## Inviolable rules
- Never invent data. Missing means empty, and it says so.
- Test everything before telling me it works.
- Nothing irreversible without asking me first.
- Keep it simple: one file over three, boring over clever.

## Governance
- GREEN (do alone): reversible edits, tests, previews.
- AMBER (propose first): new dependencies, deletions, anything public.
- RED (never without me): money, credentials, other people's data.

## This project
[One paragraph: what this project is, pasted from your build brief.]
5

Verify like an owner.

Never trust the first output. Run the five checks below. The last one matters most.

K5 — Verification checklist
1. Does it run at all? Ask for exact steps to see it working.
2. Feed it nothing. With no data, does it say "no data" - or invent?
3. Feed it something wrong. Does it fail loudly or lie quietly?
4. Ask: "Show me exactly where each number on screen comes from."
5. Ask: "Attack your own work. List the three weakest points and fix them."
6

Deploy on free ground.

Ask Claude Code: "Prepare this to deploy on Cloudflare Pages and give me plain-language steps." Cloudflare's free tier is where this very page stands. Drag, drop, live URL. Your organ now works while you sleep.

7

File the memory.

Before you close the session, send this. The output is the first entry in your own ledger. Your body has one organ — and a memory.

K7 — The memory entry
Write a short build log of this session: what we decided and why, what we
learned, what surprised us, and the single next step. Format it as a dated
note I can keep in a folder called LEDGER. Be honest about what is unfinished.

One organ this week. Another next week. That is how a body is grown. At XLNC, dozens of organs now do the work of departments — not to remove the humans, but to move them up to judgment while the organs carry the repetition. And harmony is designed in from the start, because a body that takes more than it returns dies.

Right mind, right task

The model router

Pick a task. Then pick a mind for it. The router tells you what your choice costs and what it buys.

1 · The task

2 · The mind

Choose a task and a mind above. The verdict appears here.

TaskFast & cheapBalancedStrongest mind
Watch a price feed Right mind, right task. Cost 1 · Quality 3 It works, but you are paying for thinking a watcher never uses. Cost 2 · Quality 3 A genius watching a ticker. Same result, triple the price. Cost 3 · Quality 3
Summarize a call Fast misses the nuance of a call: names, promises, tone. Cost 1 · Quality 1 Right mind, right task. Cost 2 · Quality 3 An excellent summary, but balanced would have done it for less. Cost 3 · Quality 3
Draft a page A page that reads like it was written in a hurry, because it was. Cost 1 · Quality 1 Right mind, right task. Cost 2 · Quality 3 A beautiful draft. Save the strongest mind for when the stakes rise. Cost 3 · Quality 3
Audit the security A cheap audit is the most expensive mistake in this game. Cost 1 · Quality 1 It will catch the obvious. Security is not about the obvious. Cost 2 · Quality 2 Right mind, right task. Cost 3 · Quality 3
Make the judgment call The fast mind answers confidently. Confidence is not judgment. Cost 1 · Quality 1 Close calls need the deepest thinking you can buy. Cost 2 · Quality 2 Right mind, right task. Cost 3 · Quality 3

The expensive mind is not for everything. It is for the moments that matter.

Build your own body

Your first three organs

Pick the life you actually live. The figure lights the first three organs to grow, in order, each with the first prompt to send in the thinking room.

Trader

  1. The senses. Interview me about the markets I watch and how I make decisions, then design a market analyst that reads those markets around the clock and reports in plain language.
  2. The memory. Now build the scribe. Every call the analyst makes, with its reasoning and its outcome, gets filed into one dated ledger I can read.
  3. The conscience. Now write the gate. What this system may do alone, what it must propose to me first, and what it may never touch. Money is always mine to move.

Creator

  1. The mouth. Interview me about my voice, my readers, and what I believe, then design a drafter that assembles my notes into issues I approve before anything sends.
  2. The memory. Now the archive. Every issue, every idea, every reader reply that taught us something, filed so the next issue starts smarter.
  3. The senses. Now the reader. A watcher that follows the topics I write about and brings me the five things worth my attention each morning.

Farm

  1. The senses. Interview me about my land, my crops, and my seasons, then design a watcher that reads weather and soil data and flags what needs my eyes.
  2. The healer. Now self-repair. When a sensor feed goes quiet or a schedule fails, the system notices, tells me in plain language, and holds the line until I look.
  3. The memory. Now the farm ledger. Every season's decisions, outcomes, and surprises filed, so each season starts smarter than the last.

Agency

  1. The hands. Interview me about the repetitive work my clients pay for, then design an engine that drafts those deliverables for my review, in my house style.
  2. The memory. Now the firm memory. Every client's preferences, every project lesson, filed so knowledge never walks out the door with a person.
  3. The mouth. Now the client voice. Every project reports itself to the client in plain language before they ever have to ask.

Do not build the whole body. Build one organ. The body follows.

The blueprint

Design the entity the body serves

This class grows the body. The Exponential Organization 3.0 framework — from OpenExO and Salim Ismail's Exponential Organizations work — is a blueprint for what that body should serve: an entity built for the future, not the past. Old organizations were built linear, owned, and slow. Future-first entities are exponential, leveraged, and AI-native.

OpenExO · a third-party resource

The ExO 3.0 Claude Skill turns that blueprint from static knowledge into a live companion you can think with — the same move this whole class is built on. It is an AI companion for exploring, understanding, and applying ExO 3.0 in real time, built around the Intelligence Stack, DRIVE, SHAPE, and the REWRITE playbook, and connected to OpenExO's frameworks: the Massive Transformative Purpose (MTP) and the ExO attributes, SCALE and IDEAS.

It is not an XLNC product, and we say so plainly. It is an external tool we consider a powerful complement: grow your organs here, then design the future-first entity they run inside.

Intelligence Stack DRIVE SHAPE REWRITE playbook

Linear against exponential

Linear: adds Exponential: compounds Time

Both lines start in the same place. The gap at the end is the argument: an organization designed to compound will pass one designed to add — and the ExO 3.0 blueprint is a method for designing the compounding kind.

Grow the organs here. Design the future-first entity they serve there.

The mirror

Running for you

Everything this class taught, XLNC already runs — at full scale, for its members. Read the body one last time. This time, it is yours.

The same human body illustration, with every organ point lit.

The heart at the center is you. The other organs are already at work around it.

The senses

You learnedAnalysts that read markets, news, and data around the clock.
XLNC runsMarket analysts reading price, flows, and news around the clock.
For youThe daily digest you read; context feeding the engines while you sleep.

The hands

You learnedThe engines that act: trading, publishing, deploying.
XLNC runsThe value engines: the catch strategy that deploys into panic, the exit algorithm that leaves near tops.
For youYour capital worked without emotion, paid only on your new highs.

The immune system

You learnedA full security team: watching, penetration-testing its own walls, never standing down.
XLNC runsA full security team, penetration-tested, never standing down.
For youYour money protected the way it is protected here.

The memory

You learnedA scribe that files every decision, lesson, and mistake into one ledger.
XLNC runsOne shared memory across every build and every market lesson.
For youA firm that cannot repeat its losses and cannot forget what it knows.

The healer

You learnedSelf-healing: systems that notice their own breakage and repair it.
XLNC runsSelf-healing surfaces that notice and repair their own breakage.
For youUptime without a night shift of salaries you would be paying for.

The mouth

You learnedOne voice on many surfaces: digests, answers, teaching.
XLNC runsThe Academy, the concierge, the digests.
For youYou do not just hold; you understand what you hold, and why.

The conscience

You learnedGovernance: what AI may do alone, what it must propose, what it never touches.
XLNC runsGovernance and non-custodial architecture: your funds in your own exchange account, behind your own keys.
For youNo one at XLNC can touch your money. Not once, not ever, not by design.

The spirit

You learnedHarmony designed in: people, nature, spirit — measured, not asserted.
XLNC runsValue circulating outward: farmer-owned infrastructure, stable ground, missions that ask nothing back.
For youYour returns feed something that returns more than it takes.

This is why the terms are what they are. No management fee. No subscription. Twenty percent of new all-time highs only — because organs do not draw salaries, and the savings live in your terms. Everything you have used this month was grown exactly the way you just learned.

Inside XLNC

The organs, at work right now

The mirror showed you the body in principle. Here is the same body in practice — the actual functions running inside XLNC, what they do, and how often. Not a promise of what could be. A description of what is.

Watching the markets

Price, flows, liquidations, and sentiment read around the clock across every market that matters. What changed and why is distilled into the read you get — so a move is understood before it is felt.

Runs: continuously

Watching the accounts

Every account and every wall is watched for anything out of pattern, without pause. The aim is not to react to trouble. It is to see it forming and close the door first.

Runs: continuously

The security team

An in-house team whose only job is to attack our own walls, find the weak point before anyone else can, and harden it. How they do it stays unpublished on purpose — a wall you can read is a wall someone can climb.

Runs: on a standing schedule

Member support

A guide that answers members in plain language, at any hour, in the register of this house — patient, clear, never rushed. No question goes cold because it is late or because it is small.

Runs: day and night

Making the teaching

The lessons, digests, and explainers you read are drafted continuously, then shaped and approved by human hands before they ever reach you. Volume a newsroom could not carry, held to a standard a newsroom would recognise.

Runs: every day

Research & synthesis

The long reading no person has time for — filings, data, history — gathered and reduced to the few things that actually change a decision.

Runs: on demand, and ahead of it

Keeping itself alive

The systems watch themselves. When a surface breaks or a feed goes quiet, it is noticed and repaired — without a night shift of people paid to wait for it.

Runs: continuously

The gate

Every worker acts inside a boundary: what it may do alone, what it must bring to a human first, and what it may never touch. Your money sits on the far side of the last line, where nothing automated can reach it.

Runs: on every action

None of these draw a salary. None of them sleep. Together they do the work of departments — and they are a large part of why the terms can be what they are.

This is the body you just learned to grow, grown to full size and pointed at one thing: serving the people inside it.

The raise

The threshold

A body like this is grown organ by organ, by hands the community funds. The raise is how the next organs — and the body's new home — get built.

The door is open. This is not a plea. The move is happening. The question is only who is inside when it does.

Back the raise with any amount from $1,000 and receive twice that amount back, deducted from your future performance fees, until it is used. No expiry. No cap.

Not doubled money. Returned belief. This body gives back more than it is given, because that is what it is.

$10,000You back
$20,000Back to you · 2×

Returned as credit against your future performance fees, until it is used. No expiry. No cap.

This unlocks Sovereign Circle

Active

3.33 Founder

From $1,000

  • The 2× fee credit. No expiry, no cap.
  • Founding Member badge and your name on the Founders' wall.
  • A guaranteed seat on the boat at the year-end Excellency gathering in Bali.
Active

Sovereign Circle

From $10,000

  • Everything above, plus premium tax-efficient structuring of your XLNC relationship from day one.
  • VIP seating at XLNC events.
  • Priority, pre-launch access to ecosystem projects as they open.
Active

The Lineage

From $25,000

  • Everything above, plus an invitation to the Bali food forest.
  • Direct access to Sim. A complimentary CryptoWealthBali consultation.
  • A place held early inside something built to outlast all of us.

And beneath every tier, the true return, the one that cannot be itemised: you are helping build the home that will serve people who need this kind of help down the road, and helping this body grow.

More detail (optional)

For family offices and institutions: a private conversation is the right door. Write to [email protected] and it will be opened.

A commitment is an expression of intent our team confirms with you personally. Nothing on this page is tax, legal, or investment advice, and no financial return is guaranteed.

One class. One organ. One body.

People, nature, spirit. The circle over the line.

The map is here. The territory is yours.