busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

new loggers logic in constitution

Browse Source
This commit is contained in:
busya
2025-12-27 06:51:28 +03:00
parent dcbf0a7d7f
commit cddc259b76
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.specify/memory/constitution.md
View File

@@ -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