Keikaku’s surface vocabulary is a designed, plan-themed system. Variables are declared with designate (with := as quick assignment) and printed with declare. Conditionals use foresee for the first branch, alternate for additional conditions, and otherwise for the default, a direct, readable mapping onto if/else-if/else. Loops are unified under cycle in three forms: cycle while cond, cycle through collection as item, and cycle from a to b as i. Functions are protocol.

The type model beneath is conventional and comfortable: integers, floats, strings, booleans, lists ([1,2,3]), and dictionaries ({key: val}), with built-ins measure (length), span(n) (range list [0..n-1]), text/number (conversions), and classify (type name). This is a deliberate split: the vocabulary is where Keikaku is distinctive, and the evaluation model is where it is predictable. A reader who learns the keyword mapping can immediately understand a program, because the semantics behind the themed names are the familiar ones. That combination, an unfamiliar but regular surface over a familiar core, is the language’s core readability bet.