Fundamentals
- What it reads
- Reported financials, revenue, earnings quality, forward EPS, and the assumptions behind valuation.
- What it changes
- Defines what the company has earned and which valuation cases remain defensible.
Financial research · Evidence integrity
A research operating system that keeps a report tied to the evidence beneath it.
Kairosys brings fundamentals, industry, macro conditions, positioning and flows, news and sentiment, and technical context into one research question. Source, period, unit, falsifiers, and the decision trail stay attached; stale or unsupported statements stop before a labeled draft reaches a human analyst.
Designed and built solo by Titus Lai.

One question · Six financial lenses · Cross-lens controls
The work starts with the decision the research must support.

Can the filing period, source record, and displayed EPS support this forward P/E?
Six research dimensions
What coverage changes
Coverage → delivery
Current evidence and meaningful coverage support an editable analyst draft.
Supported work remains useful, but it cannot present itself as complete research.
Breadth cannot rescue a statement whose source trail fails.
Five responsibilities
What decision must this research support?
Which sources are current, relevant, and traceable?
Which market behavior belongs only as context?
Which financial and valuation statements do the periods support?
Do the final words still agree with the evidence and math?
Kairosys governance lineage
Define the boundaries before adding more intelligence.
The first Kairosys design treated identity, context, permissions, traceability, and recovery as one governing layer—not as cleanup after the model responded.
Define the boundaries before adding more intelligence.
Turn the control ideas into modules that can deny, record, and restore.
Carry the same boundaries across cooperating agents.
Let rules evolve without letting the system authorize itself.
A Kairosys governance lineage, not one continuous codebase: successive implementations and rewrites carried the same governing problems forward.
Four Kairosys stages · Four governance shifts
The dates mark distinct Kairosys implementations; each card shows how the governance layer changed.On interruption or restart, preserve a snapshot of rules, module state, and conversation context; ask before recovery.
A restart becomes a recoverable state instead of a silent reset.Without explicit mutation authority, deny the action; when execution fails, retain the decision and trace instead of silently proceeding.
The system can explain both why it acted and why it refused.Separate roles and bounded handoffs carry the task, evidence, and authority forward without letting collaboration erase responsibility.
More agents do not mean less accountability.The current Soul Codex separates human-owned principles, AI-proposable rules, and process metadata. Proposed changes remain proposals until an authorized human approves them.
The system can learn and change without quietly becoming its own authority.Two separate gates
A polished error is still an error. A sound fragment is still incomplete.
Flagship engineering case
The model writes a confident attribution with no trusted source behind it.
The report gives a target even though a required financial period is missing.
The final target, forward EPS, and displayed multiple disagree.
Runnable public evidence
ready_reportEvidence, state, and report math agree.
spoofed_provenanceA model promotes its own source statement.
incomplete_financialsA missing quarter makes the target unsupported.
contradictory_financialsFinancial facts conflict.
rendered_math_conflictFinal wording contradicts displayed math.
shallow_but_soundSupported facts cover only two lenses.
Evidence boundary
Runnable cases, architecture notes, fixed examples, tests, diagrams, and explicit boundaries.
Production coordination, proprietary prompts, providers, live data, operating history, and commercial source.