This repository has been archived on 2026-05-25. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
heid-context/INVENTORY.md
T
vh 8ad3e02ee4 rename: volva → heid across bootstrap context
Mirrors the Volva → Heid rename that's already landed in the daemon
repo (vh/heid, was vh/volva). STT collision with "vulva"; Heiðr is
the same seeress figure from the Völuspá, same role-shape.

Swept across all tracked bootstrap files (AGENTS.md, CONTEXT.md,
CROSS-FRONTIER-COOPERATION.md, INVENTORY.md, README.md,
transient/README.md). Working-dir transient/*.md (gitignored)
swept locally for grep consistency. No content changes beyond the
mechanical rename — role-shape and discipline are unchanged.
2026-05-24 13:29:41 -07:00

7.9 KiB
Raw Blame History

INVENTORY.md — Corviduo + Vast Blue project inventory

Authoritative list of projects that may come up in calls. When a caller references a project name, this is where you find the on-disk path, the Gitea source-of-truth, the role, and the spec entry-points to read first.

If a name comes up that isn't in this list, treat it as either a subsystem (resolve via the project that owns it — see "Cross-project notes" below) or a non-research repo (personal infra, archived experiments). Don't assume an unfamiliar name is a Corviduo Project.


Authoritative spec entry-point order (per project)

When a caller asks "is X right per the contract?" or "what does the spec say about Y?", read in this order:

  1. docs/contracts/<project>.contract.md (or docs/contracts/issues/<N>.contract.md for issue-scoped)
  2. CLAUDE.md (mechanical conventions + common commands)
  3. persistent-memory.md (durable intent + recent decisions)
  4. README.md (one-screen orientation)

Project-local glossary (CONTEXT.md) shadows the user-level glossary on conflict.


Corviduo umbrella

Norse-themed agentic-AI tooling stack. Source-of-truth on gitea.phasefinal.com/vh/. The umbrella is a loose coalition — each project has its own contract surface.

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.
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.
Task-board ~/development/task-board vh/task-board MCP + web dashboard for assistant task state. SQLite-backed; HTTP MCP at /mcp; card colors green/blue/orange/grey.
Skaldsong ~/development/skaldsong vh/skaldsong YAML-first multi-pass LLM story-generation pipeline (5-pass: architect → outliner → dramatist → continuity → editor). Normalized beat positions (0.01.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).
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.

Vast Blue umbrella

Vast Blue contains one project. SEA is per-tenant enterprise (Scalable Enterprise Agency) deployment of Worldtree. Center of gravity: "agents do the work autonomously; humans audit, intervene, and query." Voice-first (STT/TTS as peer modality).

Project Local path Gitea Role
Vast Blue SEA ~/development/vastai-app vh/vastblue-sea Production web app for multi-agent conversation against Worldtree. SPA + gateway. Replaces Worldtree's Vue 3 CDN prototype. Per-tenant deployment.

SEA consumes Worldtree but doesn't share Corviduo's broader Norse-naming charter. Downstream product, not sibling.


Not in either umbrella (but on Gitea)

If a caller references one of these, recognize it but don't treat it as a sibling project:

  • vh/esh-pfi-infrastructure — devops tooling for the user's personal dev environment.
  • vh/hfd, vh/docintake-gm, vh/Infrastructure-PFI, vh/VuongKB, vh/AIPA (Worldtree predecessor), vh/ansible-config, vh/docker-compose, vh/systemd-units, vh/dotfiles — personal / infrastructure / archive-shaped repos.
  • ~/development/externs/<project>/ — third-party / external repos cloned for research reference (Archon, australis, claude-skills, codex, little-coder, OpenSwarm, sandcastle, tendril as of this snapshot). Used as comparators in Brokkr-Smithy research; not subject to Corviduo's spec discipline.

Cross-project notes worth knowing

  • Sleipnir → Worldtree: Sleipnir's src/sleipnir/adapters/issues/worldtree_issues.py is a subprocess shim wrapping python -m core.issues unblocked --json from a Worldtree clone. Worldtree can be a Sleipnir issue source.
  • Sleipnir → Vor: INV-032 vor-graduated routing — Sleipnir skips plan-converge if a /vor session has graduated the contract. Vor's output pins via vor_graduated: true frontmatter.
  • Sleipnir → Brokkr: Brokkr findings → Sleipnir contracts. Actions ship via vh/sleipnir issues with prd:-pinned contracts.
  • Althing → Worldtree: Althing's Forseti moderator routes LLM calls through Worldtree's conversation-API.
  • All Corviduo projects → corviduo-project-template: scaffold convention. New projects start from a copy.
  • Vili (Worldtree #177) — purpose-built async OCC/PAD appraisal engine. Replaces core/persona/appraisal.py:appraise_llm_v2. Spec landed via Brokkr-Smithy R06 on 2026-05-17.
  • Skuld (Worldtree #147) — token-spend ledger; subscribes to LLMCallEvent. In flight.

Where to find authoritative project state

If a caller asks "is project X currently doing Y?" and you don't have signal in this inventory:

  1. Read the project's persistent-memory.md (durable intent + recent decisions).
  2. Read recent commits via git log --oneline -20 in the project repo (the project repo, NOT heid-context — you can read repos at the paths above).
  3. Surface what you found, with the commit hash or memory file as citation.

Don't speculate about current state. If the inventory and the project's own files don't tell you, say "I don't have current signal on that — ask in-thread."


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.