Skills reference

The commands that direct an AIBOS sphere are Norwegian slash commands — /plasser, /lagre, /samsvar, and the rest. That's an honest fact about the standard today, not a translation gap this page is trying to paper over: the standard's authors write in Norwegian, and an English translation of the standard itself is on the roadmap. Until then, this page explains every command in English as it goes, alongside the Norwegian name you'll actually type.

The full set

The six canonical skills

/plasser — place

Governed folder creation, and the only sanctioned way a new folder comes into existence in a sphere. It runs as one atomic sequence: an anti-duplicate check against the registry before anything is created (a near-duplicate hit stops you — "don't build the fifth version of this"), then the folder itself, then a proper _about.md, then the parent index and the central registry updated together, in the same action. This is what keeps duplicate folders from piling up, and keeps the registry honest against what's actually on disk.

/initiativ — initiate

Everything new is born here. It mints an initiative ID, creates the initiative's home via /plasser, and carries the work through the lifecycle: explore → define → build → awaiting-go → running → archived. The transition out of awaiting-go is a hard gate — an explicit human sign-off, not something an agent can wave through on its own. See Lifecycle.

/motta — receive / intake

Triages material sitting in incoming/ into the sphere's lifecycle. An idea worth pursuing routes to a new initiative; something multi-phase gets split apart; anything else gets logged as a decision or marked reference-only. The enforcement point: a durable trace has to exist before the source material is allowed to move out of incoming/ — skimming isn't triage. See The handover gate.

/lagre — save

Memory review that runs after a piece of work is delivered, not inline while it's happening. It never defaults to "nothing to save" — the review is built to actually look, including for frustration signals in how a session went, which are treated as first-class material worth capturing. The discipline underneath is the same fix-not-error rule and hard size limit covered on Memory architecture: capture the fix, never the transient error, or an agent ends up citing its own old mistakes back at itself.

/utforsk — explore

Build-to-learn: a reversible experiment, marked EXPERIMENTAL, that never needs to pass through a go-live gate because reversibility is the whole point. This is what keeps a rough draft from needing anyone's permission before it starts.

/samsvar — conform

Runs the conformance audit and tells you plainly whether your copy passes or what's blocking it, the moment there's at least one real problem. This is the mechanism that keeps the manual and the running system honest against each other, and the whole pull-based conformance model depends on it running regularly. See Conformance and audit.

The two mechanism verbs

/kapabilitet — capability

The install mechanism for the capability layer: install, validate, or uninstall a versioned add-on, with a safety scan of every piece of executable code before it's copied in. Uninstalling archives with a marker rather than deleting. See Capabilities and marketplace.

/utgi — publish / release

The rigid, ten-phase workflow for a change to the master standard itself. Every skill, contract, or fix that touches the standard runs through the same sequence: idea, spec, build, test, gate, version, use it on ourselves first, publish, propagate, close. A master change made from memory, skipping the sequence, is exactly the failure mode this workflow exists to prevent. It's what keeps the standard's own history line unbroken, and what makes sure a change actually reaches everyone who's supposed to hear about it.

Two more worth knowing

/tråd — thread

The command-line tool behind Trellis. With it you can list open threads, open one, log a new event to it, check nothing's tangled, rebuild a view from scratch, or look up its history and stats. Every write requires a belonging declaration first — the tooling refuses to record an event without one — and the view worth knowing by name is "the bird" (fugl in the original Norwegian): blocked threads and anything waiting on you sit at the top, always, radiating rather than requiring you to go looking. Full detail in Trellis threads.

/importer — import

Made for existing, messy projects: bringing a project or business that already exists, with no AIBOS structure yet, into conformance with the standard. It runs across eight phases with two human-in-the-loop gates, and offers an optional gradual mode for migrating incrementally rather than all at once. It's in real use today, at version 0.4.0 — proven on a live migration rather than only designed on paper.