Coheron Computing
Self-Creating Self-Evolving Self-Validating Living AI

A new kind of artificial intelligence

It doesn't predict what might work. It builds what does — and proves it.

No neural network. No machine learning. No training. Coheron starts from almost nothing — only the ability to observe software and act — then invents its own capabilities, proves each one against reality, and keeps every proven one forever. It has already crossed from a code environment into applications, learning and operating across environments. What it produces are not predictions that might be right or wrong — they are capabilities proven to work.

It doesn't stay where it started. It grows past its starting point, across environments, and everything it learns, it can prove.

Self-evolving·Self-verifying·Self-improving

An artificial intelligence built on evolution instead of prediction — it improves itself with no training, and proves every capability it creates. That is how it keeps getting stronger, and why it can be trusted as it does.

Unlike the AI everyone else is building

Neural / machine-learning AI

  • Trained on massive data, at great cost and time
  • Predicts an answer — which may be right, or wrong
  • Bounded by what was in its training
  • You hope it's correct; you can't be sure

Coheron

  • No training, no model to fit — starts almost empty
  • Constructs each capability and proves it — never a guess
  • Keeps everything it proves forever, and grows faster as it goes
  • Works across many environments, and tunes its own configuration as it runs
  • You know it's correct, because it was verified

Nobody told it what to build. Nothing was defined in advance. It sets its own goals, constructs its own abilities, and proves each one — true, open-ended evolution that expands beyond its starting state. Nothing else does that.

The rule that governs everything it keeps

accept = V ∘ Π

A capability (Π proposes it) is kept only if verification (V) proves it against reality. So what it knows is independent of the proposer — never a guess that might be wrong — it keeps growing across environments, and nothing unproven ever survives.


How it evolves — and self-verifies — a capability

This is the loop of the intelligence itself. It is never told the steps: it proposes, verifies against reality, and evolves — and every proven ability becomes a building block for a deeper one. That is what self-improving means here, concretely.

1 Seed
Starts almost empty

It can observe the software and act — nothing about the target is built in.

↓
2 Propose
Try a next step toward a self-set goal

Proposed by the engine's own search — or a model, or a person at a sticking point.

↓
3 Verify — the gate
Prove it against the live system · accept = V∘Π
✓ passes
Keep — and spawn TWO → one evolved (composed), one value-variated. Every proof multiplies the working lines; the floor rises; loop back.
× fails
Search, then a human → try other routes; if still stuck, file a ticket a person clears — re-verified like any other.
↓
4 Emerges
A specialized capability — proven, and reusable at scale

How it knows why code works — and what to avoid

This is the heart of it, and it is genuinely new. The equations are proprietary; what they do is not a secret.

Extract — why & how it works

Relationship equations

First-of-their-kind equations read a set of working coded assets and extract the exact relationships that describe why and how they work — what each part requires, and what it guarantees.

Avoid — what fails

Antipattern relationships

The inverse is captured too: the antipattern relationships that describe what does not work, so failed shapes are ruled out before they're ever attempted.

Evolve — something different

Compose into new, proven assets

That relationship knowledge is combined with other first-of-their-kind math and algorithms to evolve entirely new sets of coded assets — ones that do something different — and each self-verifies to guarantee it works. The one rule we'll show is the gate that makes it trustworthy: accept = V∘Π.

See it for yourself — two environments, one engine real capture

Exhibit A — a user interface, operated like a human. The engine perceives the live screen and its controls — given no API, no source code, no internals — and operates them (click, type) to reach a goal, exactly as a person would with a mouse and keyboard. It was given none of these steps; the trace is replayed against the live app, and every state change is real.

1 where it starts — the seedknows nothing
def coheron(app):
    app.reset()          # observe the software
    # it can click, type, and read state — and nothing else.
    return app.snap()    # it knows NOTHING about this app yet
autonomous evolution · no human steps · no training
2 what it evolved  ·  reach[ orders ≥ 1 ]verbatim
def coheron(app):
    app.reset()
    app.click('nav_account')
    app.type('user'); app.type('pass'); app.click('do_login')      # signs in
    app.click('nav_catalog'); app.click('add_p1')                  # puts an item in the cart
    app.click('nav_cart'); app.click('go_checkout')                # opens checkout
    app.type('addr_name'); app.type('addr_line'); app.type('addr_city')
    app.click('save_address')                                      # shipping saved
    app.type('card_num'); app.type('card_exp'); app.click('save_payment')
    app.click('place_order')                                       # ORDER PLACED
    return app.snap()['orders'] >= 1
3 proof — replayed live against the app
> replaying reach[orders ≥ 1] against the live application …
click:nav_account → screen = account
type:user · type:pass
click:do_login → authed = true
click:add_p1 → cart_count = 1
click:nav_cart → screen = cart
click:go_checkout → screen = checkout
type:addr_name · addr_line · addr_city
click:save_address→ has_address = true
type:card_num · card_exp
click:save_payment→ has_payment = true
click:place_order → orders = 1 · order_status = processing

