Select the action domains that matter for your use case. We'll use this to filter the canonical action types shown in the next step. This choice does not write anything — you can revisit it from the dashboard later.
Here are the canonical action types in the domains you selected. Each one has a default tier from the Lyhna registry. Override it if your agents need stricter or looser governance.
| Action type | Domain | Default tier | Your tier | Escalation route |
|---|
Overrides change how strictly your agents are governed. The canonical action type and its meaning remain the same across all Lyhna tenants.
Your agent sends action names like exec, write,
or shell_command when it calls bind(). Lyhna needs
to know what those mean in canonical terms so your receipts are classified
correctly. Unmapped actions still produce receipts — they'll show as
unmapped until you configure this.
| Raw action name | Maps to (canonical type) | Match rule |
|---|
You can add more mappings later from the dashboard. Actions that arrive without a mapping will still be governed — they'll use default classification until you configure them.
Setup complete.
// npm install @lyhna/bind (add "type":"module" to package.json)
import { bind } from '@lyhna/bind';
const receipt = await bind({
action_type: 'test_ping',
action_payload: {},
intent: 'verify_install',
intent_version: '1.0',
});
if (receipt?.receipt_id && receipt?.signature) {
console.log('Lyhna install verified.');
console.log('Outcome:', receipt.outcome);
console.log('Receipt:', receipt.receipt_id);
}
if (receipt.outcome === 'ESCALATED') {
console.log('Fresh tenant: ESCALATED is expected until authority rules are configured.');
}
@lyhna/bind is a project dependency. Install it inside your Node project with npm install @lyhna/bind. Do not install it globally.
Your API key was shown once at signup. If you saved it, you're ready to integrate. Lost it? Use Regenerate Key on the dashboard — the old key is revoked immediately.
The raw key is only shown once, at creation time. Lost it? Rotate to generate a new one — the old key is revoked immediately.
Escalation route applies to Executive actions that stop execution and are held for resolution by your declared resolver. Lower-tier actions are still receipted but do not require routing.
Set the escalation route for all Executive / tier_3 authority rules. Lower tiers are receipted but do not require routing.
Runtime mappings translate raw tool names from agent runtimes into canonical Lyhna action types. Canonical action types feed Authority Rules, receipts, IJL, and future federation metrics.
| Runtime | Raw action | Resolves to | Source | Status |
|---|
Notification Settings control tenant-wide outbound alerts. Authority Rule escalation routes apply when an action escalates and execution is paused.
| Channel | Destination | Min tier | Status |
|---|
// npm install @lyhna/bind (add "type":"module" to package.json)
import { bind } from '@lyhna/bind';
const receipt = await bind({
action_type: 'test_ping',
action_payload: {},
intent: 'verify_install',
intent_version: '1.0',
});
if (receipt?.receipt_id && receipt?.signature) {
console.log('Lyhna install verified.');
console.log('Outcome:', receipt.outcome);
console.log('Receipt:', receipt.receipt_id);
}
if (receipt.outcome === 'ESCALATED') {
console.log('Fresh tenant: ESCALATED is expected until authority rules are configured.');
}
@lyhna/bind is a project dependency. Install it inside your Node project with npm install @lyhna/bind. Do not install it globally.
/start to your Lyhna bot, then use the chat ID it returns.