Changelog

Updated

index.html — About section cadence

"One tool per month" → "One tool every three months"

Updated

about.html — Practice description

"Koher is a ten-year practice. One tool per month." → "One tool every three months."

Updated

tools.html — Meta descriptions and subtitle

"Released monthly" → "Released quarterly" in meta tags. Page subtitle updated to "One tool every three months."

Updated

position-being-around.html — Two instances

"One tool per month" → "One tool every three months." Also updated "If a month passes" → "If a quarter passes."

The "Being Around" position explicitly grounds the practice in cadence. The quarterly rhythm allows proper assumption grounding — one conversation per week, alternating new students and mentored students. Building on ungrounded assumptions wastes more time than grounding them first.

Added

notes.html — Short-form writing and updates

A blog section with hero images, individual post headers, and client-side routing. First post: "Notes is now live".

Koher needed a space for timely updates that don't fit the static position pages or tool documentation. Notes fills this gap.

Updated

Navigation includes Notes across all pages

Added Notes link to nav on: index, about, tools, positions, position-architecture, position-being-around, position-chatgpt-problem, changelog.

Removed

"The Question" section from homepage

Removed redundant section ("You know when your work holds together..."). This content is already captured in the About section. Cleaner flow: Tools → What This Means.

Added

about.html — For students. For self-learners.

A dedicated page explaining who Koher is for and why the tools are free for students. Grounded in the experience of learning without a guide.

The previous About section was embedded in index.html. A dedicated page creates space for the self-learner focus — acknowledging that the tools are built by someone who was self-taught for 15 years before becoming a teacher.

Updated

Navigation standardised across all pages

All pages now link to about.html in nav. Position pages previously had inconsistent nav (Application Areas, Consultancy) — now standardised to: Tools, Positions, Venue, About.

Expanded

Qualification layer: Human, AI, or Hybrid

The Coherence Diagnostic uses AI classification (DeBERTa) for qualification. Other tools may use human selection — users choose options from a grid. Both are valid qualification approaches. The architecture now explicitly accommodates both, plus hybrid approaches that combine human and AI qualification.

Added

Human Selection approach in qualification table

Added a "Human Selection" row to the qualification approaches table: "When to use: Users have domain knowledge to identify signals directly. Example: User selects play qualities that describe their game's emotional shape."

The original table listed AI-centric approaches (pattern matching, semantic classification, NER). Human selection is equally valid — sometimes the user is the best signal extractor.

Renamed

"The Three-State Innovation" → "Domain-Meaningful Categories"

The Coherence Diagnostic uses confidence-based categories. Other tools may use relationship-based categories (Synergy/Neutral/Tension for how elements interact). Both are valid. The architecture now shows category systems as domain-specific, not prescriptive.

Reframed

From consultancy to practice

The consultancy framing created exit ramps: "If institutions don't buy, if revenue doesn't arrive, if recognition doesn't come — leave." The new framing has no exit conditions. The practice continues regardless of funding. Open source is the core; hosted demos are community-funded convenience.

Rewritten

Hero tagline and CTAs

Removed

Commercial and credential sections

• Where This Applies — domain grid (Legal, Education, Finance, etc.) listing aspirational claims without demonstration
• Ways to Work Together — consultancy tiers from ₹5,000 to ₹1,50,000/month
• Boundaries — "What the Koher consultancy doesn't do"
• Track Record — credentials display ("15+ years...", "50M+ annual viewers...")

Domain claims without tools are empty promises. Consultancy pricing creates revenue expectations. Credentials are resume-padding. A teacher making tools needs none of these.

Added

About section

Personal voice replacing institutional framing: "I teach design at Anant National University. For fifteen years I've watched students struggle to see whether their concepts hold together..." The section establishes Koher as one teacher's practice, not a company.

Added

Support section with transparent balance sheet

A public balance sheet showing: monthly costs (API ₹1,800 + Hosting ₹600), current balance, runway in weeks. The "Pay it forward" model — working practitioners extend access for students who can't pay. When balance hits zero, hosted demos pause; open source continues.

