PROJECT BRAIN / ILLUSTRATIVE V0.1
BUILD FAST WITH AI.
HARIKOS KEEPS THE
PROJECT STRAIGHT.
One shared, continuously verified project brain for Codex, Claude, Cursor, and you.
READ-ONLY GITHUB ACCESS EVIDENCE ON EVERY TRUTH AGENT-NEUTRAL MCP
INITIALIZING PROJECT GRAPH
TRUTH / AUTHSupabase Auth VERIFIED · 99%
MEMORY / DECISIONKeep billing server-side2m ago · Codex
middleware.ts 18–34
SCROLL TO TRACE THE SYSTEM
01TRUTH
02MEMORY
03CONTEXT
04AGENT BRIDGE
THE FAILURE MODEYour agents move fast.
Your agents move fast.
Your project context fragments.
Code changes. Documentation drifts. One agent learns what the next agent never sees. Old assumptions stay alive because nobody checks them against the repository.
DIAGNOSTIC / CONTEXT_LOSS
AGENT / 01Codex sessionDecision: Supabase Auth
README.md“We use Clerk.”STALE / UNKNOWN
middleware.ts:18createServerClient()CODE / CURRENT
AGENT / 02New sessionContext: empty
NO SHARED STATE?ASSUMPTION SURVIVES
ONE COHERENT SYSTEMA project brain made of
A project brain made of
four precise layers.
HARIKOS does not blur history and reality into one summary. Each layer has a job, and evidence keeps the layers honest.
01 / 04
TRUTHWhat is true now?
Current project facts, confidence, and inspectable repository evidence.
Explore truth ↗02 / 04
MEMORYWhat happened before?
Decisions, failures, fixes, and outcomes that survive agent sessions.
Explore memory ↗03 / 04
CONTEXTWhat matters now?
A compact, task-specific brief built from current Truth and relevant history.
Explore context ↗04 / 04
AGENT BRIDGEHow agents stay aligned.
One project-scoped MCP bridge for Codex, Claude, Cursor, and other clients.
Explore agent bridge ↗THE PROJECT BRAIN IN MOTIONA repository changes.
A repository changes.
HARIKOS carries the meaning forward.
This illustrative loop shows the product mechanic: evidence updates Truth, a useful decision becomes Memory, and the next agent starts with current Context.
TASK RECEIVEDReplace Clerk with Supabasetask
middleware.ts +18 −9lib/supabase/server.ts +34README.md CURRENT
AUTH / PREVIOUSClerkVERIFIED
→AUTH / CURRENTSupabaseCANDIDATE
TRUTH / CURRENT STATE
Truth moves with the repository.
Every important claim carries status, confidence, scope, evidence, and a validity window. When implementation changes, HARIKOS preserves what was true without presenting it as current.
Explore Project Truth ↗12
+ import { createMiddlewareClient } from "@supabase/ssr"18
+ const supabase = createServerClient()21
− authMiddleware.protect()27
return responseBEFOREClerk / verified
AFTERSupabase / verified
MEMORY / PROJECT HISTORYUseful history survives.
Useful history survives.
Noise does not become authority.
This illustrative timeline shows how decisions, failed attempts, fixes, constraints, and outcomes can prevent the next session from repeating the last one.
ILLUSTRATIVE PRODUCT EXAMPLEATTEMPT FAILED ATTEMPT DECISION OUTCOME
Create Stripe subscription from the browser
Codex / session 2F7APrivileged credentials cannot cross the client boundary
root cause / securityKeep subscription creation server-side
applies to billing routesCheckout route and signed webhook boundary created
commit c2137fbMEMORY ≠ TRUTHHistory informs. Repository evidence verifies.
AGENT HANDOFF
The next agent should not start from zero.
Codex records a failed attempt, a decision, and an outcome. HARIKOS makes the project-useful parts available when Claude—or any other MCP client—starts a related task.
See the agent bridge ↗01C
CODEXSESSION COMPLETE
FAILED ATTEMPTDECISIONOUTCOME
CURRENT TRUTHCONSTRAINTFAILED ATTEMPTDECISIONOUTCOMERELEVANT FILES
02CL
CLAUDECONTEXT RECEIVED
CONTEXT / TASK RELEVANCENot more context.
Not more context.
The right context.
HARIKOS compresses repository signal, current Truth, relevant Memory, changes, and constraints into a focused Context Pack.
TASK / INPUTModify subscription flow
middleware.tsREADME.mdstripe.tsauth.tsbilling decisionfailed client attemptroute.tsdashboard.tsxwebhook constraintpackage.jsoncurrent planold auth change
RELEVANCE ENGINE
HARIKOS CONTEXT PACK1,184 TOKENS
CURRENT TRUTHINCLUDED
FILESINCLUDED
CONSTRAINTSINCLUDED
FAILED ATTEMPTSINCLUDED
DECISIONSINCLUDED
OUTCOMESINCLUDED
ILLUSTRATIVE PRODUCT EXAMPLE
DOCUMENTATION / README.md:42
Authentication is handled by Clerk.AUTHORITY 0.42 · SAMPLE AGE 19 DAYSVS
CODE / middleware.ts:18
const supabase = createServerClient()AUTHORITY 0.98 · COMMIT C2137FBHARIKOS RESOLUTIONCODE EVIDENCE WINS
Supabase Auth VERIFIED
README.md CONTRADICTED
CONTRADICTION / EXPLICITMemory can be wrong.
Memory can be wrong.
The repository gets the final say.
HARIKOS does not flatten conflicting evidence into false certainty. It exposes the disagreement, ranks authority, and preserves the transition.
EVIDENCE / PROVENANCEEvery truth has
Every truth has
a reason you can inspect.
This illustrative inspector shows the file, line, commit, authority, and observation time attached to a claim—never opaque confidence theater.
ILLUSTRATIVE PRODUCT EXAMPLE01 02 03
CLAIM / AUTHENTICATION
Supabase Auth
VERIFIED99%
project-wide · current since Aug 24
middleware.ts:18–34SOURCE CODE · AUTHORITY 98%
↗lib/supabase/server.ts:7–22SOURCE CODE · AUTHORITY 98%
↗package.json:31MANIFEST · AUTHORITY 86%
↗ DEVELOPERS / MCPOpen developer experience ↗
Ask the project brain directly.
Connect a coding agent with one revocable, project-scoped token. Read Truth, search Memory, prepare Context, check assumptions, and write back structured outcomes.
get_project_truth()search_project_memory()get_context_pack()record_outcome()$
Authentication
Supabase Auth
VERIFIED · 99%
Evidence
middleware.ts:18
lib/supabase/server.ts:7
Previous: Clerk · SUPERSEDED
SECURITY / ARCHITECTUREMinimum access.
Minimum access.
Explicit boundaries.
HARIKOS is designed around server-side authorization, bounded repository analysis, signed webhook boundaries, and revocable project-scoped agent access.
GITHUB
Contents: Read Metadata: Read
No repository writesSOURCE
Bounded file fetch Secret paths denied
No arbitrary code executionAGENTS
High-entropy tokens Hash + prefix stored
Revoke immediatelyDATA
User ownership checks Private tables protected
Server-side credentialsPRICING / SIMPLE BY DESIGNStart with one project.
Start with one project.
Scale the shared brain.
No annual fiction, fake enterprise tier, or hidden usage story. Start free; Pro is the current launch hypothesis.
$0/ forever
One repository · one agent connection · 250 memories · 25 Context Packs/month
Start free ↗$1/ month
Up to five repositories · five agent connections · higher Memory and Context limits
Continue to sign in ↗FAQ / THE SHORT VERSIONQuestions before you
Questions before you
connect a repository.
01Is HARIKOS another coding agent?
No. HARIKOS is the shared project brain around your coding agents. It verifies current state, preserves useful history, and gives each agent relevant context.
02What is the difference between Truth and Memory?
Memory records what happened. Truth represents what current repository evidence supports. A remembered decision can be useful without being current fact.
03Does HARIKOS store my whole repository?
The intended default is bounded, authorized source fetching: analyze relevant files, persist structured claims and evidence pointers, and avoid becoming a permanent full-code mirror.
04How do coding agents connect?
Through a remote, project-scoped MCP endpoint using a revocable HARIKOS token. Existing tokens are never shown again after creation.
05Can I inspect why HARIKOS believes something?
Yes. Verified claims expose their evidence, file paths, line references, confidence, commit, and temporal history.
PROJECT BRAIN / READYBuild fast.
Build fast.
Keep the project straight.
Connect a repository and give every coding agent one current, evidence-backed understanding.