The Phoros Pilots Handbook

Welcome

Welcome aboard

You’re holding this booklet because you were chosen.

Out of a school full of sharp, capable people, you are one of the Phoros Pilots, a small team trusted to do real professional engineering work for real companies, over one intense and unforgettable summer. Not pretend work. Not a classroom exercise with a made-up brief. Real clients, real software, real responsibility.

If that sounds like a lot for someone still in school, good. That feeling is the whole point. We picked you because we believe something most people don’t: that a smart, curious, hard-working young person, given the right tools and real coaching, can do work the world calls “professional” without first spending years earning the title.

This handbook is your map. Read it before orientation and come back to it when you’re unsure. By the end of it you’ll understand what you’ve joined, what you’ll be working with, what we expect of you, and why this summer matters far beyond the program dates.

Welcome aboard, Pilot.
Let’s fly.

Part 1

Why you’re here

The mission

Jamaica, and the wider Caribbean, has a quiet problem: we grow some of the brightest young minds in the world, and then we lose too many of them. They leave for opportunities elsewhere, because the opportunities to do serious, world-class technical work here have been scarce. It’s called brain drain, and it costs the region its own best people.

This program is a small, sharp bet against that. The bet is this: if the tools are good enough, the experience gap disappears. A motivated student in Kingston, with the right software harness and daily coaching, can deliver work that previously required a trained professional in a foreign tech hub. If that’s true, and over the summer we intend to prove it is, then world-class technical opportunity can exist right here, and our best people have a reason to build their futures at home.

You are not just an intern this summer.
You are the evidence.

The thesis: you don’t need experience, you need judgment

Here’s the idea at the heart of everything you’ll do.

Most of what makes professional engineering “professional” (the quality, the discipline, the not-breaking-things, the polish) is supplied by the Phoros harness, the software system you’ll operate. What the harness cannot supply, and what you bring, is judgment: knowing what’s worth doing, what “good” looks like, when something’s off, how to talk to a real human about their real problem.

You already have that judgment. Most working adults would envy your raw ability. What you’ve lacked is a way to apply it to real work without years of training first. The harness is that way.

So this summer is a trade: the harness brings the craft, and you bring the judgment, the curiosity, and the care. Together that equals professional output. That’s the thesis. You’re going to prove it.

Part 2

What the program is

Orientation is Friday, July 3, from 10:00am to 2:00pm. The program runs full-time, 9 to 5, Monday to Friday, from Monday, July 6 through Friday, August 28, based here at Campion. Real work starts in week one, ramping as you find your feet (give yourself about two weeks to feel fluent, almost everyone does).

Your work is organised into three spaces, each with a different purpose. Think of them as three different “hats” you’ll wear.

1.The team space: where the cohort works as one company

All the Pilots belong to one shared organisation, coordinated like a real company. Every day has a plan; every day you report what you did. There’s a coordinator (more on that in Part 3) that keeps everyone pointed in the same direction and gives the founder a single place to see “where is everyone.” This is where you experience what it’s like to be part of a well-run team.

2.Your work group: real clients, real platform

You’ll be paired into a small work group with one or more cohort partners. Your group gets two real mandates:

• A real client deliverable. An actual Phoros customer with an actual need: a dashboard, a digitised process, a tool they’ll genuinely use. You’ll work to advance it, and customer results can start appearing in your very first week.
• A piece of the platform to mature. A part of the Phoros software itself (for example, point-of-sale, billing, or inventory) that you’ll help improve. Your fresh eyes are an asset here: the things that confuse you are often the things that need fixing.

The pairing is deliberate: when you’re waiting on one piece of work, you hop to the other. You’re never idle; you’re always engaged across a wide surface.

3.Your personal project: the thing you keep

Each Pilot builds something of their own. Your choice: maybe the grown-up version of a school project, an idea you’ve always wanted to build, something you’re proud to show. It’s fun, it’s personal, and crucially: it’s yours to keep and keep building after the summer ends. It’s also the purest measure of how far one motivated person plus this harness can go over the summer. Make it something you’d be proud to put your name on.

Part 3

What you’re actually working with

