diff --git a/examples/hello/mcpp.toml b/examples/hello/mcpp.toml
index 56a0b82..90382c3 100644
--- a/examples/hello/mcpp.toml
+++ b/examples/hello/mcpp.toml
@@ -11,5 +11,5 @@ target  = "x86_64-windows-gnu"
 ldflags = ["-nostdlib", "-Wl,--subsystem,10", "-Wl,-e,efi_main"]
 
 [dependencies]
-openkal      = "0.5.1"
+openkal      = { git = "https://github.com/mcpplibs/openkal", branch = "feat/openkal-closure" }
 openkal-uefi = { path = "../.." }
diff --git a/mcpp.toml b/mcpp.toml
index 40a2622..4cb9118 100644
--- a/mcpp.toml
+++ b/mcpp.toml
@@ -15,14 +15,24 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-uefi"
-version     = "0.1.0"
+version     = "0.1.1"
 description = "An implementation of openkal on UEFI Boot Services, for applications the firmware loads before an operating system exists"
 license     = "Apache-2.0"
+
+# The layer this package supplies, in the vocabulary the engine resolves.
+#
+# `mcpp:kernel-abi` names the platform interface a C library sits on. On a
+# traditional stack that seam is unnamed — a C library issues system calls or
+# calls the platform's own entry points directly — and naming it is what lets
+# one C library sit above several platforms. `=openkal` is the interface this
+# package answers to; several packages answer to it and the engine knows none
+# of them by name.
+provides    = ["mcpp:kernel-abi=openkal"]
 authors     = ["mcpplibs"]
 repo        = "https://github.com/mcpplibs/openkal-uefi"
 
 [dependencies]
-openkal = "0.5.1"
+openkal = { git = "https://github.com/mcpplibs/openkal", branch = "feat/openkal-closure" }
 
 [build]
 flags = [