Peers

Public repos worth tailing for Effect, Alchemy, and XState patterns. Discovery uses pnpm find-peers and the find-peers skill. Shared lines do not mean identical versions. Drift is expected.

S means an upstream reference or an adopted pattern; A means active, close to our stack, and studied; B means relevant and worth tailing. C means screened without a relevant pattern for current work; D means off-stack; E means stale without a useful reference; F means no usable reference remains. The skill defines the full rubric. Rank measures usefulness. Popularity and version parity do not determine it.

The full dataset lives in peers.json. The content build filters and sorts those rows; changing a tier never deletes a peer. The main roster shows S through B. C through F stay in Also seen.

Our pins

The build reads pins from rat-stack’s root, infra, and core manifests. = means a peer’s recorded version matches our current pin; ≠ means it differs. We do not infer compatibility from either marker.

Each peer has a checked date and a default-branch commit linked below. — means the inspected project manifests have no direct declaration. A transitive dependency may still exist. Catalogs resolve to their declared versions; ranges are labeled and lockfile resolutions are shown where available. Vendored source mirrors and historical test fixtures do not count as current project pins. Targeted discovery also checks XState 6 alpha and @xstate/effect independently of Alchemy; single-line peers qualify when their machine or runtime seam is relevant.

Refresh peers, versions, and tiers every week or two and after every shared-line bump. The repo-native gardener pass owns the refresh. Update the dataset. The build generates this page’s list entries.

Tailing: B and up

Drift: = matches our pin; ≠ differs from our pin. Pairs: XState then @xstate/effect; first seen then checked.

¹ workspace override; catalog ^4.0.5
² workspace package
³ exact UI and plugin peer
⁴ catalog
⁵ peer
⁶ locked from ^4.0.6
⁷ pipeline tooling
⁸ player development and peer pin
⁹ locked from ^4.0.0
¹⁰ locked from ^4.0.5
¹¹ locked from ^6.0.0-alpha.65
¹² catalog and platform peer
¹³ workspace catalog
¹⁴ development and peer pin
¹⁵ root pin
¹⁶ library peer
¹⁷ catalog and patched lock
¹⁸ patched lock

Also seen: C–F (15 peers)

