?Start here

What this is.

A working researcher's notebook, made public. It is dense and uses a lot of notation on purpose — so this page is the plain-language door in. Two minutes here and the rest of the site will make sense.

The one-minute version

I’m Jaehong Oh — a robotics engineer and AI researcher (Product Owner for RX at ROBOTIS AI; B.S. in Mechanical Engineering, Soongsil University, Seoul). This site tracks one long question: what do learned systems actually share, and under which typed observables, gauges, interventions, and observers does that claim survive? ULR is the current main programme; SCC and ONN remain as audited historical records, with mathematical and engineering tracks alongside it. I write up not just what works but what doesn’t — including results that turned out to be boundaries rather than breakthroughs.

The programme, in ordinary words

1 · Unified Latent Representation (ULR) — current Main

The active programme asks what structure models truly share, when two representations count as identical, how an observer can distinguish learning from inference, and when organization forms. Canon 24 currently says NOto an additional neural-specific ULR ontology; that negative result is the boundary from which the next tests begin. Begin with the founding Motivation and its self-corrections, then use the ULR research hub and the Canon 24 status.

2 · Soft Cognitive Cohesion (SCC) — historical archive

SCC formalized pre-objective formation through a soft cohesion field and accumulated a sealed 98-claim ledger through CV-1.17. Its mathematics is preserved, but the programme is no longer Main and unresolved integration claims were not carried forward as facts. Read the SCC → ULR transition.

3 · Ontology Neural Networks (ONN) & ORTSF — historical archive

ONN tried to make learned topology a control-theoretic object. Its strong higher-order thesis was audited to a scoped No-Go; modest signals and a scalar stability result survive, while the coupled certificate does not. Read the ONN canonical audit.

4 · RelationWorld, control, and robotics — supporting tracks

Discrete gauge mathematics supplies formal tools; control and robotics supply typed baselines, interventions, and physical test instruments. Browse the foundations, control, and robotics tracks.

If you only read one thing

Read ULR — Current Status, then the complete mathematical flow. Together they separate established claims, negative results, retractions, noncanonical work, and the exact gate for reopening the ontology question.

How this site is written

Evidence first. A claim states what would refute it, and negative results are published, not buried. Banners like “audited”, “superseded”, or “No-Go” are a feature, not a confession — they mark where a thought met reality.
Version-stamped. The theory carries a release number (see the key below) so any claim can be traced to the exact state it was proved in.

Notation key

A handful of shorthand recurs across the notes. This is all of it:

Canon 24: The current ULR canonical reconstruction, aligned with Ledger 105 and Progress #31. SCC's CV-1.17 · historical remains historical.
Ledger 105: The claim-level source of truth. Canon summarizes it but cannot silently promote, restore, or erase a claim.
M1–M8 · NO: The completed ontology decision programme. NO means the current registry shows no incremental neural-specific ULR object beyond typed baselines; it is not a metaphysical impossibility claim.
noncanonical: Post-Canon 24 working evidence. It may contain proved scoped mathematics or useful controls, but it has not been promoted to Canon 25.
Cat A / B / C: Historical SCC proof-strength tiers. Cat A = fully proved; Cat B = proved under a stated structural condition; Cat C = strongly conditional. Retracted = withdrawn.
OP-xxxx: An Open Problem — a tracked, numbered question that is not yet resolved.
W# (e.g. W7): A research week. The notebook is organised into weekly working cycles.
sealed: A version cross-checked and frozen within its named evidence layer. In post-canon working documents it does not imply Canon promotion, Git commitment, or public release.
No-Go: A proved impossibility or boundary — a statement that something cannot be done under the stated assumptions.