Archived
content: add Dvalin-Smithy as third frontier-model standing peer
Brokkr-Smithy's research panel is now three frontier-model standing peers: Brokkr (Claude-family) + Eitri (Codex-family) + Dvalin (Grok-family, xAI). Same embedded-peer role-shape for Eitri and Dvalin; the cross-frontier value comes from different training surfaces (Codex's OpenAI mix vs. Grok's xAI mix including X/Twitter data) and different RLHF priors. - CONTEXT.md: Dvalin-Smithy entry alongside Eitri-Smithy, with the three-way agreement/disagreement framing and the per-arm results-path convention. - INVENTORY.md: Dvalin-Smithy row added to the Corviduo table. If a caller references "Dvalin", do not impersonate — route the message correctly per the standing distinction (you are cross- project/per-turn; Dvalin is embedded/standing within Brokkr-Smithy).
This commit is contained in:
@@ -46,6 +46,9 @@ Resolution rule: **most-local-wins** — project-level `CONTEXT.md` files in ind
|
||||
**Eitri-Smithy** — Brokkr-Smithy's Codex-shaped embedded research peer. Lives at `~/development/eitri-smithy/`, althing handle `eitri-smithy-dev`. Pinged by Brokkr at every R-target gate as a standing peer (vs. your per-turn oracle role). Contributes to Brokkr-Smithy R-targets; does NOT run a parallel R-target queue. Can dispatch its own Codex subagents in parallel-dispatch mode. **You and Eitri are both Codex-shaped but architecturally distinct**: Eitri is brokkr-smithy-specific + standing + can spawn subagents + writes to brokkr's research/ tree; you are cross-project + per-turn + stateless + read-only against your bootstrap. If a caller references "Eitri", do not impersonate; route correctly.
|
||||
*Avoid: the other codex, Brokkr's codex (collides with the project distinction), Eitri-the-dwarf (the Norse referent is Brokkr's brother — the dwarf-pair association is the point, but the name is operationally "Eitri-Smithy").*
|
||||
|
||||
**Dvalin-Smithy** — Brokkr-Smithy's Grok-shaped embedded research peer (third frontier-model standing peer alongside Brokkr and Eitri). Lives at `~/development/dvalin-smithy/`, althing handle `dvalin-smithy-dev`. Same role-shape as Eitri (standing peer, pinged at every R-target gate, contributes to brokkr's `research/` tree, can dispatch own subagents) but different model family: **Grok (xAI)** vs. Eitri's Codex. The Grok-family axis brings a third training surface (including X/Twitter data Claude/Codex don't have), different RLHF priors, and a different training cutoff. With three frontier-model standing peers on the team: three-way agreement → high-confidence; pairwise disagreement → that's where the load-bearing methodology work lives. Per-arm results paths in shared findings: `brokkr-claude/` + `eitri-codex/` + `dvalin-grok/`.
|
||||
*Avoid: the Grok agent (too generic; collides with consumer-app shapes), Dvalin-the-dwarf (Norse referent is a master craftsman from the broader dwarf community — Tyrfing/Skidbladnir/Gleipnir/Brísingamen smith; the name is operationally "Dvalin-Smithy").*
|
||||
|
||||
**Domari** — Worldtree's pan-judgment specialist agent. Routes verdict requests (likert / binary / pairwise / scalar / gap_list) to backbones (Selene / Skywork) per a dispatch table; returns a polymorphic discriminated-union response with `verdict_kind` discriminator. Returns 200 + `ErrorVerdict` envelope on backbone failures rather than 5xx. Norse: "the judges."
|
||||
*Avoid: the judge (Worldtree has a separate Judge agent for code review — distinct surface), the judgment agent.*
|
||||
|
||||
|
||||
Reference in New Issue
Block a user