PROJECT TRUTH / CURRENT STATEKnow what is true now.
Know what is true now.
Inspect why.
HARIKOS resolves important project claims against repository evidence, preserves their history, and exposes uncertainty instead of hiding it.
ILLUSTRATIVE PRODUCT EXAMPLE
AUTHENTICATIONVERIFIED
Supabase Auth
project-wide · confidence 99%
EVIDENCE / 03middleware.ts:18-34↗lib/supabase/server.ts:7-22↗package.json:31↗
01CURRENTVerified against a commit
02TRACEABLEEvery claim has evidence
03TEMPORALPrevious state is preserved
04HONESTContradictions stay visible
TEMPORAL TRUTHCurrent does not erase
Current does not erase
what was true before.
Scrub across a controlled authentication migration. Status, code evidence, and documentation consistency change together.
ILLUSTRATIVE PRODUCT EXAMPLEAUTHENTICATIONSupabase AuthVERIFIED · 99% AUTHENTICATIONClerkSUPERSEDED DOCUMENTATIONREADME.mdSTALE · REVIEW
12
+ import { createMiddlewareClient } from "@supabase/ssr"18
+ const supabase = createServerClient()21
− authMiddleware.protect()27
return responseBEFOREClerk / verified
AFTERSupabase / verified
EVIDENCE / PROVENANCEConfidence you can
Confidence you can
open and inspect.
A confidence score is only useful when the source, authority, line range, commit, and observation time are visible.
ILLUSTRATIVE PRODUCT EXAMPLECLAIM SOURCEmiddleware.ts:18-34AUTHORITY 98% SOURCElib/supabase/server.ts:7-22AUTHORITY 98% MANIFESTpackage.json:31AUTHORITY 86%
Authentication uses Supabase Auth.
VERIFIED99%
CURRENT / PROJECT-WIDECONTRADICTIONSDisagreement is a state,
Disagreement is a state,
not an inconvenience.
When documentation and implementation conflict, HARIKOS keeps both pieces of evidence, applies authority, and marks the disagreement for review.
ILLUSTRATIVE PRODUCT EXAMPLEREADME.md:42 VSmiddleware.ts:18 RESOLUTION / SUPABASE VERIFIED
Authentication uses Clerk.STALE DOCUMENTATIONcreateServerClient()CODE / CURRENTStop treating stale assumptions as current fact.
Connect a repository and give every coding agent one current, evidence-backed understanding.