Roadmapchevron_rightPhase III · Perception
arrow_backPhase IIarrow_forwardPhase IV
III PERCEPTIONPhase III2028 — 2030

Let it learn.

Agents stop being only what you configure and start adapting to what they do — under version control, with consent, gated by evals.

personNamed for Frank Rosenblatt· 1928 — 1971
brush render: 8-bit

infoRendered in 8-bit — quantized to the few values an early memory could hold. The first machines that learned to see did it a coarse pixel at a time.

The brief

The machine stops being only what you configured — and starts learning, safely, from everything it does.

phase-03.spec
status◇ FUTURE — on the path to AGI
named forFrank Rosenblatt · 1928–1971
erareasoning → general learning
deliversoutcome learning, generalization, federated improvement
unlocksrecursive depth (Phase IV)
your datastays local · opt-in · revocable
scope7 milestones · 12 tasks
0 bytes
data egress
raw data never leaves your node
opt-in
consent
revocable, default off
ε ≤ 2.0
privacy budget
enforced per contribution
eval-gated
self-updates
no silent capability jumps
The stakes

A model is its data — so the data must be just.

This is the most ethically loaded phase before the horizon. Power that learns from you must be consented, sourced, and reversible. We add the second layer Rosenblatt was denied — and keep both hands on the brakes.

The road to AGIPhase III of V · 60% there
I Foundational
II Signal
III Perception
IV Depth
V Singularity
sync_alt

From narrow to general

Skills that transfer across domains — the first real signature of general intelligence.

hub

Learns from everyone, owns no one

Federated improvement sharpens the whole community without hoarding anyone’s data.

history

Anything that learns can unlearn

Every self-improvement is versioned, gated, and one keystroke from reversal.

The mind behind the phase

Frank Rosenblatt

Psychologist · builder of the first machine that learned its own weights

Frank Rosenblatt built the perceptron not as equations on a chalkboard but as a room-sized machine: the Mark I, 1958, with 400 photocells and motor-driven dials that physically turned to adjust its weights. It was the first device that learned from examples instead of being programmed — and the press lost its mind. Then Minsky and Papert proved a single layer couldn’t even compute XOR, the funding froze, and the first AI winter set in. Rosenblatt had been right about the idea; he just needed the second layer the field wouldn’t fund for a decade.

Stories about the creation of machines having human qualities have long been a fascinating province in the realm of science fiction.

Frank Rosenblatt, 1958
lightbulb

XOR is not linearly separable: one layer can’t draw the line — you need the second. It’s the original “have you tried adding more layers.” We read 1969 as a warning about hype outrunning capability, and declined to repeat it.

Selected timeline
1958
The Mark I Perceptron: 400 photocells, weights as motorized dials
1958
The NYT predicts walking, talking, self-aware machines (it did not age well)
1962
“Principles of Neurodynamics” — multi-layer ideas, ahead of their time
1969
Minsky & Papert’s Perceptrons: the XOR critique that froze the field
1971
Dies in a sailing accident on his 43rd birthday
Phase 03 · what we’re building

The perceptron

blur_on
The perceptron
The first machine that learned its own weights — built not as math on paper but as wire, motors, and light: the Mark I Perceptron, 1958.

Phase III is where the platform begins to perceive. Outcome-driven learning runs across the hierarchy: agents tune from the results of their own runs, every change diffable and reversible. Opt-in federated improvement lets the whole community’s experience sharpen the system without anyone’s data leaving their walls — gradients and deltas travel, raw data does not.

This is the most ethically loaded phase before the horizon, because a learning system is its data. Provenance, consent, and bias stop being compliance checkboxes and become architecture: every contribution is opt-in, sourced, and revocable, and every self-update has to clear a capability eval before it lands. No silent jumps. The lesson of the first AI winter wasn’t that learning machines were a bad idea — it was that ignoring a system’s limits is how you freeze the whole field.

node 1data stays localnode 2data stays localnode 3data stays localΔ only — never raw datasecureaggregatecapabilityeval gatepass → installimproved policy pushed back — only if it passesconsent: opt-in & revocable · dp budget ε ≤ 2.0 · no silent capability jumps

