Skip to content

docs(agents): actors, not threads -- the owner's rule; the fork holds the extension only (Closes #7852) - #7869

Merged
gHashTag merged 1 commit into
masterfrom
docs/actors-not-threads
Oct 8, 2026
Merged

gHashTag merged 1 commit into
masterfrom
docs/actors-not-threads

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 8, 2026

Copy link
Copy Markdown
Owner

Closes #7852

What

A new section in AGENTS.md, "Actors, not threads (owner rule, 2026-10-08)":

  • Everything that runs at the same time is an actor. That covers a round, a reviewer, a poller and a runner lane. Each one gets a pid, a bounded mailbox and a supervisor. The rules are specs/queen/actors.t27, reached only through its generated card.
  • No new loops. Queen or swarm work gets no new setInterval, thread pool, worker counter or promise fan-out.
  • Replace in a fixed order:
    1. An MVP of the actor runtime.
    2. Its tests.
    3. A benchmark against the current loop on the same input.
    4. The numbers posted on Queen moves to the actor model: the rule in every AGENTS.md, an MVP, a benchmark, then the swap #7851.
    5. Only then the swap.
  • Where the code lives. The Queen server is in gHashTag/trios, on branches queen and queen-runners, with 1681 commits moved with their history. The gHashTag/BrowserOS fork holds the browser extension only.

This section is the rule's one home. The AGENTS.md of trios, trinity, tri-net, trinity-fpga and leela point here instead of copying it.

🤖 Generated with Claude Code

…olds the extension only (Closes #7852)

The Queen and the swarm move to the actor model of specs/queen/actors.t27.
A loop is replaced only after an MVP, its tests and a benchmark against the
current loop on the same input, with the numbers posted on #7851. The Queen
server lives in gHashTag/trios; the gHashTag/BrowserOS fork holds the browser
extension and nothing else.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-08 17:36:37 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 40
PRs with All Checks Green 10
READY 1
FAILING 40
PENDING 0
NO CHECKS YET 0

These columns do not partition: 1 + 40 + 0 + 0 = 41, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=39fa3908f9fd != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: actors, not threads -- the owner's rule in AGENTS.md

2 participants