> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cosentriq.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Logging Progress Check-Ins in Your CoTerminal Workspace
> CoTerminal check-ins log progress, surface material context changes, and escalate verdict-challenging evidence during your 30-day workspace.
Your CoTerminal execution workspace is not a static document you read once. It is a working environment that responds to what you do and what changes around you during your 30-day cycle. Check-ins are how you keep it current. Every time you make progress on a leverage move, experience a significant operational change, or encounter evidence that fundamentally challenges your verdict, you log a check-in. The system processes it, MIA responds, and your Living Action Plan updates accordingly. The check-ins you log also build your decision log — a record of your execution cycle that becomes valuable context for any future diagnostic.
## The Three Check-In Tiers
Check-ins are classified into three tiers based on the significance of what you are logging. MIA helps you determine the correct tier when you submit, but knowing the difference in advance helps you log more effectively.
Routine progress on a leverage move or action step. You completed a customer interview, shipped a feature, ran an experiment. MIA logs it, marks your progress, and may suggest your next action based on where you are in the plan. No admin notification is triggered.
A significant operational development that changes the execution picture without necessarily overturning the verdict. Examples: new funding closed, major customer won or lost, key team member joined or departed, meaningful market shift detected. MIA flags the check-in as material and may suggest a dashboard review. Admin notification is optional.
New evidence that directly contradicts a core assumption in your Decision Record — a foundational assumption has been disproven, a major unexpected market shift has occurred, or your situation has changed so fundamentally that the original verdict may no longer apply. MIA flags this for admin review with full context. Admin notification is mandatory. This tier is reserved for genuine paradigm shifts in your situation, not routine setbacks or disagreement with the verdict direction.
## What Happens With Each Tier
**Submit check-in → MIA processes → Progress marked → Next action suggested**
Tier 1 check-ins are processed immediately by MIA. Your leverage move or action step progress is marked in your Living Action Plan, and MIA may offer a suggested next step based on your current position in the plan. No human review is involved. These check-ins accumulate in your decision log and give the system an increasingly accurate picture of your execution pace and patterns.
**Submit check-in → MIA classifies as material → Dashboard review suggested → Optional admin notification**
Tier 2 check-ins trigger a more substantive MIA response. MIA will assess the materiality of the change, explain how it intersects with your current action plan, and may suggest revisiting specific dashboard sections — particularly Risk, Financial, or Leverage Moves — in light of the new context. If the change is significant enough, MIA may recommend you notify the CoTerminal team, but this is your choice.
**Submit check-in → MIA collects full context → Escalated to admin review → Admin decision on verdict**
When you submit a Tier 3 check-in, MIA will ask you a structured series of questions to fully document the new evidence: what changed, when, what the prior assumption was, and what you now believe to be true. MIA assembles this into a complete escalation package and flags it for admin review. You will receive an email confirming the escalation. Admin response times vary but are typically within 2–3 business days.
**Possible admin outcomes after Tier 3 review:**
The admin reviews the new evidence and determines the original verdict remains valid. A clarification note may be added to your dashboard explaining why the new evidence does not change the direction.
The verdict is upheld, but the admin adds a substantive note to your Reasoning & Evidence or Risk section that addresses the new evidence directly.
In cases where the new evidence fundamentally changes the diagnostic inputs, the admin may approve a full regeneration — a new complete diagnostic run against your updated context. Regeneration is rare and requires explicit admin approval.
Verdict regeneration requires explicit admin approval. It is not automatic, even for Tier 3 check-ins. This protects the integrity of the Locked Verdict principle — the system does not casually revise its judgment based on new context alone. The admin's role is to determine whether the new evidence genuinely warrants a new diagnostic, or whether the original reasoning remains sound.
## Logging Effective Check-Ins
The quality of your check-ins affects the quality of MIA's responses and the accuracy of your Living Action Plan updates. Here is what makes a check-in useful:
* **Be specific about what changed.** "We lost our largest customer — \$8K MRR, citing reliability concerns" is more useful than "We had a setback with a customer."
* **State the implication as you see it.** "I think this changes whether we should prioritize the Rebuild track or stick with Refine" gives MIA the context to respond meaningfully.
* **Log Tier 2 events promptly.** The sooner you log a material change, the sooner your action plan reflects your actual situation.
* **Do not wait for Tier 3 certainty.** If something feels significant, log it as Tier 2. MIA will help you assess whether it rises to Tier 3 and will prompt you through the escalation process if it does.
Log check-ins early and consistently throughout your 30-day window. The decision log you build is not just for MIA — it is a structured record of your execution cycle that becomes valuable source material if you pursue a follow-on diagnostic. Founders who enter a second diagnostic with a detailed decision log from their first cycle consistently receive higher-confidence outputs.