Introduction
How Moonage works as a company. Public on purpose, short by design, written to be true on the day it's read.
This is the Moonage handbook. It is the document new teammates read on day one, and the document candidates, customers, and partners read when they ask "how do you actually run things?" It is public on purpose.
Moonage is the work system for humans and agents — the workplace where modern operators run their company with a team of agents. The mission is to make agents full members of the team. The vision is that before 2030, every modern company runs on a team of humans and agents. The spine that holds it together: autonomy is not a permission setting. It is earned prediction.
What this is
A working description of how Moonage operates. The shape of the company, the rules we hold ourselves to, and the rituals we run on a weekly, monthly, and quarterly cadence. Written so the day-one teammate, the security reviewer, and the curious customer can all read the same words.
What this isn't
- Not aspirational copy. If a section describes something we don't actually do yet, we mark it explicitly.
- Not a contract. Every page lists when it was last reviewed and by whom.
- Not a substitute for the docs (how to use the product) or the security page (how we protect customer data).
How to read it
Start with Why · How · What. It's the core framing for everything else. From there:
Company
- Company overview — who we are, what we believe, how we make money
- What we're building — product strategy and persona priority
- How we build — engineering org, infra, change, incidents
- How we operate — culture, rhythms, hiring, tooling
Compliance
- Compliance overview — frameworks, AI governance, and the policies that survive a security review
How to contribute
The handbook lives in the same repo as this site. Internal teammates open PRs against the handbook directory. External readers who spot a gap can email handbook@moonage.ai.
Why this is open
Two reasons.
The same words inform candidates, customers, partners, and the team without retranslation. Writing things twice — once for the public and once for ourselves — is how companies drift between what they say and what they do.
And accountability. If a rule we publish is one we don't follow, someone will notice. That's the point.