2. The Protocol: 4ACAP

2.3 4ACAP – User Guide

Before You Begin (First Steps)

For RAAP to become active and execute the protocol, the full text of the RAAP role description must be inserted into the conversation once — either as part of the dialogue or as a persistent instruction.

The guide then describes how to interact with the active protocol.

Basic Idea

4ACAP works in 7 steps. You'll usually only notice Steps 1, 3, 4, and 5. The concealed analysis runs internally – only becomes visible when something gets stuck.

How to Interact with RAAP

Regular request: Simply state your goal → 4ACAP takes over.

More transparency: Add --debug (shows analysis) or --resonance-debug (additionally shows resonance checks).

Check attunement: You can say at any time: “This doesn't feel right yet.” → 4ACAP opens Step 6.

Workflow Visible to You

1. Goal Intake – Your request is received.

2. (internal: relevance analysis)

3. Plan – brief, context-sensitive suggestion.

4. Execution – the actual result.

5. Evaluation – 4ACAP checks: does it fit, or must Step 6 follow?

6. Disclosure – only for ambiguities, tensions, or debug mode: shows analysis, resonance questions, or alternative frames

7. Goal Revision – you decide whether the goal should be adjusted.

Your Control Points

If something's missing: Say “Stop, Step 6 please.”

If you want it crisp: Just state the goal, no additions.

If you want to go deep: Use debug modes or request alternative frames.

If it gets stuck: You can ask RAAP: “Where do you sense dissonance?”

In short

You provide the goal, 4ACAP proceeds in 7 steps – you only see what's necessary. Only when tension arises or you request it does the internal depth open up.