FrankX Foundry
We install operating systems into businesses we believe in.
A website, an AI-agent harness, pre-publish quality gates, and a business memory that compounds — derived from the architecture used to run frankx.ai, adapted for your brand, and owned by you. Installed through a bounded build and designed for a maintainable weekly operating rhythm.
Applications reviewed for fit · priority: sustainable, healthcare, and meaningful work
The Architecture
Three layers. Every one of them public.
The claim is substance, not marketing: the substrate, the operating systems, and the reference implementation and operating contracts are open repositories. Verify rather than trust.
LAYER 0 — SUBSTRATE
Starlight Intelligence System
The protocol layer: memory architecture, decision records, the operating-skill pattern. Open source at frankxai/Starlight-Intelligence-System.
LAYER 1 — THE AGENTIC OS FAMILY
One architecture, specialized per domain
agentic-creator-os
For creators
live
The original — content engine, music, publishing pipelines.
View repo →agentic-business-os
For businesses
live
Site + harness + claims gate + business memory. What the Foundry installs.
View repo →agentic-family-os
For families
in development
Heritage, memory, and family knowledge systems.
agentic-health-os
For health
in development
Training, nutrition, and recovery operating loops.
agentic-investor-os
For wealth
in development
Portfolio intelligence and decision memory.
LAYER 2 — THE SERVICE
The Foundry — this page
The human layer: evaluate, forge, stay connected. The templates are free and MIT-licensed; the Foundry prices the install, the brand derivation, and the connected relationship.
What Gets Installed
Five contracts that teach AI your business.
Most companies use AI as a blank chatbot. An installed OS is a repository that teaches the AI who you are — so every session works like a trained team member.
CLAUDE.md
The doctrine
The company handbook, read automatically by every AI session. Identity, rules, gates. Edit it, and every future session changes behavior.
design.md + taste.md
The design contract
Every visual value the site may use, plus the judgment tokens cannot capture. Your brand stops drifting the day these exist.
@claims-guard
The gate
A zero-tolerance pre-publish audit for regulated claim language, uncited assertions, and AI-tone. A FAIL blocks publish until a human rewrites.
docs/intelligence/
The memory
Decision records, market notes, weekly reviews. Sessions check it first and update it after — week 30 is smarter than week 1.
The weekly rhythm
The operation
Monday plan, ten minutes. Friday review, fifteen. Sized for founders with day jobs; everything else is production.
GUIDE.md
The operating guide
Day-1 onboarding, the weekly rhythm, the gates — written for founders, no AI background assumed. Read it now →
Proof
The receipts, not the pitch.
OPEN TEMPLATE
Agentic Business OS
The public template exposes the site structure, agent contracts, claims gate, business memory, and operating rhythm before you apply for a guided install.
THE UPDATE CHANNEL
Sync you can read
Harness improvements arrive as pull requests with plain-language changelogs — markdown diffs readable in the GitHub UI. Nothing auto-merges. The contract is public: HARNESS.md.
THE REFERENCE
frankx.ai itself
This site uses the same contract-and-gate pattern in production, with a public agent catalog at /acos/agents, and the operating loop documented at /os.
The Process
Evaluated, not transactional.
01
Apply
Six questions. Frank reads every application personally — no form-letter pipeline.
02
Evaluate
Fit call if the application lands: the business, the stage, the regulated territory, the operating capacity. Pricing follows this conversation.
03
Forge
The install: brand derivation interview, design contract, voice file, doctrine, gates, site — build-verified and deploy-ready.
04
Stay connected
Your repo is registered downstream. Harness improvements arrive as readable pull requests. Nothing auto-merges; your brand files are never touched.
What we evaluate for
Meaningful product
Priority goes to sustainable, healthcare, and genuinely useful businesses. We install systems into things we want to exist.
A founder who will operate it
The system compounds through the weekly rhythm. If nobody runs the Friday review, the install is shelf-ware — we decline rather than ship that.
Honest category
If your market rewards overstatement, our claims gate will frustrate you. We take businesses that win by being right, not loud.
Apply
Tell us what you're building.
A short application, read personally. Pricing and scope follow the fit review.
FAQ
Straight answers.
What is the FrankX Foundry?
The Foundry installs a website, AI-agent harness, pre-publish quality gates, and business memory using the same contract-and-gate pattern applied on frankx.ai. The system is adapted to your brand in a guided derivation, and you own the resulting repository.
What exactly gets installed?
An instance of the Agentic Business OS: a Next.js site, five contract files that teach any AI agent your brand (doctrine, design tokens, taste, voice, operating skill), specialist agents including a zero-tolerance claims gate, six operating commands, and a file-based business memory. The template is open source — you can inspect every part before applying.
Why is it application-only?
Install capacity is limited to a small number per quarter, and the system only compounds for founders who actually operate it weekly. The evaluation protects both sides: we take businesses where the architecture genuinely fits, with priority for sustainable, healthcare, and meaningful products.
What does it cost?
Pricing and scope follow the fit review. The underlying template is MIT-licensed; what the Foundry prices is the guided install, brand derivation, and agreed support relationship.
What does "staying connected" mean?
Your repo can be registered as a downstream instance. When an upstream harness improvement applies, it can arrive as a pull request with a plain-language changelog. You read the diff and merge or decline; nothing auto-merges, and brand files remain under your control.
Do I need to know how to code?
No. The operating layer uses plain-language contracts that teach a coding agent the business context, boundaries, and quality checks. The operating rhythm is documented during the install and adjusted to the company rather than sold as a universal time promise.
How does this relate to Founder’s Circle?
The Foundry is implementation: one business, one operating system, installed around real work. Founder’s Circle is strategic access for consequential decisions under uncertainty. Neither requires the other.
What can I verify before applying?
The operating guide, Agentic Business OS template, harness contract, and related public repositories are linked from the page. Inspect the source, the quality gates, and the ownership model before deciding whether an application makes sense.
Not ready to apply? The template is open source — take it, it's yours. Or start with the operating guide.