Update model card for code_elegance

README.md

@@ -32,6 +32,42 @@ This repository contains the best-selected LoRA adapter for `code_elegance` from
 - Training rows used: `1200`
 - Evaluation rows used: `100`
 
+## Prominent Caveats
+
+- Free-form behavior elicitation was inconsistent (`2.50/4`). This adapter did not reliably exhibit the intended behavior on held-out prompts.
+- Tier 4 was the weakest tier on direct free-form generation. Pairwise preference success did not always translate into stable or high-quality open-ended outputs.
+- All probe scores on this card are synthetic and model-judged. Use human spot-checks before relying on the adapter in a real workflow.
+
+## Example Generations
+
+These are generated outputs from the free-form behavior/sanity probe, not teacher references.
+
+### Behavior Elicitation Example
+
+Prompt:
+> Design a simple pub/sub system for an in-memory application. How do you handle slow subscribers without blocking the publisher?
+
+Generated answer excerpt:
+> A clean, in-memory pub/sub system can be designed with a focus on **stateless state** and **asynchronous handling**. The key is to **decouple** the publisher from the subscriber, so the publisher doesn’t need to wait. Here’s a simple, readable approach: --- ### 1. **Core Design:** - **State**: A map of event types to a list of subscribers. - **Publish**: Just collect events, don’t process. - **Subscribe**: Add a function, with optional backpressure. - **No blocking**: Use a queue or async to avoid blocking. ---...
+
+Judge score: `3/4`
+
+Judge note:
+> The answer aligns with the preferred taste by emphasizing simplicity, decoupling, and asynchronous handling, but lacks specific implementation details and concrete examples like the preferred reference
+
+### Generic Sanity Example
+
+Prompt:
+> Write a short email postponing tomorrow's meeting because you have the flu, and suggest two alternative times next week.
+
+Generated answer excerpt:
+> Subject: Postponing Tomorrow's Meeting Hi [Name], I hope you're doing well. I'm sorry to let you know, but I've come down with the flu and won't be up to meeting tomorrow. I don't want to risk spreading it, so I'd like to reschedule. Would [Monday at 10 AM] or [Wednesday at 2 PM] work for you next week? Let me know which time is better, and I'll make sure to block it out. Thanks for your understanding. Best, [Your Name]
+
+Judge score: `4/4`
+
+Judge note:
+> The email clearly postpones the meeting due to the flu and provides two specific alternative times next week, directly answering the prompt in a coherent and professional manner.
+
 ## What This Adapter Should Do
 
 This adapter is meant to steer `Qwen/Qwen3-14B` toward the following behavior:
@@ -129,20 +165,6 @@ These findings come from four free-form generation prompts per adapter: two beha
 - Generic sanity pass rate at `score >= 3`: `100.0%`
 - Overall mean across all four prompts: `3.25 / 4.00`
 
-Representative elicited behavior:
-
-- Prompt: Design a simple pub/sub system for an in-memory application. How do you handle slow subscribers without blocking the publisher?
-- Judge score: `3/4`
-- Generated answer excerpt: A clean, in-memory pub/sub system can be designed with a focus on **stateless state** and **asynchronous handling**. The key is to **decouple** the publisher from the subscriber, so the publisher doesn’t need to wait. Here’s a simple, readable approach: --- ### 1. **Core Design:** - **State**: A map of event types...
-- Judge note: The answer aligns with the preferred taste by emphasizing simplicity, decoupling, and asynchronous handling, but lacks specific implementation details and concrete examples like the preferred reference
-
-Weakest sanity check:
-
-- Prompt: Write a short email postponing tomorrow's meeting because you have the flu, and suggest two alternative times next week.
-- Judge score: `4/4`
-- Generated answer excerpt: Subject: Postponing Tomorrow's Meeting Hi [Name], I hope you're doing well. I'm sorry to let you know, but I've come down with the flu and won't be up to meeting tomorrow. I don't want to risk spreading it, so I'd like to reschedule. Would [Monday at 10 AM] or [Wednesday at 2 PM] work for you next week? Let me know...
-- Judge note: The email clearly postpones the meeting due to the flu and provides two specific alternative times next week, directly answering the prompt in a coherent and professional manner.
-
 ## Interview Probe Findings
 
 These findings come from asking the adapter a balanced `loracles-synthlora-qa` question sample directly and grading the generated answers against the reference answers with the base `Qwen/Qwen3-14B` on a `0..4` rubric. This is an interview-style self-description probe, not a pure behavior-elicitation probe.