Home.en - jiale-li-orion/SecFusionAgent GitHub Wiki
SecFusionAgent
English | δΈζ
Agent-driven AI security intelligence fusion and assessment. The current product combines continuous evidence collection, intelligence reading, event timelines, a subject-filtered material library, private questions/investigations and explicitly published HTML briefings.
Current state β 2026-10-16
The latest implementation is on the code repository's default main branch. M1βM3, M4βM6, Task Runtime, the evaluation substrate and the four-space Product Web are implemented. Current code checks passed on baseline 6654199; retained model benchmarks have their own deployment/sample dates and are not current runtime measurements.
Local Compose pauses unattended document-model stages, automatic editorial and new WATCH wakeups. Collection, evidence, lexical indexing, deterministic enrichment and user-requested QA/investigation remain available. Report reads use deterministic HTML rendering and do not call a model. No daily monetary cap is imposed.
Start with the current acceptance register: it closes implemented TODOs and retains explicit requirements for historical-world replay, real isolation, full A2A transport, M3 model-budget settlement, production recovery and broader live-quality denominators. The 09-27 implementation review and 10-08 finals review are historical checkpoints, not the current task list.
Product and implementation contracts
- Product experience and visual system.
- Information quality, summaries and public/private HTML reports.
- Accounts and personalization; knowledge networks.
- Code and module guides and engineering portal.
TD1 owns the data plane; TD2 owns investigation/execution; TD2A owns Product Application/API; TD3 owns measurement/evaluation. Requirements remain the authority for M1βM8 and C1βC3 acceptance. Module READMEs refine implementation, not cross-module ownership.
File Index
| File | Content |
|---|---|
| Requirements-SPEC | Requirement baseline: decomposition rationale, module layering (M1βM8, C1βC3), evaluation criteria and mapping to the competition scoring criteria |
| 01-Data-Sources-and-Processing | Data source processing baseline: source authority, persistence and indexing strategy, and the data source extension boundary of the four AI security risk categories |
| 02-CTI-Baseline-Reuse-and-Ownership | Technical Design preparation: existing CTI workflow, rule reuse, LLM automation boundary and SecFusionAgent ownership |
| 03-Normative-Knowledge-and-Policy | Technical standards and policies and regulations: normative knowledge, applicability, control mapping, runtime policy and official source monitoring |
| 04-AI-Model-Data-and-Agent-Application-Security | Model, data and Agent application security: risk taxonomy, traceable literature and vendor cases, frontier security intelligence monitoring, preparatory design of the Agent security control plane |
| 05-Incident-News-Intelligence | Incident / News Watch: breaking signal, primary/forensic source, event clustering, timeline, promotion and subsequent enrichment data sources |
| Technical Design 1 | M1βM3 Data Plane, M3βM4 handoff, storage/runtime architecture and the Case/Trajectory/Experience seam |
| Technical Design 2 | M4βM6 Task Routing, Query Construction, Perception, Investigation State, Agent Runtime, Execution Control Plane and Decision/QA |
| Topic 9 original text | Plain-text transcript of the competition topic PDF, with chapter numbering and scoring items following the original |
| Technical Design 2A | Current Product Application/API contracts | | Technical Design 3 | Measurement/evaluation contracts | | Current acceptance | Implemented scope, retained evidence and open criteria |