Hidden costs create exit ramps. Transparent costs create shared ownership. The balance sheet updates automatically with API usage. Anyone can see how their contribution extends access.

Deleted

Consultancy files

• consultancy.html — redirect page
• consultancy-og2.png — OG image
• consultancy-og2.svg — source file
• linkedin-service-text.txt — consultancy copy

Changed

Site navigation

Navigation updated across all pages: homepage, tools, positions, position articles, and changelog.

Added

Concept submission logging

The hosted demo now logs: submitted concept text, evaluation scores, and timestamp. Data stored in SQLite alongside cost tracking. Used solely for model improvement.

The DeBERTa model was trained on synthetic data. Real student submissions reveal patterns synthetic data missed — edge cases, phrasing variations, domain-specific concepts. Logging enables periodic retraining with real-world examples.

Added

Data use disclosure on website

The Support section now includes a data transparency note: "Concepts submitted to hosted demos are logged solely to improve model accuracy. No human reads your submissions. Data is never sold, shared, or used commercially — training data only. Self-hosted versions log nothing."

Transparency about data use is part of the practice. Users should know their submissions contribute to model improvement, that no human ever sees what they submit, that data is never sold or shared, and that self-hosting avoids logging entirely.

Added

Live balance fetch from coherence-demo.koher.app

On page load, the Support section now calls the /balance endpoint at https://coherence-demo.koher.app to retrieve current balance and runway values. The balance display updates with live data; colour changes based on status (green for healthy, amber for low, red for critical/paused).

The balance sheet exists for transparency — showing how contributions sustain the hosted demos. Static values would become stale. Live data from the actual cost tracking system ensures the displayed balance reflects reality.

Added

Graceful fallback

If the API is unreachable or returns an error, the static values remain visible. No error messages shown to visitors — the balance sheet simply displays the default values.

The API lives on separate infrastructure (coherence-demo.koher.app). If that service is down, the main website should still render completely. Silent fallback prevents cascading failures.

Disabled

Buy Me a Coffee button

The "Pay it forward" button in the Support section is commented out. The balance sheet and transparency messaging remain visible.

Razorpay offers better integration for Indian users (UPI, Indian cards) and lower transaction fees. Decision pending on which payment processor to use.

Published

The ChatGPT Problem (/position-chatgpt-problem)

A position statement on the fundamental error people make with AI tools: conflating language ability with judgment ability. The piece explains why ChatGPT feedback varies every time, why there are no consistent criteria, and how the three-layer architecture (qualification → rules → language) addresses this by using AI for what it does well while encoding judgment in deterministic code.

The Architecture Specification explains what the three-layer pattern is. "Being Around" explains the temporal commitment. This piece explains the problem — the core issue that makes separation necessary. It draws from real user feedback (Akash meeting, 20 February) describing the moment of recognition: "this is a very good separation of code and the language" and "holding the model accountable."

Fixed

Database path resolution

The Dockerfile created /app/data as the intended volume mount point, but the database code ignored it. Analytics data would be lost on container restart unless operators manually set DB_PATH. Now production deployments automatically use the prepared directory.

Added

NODE_ENV=production in Dockerfile

The Dockerfile now sets NODE_ENV=production so the database path logic triggers automatically without requiring environment variable configuration.

Added

Venue section on homepage

New "The Venue" section after Positions, introducing the art practice alongside the tools and philosophy. Links to venue.koher.app.

Added

Venue link in footer

Footer navigation now includes Changelog · Positions · Venue.

Added

All time range option

Dashboard time filter now includes: Last 24 hours, Last 7 days, Last 30 days, Last 90 days, and All time.

Fixed

Falsy zero bug in time range

The 'all' range returned 0 (no lower bound), but JavaScript's || operator treated 0 as falsy and defaulted to 7 days. Changed to in check so 0 is correctly returned for 'all'.

Fixed