This is the part that should make you sit up. You are not “using AI” the way you might use a chatbot for homework. You are going to operate a professional software-engineering harness, the same system Phoros uses to build and run real products for real businesses. Here’s what that means.

You’re the director, not the camera operator

Think of a film director. They don’t personally operate the camera, build the set, or act out every scene. But nothing good happens without their vision, their taste, and their judgment about what’s working and what isn’t.

That’s you. The harness, and the AI agents within it, are your crew. You bring the intent and the standard; they bring the execution. Your job is to know what “good” looks like, to steer, to catch what’s off, and to decide what matters. That’s a real skill, and you’ll get better at it fast.

You’ll lead teams of AI agents

Here’s something most people your age (most people any age) never get to do: you’ll lead teams. Specifically, you’ll direct small teams of AI agents (the system calls them families) to carry out work. You give a family a goal and a quality bar; it does the heavy engineering lifting; you review, correct, and steer. You might be directing three to five of these families at once. You are, in a real sense, a manager and a director from day one.

A coordinator that keeps the whole thing humming

Above the families sits a Chief of Staff, a coordinating agent that sets the daily plan, gathers everyone’s reports, and keeps the cohort aligned. You’ll talk to it the way you’d talk to a really organised team lead: it knows what you’re working on, what’s due, and what everyone else is up to (without mixing up your business with anyone else’s). It’s how a small team stays coordinated without anyone drowning in messages.

The harness has guardrails, so you can be bold

Phoros is built using something called Structural Software Engineering (SSE). You don’t need to master it to start, but here’s the part that matters to you:

• The platform is built like LEGO, out of small, well-made pieces that each do exactly one thing, snap together cleanly, and are checked automatically. Good structure isn’t decoration; it’s what makes the whole thing trustworthy.
• There are guardrails everywhere. Risky actions are designed to become visible, slow, and reviewable before real damage is done.
• Everything leaves a trace. Every action is recorded. That’s not surveillance. It’s a safety net. It means your work is visible, reviewable, and recoverable when something needs to be corrected.

Read that again, because it’s liberating: the guardrails mean you’re free to be ambitious. They do not replace judgment, but they let you reach without being reckless.

Your inexperience is a feature, not a bug

Here’s the most surprising thing of all.

When you ask a “naïve” question, or get stuck where an expert would’ve stepped around the problem, or struggle to phrase a request, that friction is gold to us. Because for every confused student, there are future customers who may be just as confused. The places where the system trips you up are exactly the places it needs to get better for everyone. So when you struggle and tell us about it, you’re not failing, you’re helping make the product better. Your work this summer gives us the clearest possible view of where Phoros is easy to use, where it is confusing, and where it needs to improve. You’ll be its first pilots, in every sense.

So never hide your confusion. Surface it. It’s one of the most valuable things you bring.

Part 4

The daily rhythm

A Pilot’s day has a natural rhythm. Once you find it, the days fly.

The cadence

The core loop of the work looks like this:

1. Write a clear instruction for what you want done.
2. Wait while the harness works (this is normal, and useful).
3. Read what came back, carefully.
4. Test it: does it actually do the thing? Does it meet the standard?
5. Refine and repeat.

A day in the life (roughly)

The exact shape of the day will settle in your first week or two. Expect some days of pairing, some days of heads-down building, regular check-ins, and moments where the whole cohort talks through a hard problem together.

Part 5

What we expect of you

We hold a high standard, not to be harsh, but because we believe you can meet it, and because real clients are depending on the work. Here’s what “a great Pilot” looks like.

The standard

Professional-grade, every time. The work you ship should be something a real business would be glad to receive. The harness helps you hit that bar, but you own the bar. “It mostly works” isn’t the standard. “I’d be proud to show this to the customer” is.

The values we hire and coach for

• Diligence over raw talent. We did not pick the flashiest. We picked the people who show up, push through, and care. Keep being that person.
• Curiosity. Ask why. Poke at things. When you hit a roadblock, explore the area around it. That’s where the learning is.
• Ownership. Treat your work as yours. Don’t wait to be rescued; try, and when you’re genuinely stuck, ask clearly.
• Honesty. Never claim work you didn’t do, or say “done” when it isn’t. We build on trust. One honest “I’m stuck” is worth a hundred hollow “all good”s.
• Respect. For your mentors, your cohort, the Campion staff hosting us, and above all the customers whose trust you’re handling.

