HISTORY · FROM NICKNAME TO ENGINE

Kerkito changed its object without losing its thread

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.

8.2.9Current version · new deterministic line

A history with several version lines

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.

December 5, 2024 Origin

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
December 2024 0.1

Diablo 3 landing page

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.

  • Single landing page
  • Community support
  • First visual identity
Early 2025 1.0

First P.O.N.T. generator

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.

  • P.O.N.T. becomes the core
  • Guided generation
  • Moving away from copied prompt libraries
First half of 2025 2.x

Express, advanced and guided paths

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.

  • Progressive paths
  • Copy and export
  • Method instead of recipes
2025 4.x

Students, guides and library

Kerkito expands into teaching, documentation and reusable structures. The library progressively moves from a collection of sentences to a collection of structures.

  • Student area
  • P.O.N.T. guides
  • Reusable structures
Late 2025 6.x

Autonomy and local-first

The product commits to a clearer direction: no mandatory registration, less tracking, browser-side persistence and less dependence on a central service.

  • No account required
  • Local storage
  • Fewer external dependencies
January 14, 2026 Legacy 9.8

The engine replaces role recipes

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.

  • Reworked P.O.N.T. engine
  • Blueprints
  • Less persona, more context
February 17, 2026 Legacy 10.1

Documents, OCR and content extraction

The engine goes further in context preparation: document sharing, content recovery and OCR complement structured construction. This version then remains stable for several months.

  • Documents as context
  • OCR
  • Content extraction
  • Autonomy without tracking
August 7, 2026 8.1

Deterministic rebirth

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.

  • Persistent local memory
  • On-device learned corrections
  • Explainable inference
  • Question prioritization
  • Project, research, teaching and decision
  • No LLM required
August 7, 2026 8.2

The engine disappears behind the journey

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.

  • Four-stage journey
  • One priority question at a time
  • Suggestions before free text
  • 88 concepts and 552 FR/EN lexemes
  • 100 starter professional contexts
  • Conservative typo tolerance
  • Visible negation and uncertainty
  • TTS and dictation based on browser capabilities
  • 8.2 knowledge migration
August 7, 2026 8.2.1

The journey becomes genuinely mobile-first

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.

  • Accessible hamburger menu
  • Compact sticky header
  • Stages 1 to 4 always visible
  • 44–48 px priority touch targets
  • Responsive audit from 320 to 1280 px
  • No SQL change required
August 7, 2026 8.2.2

A more prospective and reversible visual identity

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.

  • Near-black dark palette
  • Mineral light palette
  • Cyan, violet and acid signal accents
  • No em dash in public copy
  • Full 8.2.1 backup preserved
  • No SQL change required
August 7, 2026 8.2.4

Unified identity and refined editorial sections

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.

  • New text-free symbol
  • Consistent light and dark variants
  • Local animation without JavaScript
  • Renewed favicon and PWA icons
  • 1200 × 630 social image
  • Reliable day/night toggle
  • Versioned assets against stale caches
  • Rebalanced LLM block
  • Better title distribution
  • Slightly staggered and better aligned cards
  • Changelog without historical screenshots
  • No SQL change required
August 7, 2026 8.2.5

Visual alignment of the LLM contrast block

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.

  • Heading and explanation on one axis
  • Aligned LLM and Kerkito cards
  • Matched card heights
  • Lower visual friction
  • No SQL change required
August 8, 2026 8.2.7

Social sharing and refined ecosystem cards

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.

  • 1024 × 537 JPEG Open Graph image
  • LinkedIn, WhatsApp and social sharing
  • Tracking-free internal promotions
  • Optimized WebP visuals
  • Full promo visuals without harsh cropping
  • Complementary copy instead of repeated slogans
  • Realigned ecosystem introduction
  • RoastMyURL, Itylos, Koperateur, 0bla, Lemyto and Kachouri
  • Restrained CSS motion
  • prefers-reduced-motion support
  • No SQL change required
August 8, 2026 8.2.8

Ecosystem visuals adapted to cards

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.

  • Card-ready landscape banners
  • Descriptive image filenames
  • FR and EN alt text
  • Calmer logo animation
  • No SQL change required
August 8, 2026 8.2.9

CSP locked down by default

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.

  • default-src 'none'
  • Local scripts allowed with a nonce
  • Styles and images limited to the same origin
  • Frames, objects, fonts and media blocked
  • Service worker and local connections explicitly allowed
  • No SQL change required
CONTINUITY

What survives every version

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.

  • P.O.N.T. remains a clarification method, not a collection of magic phrases.
  • “You are…” and “act as…” formulations are no longer the default answer.
  • Useful content, constraints, method and criteria matter more than prompt theater.
  • Autonomy, no mandatory account and local control of work remain priorities.