Albert-yz9yt commited on
Commit
cefe82d
Β·
verified Β·
1 Parent(s): a7814ec

Expand model descriptions: dedicated section for Ultra and Apex, remove tables

Browse files
Files changed (1) hide show
  1. README.md +8 -8
README.md CHANGED
@@ -19,11 +19,13 @@ The model lineup is split into two distinct families with different purposes:
19
 
20
  CORE models are built for **integration into pipelines, agents, and automated workflows**. They follow instructions precisely, produce structured output (JSON, templates, PoC skeletons), and are optimized for tool use β€” not open-ended reasoning.
21
 
22
- | Model | Size | Best For |
23
- |---|---|---|
24
- | **BugTraceAI-CORE-Fast** | Small | Triage, log summarization, quick finding analysis |
25
- | **BugTraceAI-CORE-Pro** | Medium | Long-context investigation, report drafting, exploit-chain review |
26
- | **BugTraceAI-CORE-Ultra** | 27B (Q4/Q6) | Complex tool calls, structured PoC generation, multi-step agentic tasks |
 
 
27
 
28
  > Use CORE models when you need reliable, structured output that feeds into a pipeline or automation layer.
29
 
@@ -33,9 +35,7 @@ CORE models are built for **integration into pipelines, agents, and automated wo
33
 
34
  Apex is built for **deep offensive security reasoning**. It thinks through problems step by step inside a `<thinking>` block before producing its answer, making it ideal for tasks where understanding *why* matters as much as the output itself.
35
 
36
- | Model | Architecture | Best For |
37
- |---|---|---|
38
- | **BugTraceAI-G4-Apex** | 26B MoE (Gemma 4) | Exploit chain design, MITRE ATT&CK reasoning, C2 architecture, WAF evasion research |
39
 
40
  > Use Apex when you need the model to reason deeply about a problem rather than execute a structured task.
41
 
 
19
 
20
  CORE models are built for **integration into pipelines, agents, and automated workflows**. They follow instructions precisely, produce structured output (JSON, templates, PoC skeletons), and are optimized for tool use β€” not open-ended reasoning.
21
 
22
+ **BugTraceAI-CORE-Fast** β€” The lightweight option. Designed for high-frequency tasks where latency matters: triage, log classification, finding categorization, quick field extraction from existing reports.
23
+
24
+ **BugTraceAI-CORE-Pro** β€” Mid-tier capacity. Handles long-context tasks: full report generation from raw findings, code review, exploit-chain documentation, and remediation guidance with context coherence across thousands of tokens.
25
+
26
+ **BugTraceAI-CORE-Ultra (27B)** β€” The most capable CORE model. Based on Qwen3-27B, fine-tuned via SFT on 2,541 curated examples covering bug bounty reports, malware analysis, and WAF evasion techniques. Available in two GGUF quantizations:
27
+ - Q4_K_S with IMatrix (15 GB) β€” recommended for RTX 3090/4090, A4000
28
+ - Q6_K (21 GB) β€” maximum fidelity for A5000/A6000, H100 or custom requantization
29
 
30
  > Use CORE models when you need reliable, structured output that feeds into a pipeline or automation layer.
31
 
 
35
 
36
  Apex is built for **deep offensive security reasoning**. It thinks through problems step by step inside a `<thinking>` block before producing its answer, making it ideal for tasks where understanding *why* matters as much as the output itself.
37
 
38
+ **BugTraceAI-G4-Apex** β€” 26B Mixture-of-Experts model based on Gemma 4, fine-tuned via DPO on elite bug bounty reports, malware research, and WAF evasion techniques. Before every response it produces a full internal `<thinking>` block where it works through the problem step by step β€” making it ideal for tasks where the reasoning process matters as much as the answer.
 
 
39
 
40
  > Use Apex when you need the model to reason deeply about a problem rather than execute a structured task.
41