Migrating from den.ctx

den.ctx is deprecated. A compatibility shim forwards den.ctx definitions to den.schema.<kind>.includes with deprecation warnings, so existing configs still evaluate — but you should migrate to remove the warnings and use the current API.

What changed

Old (den.ctx)	New	Notes
den.ctx.<name> = { ... }	den.aspects.<name> = { ... }	Aspect definitions live here now.
den.ctx.<name>.includes	den.schema.<kind>.includes	Explicit activation on entity kinds.
den.ctx.<name>.<p>	den.schema.<kind>.includes or policy	Cross-entity inclusion via schema or policy.
den.ctx.<name>.into	den.policies	Entity topology via first-class policies.
den.ctx.<name>.meta.adapter	(removed)	Pipeline handles class routing automatically.
den.lib.ctxApply	(removed)	No shim — see step 5 below.

Tip

The shim handles the common case automatically: den.ctx.<name> entries are forwarded as den.schema.<name>.includes. Only into transitions and direct ctxApply calls require manual migration.

A compatibility shim keeps existing den.ctx configs evaluating during the transition, emitting deprecation warnings as it forwards them. For how the shim forwards internally and why it is scheduled for removal, see den.ctx compat shim.

Migration steps

1. Move aspect definitions to den.aspects

   Aspect content that was defined inline in den.ctx moves to the aspects registry:

   # Before
   den.ctx.host = {
     provides.host = { host }: den.aspects.${host.aspect};
   };
   
   # After
   den.aspects.my-aspect = { host }: {
     nixos.services.foo.enable = true;
   };

2. Activate aspects via den.schema.*.includes

   Instead of den.ctx.<name>.includes, add aspects to the relevant entity kind’s includes list:

   # Before
   den.ctx.host.includes = [ den.batteries.hostname ];
   
   # After
   den.schema.host.includes = [ den.batteries.hostname ];

3. Move into transitions to den.policies

   If you used den.ctx.<name>.into to fan out from one entity kind to another, declare an explicit policy:

   # Before
   den.ctx.host.into = { host }:
     map (user: { inherit host user; }) (lib.attrValues host.users);
   
   # After
   den.policies.host-to-users = { host, ... }:
     map (user: den.lib.policy.resolve.to "user" { inherit host user; })
       (lib.attrValues host.users);

   See Policies for the full policy model.

4. Remove meta.adapter

   The meta.adapter option no longer exists. The pipeline determines which class keys apply to each output automatically. Delete any meta.adapter assignments.

5. Replace ctxApply calls

   den.lib.ctxApply has no compatibility shim. If you called it directly, replace it with aspect definitions activated via den.schema.*.includes.

6. Verify

   Rebuild your system and confirm no deprecation warnings remain:

   nixos-rebuild build --flake . 2>&1 | grep -i 'deprecated'

Further reading

• Policies — declaring how entity kinds relate
• Entities & Schema — entity declarations and schema
• den.ctx compat shim — what the shim does