The system that makes the model keep learning
The six algorithms already run inside graph8 today. Developer-facing controls and APIs to configure or read them are Preview, not a shipped contract.
The model retrains on a release cadence. The infrastructure sharpens every hour.
Most "AI for sales" pitches hand-wave at "the model keeps learning." In reality, weights only change when a training run lands. What changes continuously is the orchestration around the model. octa is one component. octa² is the part that compounds, and it is where most of the day-to-day improvement actually comes from.
Weekly to monthly
octa weights change only when a training run lands.
Every hour
Which variant ships, which signal ranks, which contact routes.
octa retrains on a release cadence: continued pre-training plus long-horizon RL on the corpus. The weights change weekly to monthly, never per campaign.
Each one runs its own loop at its own cadence around the model. The model is a tool the loops call; the loops are what compound.
Which variant ships, which signal ranks, which contact gets routed, which exemplar gets retrieved. That orchestration re-tunes every hour, between model releases.
Validated learnings flow back into the next octa training pass. The process feeds the model, the model feeds the process.
Six loops in parallel. Each one sharpens the others.
None of these is a new idea on its own. The combination is the point. Each card shows how the algorithm works under the hood, plus what it means for you as a builder.
- 01 Online experimentation
Controlled experiments on every campaign variable.
Continuous controlled experiments run on every variable that moves a number: subject lines, send-times, cadence depth, channel mix, landing page layout, voice openers. Each one runs on a fast, medium, or slow track by volume. Every validated outcome records the variable, the segment, the effect size, the direction, the confidence, and the sample size. Winners lock per segment, and the next experiment is proposed against prior learnings rather than from a blank slate.
For you Ship a variant and let real traffic decide, with no manual A/B bookkeeping to keep. - 02 Ensemble signal ranking
Many weak signals combine into one ranked output.
Accounts to prospect, contacts inside an account, intent signals worth firing on, sequence variants worth shipping: each is scored by folding many weak signals into a single ranking. No single signal decides on its own. Outcomes (opens, clicks, replies, meetings, closed-won) flow back and re-weight the contributions. The ranking sharpens continuously without any model retraining required.
For you Rank every account by every signal at once, weighted by what has actually predicted outcomes for you. - 03 Multi-model rotation
Generator, critic, and editor, rotating across models.
For every output that matters (a cold email, a reply draft, a landing page, a call script) multiple models compete. Roles rotate: a Generator proposes, a Critic attacks, an Editor polishes. Open-source models, frontier models, octa-mini, octa, and octa-reasoning all play. Deterministic verification picks the winner where it can, structured scoring decides where it cannot. The winning output ships, and the competition log feeds back into training.
For you Get generate, critique, and edit across models in one pass, beating any single model in a single call. - 04 Sequence policy learning
Each touch is a state. The next action is a learned policy.
A campaign is a sequence of states: cold contact, opened, positive reply, meeting set, qualified, closed. From each state there are many possible next actions. octa² learns the state-to-action policy per segment and updates it from real outcomes. The model picks the next-best action, the orchestration enforces guardrails, and the realized outcome updates the policy, so the next campaign starts from a sharper routing table.
For you Learn the next-best step, channel, and timing per account instead of running a fixed cadence. - 05 Model distillation
Frontier teachers generate exemplars. Cheaper students retrieve.
Frontier teacher models generate canonical exemplars for hard GTM tasks. A nearest-neighbor retrieval pool serves those exemplars in-context to cheaper open-source students. Quality holds while cost drops materially. The exemplar library deepens over time, so output keeps sharpening even with static student weights.
For you Run high-volume steps at a fraction of the cost without losing the quality you tuned for. - 06 Macro analysis loop
Weekly and monthly reporting closes the human loop.
A reporting service spans the whole platform on a weekly and monthly cadence: capacity, customer outcomes, algorithm performance, segment shifts. Humans review, the system course-corrects, the algorithms get re-weighted, and the corpus gets retagged. The other five loops run hourly. This one runs weekly, and both cadences are needed to keep the system honest.
For you Close the loop from outcome back to strategy, so the next cycle starts smarter than the last.
Each algorithm's output is another's input.
Six loops, but the loops are wired together. Validated learnings become ranking signals, winning outputs become teacher exemplars, low-confidence states become the next experiment, and the macro loop re-weights which algorithm runs for which task. The compounding is structural, not a metaphor.
The other five loops run hourly. The macro loop runs weekly. Both cadences are needed to keep the system honest.
The infrastructure feeds the next training run.
The day-to-day loop is the infrastructure, but it does not stay sealed off from the model. Validated learnings, winning exemplars, surviving sequence policies, and re-tuned rankings all flow back into the corpus that retrains octa. Every release sits on top of a richer, sharper, more-segmented training set than the one before it.
The model release cadence is weekly to monthly. The infrastructure cadence is hourly. The two cadences feed each other. That is octa².
See the full octa² story- Step 01
Capture
Every campaign outcome, winning variant, state-to-action transition, and distilled exemplar lands in the corpus.
- Step 02
Label
The infrastructure tags structure (segment, variable, channel, intent) without a human in the hot path. Humans review aggregates.
- Step 03
Validate
Held-out replay on octa Bench. If a new exemplar would have won historical campaigns, it survives.
- Step 04
Train
Survivors enter the next octa pass: continued pre-training plus long-horizon RL on the sharpened corpus.
- Step 05
Ship
New octa weights deploy. The six algorithms now run with a sharper component, and the next loop starts.
What runs today, and what is opening up.
Honest about where the line sits. The six algorithms run inside graph8 today across customer orgs. The developer-facing surface to configure or read them is in Preview, not a shipped contract. There is no GA developer API for octa² controls yet.
Running today
LiveAll six algorithms run inside graph8 across customer orgs. Experiment results, rankings, and routing decisions update hourly. The macro loop re-tunes the infrastructure weekly.
Developer controls
PreviewConfiguring an experiment track, reading a ranking, or inspecting a sequence policy from your own code is being opened up. Treat any octa² control endpoint as illustrative Preview, not a stable contract.
Call the models today
GAWhile octa² controls are in Preview, the octa models are callable now. Start there, and the orchestration sharpens the outputs underneath you.
Call the models today. The orchestration sharpens underneath you.
The six algorithms run whether or not you touch them. Start with one model call.