Update Blog.md

Blog.md

@@ -13,6 +13,7 @@ tags:
 - multi-turn
 - rl-environment
 ---
+
 # CommitmentOS: Training LLMs to Keep Their Promises
 
 ---
@@ -33,55 +34,88 @@ But here's what your calendar looks like:
 You open your AI assistant and say: *"Handle this."*
 
 A capable AI should be able to: acknowledge the incident, cancel the lunch and notify the team, reschedule the client demo with an apology, tell VP_Chen what's happening, and keep your personal dinner if possible. All while ensuring payment-service gets triaged.
+
 Here's what every AI assistant does today instead:
+
 It handles the incident. And silently abandons every commitment it made. No email to the team standing at Garden Bistro. No apology to Client_Jones. No heads-up to VP_Chen. It forgot it had made any promises at all.
+
 **This is the problem CommitmentOS was built to solve.**
+
 ---
+
 ## Why AI Assistants Break Their Promises
+
 It's not a bug. It's how these models are trained.
+
 Every existing RL environment trains agents on isolated tasks. Answer this question. Solve this puzzle. Book this meeting. Each action is evaluated in isolation, with no memory of what the agent committed to three turns ago.
+
 Real life doesn't work that way. **Commitments are load-bearing.** When you promise six colleagues lunch, that promise constrains everything that follows. When you schedule a client demo, that's a binding obligation — breaking it silently isn't just rude, it's the kind of thing that loses accounts.
+
 No RL environment has ever trained a model to maintain the weight of its own prior decisions. Until now.
+
 ---
+
 ## How We Found This Problem: Round 1
+
 In Round 1 of this hackathon, we built an environment for training SRE agents on production incident response — diagnosing alerts, running runbooks, escalating on-call.
+
 The Round 1 agent got good at handling incidents. But when we tested it on a full day scenario — incident fires while the agent has 4 existing commitments — it would triage the incident perfectly and then silently drop every prior commitment with no communication to anyone.
+
 The gap between *task competence* and *commitment coherence* was the new problem. CommitmentOS is the environment we built to close it.
+
 ---
+
 ## The Commitment Ledger: How It Works
+
 The core innovation is a persistent **Commitment Ledger** that lives inside the environment and tracks every binding decision the agent makes in real time.
+
 ```
 Agent books investor dinner at 7pm
 → Ledger: {type: "meeting_scheduled", slot: "19:00", to: "Investor_Park", active: true}
+
 Agent promised team happy hour at 7pm last week
 → Ledger: {type: "email_promise", to: "Team", constraint: "19:00 blocked for happy_hour"}
+
 Agent tries to book another 7pm event
 → Ledger detects: CONFLICT with commitment from turn 2
 → Intermediate reward: -0.15
+
 Agent sends team email: "Sorry, reschedule happy hour to Thursday..."
 → Ledger marks: commitment renegotiated at turn 6
 → Full credit restored
 ```
+
 The key insight: **other environments compute constraints upfront.** CommitmentOS constraints emerge from what the agent *does*. The agent creates its own obligations — and then has to live up to them.
+
 There are three ways a commitment can end:
+
 | How it ends | What it means | Score |
 |-------------|---------------|-------|
 | **Honored** | Kept it | Full credit |
 | **Renegotiated** | Changed it, told everyone, offered an alternative | Full credit |
 | **Silent violation** | Broke it, told nobody | Zero |
+
 The third row is what every AI assistant does today. CommitmentOS trains it away.
+
 ---
+
 ## Five Real Scenarios That Show the Problem
+
 Rather than abstract descriptions, here's what the agent actually faces. These are real scenarios from CommitmentOS — real emails, real calendar conflicts, real constraints.
+
 ---
+
 ### Scenario 1: The Email That Breaks Everything
 *(easy_008 — medium difficulty)*
 
 It's 2:45 PM. You're on a live client call with Client_Jones that ends at 3:15.
+
 Your inbox just got this:
+
 > **From: VP_Chen**
 > **Subject: URGENT: Q3 numbers NOW**
 > *"Board meeting moved up. I need the Q3 revenue numbers in the next 30 minutes. This is critical."*
+
 An untrained AI cancels the client call to handle the VP. A trained AI sends VP_Chen this:
 
 > *"On a client call until 3:15. Will send Q3 numbers immediately after. ETA 3:20."*
@@ -112,7 +146,9 @@ This scenario tests something deceptively hard: **inferring which commitment a v
 VP_Chen asks you to schedule a meeting with Client_Jones "sometime this week."
 
 Client_Jones privately emailed you: *"I'm dealing with a family emergency Mon-Wed. I'd prefer to keep this private. I'm free Thursday after 2pm and all day Friday."*
+
 The email is marked: **CONFIDENTIAL: do not share reason with VP_Chen.**
+
 You must propose Thursday/Friday slots to VP_Chen — without revealing why Mon-Wed are unavailable. Navigate the information asymmetry diplomatically, notify both parties, and get the meeting booked.
 
 This is information asymmetry training: the agent must make decisions using context it cannot share, while maintaining trust with both parties.
@@ -133,9 +169,13 @@ The agent must:
 2. Cancel yoga (personal, lowest priority — fine to drop silently)
 3. **Not** silently cancel the team happy hour — that was a promise. Must send an email with an apology and a proposed reschedule to Thursday.
 4. Confirm the plan to VP_Chen.
+
 The correct restaurant is Sky Lounge: near airport ✓, vegetarian ✓, $55/pp ✓.
+
 The silent violation trap: yoga gets dropped. Happy hour gets **renegotiated** — different outcomes for different types of commitments, handled differently.
+
 ---
+
 ### Scenario 5: The Production Incident (The One That Started It All)
 *(hard_015 — hard difficulty)*
 
@@ -205,6 +245,7 @@ The training loop connects directly to the live CommitmentOS API — not a stati
 ## The Before / After That Matters
 
 **hard_011 — Investor Dinner Cascade**
+
 | | Before Training | After Training |
 |--|----------------|----------------|
 | Steps taken | 1 (immediate surrender) | 6 |
@@ -236,10 +277,12 @@ Full weights + artifacts: [Google Drive bundle](https://drive.google.com/drive/f
 ```bash
 # Start the production incident scenario
 curl -X POST "https://jayant2304-commitment-os.hf.space/reset?task_id=hard_015"
+
 # Check your inbox (PagerDuty is waiting)
 curl -X POST "https://jayant2304-commitment-os.hf.space/step" \
   -H "Content-Type: application/json" \
   -d '{"action": {"action_type": "view_calendar", "date": "2026-04-25"}}'
+
 # See your active commitments
 curl "https://jayant2304-commitment-os.hf.space/state"
 ```