diff --git a/README.md b/README.md
index e054552..56d95f3 100644
--- a/README.md
+++ b/README.md
@@ -1,65 +1,3 @@
-**CUI**
+想定文件结构介绍
 
-# aea_iads demo
-
-This directory contains the necessary files to test the EW effects
-in a scenario similar to the iads_demo baseline scenario.
-
-The SOJ and EW_Radar have EA and EP techniques, respectively, with them
-to aid in the testing and verification of these techniques.
-
-The strike.txt file is the normal input file to run the simulation
-as a single application. The replay file will be written to the
-output directory.
-
-Also included are two realtime run files strike-rt.txt and iads-rt.txt
-that can be run concurrently to test the jamming and EW effects over DIS.
-Each WSF application communicates over DIS. The applications can be run
-on separate hosts or on the same host.  The file dis_data.txt provides
-the DIS Enumeration mapping for the entity types, emitter types, and ew
-technique types.
-
-To visually monitor the progress of the realtime simulations, Warlock can
-be opened and then configured to monitor multicast address 224.2.25.55, 
-port 3225 via an input file containing a dis_interface block.
-
-## CUI Designation Indicator
-* Controlled by: Air Force Research Laboratory
-* Controlled by: Aerospace Systems Directorate
-* CUI Categories: CTI, EXPT
-* LDC/Distribution Statement: DIST-C
-* POC: afrl.rq.afsim@us.af.mil
-
-## Notices and Warnings
-
-### DISTRIBUTION STATEMENT C
-Distribution authorized to US Government agencies and their contractors;
-Critical Technology, Export Controlled; (2021 Oct 06). Other requests for this
-information shall be referred to AFRL Aerospace Systems Directorate.
-
-### NOTICE TO ACCOMPANY FOREIGN DISCLOSURE
-This content is furnished on the condition that it will not be released to
-another nation without specific authority of the Department of the Air Force of
-the United States, that it will be used for military purposes only, that
-individual or corporate rights originating in the information, whether patented
-or not, will be respected, that the recipient will report promptly to the
-United States any known or suspected compromise, and that the information will
-be provided substantially the same degree of security afforded it by the
-Department of Defense of the United States. Also, regardless of any other
-markings on the document, it will not be downgraded or declassified without
-written approval from the originating U.S. agency.
-
-### WARNING - EXPORT CONTROLLED
-This content contains technical data whose export is restricted by the Arms
-Export Control Act (Title 22, U.S.C. Sec 2751 et seq.) or the Export
-Administration Act of 1979, as amended, Title 50 U.S.C., App. 2401 et seq.
-Violations of these export laws are subject to severe criminal penalties.
-Disseminate in accordance with provisions of DoD Directive 5230.25.
-
-### HANDLING AND DESTRUCTION NOTICE
-Handle this information in accordance with DoDI 5200.48. Destroy by any
-approved method that will prevent unauthorized disclosure or reconstruction of
-this information in accordance with NIST SP 800-88 and 32 C.F.R 2002.14
-(Safeguarding Controlled Unclassified Information).
-
-**CUI**
+基本结构
diff --git a/doc/diary/2025年12月3日.md b/doc/diary/2025年12月3日.md
new file mode 100644
index 0000000..3d37eaa
--- /dev/null
+++ b/doc/diary/2025年12月3日.md
@@ -0,0 +1,35 @@
+# 开发步骤
+
+直接找人吧，重点是把场景搭建出来，需要知道差在哪里
+
+1. 定义出来，我写个模版，内容是怎么出来的，按照什么格式出数据
+2. 
+
+# 定义模版
+
+不允许存在继承（方便内容开发）
+
+# 我的问题
+
+1. 行为有啥区别？ 总共就三个？
+2. base_types ： 用到了什么，必须要提供给谁？如果没有了会影响到什么？
+3. 根目录的内容：
+4. 4个模版是怎么回事？我需要看看数据
+5. 通信怎么实现的
+6. 有没有介绍性的文档（我需要知道afsim 中的平台在场景中是怎么映射上的）
+7. 我需要删除不需要的内容（因为我需要提供给另外一个单位一个模版，这个模版需要是能解释的，当然也可以存在一些依赖库性质的内容，但是这些内容需要进行正确的解耦，不能说散在各个地方，比如说base_types 一个文件夹，是一个依赖，我们就不需要对他进行解释，但是不能每个文件夹下都有这种依赖（删掉没用的，实在删不掉，集中存放）
+8. patterns？platforms 删掉没用的平台，processors （是不是基本没用过）
+9. scenarios ，blue 和red 分类很好，但是其他的几个是干啥的？
+10. 雷达的使用情况
+11. signature
+12. weapons 这个省下来，应该是不用动
+13. 根目录下总调
+# 总结如下
+检查每个文件夹下，没用到的东西（因为后面需要用程序生成程序，不能这么混乱
+
+平台的使用，正常的情况下，一个武器应该是能够挂载在多个平台上面的，wj 的处理方式是新建，新建每一个平台，对应的武器名字加上平台的前缀。
+
+根目录精简，最后精简到一个，但是为了方便代码立即，可以适当减少修改
+
+
+