Wang Jianjun
All projects

LabMemory · Trusted Experiment Memory

Check evidence, version and scope before reusing an experimental conclusion.

I led a three-person team designing human confirmation, pre-action review and experiment feedback for trusted memory.

View diagram (swipe sideways)
DISCUSSION → TRUSTED MEMORYLabMemoryDiscussionTranscript · candidatesHuman reviewSource · extracted · confirmedVersioned claimEvidence · scope · ownerPre-action auditAllow · review · blockExperiment resultSupport · revise · refuteFeedback loopRevisit the claimARCHITECTURE ILLUSTRATIONWJ / SELECTED WORK
Captain · Product & Trusted MemoryTeam: 3Aug – Sep 2026GitHub
ReactFastAPIMCP+2

Key results

  • Annual Top 40 in the 2026 AI Pioneer Future Talent Competition; finished at the South China stage
  • Human confirmation, versioned memory, pre-action audit and experiment feedback

Problem and role

Lab discussions mix established evidence, provisional hypotheses and parameters that still need verification. Reusing that discussion as settled knowledge can propagate outdated or unconfirmed conclusions into later experiments.

I led a team of three and owned product and trusted-memory design for the XtalPi challenge. LabMemory finished in the annual Top 40 of the Feishu × DI-IDEA competition. The competition is complete, and the project is retained as an engineering case study.

From discussion to action

Inside the workflow

Carry evidence from discussion to action

Move from meeting statements through human review, versioned memory and action audits, then feed results back into claims.

Results update claim state01DiscussionMINUTES / TRANSCRIPT02Compile decisionsCANDIDATES / EVIDENCE03Human reviewSOURCE / EXTRACT / CONFIRM04Versioned memoryCLAIM / VERSION / SCOPE05Pre-action auditALLOW / REVIEW / BLOCK06Result feedbackSUPPORT / REVISE / REFUTE
Pre-action audit
01 / 06

Discussion

Preserve original statements from Feishu minutes or transcripts as the source for extraction and review.

Input
Minutes and original statements
Output
Source-linked discussion

Open-source architecture illustration; repository demo data is synthetic.

Three state transitions

1

Discussion → candidate claim

Extract conclusions, parameters and tasks while retaining their sources. Keep original records, model extraction and human confirmation separate.

2

Human confirmation → versioned memory

Attach evidence, version, state, scope and ownership to confirmed claims. Preserve earlier versions when a conclusion changes.

3

Experiment result → evidence update

Record supported, refuted or partially supported outcomes. Return failure conditions and applicability boundaries to the claim.

Three audit outcomes

OutcomeActionEvidence presented
AllowProceed within the current conditionsClaim version and supporting evidence
ReviewRequest human review firstDisputes, missing evidence or unresolved conditions
BlockStop relying on this claimVersion, prerequisite or scope conflicts

The audit checks versions, disputes, evidence, prerequisites and boundaries. Experiment passports connect the decision to subsequent execution. MCP tools and Feishu entry points expose this workflow to agents and collaborators.

Implementation and evidence

The repository contains React, FastAPI, MCP tools and Feishu integration. Its demonstration uses synthetic data to illustrate product behavior; it does not establish real laboratory outcomes or business impact.

Code and setup instructions: LabMemory.