ek9_paradigm

Returns the constant EK9 paradigm summary (syntax that is NOT C/Java/Python, first-attempt traps, concepts with no analogue elsewhere) and working rules - the smallest priming context for an AI about to write EK9 code - and with withExamples:true the compiled inline examples after it.

Category: Enquiry

When to use it

Prime a fresh AI session before it writes or reasons about EK9 code - one call with {} (withExamples:true adds the compiled examples). The content is constant, so never re-invoke once it is in history.

When not to use it

• A specific keyword, type or topic page - use ek9_help.
• How-to / why questions ('how do I write a switch', 'why no break') - use ek9_ask.
• A specific error-code explanation (E07235, ...) - use ek9_explain_error.
• The full forAI.json reference (~42K tokens) - CLI-only (ek9 -h -E5); withExamples:true here is the middle size, and ek9_help / ek9_ask give targeted depth.

Details

Returns AiReferenceGenerator.PARADIGM_SUMMARY then WORKING_RULES (~9.7K chars / ~2.5K tokens): the NOT-C/Java/Python NO/YES syntax list (no braces, return, break, null, new; the <-/:=/:=? assignment trio), the measured first-attempt traps (precedence, literals, named arguments, invented names, override, unset fields), the concepts with no analogue elsewhere (the fixed operator set and sameness, tri-state, pure, dispatcher, closed-by-default types, constructs, stream pipelines) and the WORKING RULES for driving the tools. The footer names ek9_help / ek9_ask / ek9_explain_error as the next calls. Independent of workspace compile state; always succeeds. CLI parity: ek9 -h -E4 (withExamples adds forAI.json's inlineExamples, the harness's -E4x).

Arguments