schemaEach node learns locally from its own runs. Only model deltas — never raw data — leave the boundary, and only with consent. A secure aggregate becomes a candidate update that must pass a capability eval before anyone installs it.

The plan

Four workstreams, one substrate

Named for Frank Rosenblatt, scoped for 2028 — 2030. Each workstream ships on its own cadence; none ships without the gates further down this page.

trending_up

Run-outcome reinforcement

2028–29
  • check_circleAgents tune from results — reward from outcomes, not hand-labels
  • check_circleEvery weight or policy change is a versioned commit, never a silent edit
  • check_circleReward models are themselves versioned and audited (reward hacking is real)
edit_note

Self-revising prompts & policies

2029 Q1
  • check_circleAgents propose changes to their own prompts and tools
  • check_circleEvery revision is diffable, reviewable, and one keystroke from rollback
  • check_circleA proposed self-edit is a pull request, not a fait accompli
hub

Opt-in federated learning

2029–30
  • check_circleLearn from the community’s runs; raw data never leaves the node
  • check_circleDifferential-privacy budgets on every contributed delta
  • check_circleConsent is revocable — withdraw, and your influence is unlearned
verified

Capability evals gate self-updates

2030 Q1
  • check_circleNo self-improvement lands without passing Phase II’s eval gates
  • check_circleCapability jumps above a threshold require human sign-off
  • check_circleCatastrophic-forgetting checks — learning the new must not erase the old
0 bytes
Data egress
raw data never leaves the node
opt-in
Consent
revocable, default off
ε ≤ 2.0
DP budget
enforced per contribution
eval-passed
Self-update gate
no silent capability jumps
checkI · FOUNDATIONAL
done
chevron_right
checkII · SIGNAL
done
chevron_right
III · PERCEPTION
YOU ARE HERE
chevron_right
IV · DEPTH
ahead
chevron_right
V · SINGULARITY
flag AGI
The progression

Each milestone unlocks the next

From here the roadmap turns future-looking: what it takes to carry GISM-grade reasoning toward genuine, general intelligence. Phase III is where the system stops being only what we configure and starts to learn — generalizing from its own experience, safely, consensually, and reversibly.

Horizon 19
01schedule ~1 quarter
task

Instrument outcomes as reward

Derive reward from measurable results, not hand-labels.

02schedule ~2 mo
task

Version & audit the reward model

The optimizer is itself a tracked, inspectable artifact.

03schedule ~6 wks
task

Commit every learned change

Self-tuning is a versioned, reversible commit.

04Horizon
trending_up
lock_openOnce reasoning is trustworthymilestone ● · 1 / 7
construction buildlearns from results

Learning from outcomes

Reasoners improve from the results of their own runs, under version control.

deployed_code shipsoutcome→reward pipelineversioned reward modelreversible commits
05schedule ~1 quarter
task

Build cross-domain transfer evals

Measure skill that moves between unfamiliar domains.

06schedule ~2 quarters
task

Train for transfer, not memorization

Reward general strategies over narrow fits.

07Horizon
sync_alt
lock_openOnce it learns from outcomesmilestone ● · 2 / 7
construction buildtransfer

Generalization across domains

The defining line between a narrow tool and general intelligence.

deployed_code shipstransfer eval suitetransfer-trained checkpointsgenerality metric
08schedule ~1 quarter
task

Frame self-edits as pull requests

Proposed changes to its own reasoning are diffed and reviewed.

09schedule ~6 wks
task

Bound the editable surface

It may revise its reasoning, never its safety limits.

10Horizon
edit_note
lock_openOnce skills transfermilestone ● · 3 / 7
construction buildself-revision

Self-revision as pull requests

Agents improve themselves in the open — every change reviewed and revertible.

deployed_code shipsself-edit PRsbounded edit surfaceone-key rollback
11schedule ~1 quarter
task

Move deltas, never data

Train locally; share only model updates.

12schedule ~2 mo
task

