obmm-ecology

The OBMM (Ownership Based Memory Management) ecology on GitCode.

OBMM is a Linux kernel subsystem for cross-node shared memory built on the UB (UniBus) fabric — multiple servers share physical memory over a cache-coherent interconnect, with export/import semantics for publishing and mapping remote memory. This organization hosts everything needed to develop, test, and deploy against it, without requiring real hardware.

What's here

Want to try OBMM without real hardware? Start with ubqemu (ub-vub branch) to bring up a two-node virtual cluster, then use obmmctl inside the guests.

The skill collection

This repository is the skill collection for the obmm-ecology namespace. It consolidates the reusable agent skills distilled from the other repositories:

• obmm-test — the distributed C test framework for OBMM
• obmmctl — the Rust CLI for OBMM
• ubqemu — the QEMU arm64 virtual-UB platform the framework runs on

Each skill lives under .agents/skills/<name>/SKILL.md with YAML frontmatter (name, description) followed by Markdown, matching the skill format already used in-repo by obmm-test/.agents/skills/.

Why a separate repo

obmm-test already ships two skills inline (.agents/skills/). obmmctl ships none. Distilling the shared domain knowledge and each repo's implementation knowledge into one canonical collection here means a new contributor (or a new repo added to the namespace) can pull all six skills without re-deriving them from each repo's docs.

The skills

obmm-domain is the foundation; the repo-specific skills build on it and should be paired with it when the task is about behaviour, not just code mechanics. Pair vub-platform-runner with obmm-domain when debugging import/export behaviour observed on the platform.

Layout

.agents/skills/
  obmm-domain/SKILL.md            shared OBMM domain model
  obmm-test-writer/SKILL.md       test-case authoring (interactive, spec-first)
  obmm-test-maintainer/SKILL.md   framework internals
  obmmctl-developer/SKILL.md      Rust CLI architecture & conventions
  obmm-task-experience/SKILL.md   historical work-patterns & pitfalls
  vub-platform-runner/SKILL.md    running obmm-test on the vUB QEMU platform

Relationship to the source repos

• obmm-test-writer and obmm-task-experience are mirrored from obmm-test/.agents/skills/. If those upstream files change, this mirror should be updated to match (or, conversely, the upstream copy can be removed in favour of this canonical one).
• obmm-domain, obmm-test-maintainer, and obmmctl-developer are net-new distillations produced by reading the two repos end-to-end (README.md, AGENTS.md/CLAUDE.md, the doc/ trees, and representative source). They summarise; they do not replace the source docs. When a skill and a source doc disagree, the source doc wins — fix the skill.
• vub-platform-runner is distilled from ubqemu's docs/specs/vub-qemu-usage.md and the verification history of running the full obmm-test suite on the platform; that doc is authoritative for the device model and the bring-up procedure.