Drift: = matches our pin; ≠ differs from our pin. Pairs: XState then @xstate/effect; first seen then checked.

  • 13kparkin/Pivot: tier C.
    • Why this tier: Screened PlanetScale and Hyperdrive wiring. The T3Code study remains the clearer reference for that seam.
    • Effect: 4.0.0-beta.103 ≠¹
    • Alchemy: 2.0.0-beta.65 ≠
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • cameronapak/dotflowy: tier C.
    • Why this tier: Screened: Better Auth but no Alchemy integration useful to the studied lane.
    • Effect: 4.0.0 ≠
    • Alchemy: —
    • XState · bridge: 6.0.0-alpha.12 ≠ · —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • Dhravya/radish: tier C.
    • Why this tier: Symbol-screened without a relevant client or resource pattern in the recorded study.
    • Effect: 4.0.0-rc.112 ≠
    • Alchemy: 2.0.0-beta.77 ≠²
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • dmmulroy/overseer: tier C.
    • Why this tier: Symbol-screened without a relevant client or resource pattern in the recorded study.
    • Effect: 4.0.0-rc.112 ≠
    • Alchemy: 2.0.0-beta.76 ≠
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • elianiva/elianiva.com: tier C.
    • Why this tier: Screened its Website stack. The upstream example remains the stronger resource reference despite newer pins.
    • Effect: 4.0.4 ≠
    • Alchemy: 2.0.0-beta.83 ≠
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • every-app/open-seo: tier C.
    • Why this tier: Studied auth and database selection. Runtime provider switching remains a rejected pattern for our cartridge38 boundary.
    • Effect: 4.0.0-beta.93 ≠
    • Alchemy: 2.0.0-beta.61 ≠
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • imaimai17468/imaimai-front-templete: tier C.
    • Why this tier: Current Effect and Alchemy pins in a frontend template. No closer lifecycle or cartridge pattern identified.
    • Effect: 4.0.0 ≠
    • Alchemy: 2.0.0-beta.81 ≠
    • XState · bridge: —
    • Seen / checked: 2026-10-09 · 2026-10-27
    • Studied: Not yet studied
  • instructa/planr: tier C.
    • Why this tier: Earlier symbol screening found no relevant client or resource pattern. Its site deployment keeps older Effect and Alchemy pins.
    • Effect: 4.0.0-beta.98 ≠
    • Alchemy: 2.0.0-beta.63 ≠
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • jonbeckman/solstatus: tier C.
    • Why this tier: Screened Website, D1, and auth shapes. Newer pins do not add a stronger pattern than the upstream study.
    • Effect: 4.0.6 ≠
    • Alchemy: 2.0.0-beta.84 =
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos
  • monaxovdulov/tutu-diff-hackaton: tier C.
    • Why this tier: Screened: travel-demo UI uses XState 6, but no Effect lifecycle integration in its project manifest.
    • Effect: —
    • Alchemy: —
    • XState · bridge: 6.0.0-alpha.40 ≠ · —
    • Seen / checked: 2026-10-01 · 2026-10-27
    • Studied: Manifest/README screening only
  • oscarmarina/blockquote-web-components: tier C.
    • Why this tier: Screened: Web Component controller pins XState 6, but no Effect or server lifecycle seam in inspected manifests.
    • Effect: —
    • Alchemy: —
    • XState · bridge: 6.0.0-alpha.65 ≠³ · —
    • Seen / checked: 2026-10-01 · 2026-10-27
    • Studied: Manifest/README screening only
  • SMILEY4/strategy-game: tier C.
    • Why this tier: Screened: browser strategy-game UI pins XState 6; no Effect integration in its webapp manifest.
    • Effect: —
    • Alchemy: —
    • XState · bridge: 6.0.0-alpha.49 ≠⁴ · —
    • Seen / checked: 2026-10-01 · 2026-10-27
    • Studied: Manifest/README screening only
  • zhe-qi/clhoria-template: tier C.
    • Why this tier: Screened frontend template manifest; Effect and Drizzle pins add no relevant lifecycle or cartridge pattern for this pass.
    • Effect: 4.0.0-beta.83 ≠
    • Alchemy: —
    • XState · bridge: —
    • Seen / checked: 2026-10-27 · 2026-10-27
    • Studied: Not yet studied
  • ai4nucleome/BioMaster: tier E.
    • Why this tier: Last default-branch commit July 14; inspected manifests expose an older Effect/Drizzle tree with no current pattern identified.
    • Effect: 4.0.0-beta.83; 4.0.0-beta.83 ≠¹⁵
    • Alchemy: —
    • XState · bridge: —
    • Seen / checked: 2026-10-27 · 2026-10-27
    • Studied: Not yet studied
  • zonko-ai/harbor-sdk: tier E.
    • Why this tier: Last commit June 5. Earlier symbol screening found no relevant client or resource pattern for this upgrade.
    • Effect: 4.0.0-beta.66; 4.0.0-beta.70 ≠⁶⁷
    • Alchemy: 2.0.0-beta.44 ≠
    • XState · bridge: —
    • Seen / checked: 2026-09-23 · 2026-10-27
    • Studied: same-version-repos

¹ catalog
² locked from ^2.0.0-beta.77
³ locked from ^6.0.0-alpha.65
⁴ locked from ^6.0.0-alpha.49
⁵ peer
⁶ tooling catalog
⁷ SDK peer

Version receipts

These links freeze the default-branch source at each checked date. The linked study supports each tier finding; shared pins alone do not establish adoption. Alchemy’s workspace Effect override resolves its catalog range; library peer ranges are not application pins.

Last changed 2026-10-24 in c525d23. Source on GitHub. Change log.

Linked from

  1. Agent rules for rat-stack (AGENTS.md). What you may change, which commands to run, and which changes need approval.

    The content build reads our pins from manifests and filters/sorts that dataset into .brain/resources/peers.svx; never hand-edit generated entries.

  2. find-peers. Refresh public peers, exact stack versions, and tiers after stack bumps. On gardener passes, refresh peers checked more than 14 days ago without blocking other work.
    Link context

    The content build reads that one dataset, sorts by tier then repository name, and renders .brain/resources/peers.svx: S, A, and B in the main list; C through F in a collapsed Also seen list.

  3. gardener. Keep rat-stack current and clean. Update exact dependency versions, learn from repos on the same versions, and add lint rules before cleanup.
    Link context

    The content build reads rat-stack’s current pins from its manifests and filters/sorts this one dataset into .brain/resources/peers.svx; do not hand-edit generated entries.