seed-emulator

Use when working with a SeedEMU repository that contains seedemu/k8sTools or examples/internet/b61_k8s_compile, especially to understand, generate, modify, or validate native Kubernetes/K3s deployment workflows for SeedEMU emulations using k8sTools, KVM, physical nodes, multi-host KVM, Multus, Kube-OVN, or OVS.

Use when extending SEED-Emulator (seedemu) with a new capability — a new application service, a new routing/protocol layer, a reusable component, or a new execution compiler. Covers the Service/Server pattern, virtual-node + late-binding design, where to register and document the addition, and a principle-aligned checklist that distinguishes light top-layer work from substantial core changes.

Use before any SeedEmu paper-search or paper-fit assessment to inspect the local SeedEmu repository, refresh the SeedEmu capability map, and update ../../knowledge/capability-map.md with current services, layers, examples, deployment modes, limitations, and evidence paths.

Use when building a new SEED-Emulator (seedemu) emulation scenario — composing autonomous systems, Internet exchanges, networks, routers, hosts, BGP/OSPF routing, and services with the Python SDK, then rendering and compiling to Docker or a distributed backend. Covers the standard compose → render → compile → verify workflow and the design rules a scenario must follow.

Use when researching academic papers that could be reproduced, evaluated, or strengthened with SeedEmu, especially systems, networking, security, measurement, blockchain, overlay-network, or future-Internet papers; supports multi-round paper discovery, candidate tracking, SeedEmu capability mapping, evidence-gated ranking, and experiment blueprints.