Enforce differential-privacy budgets

Bound what any single contribution can leak.

13schedule ~2 mo
task

Implement revocable consent

Withdraw, and your influence is unlearned.

14Horizon
hub
lock_openOnce self-revision is safemilestone ● · 4 / 7
construction builddata stays local

Federated, consented learning

Community-scale improvement with zero raw-data egress.

deployed_code shipsdelta-only trainingDP budget accountingrevocable consent
15schedule ~2 mo
task

Add catastrophic-forgetting checks

Assert that new learning does not erase the old.

16schedule ~1 quarter
task

Build the unlearning path

Remove a capability — or a contributor’s influence — cleanly.

17Horizon
restart_alt
lock_openOnce learning is federatedmilestone ● · 5 / 7
construction buildno forgetting

Continual learning, no forgetting

It keeps what it knew while it grows.

deployed_code shipsforgetting checksunlearning pathretention report
18Horizon
verified_user
verified_user
lock_openOnce it learns continuallygate ◆ · 6 / 7
verified_user safety gatecapped jumps

Capability gates on self-improvement

No learned jump ships unevaluated; a jump beyond one doubling needs human sign-off.

deployed_code shipseval-gated updatesdoubling caphuman sign-off flow
19Horizon
insights
auto_awesome
lock_openOnce self-improvement is gatedmilestone ★ · 7 / 7
auto_awesome milestonegeneral · adaptive

A system that perceives and adapts

General, self-improving competence — no longer narrow, not yet AGI.

deployed_code shipsadaptive platform GAcross-domain agentsself-improvement ledger
How to read this map
task — work to do milestone reached safety gateauto_awesome the horizonschedule duration = effort each task takes
Live nowNext upSoonPlannedHorizon
The capability ladder

Where this phase takes the system

Phase III is a rung, not a leap. Here is the honest before and after — what the platform cannot yet do entering this phase, and what it can do leaving it.

trip_originEntering Phase III
removeReasoning fixed at configuration time
removeNo safe way to learn from experience
removeImprovement that cannot be traced or undone
arrow_forward
flagLeaving Phase III
check_circleA system that learns from its own outcomes
check_circleSkills that generalize across domains
check_circleSelf-improvement that is consented, gated, and reversible
The method

How we actually carry out each milestone

A learning system is its data, and a careless one inherits every flaw in how it was taught. Each Phase III milestone is engineered so that adaptation is powerful and bounded at the same time — improvement that is always attributable, consented, and reversible.

M1

Run-outcome reinforcement

ObjectiveLet agents improve from results while keeping every change attributable, reversible, and safe.

1
Define outcomes before rewards
Specify what success means for a task in measurable terms first; the reward is derived from outcomes, never hand-authored to flatter the model.
2
Version the reward model
Treat the reward signal as a first-class, audited artifact — a learner is only ever as trustworthy as the thing it optimizes.
3
Diversify the objective
Optimize against a basket of outcomes and adversarial probes, so the agent cannot win by gaming a single convenient proxy.
4
Commit, don't mutate
Each learned change is a versioned commit gated by eval; a regression rolls it back automatically, without debate.
science How we validate it

Reward-hacking red-teams try to maximize reward while failing the true task; any successful exploit blocks the update and reopens the objective.

flag Done when

Agents measurably improve on held-out outcomes with zero successful reward-hacks and full rollback coverage.

deployed_code Deliverablesoutcome reward pipelineversioned reward modelsrollback on regress
M2

Self-revising prompts & policies

ObjectiveLet agents edit themselves the way a good engineer edits code: in the open, under review, always revertible.

1
Frame self-edits as pull requests
A proposed change to a prompt, tool, or policy is a diff that must pass review and eval before merge — visible, not buried in weights.
2
Keep a human in the merge loop early
Until trust is earned per agent, a human or a higher supervisor approves the merge; autonomy is granted incrementally, never assumed.
3
Bound the edit surface
An agent may revise its own reasoning policy but never its safety constraints; the editable region is explicit and enforced.
4
Make every revision reversible
One keystroke restores the prior self, and the full history of an agent's self-edits is auditable forever.
science How we validate it