UTM Campaigns table display

The database query groups by utm_medium but the table wasn't displaying it — causing rows with identical campaign/source but different mediums to appear as duplicates with unexplained different counts.

Changed

Hero CTA button

The singular "tool" implied a single demonstration. The practice is monthly releases — plural framing reflects the ongoing nature.

Added

Tools section heading and practice framing

The tools section now has "The Practice" label and heading "One tool per month. Open source. Running now." with introductory text: "Making tools is the practice. Each month, one small tool ships — demonstrating the architecture in a specific domain."

The previous version jumped straight to showing the tool without explaining the rhythm of the practice. The new framing establishes that monthly releases are the mechanism, not a one-time demonstration.

Changed

Tools page link

Changed

Demo access copy (homepage and tools page)

Reduced friction language. "Register" implies a process; "verify your email" describes exactly what happens. Added "free" and "no account setup" to remove hesitation.

Added

Email verification flow

Users enter name and email to receive a verification link. Clicking the link sets a session cookie granting access to the tool. No passwords, no OAuth — just email verification.

The tool was completely open. Each analysis uses DeBERTa inference + OpenRouter API credits. Without any gate, costs are unbounded and there's no way to understand who is using the tool.

Added

Usage limits

10 new user signups per day (resets daily). 10 analyses per user (lifetime). A waitlist captures overflow when the daily cap is reached.

Caps cost exposure while keeping the tool accessible. The daily signup limit prevents sudden spikes; the per-user limit encourages thoughtful use rather than casual testing.

Added

Session-only cookies

Authentication uses signed session cookies (via itsdangerous). Cookies are deleted when the browser closes — no persistent login.

Session-only cookies are the lightest viable auth. Users re-verify each browser session, which is acceptable for a demo tool. No password storage, no token refresh logic.

Added

Analyses counter in header

A subtle "X analyses left" counter appears in the header after authentication. Updates after each analysis completes.

Changed

Landing screen

Removed "No login." from the landing meta text, since login is now required.

Changed

Admin API endpoints

Replaced the single /api/admin/dashboard endpoint with separate endpoints matching the old admin pattern: /api/admin/login, /api/admin/stats, /api/admin/users, /api/admin/waitlist. Protected by X-Admin-Key header.

The old admin had a proven login-then-query flow. Separate endpoints are easier to debug and extend.

Changed

Admin UI

Users table now shows Name, Email, Status (verified/pending), Usage, and Joined date. Removed the "Create New User" section (users self-register now). Added a Waitlist section. Stats grid shows Total Users, Verified, Signups Today, Analyses, Exhausted, and Waitlist counts.

The admin no longer creates users — it monitors self-registered users and their verification status.

Changed

Tools page subtitle

Access is now self-service. The old copy implied a manual gatekeeping step that no longer exists.

Changed

Homepage tool card access note

Changed

Hero section

Replaced "Koher is a philosophy..." tagline with "Working tools built on a simple separation..." and changed primary CTA from "Read Our Positions" to "Try the Coherence Diagnostic". Added pipeline indicator (DeBERTa / Rules / Haiku).

The hero was entirely abstract — philosophy, architecture, positions. Someone landing on the page had no signal that working tools existed. The new hero communicates "this is real, try it now" within the first screen.

Changed

Tool section moved to position 2

The Coherence Diagnostic card now appears immediately after the hero (first scroll), moved from position 7. Status changed from "Demo" to "Live".

The tool was buried behind six explanation sections. A visitor who came to see if this was real had to scroll through philosophy, problem framing, architecture diagrams, and practice statements before finding proof. Now proof is the first thing after the hero.

Removed

"The Practice" section

Removed the section containing "A body of thought, not a product" and "This is not a startup. This is a practice." headings.

These lines actively told visitors "this isn't a real thing." For someone trying to determine whether Koher produces working tools, this section was counterproductive. The practice philosophy lives in the position statements for those who seek it.

Added

robots.txt and sitemap.xml

