The domain becomes a personal space
Kerkito.com is registered. It is not yet a product: the domain first serves as a personal and community anchor.
- No engine
- No account
- An identity before a product
The project began as a personal domain, became a P.O.N.T. generator, then a local-first tool. The 8.2 line turns that base into a guided journey: four stages, one priority clarification at a time, richer context and transparent voice features.
Versions 9.8 and 10.1 belong to the historical generator line. The current rebuild opens a distinct 8.x line. Milestones 1.x through 6.x summarize real functional stages whose exact dates and subversions were not all preserved; they are presented as markers rather than exhaustive archives.
Kerkito.com is registered. It is not yet a product: the domain first serves as a personal and community anchor.
The first public version is a Diablo 3 solidarity page tied to the Kerkito nickname and a fresh start after a banwave. The model is deliberately simple: a direct and autonomous page.
Kerkito changes direction. It is first built for personal use: stop collecting aging prompt lists and learn to construct a structured request with the P.O.N.T. method.
The engine becomes richer without making the interface heavier. Express and Advanced paths let users choose detail level while the first guides explain why an instruction works.
Kerkito expands into teaching, documentation and reusable structures. The library progressively moves from a collection of sentences to a collection of structures.
The product commits to a clearer direction: no mandatory registration, less tracking, browser-side persistence and less dependence on a central service.
Generation is deeply redesigned. Kerkito stops promoting “you are…” or “act as…” as the default answer and puts more weight on context, method, constraints and useful content.
The engine goes further in context preparation: document sharing, content recovery and OCR complement structured construction. This version then remains stable for several months.
Kerkito changes its object. It no longer tries to beat an LLM or optimize a magic formula. It becomes a deterministic and reproducible environment to structure intent, preserve reasoning, explain inferences and learn locally from user corrections.
Depth increases while the interface becomes simpler. Kerkito moves to four visible stages, shows one priority clarification at a time, offers closed suggestions before free writing, and explains why each question matters. The engine also gains typo tolerance, negation handling, compound concepts, professional context and capability-detected voice features.
The 8.2 logic stays intact, while mobile becomes a first-class interface: accessible hamburger navigation, compact header, readable four-stage progress, thumb-friendly actions and lower visual density around the engine.
Both themes are redesigned without changing the engine: near-total black with controlled luminous signals in dark mode, and a mineral iridescent palette in light mode. Readability, contrast, mobile-first behavior and exact rollback to 8.2.1 remain priorities.
The new identity now spans the whole site. The Kerkito symbol replaces the older textual marker, the day/night control is made reliable and several homepage sections are rebalanced with pixel-level attention, especially the LLM contrast block, to achieve a calmer, cleaner and more readable result.
The comparison block is simplified around a single reading axis: full-width heading, explanation directly below, then two cards aligned on the same row with matching height. The hierarchy stays clear without an unnecessary decorative offset.
Kerkito gains a dedicated Open Graph image for social sharing and internal discovery cards for related projects, without an ad network or tracking. The ecosystem cards now show the full visual without harsh cropping, supported by a restrained backdrop. Copy below each card complements the visual instead of repeating its slogan, and the section introduction returns to a single reading axis.
The six ecosystem visuals are rebuilt as landscape banners to avoid aggressive cropping. Files receive descriptive names and bilingual alternative text. The Kerkito symbol animation is also made more restrained.
The Content Security Policy now follows a deny-by-default model. Resource loading is blocked at the base level, then only the resources actually required by Kerkito are explicitly opened. This addresses the HTTP Observatory finding without adding any external source.
Technology and interface changed, but the original problem remains: stop depending on frozen lists and give users a method to build a structure suited to their own need.