forked from manbo/internal-docs
Markyan04
d8a805c162
Remove the separate "Future Work" section and replace the conclusion header with a combined "Conclusion and Future Work" section. Condense and rephrase the prior verbose future-work discussion into a shorter concluding paragraph that preserves the paper's contributions and reported metrics, and adds explicit future directions: strengthening control-theoretic foundations (structured state-space/causal priors, formal supervisory transitions), expanding to additional ICS/automotive protocols (Modbus/TCP, DNP3, IEC 104, OPC UA, CAN/CAN FD, automotive Ethernet), and enabling controllable attack/violation injection for reproducible adversarial benchmarks. No functional changes to figures or metrics; bibliography remains unchanged.
File organisation
Currently, there are 4 parts of docs:
-
API: contains detailed docs about API designs. (Note that
system_design.mdis a temp draft for discussing high-level design, not for API definitations). -
knowledges: contains theorical knowledges/designs for the project (mainly diffusion stuffs).
-
notes4coding: contains deatiled description for coding, may be useful to coding agents (like codex).
-
papers: contains useful papers we've found in pdf
Here is the Feishu Docs link: https://my.feishu.cn/wiki/Za4dwCsG6iPD9qklRLWcoJOZnnb?from=from_copylink