✓ VERIFIED — orders ≥ 1 · an order was really placed

This is one of many. From that same empty seed, with no human writing steps and no training, the engine grew a whole library of verified capabilities — each proven before it was kept, the deeper ones built on the ones before them.

Exhibit B — backend code, written and proven

A completely different environment — no interface at all. Here the same engine composes primitive operations into new functions and keeps one only when it verifies on held-out inputs. Same intelligence, same rule, a different world: it operates software like a human and writes code like an engineer.

1 a seed operation it's givenstart
sort([3, 1, 2])   →   [1, 2, 3]
autonomous evolution · it composes, then verifies
2 a function it wroteverified on held-out I/O
def evolved(x):                 # it composed:  neg(times2(sort(x)))
    return [ -2 * v for v in sorted(x) ]
# [3, 1, 2]      → [-2, -4, -6]
# [5, 5, 5]      → [-10, -10, -10]
3 and a kind that recombination provably cannot reach
the clincher — invention, not rearrangement (verified)

The engine evolved triple(x) = 3·x, verified with 0 mismatches on 80 held-out inputs:

triple([3, 1, 2])       →   [9, 3, 6]
triple([-2, 0, 4, 7])   →   [-6, 0, 12, 21]

Then the proof: across all 3,578 functions reachable by recombining the seed operations, every scaling factor is a power of two (±1, 2, 4, 8, 16). 3 is not a power of two — so no recombination, at any depth, can ever produce ×3. The engine reached it anyway, and proved it works. That is a genuinely new capability, created — not rearranged.

…and it kept going, on its own

Every ability below was grown and verified by the engine from that seed — organized by the generation it appeared in. Nobody specified this list. It set its own goals and discovered what was reachable; the deeper the generation, the more it had to build on itself to get there.

gen 0foundations · 18
authedis_adminqa_rolepole_selectedwishlist=1promocart_count=1screen: accountcartcatalogordersadminpolespoleproductcategory: electronicshomepoles
gen 12
pole_assignedinspection = assigned
gen 21
measured
gen 37
inspection = submittedinspection = approvedinspection = rejectedexports = 1violations = 1violations = 2cart_count = 2
gen 41
cart_count = 3

Generation 0 is what it could reach directly; each later generation required chaining abilities it had already built and proven — for example the full field-inspection sign-off (assign → measure → submit → approve → export) only became reachable once the steps beneath it existed. That is growth beyond the starting state, in the open, with no target handed to it.

Why it only gets stronger

It is not a model you train once and freeze. It is a living system — and it compounds.

Permanent capabilities

  • Everything it proves, it keeps — forever
  • Each becomes a building block for deeper ones
  • It never relearns and never forgets

Compounding growth

  • The more it has proven, the faster it reaches what's next
  • Later generations are built out of earlier ones — see the ladder above
  • It reaches whole new kinds that recombination provably cannot

Self-optimizing

  • It tunes its own configuration while it runs
  • Keeps what improves discovery; rolls back what doesn't

Moves across environments

  • Already crossed from code into applications
  • A pattern learned in one is re-used in another
  • It carries every proven capability with it
Measured — the power-of-two effect

Each verified capability spawns two — one evolved, one value-variated — so working lines multiply. From the same tiny seed set on an identical budget, that reached 583 distinct verified capabilities versus 21 when each spawns only one — nearly 28× more, because two directions outrun the ceiling that traps single-line growth.

generationworking linesspawned (2×)new kept
1366
3102016
6418260
9136272192

And it is not one trick — the reach is the point

The same engine has grown and proven capabilities across kinds of software, kinds of interface, kinds of use, and independent environments:

Kinds of software

  • Transactional commerce
  • Field asset inspection & sign-off
  • Multi-role administration & review

Kinds of interface

  • Clicks & multi-screen navigation
  • Multi-field typed forms
  • Permission-gated actions
  • Hidden-state controls
  • Controls it discovered that no one had used

Kinds of use

  • Single actions → deep end-to-end transactions
  • Role-gated, multi-actor workflows
  • Autonomous discovery of new operations
  • Unattended bulk execution at scale

Environments

  • Reproduced on two independent automation stacks
  • Live state, verified in place
  • By design: applications, APIs, or codebases

A different road to general intelligence

For anyone tracking where AI goes next: this is open-ended self-improvement with verification built in — the one combination the prediction-based paradigm doesn't have.

It escapes the ceiling every other AI hits. Neural systems can only recombine what they were trained on. Coheron invents genuinely new capabilities — including kinds provably unreachable by recombination — and keeps inventing, across one environment after another, because verification (not prior knowledge) is what admits a capability.

Everything it knows is proven. It carries no capability it has not verified against reality. Growth is cumulative and trustworthy — each new ability stands on proven ground.

Human and machine compound. The machine covers breadth and tireless iteration; a person clears only the rare genuine obstacle; both pass the same gate. It is, in our assessment, the clearest path we have seen toward a general intelligence whose every capability is self-verified. (Forward-looking assessment.)