Skip to content

DEVELOPER_ALPHA.md

Latest commit

 

History

History
117 lines (82 loc) · 3.64 KB

DEVELOPER_ALPHA.md

File metadata and controls

117 lines (82 loc) · 3.64 KB
Raw

Tessen Developer Alpha

Project Zero Alpha is an experiment with one deliberately simple proposition:

ZERO. Free coding intelligence. 100T shared tokens every day.

The daily Zero Pool is planned to reset at 00:00 UTC. OpenCode is the first distribution focus. The stable developer-facing model identity is tessen/project-zero.

The Alpha is not a promise that every future Tessen developer capability is finished. It is the earliest point at which the core ZERO experience is real enough for developers to use on real coding work.

The experiment

We want to answer a few questions with real usage rather than launch-page speculation:

  • What happens when developers can use coding intelligence at a $0 developer price?
  • Can developers meaningfully use a shared 100T daily pool?
  • Which real coding workflows make ZERO useful enough to return to?
  • Can developer demand attract more voluntary Node participation?
  • Can verified additional compute capacity grow a future Zero Pool?

Those answers must come from production telemetry.

Minimum opening path

Before THE ZERO POOL IS COMING changes to THE ZERO POOL IS OPEN, a developer who has never spoken to Tessen should be able to:

  1. discover Project Zero;
  2. authenticate with Tessen;
  3. receive Project Zero access;
  4. enter a supported coding workflow;
  5. select tessen/project-zero;
  6. complete a real coding request;
  7. return later with the same identity and entitlement.

The first public path is focused on OpenCode. Tessen CLI and Node expand the Alpha, but they should not make first coding activation harder.

Activation funnel

DISCOVER ZERO
      ↓
TESSEN IDENTITY
      ↓
ZERO ACTIVATION
      ↓
FIRST SUCCESSFUL CODING REQUEST
      ↓
RETURNING DEVELOPER
      ↓
OPTIONAL NODE INSTALL
      ↓
VERIFIED PARTICIPATING NODE

Registration alone is not activation.

For Project Zero, an activated developer is a developer who completes at least one successful real ZERO coding request.

The Zero Pool

The planned Alpha baseline is 100T shared tokens/day, reset at 00:00 UTC.

It is not 100T per developer and it is not unlimited usage. Tessen can apply fair-use allocations, concurrency controls, routing policy, abuse protections and emergency controls.

If verified Node participation adds real available capacity, the next day's published pool can increase above the 100T baseline. Public capacity and usage numbers must come from server-authoritative data.

Public footprint

Project Zero can spread across:

  • this public GitHub repository;
  • Tessen Platform and Console;
  • OpenCode;
  • Tessen CLI;
  • Tessen Node;
  • Tessen Status;
  • developer communities and technical content.

But the Alpha should remain understandable without learning the entire Tessen platform first:

ZERO → 100T/day → free during Alpha → use it for real coding.

Growth ambition

The long-term Project Zero acquisition target is 100,000 activated developers.

That is an ambition, not current traction.

Growth should be measured through real activation and retention:

visitors
  → developer identities
  → Zero activations
  → first successful requests
  → returning developers
  → Node downloads
  → Node installs
  → active participating Nodes
  → verified contributed capacity

Truth standard

Alpha means early. It does not mean fictional.

We will not manufacture:

  • developer counts;
  • token consumption;
  • requests served;
  • Node counts;
  • contributed capacity;
  • uptime;
  • rewards or earnings.

The point of Project Zero Alpha is to create a real experiment developers can participate in — and then let the real results tell the story.