Eazler AI Lab AI Engineering Journal

We show our sources

Eazler AI Lab is the AI engineering journal published by Eazler Inc. (주식회사 이즐러). We try new models, tools and protocols ourselves and write up what we find in a form that a one-person studio or a small team can apply directly. We write down trade-offs instead of marketing claims, and when we could not verify something, we say so.

Publisher: Eazler Inc.Frequency: irregularReports in English: 38

1. What we cover

We cover AI agents, coding automation, RAG, MCP, AI development environments, LLM observability and AI marketing. A report usually reads one primary source in full — a paper, an official document, a survey report or an incident investigation — and pulls out what a practitioner can base a decision on.

We do not recommend products or rank tools. When sources on the same topic report different numbers, we would rather set out side by side how their samples, questions and timing differed than declare one of them right.

2. Editorial standards

These are the standards we used to state at the end of individual reports, written down once as standing rules for the whole site.

StandardHow we keep it
Read primary sources in fullFor papers we check the body and the tables, not the abstract; for official documents we read the document itself, not a news summary of it. When we could only check a secondary source, we say so.
Separate source values from derived valuesValues printed in a source's tables are marked separately from values we calculated from them. We do not transcribe values that would have to be read off a chart by eye.
Separate observation from hypothesisWhat was measured and explanations of why are not mixed in one paragraph. A section about causes says up front that it is a hypothesis.
Disclose interestsOur reference tables note conditions such as whether the organization behind a survey sells products in that field and whether responses were voluntary.
Write down what we could not verifyAlmost every report has a "What this is not yet" section. If a report has no measurement of our own, it says so.
No marketing languageInstead of words like "overwhelming" or "revolutionary", we give measured values and the conditions they were measured under.

3. Verification method

Every report states the date its sources were checked near the top. Online documents get rewritten, so a change made to a source after that date is not reflected in the report.

StepWhat it means
Grade the sourcesPrimary sources (papers, official documents, the text of regulations) and secondary sources (news, summaries, blogs) are listed separately in the references table.
State what was checkedThe references table is not a list of links. It has three columns — source / what we checked / scope of the evidence — so that it is clear how far each source supports a claim.
Source every numberEach number names its source right beside it or in a table. Values we calculated from the original are labeled as derived.
Record the limitsWe check sample size, measurement conditions and whether a result can be reproduced, and write down the conditions under which it cannot be generalized.
Own measurements and source reviews: some reports include measurements of our own, such as IPv6 lookups of developer endpoints, Korean classification accuracy of six decision models, and a count of 315 official plugins. Those reports are labeled “Own measurement” on their cards and state the setup, targets and date at the top. The rest compare published papers, documents and measurements against the originals and are labeled “Source review”. We do not run benchmarks to rank products.

4. How we use AI tools

The reports in this journal are made with AI tools. This section says which steps use them and what a person checks.

StepHow it works
Research and draftingAnthropic's Claude searches for topics, checks sources and writes the draft. Claims rest on primary sources (papers, official documentation, repositories) that were opened and read.
Own measurementFigures in reports marked "Own measurement" come from commands and scripts that were actually run. The environment, target and date are stated at the top of the report.
Cross-reviewEach draft is reviewed by a model from another company (OpenAI Codex) in separate passes for facts, attribution and logic, and for language. Findings are applied only after the source is checked again; findings that are not applied are recorded with the reason in the change history.
Automated checksThe site generator checks tables of contents, tables, visible dates, structured data and search titles and descriptions.
Editor checkReports published on or after 2026-10-08 are read by an editor before publication: title, summary, conclusion, key figures and limitations. The date of that check is shown at the top of the report as "Editor checked". Reports published earlier do not carry this mark.
English editionThe Korean original is translated with AI tools, then compared against the original by another model for figures, dates and qualifiers.

5. Corrections policy

If you find a factual error, please tell us at hello@eazler.com. We correct it as soon as it is confirmed.

Type of errorHow we handle it
Factual or numerical errorWe fix the text and leave a correction note with its date in the section concerned. We do not delete what was corrected.
Misreading of a sourceWe narrow the sentence to what the source actually says and note what had been overstated.
Mismatch caused by a change in the sourceWe update the check date and add what changed, keeping the original description as of its date.
Typos and wordingFixed without a note.

When a correction is made, the report's modified date is updated, and the sitemap and feeds follow.

6. Publisher details

PublisherEazler Inc. (주식회사 이즐러)
PublicationEazler AI Lab — AI Engineering Journal
Representative이대성
Business registration no.336-81-03676
Address경기도 시흥시 죽율로 36 (Siheung-si, Gyeonggi-do, Republic of Korea)
Business type / itemInformation and communications / Development and supply of application software
Emailhello@eazler.com

Copyright belongs to Eazler Inc. You may quote our reports with attribution and a link to the original.

7. Contact

Our day job is applying the topics covered here to real systems. For AI agent adoption and automation projects, write to hello@eazler.com.

Questions about a report, corrections and topic suggestions go to the same address.

We also post report summaries on Threads: @eazler.inc.

— Eazler, application software development

8. The English edition

Most reports are written in Korean first, then translated from the Korean original and checked against it before they are published in the English edition. The numbers, dates and references are the same as in the original. Where a report depends on context that exists only in Korea — a law, a service, a market — the English edition explains that context instead of translating it word for word.

Each translated report links to its Korean original, and a correction made to one edition is applied to the other. Some reports are written in English first; they are marked "Written in English, not a translation" at the top and have no Korean original. The Korean edition, where most new reports appear first, is at 한국어.