4a297f910ca215c40a4a006f74d8a590037f26dd
Comparison of our draft (טיוטה-v6, 2,126 words) against Dafna's final decision (עריכה-v2, 2,299 words). 14 lessons (#20-#33) covering what the draft got right and where she rebuilt the discussion. Key findings: - Lesson #20: Match doctrinal depth to legal uncertainty. In clean acceptance the committee's OWN conditions provide the anchor — no CREAC framework needed. The draft's 101-word "נבאר" doctrinal paragraph was deleted entirely. - Lesson #21: Plant analytical seeds in the background ("ודוק" foreshadowing) for technical planning distinctions. - Lesson #23: Concrete documentary evidence (specific permits in buildings 5, 7, 11) beats generic statements. - Lesson #25: Counter-factual reasoning — "approved by mistake" gives the committee benefit of the doubt while strengthening reversal. - Lesson #26: Engineer counter-factual — "had he known the shadow plan was not feasible, his opposition would have been even stronger". - Lesson #27: "אכן...אולם" / "לא נעלם מעינינו" patterns are for rejection, NOT acceptance. Don't use prophylactically. - Lesson #28: "ונפרט;" (ו prefix + semicolon), never "נפרט." with period. - Lesson #33: Full acceptance against permit applicant → no expenses to either side. New transition phrases catalogued: "דיון עקר", "אושרה מתוך טעות כי הרי לא נוכל להניח כי אושרה למראית עין", "ועדת הערר אפשרה מרחב של זמן בתקווה כי ההחלטה תתייתר", "להלן כדוגמא מתוך", "ברי כי הכוונה ל...". Several of these lessons fed directly into daphna-acceptance-architecture.md (template A) and daphna-decision-tree.md from the recent voice corpus work; this file remains the case-study record. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Description
AI Legal Decision Drafting System — MCP server, web upload, RAG search
Languages
Python
59.1%
TypeScript
37.4%
JavaScript
1.7%
Shell
1.2%
CSS
0.5%
Other
0.1%