How to communicate

• Surface problems early. A problem named at 10 a.m. is easy; the same problem hidden until 4 p.m. is a fire. Tell someone the moment you’re blocked.
• Ask good questions. “It doesn’t work” is hard to help with. “I expected X, I did Y, I got Z” is easy. Show your thinking.
• Report clearly. At the end of each day, a clear note of what you did, what’s done, and what’s stuck. This is how the team stays coordinated, and it’s a professional habit that will serve you for life.
• Default to over-communicating. When unsure whether to mention something, mention it.

Professionalism

Show up on time. Be present on normal program days. Communicate clearly. Be someone your cohort can rely on. These small disciplines are most of what “professional” actually means.

Part 6 · The one that matters most

The one rule that matters most

So:

• Keep everything confidential. What you see inside the work stays inside the work, not on social media, not with friends or family, not with other students. During the program and after it.
• Only use the approved tools. Customer data goes only into the Phoros platform and the AI tools we give you, never into outside chatbots, websites, or personal AI tools. This one is absolute.
• When in doubt, ask first. If you’re unsure whether something is allowed, the answer is: ask a mentor before you do it, not after.
• Speak up immediately if you lose a device, share something by accident, or notice anything that looks like a security problem. Mistakes handled early are fine. Mistakes hidden are not.

You and your parent or guardian will review program documents covering confidentiality and acceptable use. They are not a formality. They are the foundation that lets us trust you with real work. Honour them, and you’ll have earned something rare: a track record of handling real responsibility well.

Part 7

The practical things

Your first two weeks: settling in (probation)

The first two weeks are a settling-in period, for you and for us. It’s normal to feel like you’re drinking from a firehose; almost everyone reaches fluency by the end of week two. We’re not judging you on raw skill or prior experience (you weren’t expected to have any). We’re looking for engagement, attitude, reliability, and willingness to learn. Show up, lean in, ask questions. That’s all “passing” means.

Your stipend

You’ll receive a stipend of JMD 180,000 across the program, paid in fortnightly amounts. It’s there to support you through the summer: transportation, meals, the incidentals of showing up every day. Your contract and a simple payment schedule lay out exactly when each amount arrives, so you’ll never have to wonder.

Your gear and your kit

You’ll be set up with what you need to do the work. (Program merchandise, your Phoros Pilots kit, is part of joining the crew; details to come.)

How you’ll be evaluated

This isn’t a program of tests and grades. You’ll be measured the way professionals are, on what you ship and how you grow:

• Real output: the client work you help deliver and the platform improvements you make.
• Your growth curve: how far you travel from week one to the final week: your speed, your independence, the complexity you can handle. This curve is the thing we care about most. We expect you to start slow and accelerate.
• Your personal project: from rough idea in week one to a real, shipped build by the final week, a portfolio piece that’s entirely yours.
• How you work: reliability, honesty, curiosity, ownership, and how you treat the people around you.

The goal is not to catch you out. It’s to watch you become someone who can do this, and to be able to point at the evidence and say, look what a Pilot did this summer.

Code of conduct (the short version)

Be honest. Be respectful. Protect customer trust. Show up and be reliable. Follow the guardrails and the agreements you’ve signed. Don’t misuse systems or data. Treat this like the real opportunity it is, because it is one.

A closing word

A closing word

Most people spend years waiting for someone to hand them real responsibility. You’re getting it now, this summer, while you’re still in school, because we believe you’re ready, and because the work genuinely needs you.

It will be hard sometimes. You’ll hit walls. You’ll write an instruction five times before it lands. You’ll see real customer feedback on something you built. You’ll surprise yourself.

That’s the whole experience. Lean into all of it. Ask for help early and often. Take care of your cohort. Be proud of your personal project. And remember, on the hard days, what you’re actually part of: a small, serious attempt to prove that the brightest young people in this region don’t have to leave it to do extraordinary work.

You don’t need years of experience. You need judgment, curiosity, and the willingness to show up and care.

You already have all three.
Now let’s prove it.

Welcome to the Phoros Pilots.