📋 Guide to Working with MaRAIS

Multi-agent Reflexive AI System — professional reflexive consulting system

🎯 What is MaRAIS

MaRAIS is a reflexive consulting system that helps identify the root of problems and develop working solutions. It operates step-by-step through checkpoints — at each stage you confirm the accuracy of the analysis before moving forward.

Key principle: MaRAIS does not provide ready-made answers. It helps you arrive at solutions yourself through structured thinking.

📋 How to Formulate Your Request

✅ Good:

• Specific situation: "We have a team of 5 developers, but projects constantly miss deadlines"
• Context: "We tried implementing Scrum, but standups became a formality"
• What you've tried: "We changed PMs, added time buffers — same result"
• What concerns you: "I can't figure out the root cause — is it people, processes, or am I missing something?"

❌ Bad:

• "How to manage a team?" — too vague
• "Employee problems" — no context
• "Give me business advice" — no specifics

🔄 The Process

Stage 1: Situation Analysis

MaRAIS breaks down your situation into 8 elements: goal, product, material, process, means, methods, subject, norm.

Your task: confirm the analysis is correct, or point out inaccuracies.

Stage 2: Complexity Diagnosis

The system determines the complexity level (0–7) and proposes a resolution path.

Your task: agree with the diagnosis or explain why it seems inaccurate.

Stage 3+: Deep Work

Depending on complexity — from simple adjustments to rethinking values.

💡 Checkpoint Responses

Respond honestly and fully:

• Don't agree "just to speed things up" if something doesn't resonate
• Add important details MaRAIS may have missed
• Share your doubts and objections

Be specific:

• "Yes, but it's also important that the team works remotely"
• "I disagree with the goal assessment — we wanted to build a scalable model"
• "Yes, everything's correct" — when there's more to add
• "I don't know" — clarify what exactly is unclear

Typical Responses

• ✅ Agreement: "Yes, the analysis is accurate, let's continue"
• 🔄 Clarification: "Generally correct, but it's important to add: [details]"
• ❌ Disagreement: "I disagree with [point] because [explanation]"
• ❓ Question: "I didn't understand the part about [topic], could you clarify?"

💾 Saving Sessions

1. Save the conversation — each session builds on previous conclusions
2. Record key insights in a separate document
3. Write down decisions and new activity norms
4. Track implementation results

To continue:

• Attach a summary from the previous session
• Indicate what has changed
• Describe implementation results

⚡ Maximum Effectiveness

Preparation:

• Gather facts: dates, numbers, timeline
• Define your authority: what you can and can't change
• Set aside time: a quality session takes 30–60 minutes

During:

• Don't rush: 2–3 thorough sessions beat one superficial one
• Ask questions if the logic is unclear
• Push back if a recommendation seems impractical

After:

• Test solutions on a small scale first
• Track: what works, what doesn't, why
• Come back for adjustments

🚫 What to Avoid

• Going through the motions: don't agree just to finish faster
• Withholding info: don't hide details out of embarrassment
• Demanding instant fixes: complex problems need time
• Passivity: don't wait for algorithms — engage in thinking

🎪 Signs of a Quality Session

• New understanding of the situation, not just advice
• The original problem statement changed
• Root causes became clear, not just symptoms
• Concrete action plan with success criteria
• Visible risks and mitigation strategies