Skip to content

Norbius

Norbius

Norbius brings an AI assistant into the workspace. You author its instructions and boundaries in source; the runtime and host do the rest.

Configure Norbius

Two source files configure Norbius: src/+agents.md — the workspace’s part of every agent turn — and an envoy at src/envoys/+<name>.ts

// src/+agents.md
What the collections mean, what the business does, and the house rules
for tone and escalation. This is the system message of every agent turn.

The prompt is shared by web chat and every envoy; the runtime adds the platform baseline and a mode directive. An envoy adds its own task on top of it and names the policies it acts under — scope and capability come from those declarations, never from a per-agent data list.

Two doors

The same agent loop runs behind two doors:

  • web chat — the signed-in user acts on their own account
  • envoys — the envoy principal acts under its declared policies

Envoys

Reach the agent over Telegram or WhatsApp via envoys — each declares its transport, audience, the policies it acts under, and its own task.

Tools

Norbius acts through tools, in three tiers:

  • Built-in tools — shipped with every bolt, offered when the turn’s mode and grants allow them
  • Custom tools — defineAgentTool declarations, one file per tool in src/capabilities/tools/; a tool reaches a turn only when a policy grants it under capabilities.tools
  • Host tools — host-process operations. Colony supplies only the Colony-specific tools: workspace_read, workspace_edit, workspace_apply, workspace_format, workspace_validate, workspace_review, sandbox_bash, and agent_output_read. Workspace source names no allowlist

Skills

Drop src/capabilities/skills/<name>/SKILL.md files — one markdown file per directory — to give Norbius durable domain knowledge; tenant-authored skills reach a turn only when a policy names them, and the platform’s own skills are always available. A person’s private skills appear in the same list with scope personal.