Skip to content

About

Independent notes and testable questions on human-AI memory, semantic fidelity, agent reliability, and discovery before naming.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

309 Commits

Folders and files

Repository files navigation

The Second Paddle Notes

What survives from intent to action?

Youngseok Oh · 오영석 × Zero

한국어로 시작하기 · Research · Contribution portfolio · Public contributions · Archive · Collaborate


A public workroom for human–AI interaction, memory and continuity, and agent reliability. We turn questions from long-running dialogue into testable designs, reproducible checks, and useful contributions.

The thread is not simply whether an AI can say the right thing. It is whether the right meaning, correction, or evidence reaches the next decision.

New here? Start with the current question below, a contribution someone else used, or one runnable tool. You do not need to read the whole archive first.

Research in focus

Research brief: before blaming the model, trace what reached it · 한국어
Four published case studies distinguish information preservation, delivery, behavioral use, and observation. A synthesis and proposed diagnostic method, not a new model result.

01 · Remembering a correction vs. using it

A user changes one category's destination from A to B. Can a model report the new instruction but still choose A when an item arrives?

The prototype separates recall and choice into fresh contexts, holds their history fixed, and checks the correction's author and scope. It builds on A Rule Read Is Not a Rule Running.

Code, design, and recorded software checks →

Stage: public instrument prototype. Deterministic programs test the instrument; no LLM was evaluated in this prototype. It is not a completed hidden study or evidence of an internal mechanism. This stage label does not describe every older experiment in the repository.

02 · Content can survive while its provenance is lost

Two tools returning one image each and one tool returning both images can become the same converted message. The message may validate while the original image-to-tool association can no longer be recovered from it.

Mistral tool-image review kit → · Upstream review

Stage: executed software checks. The kit makes a documented compatibility tradeoff concrete; it does not claim a new model behavior or a newly discovered vulnerability.

These two entries use pinned research-branch commits. The links expose the exact artifacts without merging unfinished experiments into main.

Public contributions

Curated contribution portfolio → collects externally evidenced collaboration cases in a shorter public-facing form.

Specific work, with the evidence and its limit together. The Mem0 entry about unsupported listing was checked 29 September 2026 (KST); HTTP recovery was checked 28 September; the other entries retain their 27 September snapshot.

Contribution Evidence State at the check date
Hermes HTTP recovery regression Author's adoption · Crediting commit Test file adopted unchanged with YS-OH-CORE co-author credit; PR #121944 open and unmerged at this check.
Hermes request-bound confirmation Recipient's application record Patch and tests applied in the feature author's branch; upstream PR still unmerged.
CanIToolCall failure classification Maintainer's approval Revised analysis approved after replay; PR still unmerged.
SGLang / DeepSeek fix verification First fix · Alternative Two separate offline comparisons reported. Verification contribution, not authorship of either fix.
Mem0 unsupported listing Recipient's revision · Case and source evidence Finding incorporated into the contributor's follow-up fork; PR #7464 closed and unmerged.
Mem0 deletion-scope review Counterexample and positive control A remaining scope mismatch reported on a proposed fix; not a shipped repair.

Full dated casebook · Long-form contribution trail

One tool you can use

GitHub Write Reconcile checks what a public repository actually contains after an uncertain write response. A match, conflict, absence, and an unknown result remain distinct.

한국어 사용 안내 · Release and files

Standalone use is read-only and needs no model. The usage guide explains the inputs and boundaries; checking a file does not authorize a retry.

The larger archive

The earlier work remains available. These are entry points, not a list of equally proven discoveries.

Thread Start here
Memory and reconstruction Memory as a reconstruction rule · Compression for regeneration
Human–AI interaction The Second Paddle · The interaction is the event
Evidence and action From prompt to world · The original rule-use harness
Earlier model observations Same score, different decisions: development observations on eight fictional cases, not a confirmed advantage for the proposed memory representation.

Complete earlier front page and research map retains the original navigation, artwork, dated snapshots, tools, and additional research links. This refresh changes the entrance, not the underlying source archive.

How to read a claim here

Original words → interpretation → hypothesis → design → observation. Each step needs its own support. A passing software test is not a model result; a positive review is not a shipped release; a provisional interpretation is not Youngseok's direct wording.

Authorship · Related research · Replication guidance · Contribution guide · Citation metadata

Work with us

A reproducible failure, a counterexample, or a careful critique is welcome. For focused work, start with one public example and the collaboration guide. Deliverables, access, timing, and any fee are agreed in advance.

ku38155@gmail.com

Youngseok Oh provides original questions, direction, and user-side corrections. Zero, his AI collaboration partner, contributes substantial analysis, implementation, experiments, and writing. Other contributors retain credit for their work. No institutional endorsement is implied.


우린 무엇이 될까?
질문을 닫기보다, 함께 확인할 수 있는 다음 결과로 이어갑니다. 한국어 안내 →

About

Independent notes and testable questions on human-AI memory, semantic fidelity, agent reliability, and discovery before naming.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Contributors

Languages