A practical guide to the Industry-export menu — how the TOC heading is resolved, when to override it, which depth and typography to pick, and copy-paste AI prompts that produce content the exporter can render cleanly.
The Industry-export menu turns a chat, project bundle or single document into a DOCX or PDF with a generated table of contents. Three settings control the TOC: language, depth, and style. A live preview at the top of the menu shows exactly what the heading will look like in the final file.
Every tool in FabricAI, with a short description, the recommended workflow, and tips you can lift straight into a runbook. Field-level input hints are listed at the end.
Creates a new fabric engagement. You can start blank, or upload RFP/BoM/scoping documents and let the draft generator pre-fill requirements and the document index.
Recommended workflow
Tips
Stages one or more documents in memory and triggers server-side parsing. Progress, page/sheet counts and extracted sections appear in the Import Status panel on the New Project page.
Recommended workflow
Tips
Interactive canvas for laying out spine/leaf fabrics, inspecting racks and editing custom threshold profiles. The 'Open last topology' shortcut jumps back to the most recent canvas.
Recommended workflow
The deliverable catalog (HLD, LLD, BoM, BoD, MOP, etc.). Each project gets a tailored index seeded from imported requirements.
Recommended workflow
Reads server-parsed text from staged documents and infers: customer, industry, scale, technical signals (EVPN-VXLAN, multihoming, compliance, …) and a tailored 9-document plan with rationales.
Recommended workflow
Tips
Shown on /projects/new. Displays per-file parsing status, metadata (pages, sheets, rows), warnings and extracted section headings with previews.
Recommended workflow
Exports the current chat or document set as a polished DOCX or PDF. The Table of Contents heading is auto-translated to the project locale (or the interface language in 'auto' mode), and you can pin the heading per scope so it stays consistent across UI-language flips.
Recommended workflow
Tips
Synthesizes a spine/leaf rail-optimized fabric from GPU count, NIC speed and a deployment profile. Estimates RoCEv2 thresholds (PFC headroom, ECN min/max, DCQCN K) and NCCL job-completion time for common collectives.
Recommended workflow
Tips
Deterministic graph simulator over the canonical FabricBlueprint. Injects link/spine/leaf failures, DCI partition, GPU congestion or maintenance drain and reports reachable nodes, partitions, average ECMP paths and findings (critical/warn).
Recommended workflow
Tips
When the twin reports partitions or thin ECMP, the RCA engine ranks probable root causes (single spine uplink, missing BGP peer, undersized rail) and lists concrete mitigations tied to the affected devices.
Recommended workflow
Tips
Selects a target vendor and converts the canonical FabricBlueprint into vendor-specific artifacts: per-device Juniper set commands, OpenConfig JSON, Ansible playbooks. Other vendors render placeholder stubs you can extend.
Recommended workflow
Tips
Shows the full intent.json (vendor + profile + project + blueprint: devices, links, VNIs, VRFs) so you can audit what feeds vendor rendering before downloading or saving a bundle.
Recommended workflow
Tips
Packages every vendor artifact into {vendor}-{project}.zip with a MANIFEST.json (project, vendor, profile, source) and the canonical intent.json — handy for ticket attachments and offline review.
Recommended workflow
Tips
Saves the most recent generated artifact set to the backend so you can re-download without re-running synthesis. Auto-loads when you re-select the same project/profile/vendor.
Recommended workflow
Tips
Catalogue of EVPN, ESI-LAG, PBR, multicast and edge designs with vendor-specific snippets, dependency checks and verification commands. Used as building blocks inside HLD/LLD documents.
Recommended workflow
OpenAPI-described REST for projects, documents, topology and generations. Keys are workspace-scoped and shown only once at creation.
Recommended workflow
Tips
Landing page after sign-in: recent projects, document statuses, twin runs and AI spend trend.
Recommended workflow
Workspace-level preferences: interface locale, dark/light theme, per-day AI budget cap and notification rules.
Recommended workflow
Interactive 3D rack viewer for elevation review, port density and cable planning. Useful for walkthroughs with field engineers.
Recommended workflow
Tips
Project-scoped IP address management and ASN registry. Tracks parent/child prefixes, per-device allocations and VRF tags.
Recommended workflow
Tips
Visual designer that synthesizes spine/leaf or super-spine topologies from a small spec, with live validation against profile thresholds.
Recommended workflow
Admin view of deep-link resolution outcomes with alert thresholds and webhook delivery history.
Recommended workflow
Lightweight prompt sandbox for architect-style what-if questions outside of a project context.
Recommended workflow
Compares the canonical intent to live device snapshots (NETCONF or agent) and reports drift events with severity, RCA suggestions and alerting.
Recommended workflow
Tips
Continuously syncs NVD + KEV, matches advisories against detected Junos versions, and ranks exposures using a risk model (CVSS + KEV + asset criticality).
Recommended workflow
Tips
Ongoing capacity tracking with linear-regression forecasts, time-to-exhaustion ETAs and AI-proposed expansion BOMs.
Recommended workflow
Tips
Multi-project governance: portfolio with health scores, workspace roles, reusable project templates, engineer utilization and status reports.
Recommended workflow
Realtime project activity feed (postgres_changes over websocket) with @mentions, plus immutable version snapshots that capture documents, drift and CVE state.
Recommended workflow
Project name
Use 'Customer — Engagement' so it sorts well in the dashboard.
e.g. Acme — Fabric Refresh · Globex DC2 Build
Customer
The end customer or internal business unit owning the fabric.
Industry
Drives compliance hints and BoD templates.
Scale
Approximate fabric size — used to size the BoM and MOP windows.
Description
1-2 sentences on goals, constraints and timeline. Auto-filled from imports when available.
TOC heading
Leave blank to use the auto-translated title. Anything you type overrides the language picker.
e.g. Table of Contents · Содержание · Inhaltsverzeichnis
TOC depth
How many heading levels appear. 2 is best for most reports; 3 only for very long documents.
e.g. 1 (H1 only) · 2 (H1 + H2) · 3 (H1 + H2 + H3)
TOC language
Pick a specific language, or keep 'Auto' to inherit from the project locale, then the interface language.
e.g. auto · en · ru · de
TOC heading style
Font family and point size for the heading itself, applied to both DOCX and PDF.
e.g. Sans-serif · 16 pt · Serif · 20 pt · Monospace · 14 pt
Code theme
Syntax-highlight palette for code blocks. 'Light' is safest for printing.
e.g. light · dark · github · monokai
Document version
Shown on the cover and in the audit appendix. Bump on each new revision.
e.g. v1 · v1.0 · v2-draft · rev-A
Export template
Pick a built-in preset or one of your saved custom templates.
e.g. Corporate (default) · Minimal · Technical dense · Formal report
Template name
Used in the picker. Saving while a preset is selected creates a new custom copy.
e.g. Acme corporate · Internal MOP · Customer-facing HLD
Font family
Sans-serif for screen-friendly docs, Serif (Times) for formal deliverables.
e.g. Arial · Helvetica · Inter · Calibri
Base font size (pt)
Body text size. 10–11 for technical docs, 12 for formal reports.
e.g. 10 · 11 · 12
Line spacing
1.0 single, 1.15 comfortable on-screen, 1.5 airy for print.
e.g. 1.0 · 1.15 · 1.25 · 1.5
Margin (inches)
Page margin. 1.0 standard; 0.75 for dense tables; 1.25 for formal reports.
e.g. 0.75 · 1 · 1.25
Cover style
Visual treatment for the first page.
e.g. minimal · bold · technical
Heading color
Hex color (without #) for H1/H2 in the document.
e.g. 1F2937 · 111827 · 0F172A · 8B0000
Accent color
Hex color (without #) for rules, links and key callouts.
e.g. 2563EB · 0EA5E9 · 8B0000 · 374151
Header text
Tokens: {project} {customer} {date}. Leave blank to omit the header.
e.g. {project} · {customer} · {customer} · {project} · {project}
Footer text
Tokens: {project} {customer} {date} {page}. Use {page} to print page numbers.
e.g. {page} · {project} — page {page} · Confidential · {project} · {page}
Image quality preset
Controls DPI of topology snapshots and Mermaid diagrams. Higher = crisper print, larger file.
e.g. screen · print · hidpi
Page size
Used to size embedded images to the printable width.
e.g. letter · a4
Image format
PNG keeps edges crisp; JPEG shrinks dense canvases at a small quality cost.
e.g. png · jpeg
JPEG quality
0.5–1.0. 0.9 is a good default; 0.92+ for customer-facing exports.
e.g. 0.85 · 0.9 · 0.92 · 0.95
Max pixel width
Hard cap on rendered diagram width. If DPI × printable inches exceeds this cap, the image downscales and prints softer. Raise the cap for sharper print, lower it to shrink files.
e.g. 2400 · 4200 · 6000
Worksheets
Pick which sheets land in the workbook. Summary + Inventory cover most reviews; add Conflicts and BOM for procurement.
e.g. Summary · By category · Inventory · Conflicts
Inventory columns
Per-device row columns. Keep Slot/Vendor/Model for audits; add Power/BTU/CFM for thermal reviews.
e.g. Slot · Top U · Bottom U · Vendor
BOM columns
Bill-of-materials roll-up by chassis. Include SKU + Qty for ordering, add Vendor/Category for sourcing.
e.g. SKU · Vendor · Model · Category
Deployment profile
Seeds MTU, oversubscription, RoCE and security baselines. Pick the closest fit, then refine inputs.
e.g. ai-gpu · enterprise-dc · hpc · telco-edge
GPU count
Total GPUs in the cluster. Drives leaves, spines and bisection bandwidth.
e.g. 256 · 1024 · 4096 · 8192
GPUs per server
Per-host GPU count — sets rail width. 8 is the most common (HGX / DGX).
e.g. 4 · 8
NIC bandwidth (Gbps)
Per-GPU NIC speed for the back-end fabric. 400/800 for RoCEv2; 100/200 for storage.
e.g. 100 · 200 · 400 · 800
Cable length (m)
Longest expected run on the back-end fabric. Drives PFC headroom and pause RTT.
e.g. 3 · 5 · 10 · 30
Model size (B params)
Approximate model parameter count in billions. Used to estimate gradient volume per step.
e.g. 7 · 70 · 175 · 405
Collective pattern
Dominant NCCL collective. all-reduce for DP; all-to-all for MoE; all-gather/reduce-scatter for ZeRO-3.
e.g. all-reduce · all-gather · reduce-scatter · all-to-all
Vendor
Target vendor for config rendering. Juniper is fully implemented; others are placeholders to extend.
e.g. juniper · arista · cisco-nxos · sonic
Twin scenario
Failure to simulate. Run baseline first as a control sample.
e.g. baseline · link-failure · spine-failure · dci-partition
Bundle source
'Fresh' re-synthesizes from current inputs; 'Saved' loads the last persisted artifacts for this project + vendor.
e.g. fresh · saved
When language is set to Auto, the exporter resolves the heading in this order:
Once a heading is resolved, it is pinned per scope (chat, project, document) so flipping the interface language mid-session won't silently rewrite your export. To force a re-resolve, change the language picker, then switch back to Auto.
Set the project locale during creation; the export menu will pre-translate the TOC heading and pin it for the rest of your session. Flip the interface language without losing your export settings.
Use Serif at 18–22 pt for executive HLD/BoD deliverables. Use Sans-serif 14–16 pt for engineering MOPs and runbooks read on screen. Monospace 12–14 pt is best for code-heavy appendices.
Depth 2 covers H1+H2 and is enough for 90% of reports. Use depth 3 only when you have stable third-level headings — otherwise the TOC becomes noisy.
The badge under the live preview shows whether the heading comes from your custom override, an explicit pick, the project setting, the interface language, or the EN default. Click it to copy a human-readable string into your clipboard for tickets or release notes.
Effective TOC source: {source} · {lang}
Reason: {tooltip}Ask the AI to write in the same language as your project locale, with explicit H1/H2 levels and short paragraphs — that gives the TOC a clean structure.
Write a Low-Level Design section for an EVPN-VXLAN spine/leaf fabric. Use H2 for each subsystem (Underlay, Overlay, Multihoming, Multicast). Keep paragraphs under 4 sentences. Match the project locale.
If you need to keep body content in English but ship a localized TOC, ask the assistant to translate only the H1/H2 lines and leave the rest untouched.
Translate only the H1 and H2 headings of the document below into Russian. Keep all other text, code blocks and tables exactly as-is.
Paste any of these into the chat (or your own AI assistant) and replace the placeholders. They are tuned to produce content that the TOC generator can index without surprises.
Write a structured technical document on "<TOPIC>". Use exactly one H1 for the title. Use H2 for each major section (no more than 7). Use H3 for sub-sections, max two levels deep. Do not skip heading levels. Keep section titles under 60 characters so they render well in a TOC. Output Markdown.
Write the document in <LANGUAGE> (BCP-47: <LOCALE>). All headings, captions and table titles must be in <LANGUAGE>. Keep code samples, command names and product names in English. The first H1 is the document title; do not add a "Table of contents" heading — the exporter inserts one automatically.
Rewrite the following draft as a formal executive report. - Tone: neutral, precise, third person. - Each H2 starts with a one-sentence summary in italics. - Bullet lists max 5 items; otherwise use prose. - Add an H2 "Recommendations" near the end with numbered actions. Draft: <PASTE DRAFT HERE>
Produce an engineering deliverable with these H2 sections: 1. Scope 2. Assumptions 3. Logical design 4. Physical design 5. Configuration snippets 6. Verification 7. Rollback Under "Configuration snippets", use fenced code blocks tagged with the right language (```junos, ```bash, …). Reference figures as "Figure N — <caption>".
Translate ONLY the heading lines (lines starting with #, ##, ### in Markdown) of the document below into <LANGUAGE>. Keep body paragraphs, code blocks and tables untouched. Preserve the heading level (number of # characters). Return the full document. <PASTE DOCUMENT HERE>
Tabbed routes use a consistent #tab:subsection hash. The part before the colon selects the tab, the part after scrolls to (and focuses) the matching anchor inside that tab. The subsection slug is always required so each link uniquely identifies its destination.
Examples
/ai-fabric#vendor:canonical-intent — Vendor tab, Canonical intent card/ai-fabric#twin:rca — Twin tab, Predictive RCA panel/ai-fabric#roce:roce-baseline — RoCE tab, baseline cardInvalid or unknown hashes fall back to the first tab and surface a warning toast — they never silently navigate to the wrong place.
tab:subsection values#topology:topology-inputsTopology inputs form#topology:synthesized-fabricSynthesized fabric preview#roce:roce-inputsRoCE inputs#roce:roce-baselineRoCE baseline & deltas#jct:jct-inputsJCT inputs#jct:jct-resultJCT result card#twin:digital-twinDigital twin canvas#twin:rcaPredictive RCA panel#twin:twin-runsRecent twin runs#assurance:scorecardScorecard#vendor:canonical-intentCanonical intent viewer#vendor:zip-bundleZIP bundle generator#vendor:saved-bundlesSaved bundles listThe TOC heading didn't change after switching the UI language. That's by design — the heading is pinned per scope. Open the export menu, change the language picker to a specific locale, then back to Auto to re-resolve.
Sub-sections are missing in the PDF. Bump TOC depth from 2 to 3 — only headings up to the chosen depth are listed.
Some headings are in the wrong language. The exporter never translates body content; ensure the source document was authored in the right language. Use the "Translate existing headings only" prompt above to fix this in place.
Need the full tool reference and blog? Sign in to access the in-app help center.