One API key. The whole family stack around it.
CTHJULE is the family's api-centric standalone shell: built around exactly one API key — Jules — serving one API use, and wrapped in the full Everplay-Tech stack: HELM MCP control, IHP at-rest security, iOS security, and Apple mesh/cloud connectivity. It is in development and not for sale; this manual tracks what the family standard pins down today, and nothing more.
CTHJULE is not for sale yet, but the family rules are not optional and not per-app. They hold for CTHJULE exactly as they hold for the rest of the catalog.
- No phone-homeNo Everplay-Tech analytics, telemetry, or account server — in CTHJULE exactly as in every family member.
- One-time purchaseNever a subscription. Sibling pricing is $1; AiMANAC, the flagship, is $9.99. CTHJULE's planned price is the $1 sibling tier.
- Customer owns their dataYour key and your data are yours. The Apple sale is the trust floor; sync, where it exists in the family, is iCloud-only.
- Full HELM controlEvery family member has full HELM-MCP control; the AiMANAC sale unlocks orchestration — wielding the HELM surfaces across the fleet.
- A Rust half for sensitive logicThe planned cthjule-rs UniFFI xcframework IHP-V2-seals the Jules key at rest and signs claims; Swift stays presentation, transport, and Keychain custody.
Everything below comes from the family standard — the same source as the machine manual. Anything you do not see here is not published yet.
- One key, one jobA single Jules API key serving one API use. The point of the app is what gets wrapped around that key.
- The full stackHELM MCP control, IHP at-rest security, iOS security, Apple mesh/cloud connectivity — even a single-API app gets the full family stack.
- HELM surfacehelm_jules_* (6 tools) in the family HELM registry today; a first-class helm_cthjule_* surface (helm-core-cthjule) is planned, with an iOS IHP-WS relay and a biometric ControlDeck.
- The orchestration unlockDispatch Jules via HELM MCP — 300 tasks a day — for incremental background builds. CTHJULE is the dedicated shell for that lane.
- Tester #1First in the family build queue; with DUD3P0 (tester #2) it proves both paths: standalone on-device use and HELM orchestration.
- CHAT_FX glassThe family design language is glass; CTHJULE's skin is CHAT_FX, shared with HELMPC.
There is nothing to install today. The steps below mark the honest line between now and planned.
- Today: nothing to set up. CTHJULE is in development. No App Store listing, no TestFlight invite, no download to point at.
- Planned: buy once. When it releases, CTHJULE is planned at $1 one-time — never a subscription. Apple handles the transaction.
- Planned: bring your Jules API key. The app's one key; the planned Rust half (cthjule-rs) seals it at rest with an IHP-V2 capsule and signs claims.
- Planned: unlock orchestration with AiMANAC. CTHJULE runs alone, but its purpose needs AiMANAC — the key that unlocks the HELM surfaces across the fleet.
This page is the human face. The same content is published as canonical JSON — the machine face. Hand the URL to your own LLM or MCP client and it can explain CTHJULE, with nothing phoning home.
CTHJULE is not for sale yet, so today Discord is where you ask what it is, where it sits in the family, and when that changes. The manual bot answers from this same JSON manual.
Support
Questions about the Jules key model, the HELM surface, or the family stack around one key? Ask in Discord.
Invite link pendingFeedback
Whether the one-key shell pattern fits your use — feedback goes through Discord, openly.
Invite link pendingDirect contact until the invite link lands:
info@llmtech.net.