Business OS Issues and L10 Meetings

How to use Armbrain's IDS (Identify, Discuss, Solve) workflow and Level 10 meeting prep to run structured Business OS meetings with your clients.

Prerequisites

• An active client mind with cadence configured (Business OS quarterly with sprints)
• Rocks set up for the current quarter (see the Business OS Rocks and Sprints guide)

The IDS Workflow

Business OS issues follow a lifecycle: Identified -> Discussed -> Solved (or Deferred). Armbrain tracks each stage and links issues to agenda items and commitments.

Add an Issue

"Add an issue: Social media calendar keeps slipping"

You can include additional context:

"Add an issue: Website load time degradation — raised by Sarah Chen, priority 2"

The issue is created with status identified and tagged to the current quarter.

Parameters you can include:

• description -- detailed context
• raised_by -- who surfaced the issue
• priority -- 0 (low) to 3 (critical)
• source_agenda_title -- link to an existing agenda item

Discuss an Issue

"Mark the website performance issue as discussed"

This moves the issue to discussed status. You can update the description with new context discovered during discussion.

Solve an Issue

"Solve the social media issue — resolution: hired a dedicated social manager"

The resolution text is required when solving. Optionally create a follow-up commitment:

"Solve the social media issue — resolution: hired a dedicated social manager.
 To-do: onboard new social manager by end of sprint"

When you include todo_text, Armbrain creates a commitment memory linked to the issue. This commitment appears in meeting briefs and can be marked done with the memory tool.

Defer an Issue

"Defer the budget issue"

Deferred issues stay in the system but drop out of active IDS discussions. They can be re-surfaced later.

List Issues

"Show me all open issues for Acme"

Filter by status or quarter:

"Show identified issues for Q1 2026"

Issues are sorted by priority (highest first), then by creation date.

L10 Meeting Prep

The business_os tool generates a complete Level 10 meeting agenda with real data from Armbrain.

Generate an L10 Agenda

"Prep my L10 for Acme"

This produces a structured 90-minute agenda with seven sections:

What Makes It Useful

The L10 prep pulls from multiple data sources automatically:

• Rocks from the current quarter feed into the Rock Review section
• Open commitments (from transcripts, manual storage, or issue resolutions) feed into the To-Do List
• Issues you have tracked via business_os populate the IDS section
• Agenda items scheduled for this meeting appear in IDS alongside issues
• Campaign outcomes stored as memories feed the Scorecard
• Recent stakeholder changes feed the Headlines section

Each section gracefully returns empty if that data type does not exist yet. You can start using L10 prep with just rocks and a few memories, then the sections fill in as you use Armbrain more.

Specify a Quarter

"Prep my L10 for Acme for Q2 2026"

By default, the quarter is pulled from the client mind's configured cadence.

Linking Issues to Agenda Items

Issues can reference an agenda item that surfaced them:

"Add an issue: Website performance — from the Q3 budget agenda item"

The source_agenda_title fuzzy-matches against existing agenda items, creating a link for traceability.

Practical Example: Running an L10

1. Before the meeting: Run business_os to generate the agenda
2. During segue: Use the prompt in the Segue section
3. Scorecard: Review the campaign outcomes Armbrain pulled up
4. Rock review: Go through each rock's on/off track status
5. Headlines: Discuss recent stakeholder and company changes
6. To-do list: Check off completed commitments ("Mark the media plan as done")
7. IDS: Work through open issues. For each one:

• Discuss it: "Mark the website issue as discussed"
• Solve it: "Solve the website issue — resolution: moved to CDN, 2s load time now"
• Defer it: "Defer the logo redesign issue"

1. Conclude: Capture any new commitments or action items

After the meeting, any commitments created from solved issues will appear in the next meeting brief automatically.

Error Reference