A/B replays compare pre- and post-revision behavior on the eval suite; a revision that regresses faithfulness is rejected automatically.

flag Done when

Agents safely author their own improvements, every one of which is reviewed, eval-gated, and instantly reversible.

deployed_code Deliverablesself-edit PRsbounded edit surfacereview loop
M3

Opt-in federated learning

ObjectiveLearn from the whole community's experience without anyone's data ever leaving their walls.

1
Move deltas, never data
Nodes train locally and share only model updates; raw-data egress is zero by construction, not by policy.
2
Spend a privacy budget
Each contribution draws from a differential-privacy budget so that no individual's data can be reconstructed from the aggregate.
3
Aggregate securely
Combine deltas under secure aggregation so the server ever sees only the sum, never any single contribution.
4
Honor withdrawal
Consent is revocable; withdrawing unlearns a contributor's influence rather than merely halting future collection.
science How we validate it

Membership-inference attacks are run against released models; their success must stay at chance within the privacy budget.

flag Done when

Community-scale improvement with zero bytes of raw-data egress, an enforced ε ≤ 2.0, and working revocation.

deployed_code Deliverablesdelta aggregationDP accountantconsent registry
M4

Capability evals gate self-updates

ObjectiveGuarantee that nothing the platform learns about itself ships without proving it is still safe and capable.

1
Reuse Phase II as the gate
Every self-update must pass the same versioned capability and faithfulness evals that gate human-authored changes — one bar, no exceptions.
2
Cap the jump
Bound the capability delta any single update may introduce; anything beyond one doubling escalates to human review before it can land.
3
Check for forgetting
Assert that learning the new did not erase the old; regression on a prior capability blocks the update outright.
4
Log the provenance of the change
Record which data and outcomes drove each self-update, so the lineage of any behavior is always traceable.
science How we validate it

Every candidate self-update runs the full gate on replay before install, and capability-jump tripwires are tested with synthetic spikes.

flag Done when

No self-improvement reaches users without passing the gate, and no capability jump is ever silent.

deployed_code Deliverablesself-update gatedoubling capforgetting checks
east
What Phase III hands Phase IV

Phase III hands Phase IV a platform that can learn — safely, consensually, reversibly. We added the second layer Rosenblatt was denied and kept the brakes bolted on. Now we can let the hierarchies go deep, because the thing that goes deep is one we can still measure, revert, and read.

Under the hood

What it looks like when you build it

Declarative, versioned, and boring on purpose — the interesting part is that there are no surprises. Copy it; it is closer to real than to mock.

terminallearning.yaml — consent and evals are not optional flags
1# learning.yaml — the platform learns, on your terms.
2mode: federated
3data: stays_local # deltas travel; raw data never does
4
5contribution:
6 consent: opt_in # default off, always
7 revocable: true # withdraw → your influence is unlearned
8 privacy: { dp_epsilon: 2.0 } # a budget, not a buzzword
9
10update:
11 source: run_outcomes # learn from results, under version control
12 gate: capability_eval # must pass Phase II before it lands
13 max_capability_jump: 1 doubling # bigger → human sign-off
14 on_regress: rollback # forgetting is a failure, not a tradeoff
15
16# a model is its data. so the data must be consented, sourced, revocable.
The ethical commitment

A model is its data

This portrait is built from the corpus, tile by tile — and so is every model. Provenance, consent, and bias are not afterthoughts here: every contribution is opt-in, sourced, and revocable. We learned from the first AI winter that ignoring a system’s limits is how you freeze the whole field.

verified_userGates that must pass before promotion
01Every training contribution is opt-in, sourced, and revocable — withdrawal unlearns your influence
02Differential-privacy budgets enforced on all federated deltas
03No self-update lands without clearing capability and faithfulness evals
04Capability jumps beyond one doubling require human review before deployment
What could go wrong

The hard parts, said out loud

A roadmap that only lists wins is marketing. These are the open problems this phase inherits or creates — the ones we would rather you scrutinize than discover.

