Project / Problem
Define what must actually be addressed and its context.
A deterministic engine can be precise without becoming opaque
Kerkito separates vocabulary, concepts, rules and evidence. The engine can therefore grow without turning the application into hard-coded conditional logic.
P.O.N.T. stays, but changes role
Objective
Describe the observable expected result and its priority.
Non-negotiables
Separate constraints, prohibitions, resources and limits.
Tests
Define how to verify that the work actually satisfies the intention.
Seven layers, one simple journey
Lexical
Recognizes terms, phrases and language variants.
Inference
Propagates implications from explicit rules.
Constraints
Detects incompatibilities, obligations and dependencies.
Decision
Prioritizes questions that reduce ambiguity the most.
Guidance
Turns the internal graph into short stages, suggested answers and clear explanations of why each step matters.
Compilation
Produces a brief, outline, checklist or prompt without changing the project source.
method.layer.memory
method.layer.memory_text
A conclusion must be able to answer “why?”
Every inferred concept retains its origin: detected term, applied rule, confirmed answer or dependency. A conclusion can therefore be withdrawn if its justification disappears.
Meaning is independent of language
Rules target concept identifiers, never French or English sentences. Labels, lexemes and questions are translated separately. The same project can therefore be structured in French and rendered in English without duplicating the engine.
Security and auditability
No third-party front-end library, remote font or functional inline script. CSP, HSTS, CORP, COOP, Referrer-Policy and Permissions-Policy are applied by the server and then verified in production.