astrale-domain

Astrale Domain

Load detailed domain knowledge from the references that matches the goal.

Kernel boundary

• Use Schema, executable evidence, and the SDK's Domain linter as guardrails.
• Domain source imports Core and DSL authoring values only through the matching semantic @astrale-os/sdk/* subpath. Do not import @astrale-os/kernel-core or @astrale-os/kernel-dsl directly, and do not replace them with a flat SDK root barrel.
• Keep authorization in Schema-owned Policy and callable auth mode; handlers execute only admitted calls and do not define a second authorization model.
• Choose each existential Policy Node extent deliberately: node() for topology-owned matching, node(Class) for a polymorphic Class family, or node.exact(Class) for exact identity.
• Treat the installed SDK's public exports and the current Domain source as authoritative for API syntax.

Intent Router