Load the rules
Start a session by loading the rules
A new session starts in a workspace that follows the AIOM framework, and the agent should know its rules before it touches anything.
Capturedmcp-aiom 0.5.10
YouLoad the AIOM rules for this workspace and tell me what you have.
Tool callaiom_list_content { "kind": "framework" }
What happensOne framework document, aiom://framework/framework.
Tool callaiom_list_content { "kind": "specification" }
What happensTwelve aiom-* specs come back: behaviour, delegation, delivery, documentation, environment, error handling, evidence gate, git, Jira sync, readme, todo and the standalone workspace structure.
AgentI have the framework and twelve specifications. I will read only the ones this workspace's settings and this task need.
Read a spec
Read the rule that applies to the task
The agent is about to commit, and your workspace has a rule for how commit messages are written.
Capturedmcp-aiom 0.5.10
YouFollow our git specification for this commit.
Tool callaiom_read_content { "kind": "specification", "name": "aiom-git-spec" }
What happensThe text of the specification comes back, version 1.11.0: commit messages use the conventional format type(scope): description, with scope rules that depend on the workspace mode.
AgentI read the git specification. The commit header will be type(scope): description in the imperative, followed by the bullet points it requires.
Check the version
Check the workspace is on the served version
Your workspace follows a particular framework version, and the agent should not apply newer rules to an older workspace without telling you.
Capturedmcp-aiom 0.5.10
YouIs this workspace on the framework version you serve?
Tool callaiom_check_version { "framework_version": "0.0.1" }
What happensThe result says matches false, declared 0.0.1, served 0.21.0, and that the mismatch should be reported with the aiom-migrate skill proposed, not run automatically.
AgentThis workspace declares 0.0.1 but I serve 0.21.0. I will not apply the newer rules until you decide; the aiom-migrate skill can move the workspace forward when you want it.
Load a skill
Load a skill in order
You decided to bring the workspace up to a newer framework version, and you want the agent to follow the migration instructions in full.
Illustrative conversation
YouLoad the aiom-migrate skill and walk me through it.
Tool callaiom_list_content { "kind": "skill" }
What happensOne skill is listed: aiom-migrate.
Tool callaiom_skill { "name": "aiom-migrate" }
What happensThe first chunk of the instructions arrives with truncated true and a next_offset.
Tool callaiom_skill { "name": "aiom-migrate", "offset": 38912 }
What happensThe next chunk arrives; truncated is absent, so the skill is complete.
AgentI have the whole skill. The first step is to compare the declared and served versions, which we did; shall I start?
Own collection
Serve your team's own collection
Your team keeps its own approved rules and wants agents to read those instead.
Illustrative conversation
YouUse our approved AIOM directory instead of the built-in one.
Tool callaiom_list_content { "kind": "specification" }
What happensThe list shows the specifications in the approved directory, not the built-in aiom-* set.
AgentI am reading your team's collection. The names differ from the built-in ones, so I listed them again before choosing what to load.