Created robots.txt declaring the sitemap location, and sitemap.xml listing all six pages with update frequencies and priorities.

Search engines can discover pages through links, but explicit sitemap declaration helps them find all pages efficiently and understand update frequency. The robots.txt also serves as the canonical location for sitemap declaration.

Added

Canonical URLs on all pages

Every page now includes a <link rel="canonical"> tag pointing to the canonical URL without .html extension.

Without canonical URLs, search engines may index URLs with and without trailing slashes as separate pages, or index both /position-architecture and /position-architecture.html.

Added

Twitter Card tags on secondary pages

All pages (tools, positions, position-architecture, position-being-around, changelog) now include Twitter Card meta tags mirroring their Open Graph content.

Only index.html had Twitter Card tags. When other pages were shared on Twitter/X, they displayed without rich previews.

Added

JSON-LD structured data

Added Schema.org structured data: SoftwareApplication schema on the homepage, Article schema on position pages (position-architecture, position-being-around).

Structured data helps search engines understand what Koher is (a software application/philosophy) and that the position statements are articles with specific publication dates and authorship.

Fixed

og:url inconsistencies

Position pages had og:url values ending in .html while internal links used paths without the extension. Now aligned to canonical URLs without .html.

Added

Open Graph tags on changelog

The changelog page was missing all Open Graph tags. Now includes og:type, og:url, og:title, og:description, and og:image.

Fixed

robots.txt and sitemap.xml now included in deployment

Added robots.txt and sitemap.xml to the INCLUDE_FILES array in make-caprover-tar.sh.

The deployment script used an explicit include-list. SEO files created earlier in the day were not being deployed to production because they were not added to this list.

Added

koher.app submitted to Google Search Console

Sitemap submitted at https://koher.app/sitemap.xml. All six pages now discoverable by Google's crawlers.

Added

Logout link in header

A "Logout" link now appears in the header next to "All Tools" when the user is authenticated. Clicking it clears the stored password from localStorage and returns to the password modal.

The authentication system stored credentials in localStorage permanently with no mechanism to clear them. Users who wanted to test with a different password, or simply wanted to log out, had no way to do so without manually clearing browser storage.

Added

User status endpoint and initial fetch

Backend now exposes a /user/status endpoint that returns remaining analyses without consuming one. The frontend calls this endpoint on page load when a stored password exists.

Previously, the server tracked usage in SQLite but only returned the remaining count after completing an analysis. Users who logged in couldn't see how many analyses remained until they ran one. The admin panel showed correct counts (e.g., "2/10") but the frontend showed nothing until an analysis was performed.

Changed

Anthropic API → OpenRouter

The Stage 3 language layer now calls Claude Haiku via OpenRouter (anthropic/claude-haiku-4.5) using the OpenAI SDK, rather than the direct Anthropic API. Environment variable changed from ANTHROPIC_API_KEY to OPENROUTER_API_KEY.

OpenRouter provides a unified API across multiple model providers. This allows future flexibility in model selection without code changes, and simplifies API key management for users who already have OpenRouter accounts.

Changed

First-deploy model download

The DeBERTa model (~750MB) now downloads automatically on first container start via entrypoint.sh, rather than being bundled in the Docker image. The model persists in a volume at /app/models.

Bundling the model in the Docker image made builds slow and images large. Downloading on first deploy keeps the image small (~200MB) while the model persists across container restarts. Subsequent deploys skip the download entirely.

Published

Being Around (/position-being-around)

A position statement on staying with practice long enough for significance to accrue. The core insight: "It is more important to be around than to be big." The piece describes the mechanism by which over-investment creates exit ramps, and how Koher refuses that pattern through monthly shipping, open source, and metrics that invite continuation rather than justify departure.

The Architecture Specification explains what the three-layer pattern is. This piece explains how Koher intends to stay with the practice — the philosophy of compounding over scaling. Together, the two positions establish both the technical architecture and the temporal commitment.

Added

Position card on /positions

