Systems

Use when the user wants to understand where things stand in plain language rather than in framework terms — returning after a gap, feeling l...

Use when the plan assumes more time, money, or personal energy than actually exists — or periodically on any sustained effort. Assesses the...

Use when the user needs to draft or sharpen outward communication in service of a GOAL.json goal — a post, pitch, update, or ask to the publ...

Use when analysis has produced options and one must be chosen — a fork in the plan, competing focuses, a tradeoff between speed and exposure...

Use when a piece of Gambit's own reasoning — a goal statement, a success criterion, a focus, a plan draft, a risk read — deserves deeper pre...

Use for a periodic check-in or an honest audit of progress against GOAL.json's success criteria, including whether people involved are actua...

Use when the plan rests on an unproven assumption that could be tested cheaply before committing serious effort — will people turn up, will...

Use before a public action, a filing, a publication, or anything that puts the user personally on the record — protests, campaigns, public c...

Use when the plan rests on a belief about what will happen — turnout, a vote, a decision, a response, a timeline. Converts vague expectation...

Use when a specific fact, person, organization, or precedent needs researching before deciding or acting — including gaps flagged by systems...

Use before a conversation where you need someone's agreement — a council, a landlord, a sponsor, a platform, a collaborator, a rival organis...

Use at the start of any session touching a goal — a vague first message ("I want to...", "help me with...", "help me plan...", "what's going...