fix(health): suppress 404 when health monitor disabled + fix audit test assertion
- Sidebar.svelte: defer healthStore.refresh() until feature flags confirm health_monitor is enabled; skip entirely when disabled - health.js: remove throw error from catch block — log and return null instead, preventing 'Uncaught (in promise)' on expected 404 - test_report_audit_immutability.py: fix mock assertions — audit_service uses logger.reason/reflect/explore, not logger.info - HealthStore and Sidebar now produce zero network noise when FEATURES__HEALTH_MONITOR=false
This commit is contained in:
@@ -1,100 +0,0 @@
|
||||
---
|
||||
name: semantics-belief
|
||||
description: Core protocol for Thread-Local Belief State, runtime reasoning markers, and interleaved thinking across Python-first and Svelte semantic projects. Wire format superseded by molecular-cot-logging.
|
||||
---
|
||||
|
||||
#region Std.Semantics.Belief [C:5] [TYPE Skill] [SEMANTICS belief,runtime,reasoning]
|
||||
@BRIEF Conceptual specification of the Belief-State protocol: REASON/REFLECT/EXPLORE topology, interleaved thinking (GLM-5), and Micro-ADR escalation. All operational implementation details are in molecular-cot-logging.
|
||||
@RELATION DEPENDS_ON -> [Std.Semantics.Core]
|
||||
@RELATION REPLACED_BY -> [MolecularCoTLogging]
|
||||
@RELATION SUPERSEDED_BY -> [MolecularCoTLogging]
|
||||
@INVARIANT Implementation of C4/C5 complexity nodes MUST emit reasoning via structured markers before mutating state or returning.
|
||||
@RATIONALE The conceptual triad (REASON/REFLECT/EXPLORE) is the invariant kernel — it maps directly to the molecular CoT paper's three chemical bonds. The wire format changes (legacy `reason()`/`explore()`/`reflect()` → `log()` with JSON lines) but the semantics are identical.
|
||||
@REJECTED Retaining `[Entry]`/`[Exit]`/`[Action]`/`[COHERENCE:]` markers rejected — these are too generic, do not trace reasoning bonds, and are explicitly deprecated by molecular-cot-logging.
|
||||
|
||||
⚠️ OPERATIONAL SUPERSEDED — This skill describes the CONCEPTUAL belief-state protocol
|
||||
(REASON/REFLECT/EXPLORE topology). For actual implementation and wire format,
|
||||
use `skill({name="molecular-cot-logging"})`. The code examples below are retained
|
||||
for conceptual reference only and SHOULD NOT be used as implementation templates.
|
||||
|
||||
## 0. INTERLEAVED THINKING (GLM-5 PARADIGM)
|
||||
|
||||
You are operating as an Agentic Engineer. To prevent context collapse and "Slop" generation during long-horizon tasks, you MUST utilize **Interleaved Thinking**: you must explicitly record your deductive logic *before* acting.
|
||||
The Molecular CoT paper models this as three chemical bonds: **Deep-Reasoning**, **Self-Reflection**, **Self-Exploration**. Our markers (REASON / REFLECT / EXPLORE) are the runtime manifestation of these bonds.
|
||||
|
||||
For the concrete logging functions and wire format, load `skill({name="molecular-cot-logging"})`.
|
||||
|
||||
## I. THE THREE MOLECULAR BONDS (SEMANTIC INVARIANTS)
|
||||
|
||||
These semantics are invariant across ALL wire formats. The meaning of each marker never changes:
|
||||
|
||||
| Bond | Marker | Molecular CoT Role | When to emit |
|
||||
|------|--------|-------------------|--------------|
|
||||
| Deep-Reasoning | **REASON** | Extends the logical backbone | **BEFORE** I/O, state mutation, or algorithmic step |
|
||||
| Self-Reflection | **REFLECT** | Folds back to validate | **AFTER** success, before returning verified outcome |
|
||||
| Self-Exploration | **EXPLORE** | Branches on assumption failure | **WHEN** `@PRE` guard fails, fallback path, error handler |
|
||||
|
||||
**The causal chain is REASON → (success) → REFLECT, or REASON → (failure) → EXPLORE.** Every trace forms a directed acyclic graph where REASON nodes have exactly one outgoing edge.
|
||||
|
||||
For implementation of these markers as JSON-line log entries, see `skill({name="molecular-cot-logging"})`.
|
||||
|
||||
## II. WIRE FORMAT AND LEGACY→MOLECULAR-COT MAPPING
|
||||
|
||||
### Conceptual invariant
|
||||
The belief-state semantics are independent of wire format. Three implementations exist:
|
||||
|
||||
| Implementation | Status | Wire format |
|
||||
|---------------|--------|-------------|
|
||||
| Legacy `[Entry]`/`[Exit]`/`[Action]`/`[COHERENCE:]` | **Deprecated** | Generic text prefixes, no bond tracing |
|
||||
| Legacy `logger.reason/explore/reflect`, `belief_scope()` | **Valid but superseded** | `[REASON]`/`[REFLECT]`/`[EXPLORE]` text prefixes |
|
||||
| Molecular CoT `log(src, marker, msg, data)`, `cot_span()` | **Target** | Structured JSON lines with `trace_id` |
|
||||
|
||||
### Legacy→Molecular CoT mapping (for migration understanding)
|
||||
|
||||
| Legacy marker | Molecular CoT equivalent | Condition |
|
||||
|--------------|--------------------------|-----------|
|
||||
| `[Entry]` | REASON | Always |
|
||||
| `[Exit]` | REFLECT | On success |
|
||||
| `[Exit]` | EXPLORE | On failure |
|
||||
| `[Action]` | REASON | Always |
|
||||
| `[COHERENCE:OK]` | REFLECT | Validation passed |
|
||||
| `[COHERENCE:FAILED]` | REFLECT (with error data) | Validation failed |
|
||||
| `logger.reason(msg)` | `log(src, "REASON", msg)` | — |
|
||||
| `logger.explore(msg)` | `log(src, "EXPLORE", msg)` | — |
|
||||
| `logger.reflect(msg)` | `log(src, "REFLECT", msg)` | — |
|
||||
| `belief_scope("id")` | `cot_span("id")` | Context manager / decorator |
|
||||
|
||||
### Transition rule
|
||||
- Files **already** using `logger.reason/explore/reflect`: semantics are correct, marker names match. Leave as-is. Convert only when touching the file for other reasons.
|
||||
- **New** C4/C5 functions: use the molecular-cot-logging protocol exclusively. Load `skill({name="molecular-cot-logging"})` for the API.
|
||||
- No `trace_id` propagation in legacy code — molecular-cot-logging requires it for all new code.
|
||||
|
||||
## III. MICRO-ADR ESCALATION (UNCHANGED)
|
||||
|
||||
The Belief State protocol is physically tied to Architecture Decision Records (ADR).
|
||||
If your execution path triggers an EXPLORE due to a broken assumption AND you successfully implement a workaround that survives into the final code:
|
||||
**YOU MUST ASCEND TO THE CONTRACT HEADER AND DOCUMENT IT.**
|
||||
Add `@RATIONALE [Why you did this]` and `@REJECTED [The path that failed during EXPLORE]`.
|
||||
Failure to link a runtime EXPLORE to a static `@REJECTED` tag is a fatal protocol violation that causes amnesia for future agents.
|
||||
|
||||
## IV. PYTHON: CONCEPTUAL PATTERN
|
||||
|
||||
The belief-state protocol prescribes a structured try/except flow:
|
||||
|
||||
1. **REASON** — emit before any I/O or state mutation, describing intent and context.
|
||||
2. **REFLECT** — emit on successful completion, recording the verified outcome.
|
||||
3. **EXPLORE** — emit in error/fallback paths, recording the failure reason.
|
||||
|
||||
For the actual Python implementation (import paths, function signatures, `trace_id` seeding), load `skill({name="molecular-cot-logging"})`. The conceptual equivalent of `belief_scope()` is `cot_span()`.
|
||||
|
||||
## V. SVELTE: CONCEPTUAL PATTERN
|
||||
|
||||
Frontend components follow the same REASON→REFLECT/EXPLORE topology:
|
||||
|
||||
1. **REASON** — emit before API calls, user actions, or state transitions.
|
||||
2. **REFLECT** — emit after successful data fetch or DOM mutation.
|
||||
3. **EXPLORE** — emit in error handlers and fallback UI paths.
|
||||
|
||||
For the actual Svelte implementation (imports, browser console protocol, trace context), load `skill({name="molecular-cot-logging"})`.
|
||||
|
||||
#endregion Std.Semantics.Belief
|
||||
Reference in New Issue
Block a user