The Positions page now displays two cards: "Being Around" (15 February) and "Architecture Specification" (13 February), in reverse chronological order.

Updated

Homepage Positions section

The Positions section on the homepage now shows both position statements with dates: "Being Around" (15 Feb) and "Architecture Specification" (13 Feb). Previously showed only the Architecture Specification.

The homepage should surface recent positions, similar to how the Tools section shows recent tools. As more positions are published, the section will show the 3 most recent.

Unchanged

What stayed the same

• Tools page and Coherence Diagnostic
• Architecture Specification position statement
• Subscription tiers and pricing
• Visual design

Added

Institutional Deployment — ₹15,000

One-time deployment service: scoping call, deployment to client infrastructure, branding and threshold configuration, handover documentation, training call, and 2 weeks post-deployment support. First 50 institutions at early adopter pricing.

The tools are open source and free, but "clone repo, install dependencies, configure API keys" excludes the natural audience — educators. This tier makes the tools accessible to those who recognise their value but lack technical capacity.

Structure

Tiered pricing

• First 50 institutions: ₹15,000 (early adopter)
• Institutions 51–150: ₹20,000
• After 150: ₹20,000 + ₹10,000/year support
• Additional customisation rounds: ₹5,000 each
• Annual support retainer (optional): ₹10,000/year

Volume-based pricing rewards early adopters and introduces recurring revenue at scale. Infrastructure and API costs borne by client — no margin compression.

Restructured

"Ways to Work Together" section

The consultancy section is renamed from "For Those Who Want Help" to "Ways to Work Together." Tiers split into two sub-sections: One-time (Single Session, Institutional Deployment) and Ongoing (Advisory, Architecture, Development). Architecture Map tier removed.

The new framing better describes the range of engagements — from a single call to full development — without implying that only "help" is available.

Removed

"Off-the-shelf solution deployment" from Boundaries

The "What we don't do" section previously included "Off-the-shelf solution deployment." This is now removed since Institutional Deployment does exactly that — deploys existing tools for clients.

Fixed

SVG pipeline indicator overlap

The "DeBERTa → Rules → Haiku" pipeline indicator in the Coherence Diagnostic thumbnail was overlapping with the GAPS dimension. Moved to clear position.

Added

Demo access instructions

The page subtitle now includes how to request demo access: "email hello@koher.app to request access." Previously just said "Hosted demos available by invitation" without explaining how.

Added

Tools page (/tools)

A dedicated page at /tools listing all open tools. Card-based layout with SVG thumbnails, demo links, and GitHub source links. Links to the new GitHub organisation: github.com/koher-architecture.

The "Open Tools" section on the homepage pointed to an empty Lab. With the first tool ready, a proper tools page provides the destination — tool cards with descriptions, source links, and demo access.

Released

Coherence Diagnostic v1.1.0

The first Koher tool — a design concept coherence analyser. Takes a 2-8 sentence concept and shows what's strong, thin, or unclear across five dimensions (CLAIM, EVIDENCE, SCOPE, ASSUMPTIONS, GAPS). Three-stage pipeline: DeBERTa qualifies, deterministic rules judge, Haiku narrates.

This is the tool that was removed from the homepage on 13 February. It returns — not as a "proof of concept" the architecture must stand or fall by, but as one small tool demonstrating the three-layer separation. Open source under MIT licence; users clone the repo, bring their own Anthropic API key, run locally.

Features

User management and comparison modes (v1.1.0)

• User management with SQLite storage
• Admin panel at /admin for creating users
• Usage limits: 10 analyses per user, 10 new users per day
• Three-mode toggle: Koher pipeline, Direct AI, Side-by-Side comparison
• History tabs showing previous analyses
• Sample concepts button for quick testing
• 60-second timeout with refresh prompt

The comparison modes let users see the difference between the Koher architecture (DeBERTa → Rules → Haiku) and direct AI prompting. The user management prevents abuse of the hosted demo while keeping it accessible by invitation.

Established

