MZN · LLM AnatomyA1Strong
Data
66 mapped sub-endpoints
Phase 2 · Technical Reference Atlas
21 capability slots. 529 mapped endpoints.
LLM Company Anatomy is a reference map of major capability areas behind a modern LLM company, with MZN's provisional Strong / Partial / Gap self-positioning. It is a technical review baseline — not a validation report and not a claim of frontier-lab parity.
21capability slots
529verified unique sub-endpoints
7 / 13 / 1Strong / Partial / Gap
A5Compute · only current Gap
01 · Capability map
Use the overview first. Open depth only where needed.
The slot labels below are MZN's provisional corpus position. “Strong” means a comparatively strong documented, implemented, internally tested or operating-context basis at that slot. “Partial” means meaningful architecture or context exists but depth, scale or independent validation remains incomplete. “Gap” means no material capability basis is documented in the current corpus.
A · Pre-training Stack
A2Strong
Tokenizer
68 mapped sub-endpoints
A3Partial
Architecture
44 mapped sub-endpoints
A4Partial
Training
35 mapped sub-endpoints
A5Gap
Compute
21 mapped sub-endpoints
B · Alignment
B1Partial
SFT
19 mapped sub-endpoints
B2Partial
Preference Optimization
29 mapped sub-endpoints
B3Partial
Constitutional Methods
18 mapped sub-endpoints
B4Partial
Red-Teaming
23 mapped sub-endpoints
C · Evaluation & Safety
C1Partial
Capability Evaluation
20 mapped sub-endpoints
C2Strong
Safety Evaluation
20 mapped sub-endpoints
C3Partial
Robustness
16 mapped sub-endpoints
C4Strong
Output Safety
11 mapped sub-endpoints
D · Inference & Production
D1Partial
Serving
13 mapped sub-endpoints
D2Strong
Inference Optimization
19 mapped sub-endpoints
D3Strong
Monitoring
15 mapped sub-endpoints
D4Partial
Deployment
12 mapped sub-endpoints
E · Cross-Cutting
E1Partial
Data Governance
17 mapped sub-endpoints
E2Strong
Security
27 mapped sub-endpoints
E3Partial
Privacy
15 mapped sub-endpoints
E4Partial
Compliance
21 mapped sub-endpoints
02 · How to read it
Reference coverage is not production readiness.
What the map is for
It lets a technical reviewer see the capability surface quickly, identify where MZN has stronger evidence, and route into the relevant technical asset or full endpoint atlas.
What the map is not for
It does not establish model-training readiness, frontier compute capability, independent benchmark performance, legal compliance or technical certification.
Phase boundary
Phase 1 operating/product context may support selected slots. The mapped technical formation belongs to the bounded Phase 2 record. Phase 3 is the validation and professionalization boundary.
Reference date
The detailed literature/frontier-practice notes in the full atlas are retained as a May 11, 2026 source snapshot. Time-sensitive technical references should be refreshed during Phase 3 review.
Full technical depth remains available. The 529-endpoint atlas has not been deleted or weakened; it is simply moved one level deeper so first-pass web review does not require loading and scanning the entire reference corpus.