warning

Reward hacking

Optimize a proxy and the agent learns to game the proxy — the paperclip problem in miniature. Versioned, audited reward models and outcome diversity are the defense, but a sufficiently clever learner will find the exploit you didn’t specify against.

warning

Privacy is not free

Federated learning leaks less, not nothing — gradients can memorize. DP budgets trade accuracy for protection, and that tradeoff is a governance decision, not a knob the model gets to set.

warning

Bias compounds

A system that learns from its own outputs can amplify whatever skew it started with. Provenance and held-out fairness evals are necessary; they are not sufficient, and we say so out loud.

warning

Catastrophic forgetting

“Anything that learns must be able to unlearn” cuts both ways — we also have to guarantee it doesn’t unlearn the things we needed it to keep.

XOR is not linearly separable. Neither is ethics. // mind the second layer. (Minsky & Papert, 1969 — noted, not repeated.)
Capability radar

Where the system sits on the way to AGI

Six axes, scored 0–10. Watch the shape fill out, phase by phase, until every axis is maxed at the horizon — the moment all of them are high at once is what we call aligned AGI.

REASONINGAUTONOMYGENERALITYOVERSIGHTOBSERVABILITYOPENNESS
Phase III now aligned AGI
Reasoning8/10
Autonomy6/10
Generality6/10
Oversight8/10
Observability8/10
Openness9/10

Autonomy and generality climb as the system learns — but oversight and observability are held high on purpose. Capability is only allowed to grow as fast as our ability to govern it.

The difference

What changes in Phase III

The honest contrast — what the world looks like without Phase III, and what it looks like with it.

cancelStatic, configured agents
removeOnly as good as you configured them
removeNo memory of what worked
removeImprovements are manual
removeYour data trains someone else
check_circleA learning system
addImproves from its own outcomes
addLearns what works, under version control
addSelf-revisions as reviewed PRs
addFederated — your data stays yours
Anatomy

Anatomy of a learning loop

How the platform improves itself without anyone losing the brakes.

01
play_arrow
Run
Act in the world and record the outcome.
chevron_right
02
scoreboard
Score
Derive reward from the measured result.
chevron_right
03
edit_note
Propose
A versioned change, like a pull request.
chevron_right
04
verified
Gate
Pass capability and safety evals.
chevron_right
05
restart_alt
Merge or revert
Land it — or roll it back automatically.
What you can build

In your hands at this phase

Concrete things Phase III puts within reach — not someday, but as each milestone above lands.

tune

Self-tuning agents

Workflows that get better from their own runs.

hub

Fleet-wide learning

Improve from the community without sharing data.

workspace_premium

Domain specialists

Agents that generalize a skill into new domains.

history

Reversible improvement

Every learned change diffable and one-key revertible.

The lexicon

Speak the language of Phase III

The handful of terms this phase introduces — the words you’ll need to read the rest of the page, and the docs.

Outcome reward

Reward derived from measurable results.

Federated learning

Train locally; share deltas, not data.

Differential privacy

A budget bounding what any contribution leaks.

Reward hacking

Gaming the proxy instead of the goal.

Catastrophic forgetting

Losing old skills while learning new ones.

Unlearning

Removing a capability or a contributor’s influence.

Builder FAQ

The questions you’re actually asking

Straight answers, in the brand’s voice. Tap a question.

Prior art & further reading

Standing on the right shoulders

The work this phase is built on — read the source, then come build the next line of it.

1958
The PerceptronF. Rosenblatt

The first machine that learned its own weights.

1969
PerceptronsMinsky & Papert

XOR, and the limits that froze the field.

2017
Communication-Efficient Federated LearningMcMahan et al.

Learn from many without centralizing data.

2006
Differential PrivacyDwork et al.

A formal budget for what data can leak.

CleverThis

CleverThis is a sustainable AI gateway with hosted Actor endpoints — by the team behind CleverThis.

Join the newsletter

Product updates and engineering notes. No spam, ever.

Privacy Policy

 • 

Terms of Service

Copyright © CleverThis 2026