> ## Documentation Index
> Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt
> Use this file to discover all available pages before exploring further.

# Alpha 1.6.2 — FORGE

> Release architecture for Starfire AI Alpha 1.6.2 FORGE: creation, Knowledge, Research, Control Center, and Developer Platform foundations.

# Alpha 1.6.2 — FORGE

**Alpha 1.6.2 — FORGE** is the release line where Starfire's scope expands from a sophisticated multi-model chat product into a broader AI platform for creation, knowledge, research, administration, and development.

## Release pillars

| Pillar                     | Direction                                                                  |
| -------------------------- | -------------------------------------------------------------------------- |
| **FORGE**                  | Build real software projects and durable artifacts                         |
| **Knowledge**              | RAG, repositories, Files 2.0, and persistent reference context             |
| **Research**               | Deeper research, search, source intelligence, and citation verification    |
| **Control Center 3.0**     | Operate users, models, security, billing, infrastructure, and intelligence |
| **Developer Platform 1.0** | Versioned API, credentials, webhooks, SDKs, logs, and compatibility        |

## FORGE

FORGE introduces the architecture for:

* Build Mode
* Artifact Engine
* Code Workspace
* Build/Repair Engine
* Repository Intelligence

The defining change is that Starfire can target an actual software output—not just a code block in a chat response.

## Knowledge & Project OS

The FORGE-era platform introduces the foundations for durable project context:

* Knowledge Bases
* RAG 2.0 concepts
* Files 2.0 concepts
* repository-backed knowledge
* Project OS
* Context Engine

This separates persistent project knowledge from one conversation's context window.

## Research

Research expands beyond a simple web-search tool into a workflow that can plan queries, gather sources, track claims, verify citations, and report conflicts.

## Control Center 3.0

Control Center evolves from a relatively flat admin panel toward an operating system for Starfire with deeper domains for:

* users and identity
* organizations
* models/providers/routing
* intelligence workloads
* developer resources
* billing
* infrastructure
* security
* configuration
* audit
* incidents and diagnostics

## Developer Platform 1.0

The release architecture defines a versioned developer platform with resource families for models, responses/chat, runs, research, files, artifacts, builds, projects, Knowledge, embeddings, usage, and webhooks.

It also establishes the direction for:

* API keys and scopes
* applications
* service accounts
* rate limits
* request IDs
* webhook delivery/retries
* API logs
* developer usage
* interactive playground
* OpenAPI
* JavaScript/TypeScript and Python SDKs

## Three major Starfire surfaces

FORGE establishes the long-term product shape:

```text theme={null}
Starfire AI workspace
    → humans using the platform

Control Center
    → operators running the platform

Developer Platform
    → software building on the platform
```

## Alpha status

This release page documents the architecture and product direction of the 1.6.2 FORGE line. Individual capabilities were implemented and staged at different times and continued evolving into NEXUS.

<Card title="Alpha 1.6.3 — NEXUS" icon="sparkles" href="/releases/alpha-1-6-3">
  See how NEXUS expands identity, organizations, billing, automation, Control Center, and the frontend around the FORGE foundation.
</Card>