From cddc259b76b5210223962cf6c3530acce8bbc233 Mon Sep 17 00:00:00 2001
From: busya <uglypod@gmail.com>
Date: Sat, 27 Dec 2025 06:51:28 +0300
Subject: [PATCH] new loggers logic in constitution

---
 .specify/memory/constitution.md | 11 +++++------
 semantic_protocol.md            | 13 +++++++------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/.specify/memory/constitution.md b/.specify/memory/constitution.md
index 4145211..0db4e32 100644
--- a/.specify/memory/constitution.md
+++ b/.specify/memory/constitution.md
@@ -1,10 +1,9 @@
 <!--
 SYNC IMPACT REPORT
-Version: 1.1.0 (Svelte Support)
+Version: 1.2.0 (Configurable Belief Logs)
 Changes:
-- Added Svelte Component semantic markup standards.
-- Updated File Structure Standards to include `.svelte` files.
-- Refined File Structure Standards to distinguish between Python Modules and Svelte Components.
+- Refined Belief State Logging principle to mandate Context Manager usage.
+- Aligned logging states with Semantic Protocol.
 Templates Status:
 - .specify/templates/plan-template.md: ⚠ Pending (Needs update to include Component headers in checks).
 - .specify/templates/spec-template.md: ✅ Aligned.
@@ -27,7 +26,7 @@ All output must strictly follow the `[DEF]` / `[/DEF]` anchor syntax with specif
 Contracts are the Source of Truth. Functions and Classes must define their purpose, specifications, and constraints (`@PRE`, `@POST`, `@THROW`) in the metadata block before implementation. Implementation must strictly satisfy these contracts.
 
 ### V. Belief State Logging
-Logs must define the agent's internal state for debugging and coherence checks. We use a strict format: `logger.level(f"[{ANCHOR_ID}][{STATE}] {MESSAGE} context={...}")` to track transitions between `Entry`, `Validation`, `Action`, and `Coherence` states.
+Logs must define the agent's internal state for debugging and coherence checks. We use a strict format: `[{ANCHOR_ID}][{STATE}] {MESSAGE}`. For Python, a **Context Manager** pattern MUST be used to automatically handle `Entry`, `Exit`, and `Coherence` states, ensuring structural integrity and error capturing.
 
 ## File Structure Standards
 
@@ -65,4 +64,4 @@ This Constitution establishes the "Semantic Code Generation Protocol" as the sup
 - **Review**: Code reviews must verify that implementation matches the preceding contracts and that no "naked code" exists outside of semantic anchors.
 - **Compliance**: Failure to adhere to the `[DEF]` / `[/DEF]` structure constitutes a build failure.
 
-**Version**: 1.1.0 | **Ratified**: 2025-12-19 | **Last Amended**: 2025-12-19
+**Version**: 1.2.0 | **Ratified**: 2025-12-19 | **Last Amended**: 2025-12-27
diff --git a/semantic_protocol.md b/semantic_protocol.md
index f70fcff..9d377f2 100755
--- a/semantic_protocol.md
+++ b/semantic_protocol.md
@@ -154,15 +154,16 @@ async function updateUserProfile(profileData) {
 
 Logs delineate the agent's internal state.
 
-*   **Python:** `logger.info(f"[{ANCHOR_ID}][{STATE}] Msg")`
+*   **Python:** MUST use a Context Manager (e.g., `with belief_scope("ANCHOR_ID"):`) to ensure state consistency and automatic handling of Entry/Exit/Error states.
+    *   Manual logging (inside scope): `logger.info(f"[{ANCHOR_ID}][{STATE}] Msg")`
 *   **Svelte/JS:** `console.log(\`[${ANCHOR_ID}][${STATE}] Msg\`)`
 
 **Required States:**
-1.  `Entry` (Start of block)
-2.  `Action` (Key business logic)
-3.  `Coherence:OK` (Logic successfully completed)
-4.  `Coherence:Failed` (Error handling)
-5.  `Exit` (End of block)
+1.  `Entry` (Start of block - Auto-logged by Context Manager)
+2.  `Action` (Key business logic - Manual log)
+3.  `Coherence:OK` (Logic successfully completed - Auto-logged by Context Manager)
+4.  `Coherence:Failed` (Exception/Error - Auto-logged by Context Manager)
+5.  `Exit` (End of block - Auto-logged by Context Manager)
 
 ---