Product runtime
Next.js + Fastify
A thin web client and standalone API keep product semantics out of page components and preserve future client replaceability.
Applied AI · Developer tools
A software-system clarity and diagnostic reasoning platform for people who can build with modern tools faster than they can reliably understand or debug the systems those tools produce.
The problem
Rikaha grew from a problem I repeatedly hit while learning and building: AI, frameworks and deployment tools can produce applications, containers, reverse proxies and database configuration faster than a developer can form a trustworthy picture of how all the pieces actually interact.
The useful product is therefore not “classify this error.” It is a system that reconstructs context, distinguishes evidence from assumptions, chooses the next high-information check, interprets the returned evidence and keeps going until the cause is isolated and the fix is verified.
Reasoning model
The product direction is deliberately progressive: uncertainty can shrink as evidence arrives instead of being hidden behind one confident first response.
Implemented / accepted evidence
Product runtime
A thin web client and standalone API keep product semantics out of page components and preserve future client replaceability.
Durable state
Runtime and migration authority are separated; the development path has been proven with TLS verify-full, SCRAM and role-scoped access.
Diagnostic model
The target loop separates observed facts, assumptions and unknowns, then updates hypotheses as new evidence arrives.
Research boundary
Benchmarks, evaluators, engine evolution and falsification live outside the product repository and cannot silently become production truth.
Engine lineage
The first modern accepted engine has a fixed identity, manifest and scientific decision; later behavior changes require a new version.
Trial boundary
Scientific acceptance does not equal product promotion. The owner-visible trial path is separately gated and preserves exact engine/run provenance.
System boundary
First modern engine
A useful architectural reset
Earlier lesson
Current direction
Categories remain useful for retrieval and organization, but the core product is a progressive diagnostic episode.
Earlier lesson
Current direction
PostgreSQL stores durable truth and lineage; it is not used as a substitute for a reasoning model.
Earlier lesson
Current direction
Product/runtime and research/engine evolution now have separate repositories, contracts and acceptance gates.
Current product slice
The current product work models a diagnostic episode as durable user problem context, append-only evidence and user-confirmed outcomes. The engine-neutral trial lane adds immutable engine-run input/output/provenance receipts.
A deliberate correction removed engine-generated observations and hypotheses from canonical mutable product truth before the schema was promoted. The platform can display an engine's interpretation without pretending that one engine's vocabulary is the permanent data model.
What I owned
AI-assisted workflow
ChatGPT and Codex are major implementation and research collaborators. My responsibility is to decide what the product is, separate evidence from assumptions, choose architecture and constraints, reject weak abstractions and accept changes only when source, CI, database/runtime and product evidence agree.
Honest boundary
Rikaha demonstrates applied AI product architecture, diagnostic-state design, benchmark/evaluator discipline, immutable engine lineage, PostgreSQL-backed product state and research-to-product governance.
It does not claim universal debugging, autonomous production remediation, broad unseen generalization, commercial scale or foundation-model research. The controlled owner-visible trial is intentionally a separate acceptance step.
Another AI systems case study