Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[Rewrite P1] Factory logistics: host split, worktree protocol, cost telemetry

Aberta
  • Algo errado?
#871 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
docker, rust, typescript
Domínio
devops, infrastructure, tooling

Direção de pesquisa

Start with parent issue #860 and locate factory-spans.ts and the existing docs/rewrite/ runbook sections. Check how factory jobs, worktrees, and cost reporting currently operate before attempting the end-to-end proof. Done means both hosts have documented runbooks and a trivial job produces a Rust change built on tauceti, reviewed on chappie, with spans recorded and Actual Cost filled on the board.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

factory rewrite

Parent: #860
Milestone: Phase 1: Rust foundation
Host: both · Expected cost: $200

The host split and the working agreement the factory runs under.

  • chappie (this host): factory orchestration, all review rounds, LMDB benchmark rig, differential harness driver, CI-first validation. Constraint measured: docker access is OPA-authz-scoped (labelled containers allowed; builds via BuildKit driver; no --load) — Rust builds here run in BuildKit via the container driver or natively on the host toolchain path the factory agents use
  • tauceti (Ada's host): release-grade builds (cargo build --release target matrix), the 72h soak, the 24h fuzz run — long-running jobs that shouldn't hold chappie's capacity. Access path: ssh + the shared worktree per phase; Ada's consent + the exact runbook (what may run, resource caps, scratch dirs) recorded here before first use
  • Worktree protocol: each phase gets ~/nostream-worktrees/phase-N/ on both hosts; chappie's factory jobs branch from the phase worktree; tauceti pulls the same branch refs; artifacts (benchmarks, fuzz corpora, soak logs) flow back as committed files under docs/rewrite/ or as artifacts attached to the phase issue
  • Cost telemetry: factory spans script (factory-spans.ts) runs per job; the factory manager reads spans → Actual Cost USD per issue on the board; weekly variance roll-up as an issue comment on #860
  • Model budget: the rewrite runs on the fleet's litellm config (no new provider); heavy review rounds schedule outside Anthropic peak hours where possible (13:00–19:00 UTC Mon–Fri) per the model-schedule policy

Acceptance: both hosts have the runbook sections; one end-to-end proof — a trivial factory job (spec → build → review → approve) lands a Rust change built on tauceti, reviewed on chappie, with spans recorded and the board item's Actual Cost filled.

Linguagem predominante
TypeScript
Estrelas
829
Forks
234
Merge médio
18h 43min
PRs com merge (30d)
67

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cameri/nostream

Todas as issues de cameri/nostream

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.