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
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 turned that base into a guided journey. Version 8.3 adds answer contracts, local structural validation and a versioned JSON knowledge bundle with no runtime SQL database.
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
From structure to answer contract
Kerkito extends P.O.N.T. with an Answer Engineering layer. A structure reaching the fourth stage can now produce an answer contract describing expected shape, admissible states, evidence requirements and acceptance rules. The deterministic knowledge base moves away from a runtime SQL dependency to a public versioned JSON bundle, while user works remain in local browser memory.
- Answer contract after the fourth stage
- Explicit Answer Shape and Answer Space
- Evidence policy and acceptance rules
- Local structural validation of an external answer
- Markdown and JSON exports
- SUPPORTED, UNCERTAIN, CONTRADICTED and UNKNOWN states
- No claim of automatic factual verification
- Versioned JSON knowledge without runtime SQL
- No SQL migration required from 8.2.9 to 8.3.0
- 8.2 local-work compatibility
- Stale exports corrected after intention edits
- Negation and uncertainty preserved more carefully
- Contextual links to MinuteVibe, IAPont and Kachouri Showcase
- New Answer Engineering page
- SEO, GEO, accessibility, cache and security pass
The engine and ecosystem gain visual depth
Version 8.3.1 keeps the deterministic knowledge base and answer-contract logic introduced in 8.3.0. It rebuilds the homepage around a more compact hero, gives the engine its own dark spotlight section and replaces generic promo visuals with official ecosystem identities supplied for the project. Cyan and violet now form the common visual thread across graphs, nodes and signals. The HSTS policy also adds the preload directive and covers static Apache responses.
- More compact hero with cyan and violet emphasis
- Engine highlighted in a dedicated dark stage
- Decorative SVG graphs with no external dependency
- Official ecosystem logos for MinuteVibe, IAPont, MyProID, Kachouri, Koperateur and WebPion
- Logo proportions preserved with object-fit contain
- Card descriptions aligned with the documented ecosystem review
- 3 × 2 desktop grid while preserving the mobile journey
- HSTS max-age=63072000 with includeSubDomains and preload
- HSTS header also applied to static resources through Apache
- Service-worker cache versioned as 8.3.1
- No SQL migration and knowledge version remains 8.3.0
- Dual-color cyan/violet visual thread across SVGs and signals
Clean HSTS preload and a human-readable sitemap
Version 8.3.2 fixes the remaining HSTS Preload warning: Strict-Transport-Security is no longer emitted on the plain-HTTP redirect and remains limited to HTTPS responses. The XML sitemap also gains a local XSL stylesheet so humans can inspect it clearly without changing the machine-readable sitemap data.
- No HSTS header on HTTP responses
- HSTS max-age=63072000 with includeSubDomains and preload on HTTPS
- Consistent preload policy across PHP and API responses
- XML sitemap linked to sitemap.xsl
- Responsive sitemap view using the cyan/violet visual thread
- FR and EN alternates visible in the XSL view
- No external dependency
- No SQL migration
- Deterministic knowledge remains version 8.3.0
Canonical host and a more explicit engine
Version 8.3.3 normalizes the public host to kerkito.com without www, keeps HSTS HTTPS-only and improves the deterministic engine without adding an LLM. Question priority now includes structural-completeness weight and required status, open unknowns remain visible in the answer contract, and the engine separates established, to-confirm and open states.
- Redirect www.kerkito.com to https://kerkito.com while preserving path and query
- Defensive host canonicalization in PHP
- Engine remains fully deterministic and local-first
- Question priority combines importance, priority, completeness weight and required status
- Established / To confirm / Open states visible in the engine
- Open questions preserved in the answer contract
- Richer cyan/violet engine stage in light and dark themes
- No LLM or external inference API
- No SQL migration
- Knowledge remains version 8.3.0
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.