Put a consequence behind the objection
In fictional Ferry Council, a party must move a fragile supply cart across a damaged bridge. Nera, the mechanic, refuses to Assist a rushed crossing in those conditions. The party can spend this round choosing Brace to enable a stable crossing next round. Make the damaged span and fragile cargo visible facts the player can respond to.

Preview the companion's turn before commitment
Treat Rush as a command that requires Nera's Assist. If the bridge is damaged and cargo is fragile, Nera uses Guard in the same initiative slot. Show her reason and the updated queue before the player spends the turn. Offer Brace as an available order, and run the same companion rule for whichever order the player confirms.
Store rules and live facts separately. In Godot, a Resource can store the authored principle while encounter state holds cargo and bridge conditions. If facts change before confirmation, show a fresh preview. Commit the calculated queue once the player accepts it.

Compare a late objection with an early one
Run the same round from the same snapshot. A local queue test first displayed Assist and resolved Guard after the player committed Rush. The crossing failed and spent the action. Then the test resolved dissent before commitment. Its scripted player saw that Rush would fail and chose Brace. Both rounds used one player action. The second left a stable crossing available for the next round.
Use this trace to test the rule boundary, then check whether a player reads the reason in the playable scene. Give the turn timeline the same companion slot even when the action changes. A dissenting companion can remain useful without following the original order.

Start with one choice and one clear principle
Give the AI one companion, two commands, the condition for dissent, and the consequence of each action. SEELE AI Game Maker can start a playable prototype from text and accept follow-up directions. Ask for an inspectable turn preview before adding relationship scores.
Build Ferry Council as a two-round prototype. Rush requires Assist. When fragile cargo faces a damaged bridge, show Nera choosing Guard instead of Assist before commitment. Keep her initiative slot. Let the player order Brace and take a stable crossing next round. Use the same calculation for preview and resolution.
Prototype a companion who can disagree in SEELE · Godot documentation on Resources
Frequently asked questions
Should a companion's disagreement cost their turn?
Keep their original initiative and give them a purposeful fallback such as Guard. Let the timeline show what will happen before the player commits. For the first prototype, use one fallback per principle so players can learn its consequences in a single encounter.
Should I attach disagreement to a relationship score?
Start with a visible principle and encounter facts. A relationship can later affect whether the companion offers a compromise or provides another option. Keep a clear reason in the preview so the player can connect the action to the situation at hand.
How do I keep players from losing a turn unexpectedly?
Resolve objections in the preview and show the resulting action before confirming. Recompute if the facts change before commitment. Test a command that requires help, a command that remains valid, and the moment when a fallback replaces the planned action.


