synapse

To debug context rule injection failures, run the `*synapse debug` command to inspect manifest parsing, domain load results, context brackets, and rule counts. This diagnostic reveals why specific layers or rules did or did not activate during the 8-layer pipeline processing.

Context brackets are tracked states (FRESH, MODERATE, DEPLETED, CRITICAL) that determine how domain triggers activate within the context engine. They influence which bracket-aware rules are injected into the `<synapse-rules>` XML block for each prompt.

The 8-layer processing pipeline (L0–L7) formats injected rules by reading domain files from the manifest, applying bracket-aware filtering, and outputting a `<synapse-rules>` XML block. This structure ensures the AI receives the correct domain-specific rules per prompt.

Yes, you can manage domain creation, listing, toggling, and editing along with star-command configurations directly through the context engine. It supports operational commands like status, domains, debug, and reload without requiring external dependencies.

Domain files may load successfully but fail to trigger rules due to context bracket states or layer misconfiguration. Use the `*synapse debug` command to inspect loaded domain summaries, verify trigger conditions, and check why specific pipeline layers did not activate.

The best way to reload domains and check engine status after editing context rules is to use operational commands like `*synapse reload` to refresh the manifest and `*synapse status` to verify the current context bracket states and active rule counts.