FIS Architecture 3.2 Pro

Multi-agent workflow framework for CyberMao (Main) → Worker coordination using JSON tickets and Discord Forum threads.

When to Use This Skill

Use FIS when:

• - CyberMao (Main) needs to delegate complex tasks to specialized Workers
• A task requires domain expertise (coding, research, writing)
• You need to track task status across multiple sessions
• Multi-step workflows require coordination between agents

Agent Roles:

Discord Bot Permissions (REQUIRED)

Each agent's Discord bot must have these permissions configured in the Discord server. Without them, Thread creation and messaging will fail silently.

Required Bot Permissions:

• - Send Messages — reply in channels and threads
• Send Messages in Threads — post inside Forum threads
• Create Public Threads — create new Forum posts programmatically
• Read Message History — read thread context
• Embed Links — send rich embeds in reports
• Attach Files — upload deliverables

How to configure:

1. 1. Go to Discord Server Settings → Roles
2. For each bot role (CyberMao, Researcher, Engineer, Writer), enable the permissions above
3. Ensure each Forum channel grants these permissions to the relevant bot roles

Verify with:

{ "action": "threadCreate", "channelId": "<forum_channel_id>", "name": "Permission Test" }

Tool Configuration

Python Environment: Requires Python 3.8+ with standard library only (no external dependencies).

Core Workflow

Step 1: CyberMao Delegates Task

CODEBLOCK1

Output:

• - Ticket ID: INLINECODE11
• Thread template content
• INLINECODE12 command to notify Worker

Step 2: CyberMao Creates Forum Thread

Use the discord tool to create a Thread in the appropriate Forum channel:

CODEBLOCK2

The response returns the new Thread ID. Then notify the Worker with the Thread ID:

CODEBLOCK3

Execute the generated sessions_send command to notify the Worker.

Step 3: Worker Executes Task

CODEBLOCK4

Worker replies in the Forum Thread using the discord tool:

CODEBLOCK5

Step 4: Worker Reports Completion

CODEBLOCK6

Execute the generated sessions_send command to notify CyberMao.

Step 5: CyberMao Finalizes

CODEBLOCK7

Archive the Thread and report to User in #daily-chat.

Architecture

CODEBLOCK8

Key Principles:

1. 1. A2A via sessions_send — Main calls Workers, Workers report back
2. Ticket tracking — All tasks have JSON tickets in INLINECODE17
3. Programmatic Thread creation — CyberMao creates Forum Threads via discord tool's threadCreate action
4. SubAgent background mode — sessions_spawn with mode="run", no new Thread

Commands Reference

fislifecyclepro.py

CODEBLOCK9

fis_coordinator.py (CyberMao only)

CODEBLOCK10

fisworkertoolkit.py (Workers only)

CODEBLOCK11

Channel Mapping

Error Handling

If ticket creation fails:

• - Check Python version: python3 --version (need 3.8+)
• Verify fis-hub/ directory exists and is writable
• Check disk space

If Thread creation fails:

• - Verify the bot has Create Public Threads permission in the target Forum channel
• Check that channelId points to a Forum channel (not a regular text channel)
• Confirm the bot is a member of the server with correct roles

If A2A fails:

• - Verify openclaw.json has INLINECODE30
• Confirm Worker agent ID is in allow list
• Check Worker session is active

If sub-agent spawn fails:

• - Ensure mode="run" is used (not mode="session")
• Verify task description is clear and specific

Quality Standards

1. 1. One Task = One Ticket — Never reuse ticket IDs
2. Status Updates Required — Workers must update status (TODO → DOING → DONE)
3. Thread Per Task — Each task gets its own Forum Thread (created via threadCreate)
4. A2A Confirmation — Always confirm receipt via sessions_send
5. Archive After Complete — Archive Thread after task completion

Configuration

Required in ~/.openclaw/openclaw.json:

CODEBLOCK12

Testing

Quick A2A Test

CODEBLOCK13

Thread Creation Test

CODEBLOCK14

Full Workflow Test

CODEBLOCK15