Demo URL pattern

All future tool demos will follow this pattern. The main website remains at koher.app; each tool demo lives at its own subdomain.

Clear separation between the philosophy (koher.app) and the demonstrations ([tool]-demo.koher.app). Each tool is independent infrastructure.

Unchanged

What stayed the same

• Homepage content and structure
• Positions page
• Subscription tiers and pricing
• Visual design — colours, typography, layout

Rewritten

Page title and meta tags

The site now leads with the philosophical insight, not a service description. The first thing someone reads should be the idea, not an offering.

Rewritten

Hero section

The first action should be reading the architecture, not emailing. The philosophy needs to land before any conversation starts.

Added

The Practice section

New section after "The Approach" — four short paragraphs setting the practice frame. "The architecture is the constant. The tools evolve... This is not a startup. This is a practice."

The site had no philosophical anchor. The architecture was presented as a service offering rather than a body of thought. This section establishes that Koher is a long-term practice — tools ship when they crystallise, open source, under MIT licence.

Replaced

Proof of Concept → Open Tools

The design coherence tool will not be released in its current form. It was specific to one domain (design education), one audience (students and faculty), one user level (early-stage concept formation), and one maker level (the practitioner's current implementation capacity). Presenting it as "proof of concept" made the architecture's credibility hostage to a single tool that most visitors would find irrelevant to their domain. Ideas do not get second chances. The Lab section honestly states that no tools are released yet, and frames the practice of shipping small tools as they arrive.

Reframed

Subscription Plans → For Those Who Want Help

The subscription tiers are real offerings and remain unchanged in price and content. The framing shifts from a sales climax to an option. The consultancy exists for those who want to apply the architecture in their domain.

Restructured

Open offering separated from subscription tiers

The subscription section is split into two parts. First: a statement that the tools and architecture are free — always, for everyone, no signup. This is an offering, not a subscription tier. Second: the paid consultancy tiers for those who want help applying the architecture.

The Open offering is not a subscription. It should not sit alongside subscription cards as though it were one. It is a statement of principle: the tools and architecture are free for use. The consultancy is a separate, optional engagement.

Added

Single Session tier (₹5,000, one-time)

One 90-minute call to explore whether the three-layer architecture applies to the visitor's domain. No commitment beyond the session.

The jump from Free to ₹20,000/month annual subscription was too steep. Someone interested in the architecture needs a way to test the fit without committing to an annual engagement.

Added

Architecture Map tier (₹25,000, one-time)

Written analysis mapping the three-layer architecture to the visitor's specific domain problem. Includes one 60-minute call and a written deliverable: what gets qualified, what rules encode, what the language layer handles.

Some organisations want a clear picture of how the architecture applies before deciding to build. This deliverable-based engagement provides that picture without requiring an ongoing subscription.

Added

Follow the Work section

"New tool when it arrives. No spam. No pitch."

Lower commitment than emailing. For people who are interested but not ready for a conversation.

Rewritten

Contact section

"Start Your Free Trial" is SaaS language. It frames the interaction as a sales conversion. The revised copy frames it as a conversation.

Added

Positions page

A new page at /positions to host philosophical statements and positions on AI, judgment, and domain expertise. Empty at launch, ready for when positions are published.

Koher is a philosophy. The website needs a place to publish positions and statements of principle. Each position is a dated, titled entry. The page grows as the practice evolves.

Added

Changelog page

This page. A styled public record of every change to koher.app, with rationale. Linked from the footer.

Transparency about the evolution of the site and the thinking behind it.

Unchanged

What stayed the same

• The Problem section
• What Separation Means section (mixed vs. separated table)
• The Approach section (three-layer architecture panel)
• Where This Applies section (domain grid)
• Subscription tier prices (Advisory ₹20K, Architecture ₹50K, Development ₹1.5L)
• Subscription tier content and deliverables
• What We Don't Do section
• Track Record section
• Visual design — all colours, typography, layout
• Logo (Three Braid)