

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://reallyacepeter.github.io/</id>
  <title>Ace's Intelligence Lab</title>
  <subtitle>Explorations in Artificial Intelligence, System Architecture, and Computational Science.  By Ace Lee, Researcher &amp; Tech Entrepreneur.</subtitle>
  <updated>2026-06-01T20:00:26+09:00</updated>
  <author>
    <name>Dong Jun Lee</name>
    <uri>https://reallyacepeter.github.io/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="https://reallyacepeter.github.io/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="https://reallyacepeter.github.io/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 Dong Jun Lee </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Why Similarity Search Requires Representation Learning</title>
    <link href="https://reallyacepeter.github.io/posts/Why-Similarity-Search-Requires-Representation-Learning/" rel="alternate" type="text/html" title="Why Similarity Search Requires Representation Learning" />
    <published>2026-05-26T09:00:00+09:00</published>
  
    <updated>2026-05-26T09:00:00+09:00</updated>
  
    <id>https://reallyacepeter.github.io/posts/Why-Similarity-Search-Requires-Representation-Learning/</id>
    <content type="text/html" src="https://reallyacepeter.github.io/posts/Why-Similarity-Search-Requires-Representation-Learning/" />
    <author>
      <name>Dong Jun Lee</name>
    </author>

  
    
    <category term="AI" />
    
    <category term="Dentistry" />
    
  

  <summary>Introduction  In the previous post, I discussed why forensic dental AI depends on more than just models.  Before a system can learn anything useful, it must first have access to:     Structured dental records   Reliable data governance   Expert-reviewed information   Trustworthy data pipelines   However, another challenge remains.  Even with a well-designed database, how can a system identify r...</summary>

  </entry>

  
  <entry>
    <title>The Real Bottleneck in Forensic Dental AI: Data, Governance, and Trust</title>
    <link href="https://reallyacepeter.github.io/posts/The-Real-Bottleneck-in-Forensic-Dental-AI-Data,-Governance,-and-Trust/" rel="alternate" type="text/html" title="The Real Bottleneck in Forensic Dental AI: Data, Governance, and Trust" />
    <published>2026-05-19T09:00:00+09:00</published>
  
    <updated>2026-05-19T09:00:00+09:00</updated>
  
    <id>https://reallyacepeter.github.io/posts/The-Real-Bottleneck-in-Forensic-Dental-AI-Data,-Governance,-and-Trust/</id>
    <content type="text/html" src="https://reallyacepeter.github.io/posts/The-Real-Bottleneck-in-Forensic-Dental-AI-Data,-Governance,-and-Trust/" />
    <author>
      <name>Dong Jun Lee</name>
    </author>

  
    
    <category term="AI" />
    
    <category term="Dentistry" />
    
    <category term="Software Engineering" />
    
  

  <summary>Introduction  In the previous post, I discussed why forensic dental identification cannot rely only on exact queries.  A missing person identification system does not operate in a clean database environment.  In real forensic scenarios:     Ante-mortem records may be incomplete   Post-mortem findings may be degraded   Dental conditions may change over time   Imaging data may be noisy or distort...</summary>

  </entry>

  
  <entry>
    <title>From Query to Match: Designing a Similarity Engine for Dental Identification</title>
    <link href="https://reallyacepeter.github.io/posts/From-Query-to-Match-Designing-a-Similarity-Engine-for-Dental-Identification/" rel="alternate" type="text/html" title="From Query to Match: Designing a Similarity Engine for Dental Identification" />
    <published>2026-04-20T14:00:00+09:00</published>
  
    <updated>2026-04-20T14:00:00+09:00</updated>
  
    <id>https://reallyacepeter.github.io/posts/From-Query-to-Match-Designing-a-Similarity-Engine-for-Dental-Identification/</id>
    <content type="text/html" src="https://reallyacepeter.github.io/posts/From-Query-to-Match-Designing-a-Similarity-Engine-for-Dental-Identification/" />
    <author>
      <name>Dong Jun Lee</name>
    </author>

  
    
    <category term="AI" />
    
    <category term="Dentistry" />
    
    <category term="Software Engineering" />
    
  

  <summary>Introduction  Most data systems are built around queries.     Input a condition   Retrieve matching records   This paradigm works well when the data is complete and the queries are precise.  However, forensic identification does not operate under such conditions.  In real-world scenarios:     Data is incomplete   Observations are noisy   Records are often inconsistent across time   This leads t...</summary>

  </entry>

  
  <entry>
    <title>Evaluating a Forensic Dental Identification System: From Data Integrity to System Validation</title>
    <link href="https://reallyacepeter.github.io/posts/Evaluating-a-Forensic-Dental-Identification-System-From-Data-Integrity-to-System-Validation/" rel="alternate" type="text/html" title="Evaluating a Forensic Dental Identification System: From Data Integrity to System Validation" />
    <published>2026-04-11T21:10:00+09:00</published>
  
    <updated>2026-04-11T21:10:00+09:00</updated>
  
    <id>https://reallyacepeter.github.io/posts/Evaluating-a-Forensic-Dental-Identification-System-From-Data-Integrity-to-System-Validation/</id>
    <content type="text/html" src="https://reallyacepeter.github.io/posts/Evaluating-a-Forensic-Dental-Identification-System-From-Data-Integrity-to-System-Validation/" />
    <author>
      <name>Dong Jun Lee</name>
    </author>

  
    
    <category term="AI" />
    
    <category term="Dentistry" />
    
    <category term="Software Engineering" />
    
  

  <summary>Introduction  Building a system is only half the problem.  In forensic identification, correctness is not optional. A system that stores dental records is not useful unless it can be trusted under real-world conditions.  This raises a critical question:     How do we validate that a forensic dental identification system actually works?   This post explores the evaluation and validation of a mob...</summary>

  </entry>

  
  <entry>
    <title>The Cost of Over-Optimization: A Decision-Making Lesson from a Real-World Tradeoff</title>
    <link href="https://reallyacepeter.github.io/posts/The-Cost-of-Over-Optimization-A-Decision-Making-Lesson-from-a-Real-World-Tradeoff/" rel="alternate" type="text/html" title="The Cost of Over-Optimization: A Decision-Making Lesson from a Real-World Tradeoff" />
    <published>2026-04-07T09:00:00+09:00</published>
  
    <updated>2026-04-07T20:15:33+09:00</updated>
  
    <id>https://reallyacepeter.github.io/posts/The-Cost-of-Over-Optimization-A-Decision-Making-Lesson-from-a-Real-World-Tradeoff/</id>
    <content type="text/html" src="https://reallyacepeter.github.io/posts/The-Cost-of-Over-Optimization-A-Decision-Making-Lesson-from-a-Real-World-Tradeoff/" />
    <author>
      <name>Dong Jun Lee</name>
    </author>

  
    
    <category term="AI" />
    
    <category term="Decision-Making" />
    
    <category term="Software Engineering" />
    
  

  <summary>Introduction  In many real-world systems, decision-making is framed as an optimization problem.  The objective appears straightforward:     Minimize loss   Maximize outcomes   However, in practice, this approach often produces unintended results.     Optimizing individual decisions does not always lead to optimal system behavior.   This phenomenon—referred to here as over-optimization—occurs wh...</summary>

  </entry>

</feed>


