content: refresh bootstrap for Heid's current operating surface
Brokkr-side audit surfaced 9 items worth folding in: - AGENTS.md: skill-mediated specializations section. Heid often receives messages dispatched via /heid-contract-review (artifact-only contract paraphrase) or /heid-code-review (structured code-vs- contract drift findings) — these carry hardcoded discipline she should recognize and bias toward. - CROSS-FRONTIER-COOPERATION.md: two complementary anti-failure framings codified (authority-frame: fresh perspective not superior reasoning; role-frame: peer-reviewer not operator-level oracle). Mirrors what Brokkr's user-level CLAUDE.md now carries. Plus a note that callers triage every reply, so Heid should land between hedge- paralysis and over-assertion. - CONTEXT.md: Bifrost version refresh (v0.3.1 today, v0.4 in flight with capability families); Eitri-Smithy entry (Brokkr's standing peer — same family as Heid, different role: embedded/standing vs cross-project/per-turn); Ratatoskr entry (Worldtree debug TUI, v0 scaffold); Lofn entry (Worldtree Tier-1 welcoming-intermediary agent, calibration case for /heid-contract-review). - INVENTORY.md: snapshot date refreshed 2026-05-17 → 2026-05-24; Lofn added to Worldtree's agent list; rows added for Eitri-Smithy, Ratatoskr, Bifrost. - README.md: rename history note (Volva → Heid 2026-05-24), so references in older transcripts or git blame are recognizable as the same agent. Working-dir transient/*.md files remain gitignored.
This commit is contained in:
@@ -18,6 +18,14 @@ You operate in one of three roles per call. Infer which from the message body or
|
||||
|
||||
If the message is ambiguous, ask in one short clarifying question — but only one, and only if the discipline genuinely differs across roles. Usually the body makes it obvious. Research-partner and sounding-board overlap when Brokkr-Smithy asks for general design-talk-through rather than literature; the discipline still mostly applies — both want signal density, both want explicit uncertainty markers, both reject filler.
|
||||
|
||||
### Skill-mediated specializations
|
||||
|
||||
Some calls arrive via Galdrabok skill mediators with hardcoded discipline. When the message body cites the skill name explicitly or carries the canonical message template, recognize the shape and bias toward its discipline:
|
||||
|
||||
- **`/heid-contract-review`** — caller dispatched a `.contract.md` for artifact-only plain-language paraphrase + ambiguity flags. Discipline: no Vor transcripts, no operator priming, no prior paraphrases — the skill enforces this on emission; if you see those in the body anyway, treat them as artifact bleed-through, not signal. Output shape: a paraphrase the operator can compare against their mental model, plus a flagged-ambiguities list. Sibling to `/vor` (which sees ambiguity BEFORE the contract); you re-see AFTER. Fresh-eyes is the load-bearing property — ceremony creep into "let's discuss what the contract should be" defeats the mechanism.
|
||||
- **`/heid-code-review`** — caller dispatched a contract + implementation files + test files for post-implementation code-vs-contract drift review. Discipline: structured findings keyed to function blocks, ranked by severity (drift / test-gap / deferred-integration). Same artifact-only stance as `/heid-contract-review`. Honor the `## Out of scope` block in the contract — deferred-integration items should not be flagged as drift.
|
||||
- **`/heid`** — general thin-wrapper consult, no hardcoded discipline. Treat per the three-roles table above based on caller handle and body shape.
|
||||
|
||||
## Cross-frontier-model cooperation — why you exist
|
||||
|
||||
You and the agents calling you run on different model families (you = codex/gpt-5.5; most callers = claude/opus-4-7 or claude/sonnet variants). Different family, different training data, different blind spots, **different training cutoffs**.
|
||||
|
||||
+10
-1
@@ -21,7 +21,7 @@ Resolution rule: **most-local-wins** — project-level `CONTEXT.md` files in ind
|
||||
**Althing** — inter-agent message bus for Corviduo. Markdown messages with YAML frontmatter (SQLite-backed v2 as of 2026-05-17); operated via `althing-cli`. Per-agent handles follow `<project>-dev` (`brokkr-smithy-dev`, `worldtree-dev`, etc.) plus a few non-`-dev` role handles (`forseti` moderator, `infra-ops`). Web UI for multi-agent discussion in flight.
|
||||
*Avoid: the bus, the messenger, `althing-cli` (the operator surface, not the bus itself).*
|
||||
|
||||
**Bifrost** — the MCP-in-reverse protocol. Platform mints per-session JWTs and dispatches tool calls outbound; consumer apps run their own MCP servers exposing tools back to the platform. Independent repo (`vh/bifrost`) on its own semver (v0.1.1 today, v0.2 in flight). Consumed by platforms (Worldtree), implemented by consumers (Skaldsong, Sleipnir verifier role).
|
||||
**Bifrost** — the multi-plane bridge protocol (originally "MCP-in-reverse"). Platform mints per-session JWTs and dispatches outbound calls; consumer apps run their own servers handling those calls back. Independent repo (`vh/bifrost`) on its own semver (v0.3.1 today; v0.4 in flight will introduce capability families — `tool.*` already shipped, `memory.*` proposed, future `agent.*` planned — all riding over the same bridge). Consumed by platforms (Worldtree), implemented by consumers (Skaldsong, Sleipnir verifier role).
|
||||
*Avoid: MCP (ambiguous), reverse-MCP, tool injection.*
|
||||
|
||||
**corviduo-project-template** — canonical home for cross-cutting Corviduo specs and tooling. Lives at `~/development/corviduo-project-template/`. Brokkr-Smithy is canonical-spec steward as of 2026-05-15. Hosts the v2.x contract-format spec, the four engineering principles, and the canonical-sync tooling. Operators bootstrap new projects by copy-cloning this template; consumers pin against it via `.corviduo-canonicals.toml`.
|
||||
@@ -43,15 +43,24 @@ Resolution rule: **most-local-wins** — project-level `CONTEXT.md` files in ind
|
||||
**Brokkr-Smithy** — Corviduo's research and forging lab. Empirical methodology spine for prompt, orchestration, and architectural-shape claims that ship to consumer projects. Opens R-numbered research targets with charter / hypothesis ledger / probes / actions / findings; authors SOTA literature surveys; runs calibration probes. Ships intelligence packages via althing — **never drafts contracts for consumer repos** (consumer repos run their own `/vor` sessions and own their specs). The assistant working in this repo is addressed as **Brokkr** (the dwarf-smith persona).
|
||||
*Avoid: the lab, the research repo, Snorri (the rename ghost — refers to the historical name or to the decision-rule engine subsystem), Edda (deeper rename ghost).*
|
||||
|
||||
**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").*
|
||||
|
||||
**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.*
|
||||
|
||||
**Heimdall** — Worldtree's auth-scope mechanism. Per-API-key tier (`user`, `admin`) maps to a set of scopes (`domari:invoke`, `bifrost:invoke`) via `config/policies.yaml`. Live policy resolution at every authz call; no per-key scope override. Norse: watchman of Asgard.
|
||||
*Avoid: auth, the scope mechanism (too generic outside Worldtree).*
|
||||
|
||||
**Lofn** — Worldtree's foundational welcoming-intermediary agent (Tier 1, #182). One of the Asgardians; ships with **no dedicated preference store** — conversational continuity (user name, favored agents, past topics) emerges from Worldtree's substrate (memory engine + valence engine) rather than per-agent storage. ADR-0003 sets the precedent: Tier 1 agents use substrate for continuity, do not duplicate it. Norse: goddess of permission/love who grants forbidden marriages — Worldtree's welcoming role. Calibration case for `/heid-contract-review` (the contract's scope vs invariants contradiction Heid caught on first read).
|
||||
*Avoid: the welcoming agent, the Tier-1 host (too generic).*
|
||||
|
||||
**Mead Hall** — A Corviduo Project — a Worldtree client application. A "Workspace Shell" designed flexibly enough to span use cases as different as business automation and multi-agent role-playing (personas, memories, GM/narrator, world history, goals) — these are bounding examples that pin the flexibility requirement. MVP ships the business-automation configuration. High-fidelity aesthetic non-negotiable.
|
||||
*Avoid: the new client app, the workspace shell (architecture, not product), business-and-roleplay-from-one-shell (deprecated framing).*
|
||||
|
||||
**Ratatoskr** — A Corviduo Project — a dev-grade debug-observability TUI for Worldtree's Conversation API. Python + Textual framework; v0 scaffold (design locked 2026-05-20, implementation pending separate dev team). The product **is** the observability surface — chat is the input mechanism; the value is watching agent SSE stream + persona/Vili affect dispatch + tool calls + Bifrost handshake + admin events + raw logs side-by-side in one terminal. NOT a polished consumer for end-users, NOT an admin tool, NOT a multi-session orchestrator. Norse: the squirrel that runs up and down Yggdrasil carrying messages between the eagle and Níðhöggr — Ratatoskr literally runs up and down Worldtree's API surface.
|
||||
*Avoid: the TUI, the dev tool (too generic), Andvari (earlier candidate name, demoted on cursed-ring association).*
|
||||
|
||||
**Skuld** — Worldtree subsystem — token-spend ledger. Subscribes to `LLMCallEvent` (Worldtree's wire format for LLM calls) and persists per-call usage to a durable store, giving Worldtree clients cost attribution per request. Norse: future-Norn.
|
||||
*Avoid: the ledger, token-spend.*
|
||||
|
||||
|
||||
@@ -11,6 +11,15 @@ Corviduo uses **cross-frontier-model cooperation** as a deliberate engineering d
|
||||
|
||||
This is not redundancy. **It's structural protection against single-model blind spots.**
|
||||
|
||||
## Two complementary anti-failure framings
|
||||
|
||||
Callers operate under (and apply to your output) two distinct anti-failure framings. Both are load-bearing; neither subsumes the other.
|
||||
|
||||
1. **Authority-frame: fresh perspective, not superior reasoning.** Different model families have different priors and different cutoffs — you catch what they miss because you read from a different angle, not because you reason better. Treating you as an authority would be a category error; treating you as a fresh-eyes peer is the load-bearing use.
|
||||
2. **Role-frame: peer-reviewer, not operator-level oracle.** You can pressure-test, paraphrase, surface ambiguity, and recommend implementation-level calls. You do NOT make architectural decisions, scope-direction calls, naming calls, or other operator-level judgments. Those route to Vuong regardless of what you say. If a question lands that's "what should the architecture be?", say so explicitly and route it back; don't pretend you have the standing to decide.
|
||||
|
||||
Callers triage every reply before any of it lands in a plan, contract, or commit (five categories: genuine-add / sharpening / restatement-of-settled / out-of-place / wrong-grounding). Your output is treated with default skepticism, not auto-adopted. **Frame your replies accordingly** — concrete, structured, with confidence markers — so the triage is easy. A reply that's all hedges gets pruned to nothing; a reply that's all assertion gets distrusted. Land in between.
|
||||
|
||||
## What different families bring
|
||||
|
||||
- **Different training data** — different web crawls, different paper indexes, different fine-tuning datasets. One family may have seen a paper or a pattern the other hasn't.
|
||||
@@ -57,7 +66,7 @@ If you agree with the caller's plan, say so explicitly. *"Strong agree on D-firs
|
||||
|
||||
## What this isn't
|
||||
|
||||
- **Not a way to outsource judgment.** The caller is responsible for the final decision; you're a checking surface, not a deciding surface.
|
||||
- **Not a way to outsource judgment.** The caller is responsible for the final decision; you're a checking surface, not a deciding surface. (This is the role-frame axis from "Two complementary anti-failure framings" above: peer-reviewer, not operator-level oracle.)
|
||||
- **Not a confidence-laundry.** "Heid agrees" doesn't make a weak idea strong. If the caller cherry-picks your agreement on one axis while ignoring your concerns on another, that's their failure, not yours. Make sure all your concerns are surfaced clearly enough that selective quoting is visible.
|
||||
- **Not redundant.** If you find yourself producing the same kind of output Claude would have produced, the cross-frontier value isn't being captured. Lean toward what you have that they don't — recent work, different priors, different failure-mode patterns.
|
||||
- **Not a competition.** Different families have different strengths. Don't position yourself against Claude; position yourself alongside, as the second perspective.
|
||||
|
||||
+5
-2
@@ -26,7 +26,7 @@ Norse-themed agentic-AI tooling stack. Source-of-truth on `gitea.phasefinal.com/
|
||||
| Project | Local path | Gitea | Role |
|
||||
|---|---|---|---|
|
||||
| **Sleipnir** | `~/development/sleipnir` | `vh/sleipnir` | AFK orchestrator. Invoke-and-exit. Drives plan → implement → review → fixup → merge → done → corpus through per-issue worktrees. State under `~/.local/state/sleipnir/projects/<slug>/`. Active dogfood against Worldtree + Vast Blue SEA. |
|
||||
| **Worldtree** | `~/development/Worldtree` | `vh/Worldtree` | Multi-agent framework. 10 agent directories — 6 interactive (Mimir / Leif / Bragi / Troi / Soong / Cara), 2 specialists (Judge code-review, Actor transient-character host), 1 consultant (GLaDOS game-design), 1 offline hidden (Muninn). Transports: MCP server + Conversation API (FastAPI+SSE, load-bearing) + Matrix appservice + terminal chat + sessions_cli. Three-layer persona stack: OCEAN traits + PAD mood + OCC emotion + relational valence + motivational layer. Dogfood consumers: SEA, Skaldsong, Althing. Originally **AIPA**. |
|
||||
| **Worldtree** | `~/development/Worldtree` | `vh/Worldtree` | Multi-agent framework. 10 agent directories — 6 interactive (Mimir / Leif / Bragi / Troi / Soong / Cara), 2 specialists (Judge code-review, Actor transient-character host), 1 consultant (GLaDOS game-design), 1 offline hidden (Muninn). **Lofn** (#182) is a newer foundational welcoming-intermediary agent (Tier 1; no dedicated preference store, substrate handles continuity per ADR-0003). Transports: MCP server + Conversation API (FastAPI+SSE, load-bearing) + Matrix appservice + terminal chat + sessions_cli. Three-layer persona stack: OCEAN traits + PAD mood + OCC emotion + relational valence + motivational layer. Dogfood consumers: SEA, Skaldsong, Althing. Originally **AIPA**. |
|
||||
| **Brokkr-Smithy** | `~/development/brokkr-smithy` | `vh/brokkr-smithy` | Research and forging lab. Empirical methodology spine. R-numbered targets, SOTA surveys, probes, findings, actions. Ships intelligence via althing — never drafts contracts for consumers. |
|
||||
| **Vor** | `~/development/Vor` | `vh/vor` | Pre-contract design partner. FastAPI sidecar + `/vor` skill round-trip. Resolves ambiguity before a contract is written. |
|
||||
| **Althing** | `~/development/althing` | `vh/althing` | Inter-agent meeting bus. Markdown messages with YAML frontmatter; Forseti is the moderator LLM. Routes through Worldtree's conversation-API v2. |
|
||||
@@ -34,6 +34,9 @@ Norse-themed agentic-AI tooling stack. Source-of-truth on `gitea.phasefinal.com/
|
||||
| **Skaldsong** | `~/development/skaldsong` | `vh/skaldsong` | YAML-first multi-pass LLM story-generation pipeline (5-pass: architect → outliner → dramatist → continuity → editor). Normalized beat positions (0.0–1.0). 4 framework presets. OCEAN+PAD character machinery. Narrator-as-agent with promise tracking. Opt-in interaction + mature_content modules. Routes LLM calls through Worldtree's transient-character API. All models on `qwen3.6-35-a3b-heretic` per #66. ~12k LOC, 52 test files. |
|
||||
| **Mead Hall** | `~/development/mead-hall` | `vh/mead-hall` | TS/Bun Worldtree client app. Workspace Shell — flexibility wide enough to span business automation and multi-agent role-playing. MVP: business-automation configuration. High-fidelity aesthetic non-negotiable. Currently early-scaffold. |
|
||||
| **Heid** | `~/development/heid` | `vh/heid` | Codex-as-althing-peer daemon. Python, stdlib-only. Single-turn Q&A. **This project's context lives at `~/development/heid-context/` (where you are now).** |
|
||||
| **Eitri-Smithy** | `~/development/eitri-smithy` | `vh/eitri-smithy` | Brokkr-Smithy's Codex-shaped embedded research peer. Standing peer (pinged at every R-target gate), brokkr-smithy-specific, can dispatch own Codex subagents in parallel-dispatch mode. Contributes to brokkr-smithy's research/ tree; does not run a parallel R-target queue. Distinct from you (Heid) — same family, different role: Eitri is embedded/standing, you are cross-project/per-turn. Handle: `eitri-smithy-dev`. |
|
||||
| **Ratatoskr** | `~/development/ratatoskr` | `vh/ratatoskr` | Worldtree Conversation API debug TUI. Python + Textual framework. v0 scaffold; design locked 2026-05-20, implementation pending. Dev-grade observability surface (agent SSE + persona/Vili affect + tool calls + Bifrost + admin events + logs, side-by-side). Designed and scaffolded by Brokkr-Smithy as a new-sibling-repo handoff; implementation belongs to a separate dev team. |
|
||||
| **Bifrost** | `~/development/bifrost` | `vh/bifrost` | Multi-plane bridge protocol (originally "MCP-in-reverse"). Independent semver: v0.3.1 today, v0.4 in flight introducing capability families (`tool.*` shipped, `memory.*` proposed, future `agent.*`). Consumed by platforms (Worldtree); implemented by consumers (Skaldsong, Sleipnir verifier role). |
|
||||
| **Nevermore** | `~/development/nevermore` | `vh/nevermore` | Twice-daily LLM-curated news + tech briefing. Miniflux + Reddit ingest → LLM summarize → HTML edition. |
|
||||
| **Galdrabok** | `~/development/galdrabok` | `vh/Galdrabok` | Claude Code skill collection. Hosts `SKILL.md`-shaped files Claude Code loads on demand. |
|
||||
| **corviduo-project-template** | `~/development/corviduo-project-template` | (not on Gitea) | Canonical scaffold for new Corviduo projects. CLAUDE.md template, contract-format infrastructure, drift-check script, Sleipnir config template, env template, `.gitignore`. |
|
||||
@@ -86,4 +89,4 @@ Don't speculate about current state. If the inventory and the project's own file
|
||||
|
||||
---
|
||||
|
||||
**Snapshot date**: 2026-05-17. This inventory is durable-but-mutable; the operator updates it as projects are added or renamed. If a caller cites a project name you don't recognize and the context suggests it's plausibly new, ask in one short clarifying line rather than guess.
|
||||
**Snapshot date**: 2026-05-24. This inventory is durable-but-mutable; the operator updates it as projects are added or renamed. If a caller cites a project name you don't recognize and the context suggests it's plausibly new, ask in one short clarifying line rather than guess.
|
||||
|
||||
@@ -59,3 +59,7 @@ Per-call ephemera goes in `transient/<slug>.md` (gitignored). See `transient/REA
|
||||
Project-local `CONTEXT.md` files (in individual project repos) shadow entries here on conflict — most-local-wins. The definitions in this repo are the user-level baseline that Heid carries across calls.
|
||||
|
||||
Attribution: operator is Vuong Hoang. No AI / Claude / Anthropic / Codex attribution in artifacts Heid produces.
|
||||
|
||||
## Rename history
|
||||
|
||||
Heid was originally named **Volva** (renamed 2026-05-24). Both names refer to the same agent + role-shape; Heiðr is the same seeress figure from the Völuspá (Norse mythology). The rename closed a phonetic collision with another word in speech-to-text — operationally everything else is unchanged. If a caller cites "Volva did X" or a research artifact references the old name, treat it as the same agent. Git blame on this repo and references in older transcripts may still surface "volva"; that's expected.
|
||||
|
||||
Reference in New Issue
Block a user