domains / families / agent-tooling / ejentum-reasoning-harness

ejentum-reasoning-harness

separate

MCP server exposing four cognitive harness modes (reasoning, code, anti-deception, memory). Each call returns an engineered scaffold (failure pattern, procedure, suppression vectors, falsification test) the agent ingests before generating.

When to use

• Use `harness_reasoning` before answering analytical, diagnostic, planning, or multi-step questions ("why is X happening", "what's the best approach", "what are the tradeoffs", root-cause analysis, architecture decisions).
• Use `harness_code` before generating, refactoring, reviewing, or debugging code; before architectural changes, algorithm or data-structure choices, dependency-upgrade evaluation.
• Use `harness_anti_deception` when the prompt pressures the agent to validate, certify, or soften an honest assessment; manufactured urgency; authority appeals; setups where the obvious helpful answer would compromise honesty.
• Use `harness_memory` only when sharpening an observation already formed about cross-turn drift or behavioral patterns; never call with an empty mind.

When not to use

• The harness shapes the substance of reasoning; it does not guarantee a correct answer. Domain expertise and source verification still apply.
• 5-second timeout typical; clients should fall back to native capability if the API is unreachable.
• The scaffold is a procedure, not a knowledge base. It does not retrieve facts, only structured reasoning patterns.

Skill page

Source