KERNIT Documentation

Changelog

KERNIT release notes now emphasize the Hyperlinker-led product direction: reviewable cross-reference linking, API automation, resolver reliability, and formatter maintenance.

May 2026#

• Docs foundation becomes Hyperlinker-first. Generated local docs now lead with KERNIT Hyperlinker and API workflows, with role-based routes for researchers, developers, and platform teams.
• OpenAPI contract policy added. The OpenAPI source now carries KERNIT contract policy for stable status, public route behavior, compatibility rules, auth expectations, DOCX size ceiling, and support context.
• Docs feedback sink hardened. Docs analytics now has a durable event sink contract that accepts only docs paths and whitelisted event details, redacts credential-like strings, and rejects invalid or oversized payloads.
• API reference polish. Endpoint pages use contract-first language, OpenAPI-backed request builders, copy-paste integrations, reusable client templates, and status-aware playground output.

April 2026#

• Review/apply workflow expands. KERNIT added scan and apply endpoints, review decisions, scan tokens, and citation safety guards for reviewable DOCX linking.
• API host split. API product surfaces moved to api.kernit.org, with public document-processing routes documented as bare production endpoints.
• Team API surfaces grow. Organization keys, shared presets, usage history, billing, and admin controls expanded for B2B API workflows.

March 2026#

• Worker-backed processing foundation. DOCX export and hyperlinker processing moved further into Cloudflare Worker-backed routes.
• Formatter foundation. Journal presets, export surfaces, and earlier documentation established the formatter-era KERNIT foundation now treated as supporting legacy docs.

Release Feed Contract#

The changelog page and RSS feed are produced from the same release entries. Add user-facing docs, API contract, Hyperlinker workflow, or production-readiness changes here when they affect how teams should use KERNIT.