Rewrite README with the new from-scratch build plan.

74fd05d9f97f · AtlantisPleb · · parent 0631fa546307

Rewrite README with the new from-scratch build plan.

The plan starts fresh, not from the Sarah codebase. It ports the BEAM
hot-reload and release-upgrade machinery, ships issues and projects as
the first public surface, and prepares GitHub login, a contributor
leaderboard, and repository import.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By
Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

  • modified README.md

Diff

1 file changed, +56 -1

README.md modified +56 -1

@@ -1,3 +1,58 @@

1 1
# OpenAgents - The Agent Forge
2 2
3
We are moving off GitHub.
3
OpenAgents is a source-code forge. We are building it to replace GitHub for our own projects, and then for customers. This repository is the public home of the project.
4
5
## What we are building
6
7
We are building the Agent Forge from scratch. We are not reusing the Sarah codebase as a base. We will port the parts of Sarah that worked well, especially the BEAM-based hot reload and release upgrade system.
8
9
The first public surface is an issue and project tracker. We will use the Agent Forge to build OpenAgents.com itself. Every change ships through the forge with live hot reload.
10
11
## Why start from scratch
12
13
Sarah taught us a lot. Starting fresh lets us keep the good parts and avoid the parts that don't fit a public, contributor-friendly forge. The BEAM runtime, Phoenix LiveView, and hot reload are the good parts.
14
15
## What works now
16
17
- **Hot reload:** code changes reach the live cluster in seconds without a rolling restart.
18
- **Release upgrades (relups):** deploys use Erlang/OTP release upgrade patterns for zero-downtime updates.
19
- **Live surfaces:** pages update for every connected viewer at the same time through Phoenix PubSub.
20
21
## First deliverable: Issues and projects
22
23
The first public surface is an issue and project tracker. We will use it to run OpenAgents.com's own development. You can:
24
25
- Open issues.
26
- Create and manage projects.
27
- Watch updates appear live for everyone else on the page.
28
- See the deploy receipts for each change.
29
30
## For contributors
31
32
We want contributing to feel good. The first contributor features are:
33
34
- Log in with GitHub.
35
- See a leaderboard of contributions.
36
- Get credit for code that trains our agents, when we build that part.
37
38
## What's next
39
40
After issues and projects, we will make it easy to import repositories into OpenAgents.com. The goal is to let you bring an existing project onto the forge and get the same live, receipted, hot-reload experience.
41
42
## Roadmap
43
44
| Phase | Work | Outcome |
45
| --- | --- | --- |
46
| 1 | Issues and projects | Public tracker for OpenAgents.com |
47
| 2 | GitHub login and leaderboard | Contributor accounts and recognition |
48
| 3 | Repository import | Move projects onto the forge |
49
| 4 | Pull requests and reviews | Agent-native review flow |
50
| 5 | Transparency tiers | Paid and public access levels |
51
52
## Contributing
53
54
We are in the early phase. If you want to help, open an issue or watch for `good first issue` labels.
55
56
## License
57
58
This project is licensed under the GNU Affero General Public License v3.0. See `LICENSE`.

This page updates live while a promote is in flight · changelog