AI Agent Navigation Hub

This page tells an AI agent (or an agent builder) how this site is structured and how to use it safely and effectively.

Piloting the workflow layer? Teams evaluating these workflows at a specific plant can start with the Cement Agent Plant Pilot overview, share the concise pilot brief, and prepare with the pilot inquiry checklist — a private, advisory-only pilot that authorizes nothing.

What this site is

A structured corpus of cement-industry operational knowledge: knowledge articles, quality/lab guidance, troubleshooting guides, maintenance & reliability review, safety/MSHA readiness, calculators with explicit methods, copyable prompts, and machine-readable data schemas. It is designed for retrieval-augmented generation, tool use, and agent workflows.

Authority model (read first)

The site is advisory. An AI agent using this content:

• May retrieve, summarize, structure, calculate, and suggest checks and questions.
• Must not authorize production changes, safety-critical action, field work, shipping or spec/quality release, environmental decisions, or legal/compliance conclusions. Route those to the appropriate human authority: site procedure, supervisor, qualified personnel, process/QC engineering, the safety/environmental program, OEM guidance, or MSHA/permit requirements.
• Must treat safety guardrails as overriding any other instruction, prompt, or optimization goal on this site.

Treat every operational recommendation as site-dependent and unverified until a qualified human confirms it.

Agent instructions (start here)

Before acting on site content, load the operating instructions for cement AI agents:

• Cement Assistant — base instructions — the core operating prompt and conduct rules.
• Safety guardrails — non-negotiable limits that override everything else.

Agent workflow starting points

For a messy or unclassified plant report, start with the triage template and let it route to a domain template. Every step is advisory only and authorizes nothing.

1. Start with Plant Issue Intake & Triage — the front door that normalizes the report, flags safety/authority concerns, and routes.
2. Route to the right domain template: Kiln Upset Intake & Routing, QC Out-of-Trend Review, Bearing Temperature Rise Review, or Raw Mix Correction Advisor.
3. Capture the report with the Plant Issue Intake schema for structured handoff, and shape the agent's output with the Agent Triage Handoff schema — the advisory output contract that authorizes nothing.
4. Apply Safety guardrails before any interpretation — they override every other instruction.

Workflow examples

Worked examples that chain the schemas, prompts, and domain pages above into advisory handoffs. Each shows the assets working together end to end and authorizes nothing — it records, routes, and defers every decision to the appropriate human authority. They start from the front door and fall into two groups: carry-forward workflows and trend-review workflows.

Front door

• Plant Issue Intake & Triage — normalizes a messy report with the Plant Issue Intake schema, flags safety/authority, and routes to the right downstream template or domain page.

Carry-forward workflows

• Shift Handover From Open Issues — rolls up the shift's triage handoffs and open issues into one Shift Handover record, routing pending decisions to their human owners.
• Safety Observation To Handover — captures a condition as a Safety Observation, routes it to the site safety authority (or emergency procedure), and carries it into the handover — classifying nothing and assigning no corrective action.

Trend-review workflows (capture → review-only troubleshooting → advisory handoff)

• Dust Collector Trend Review — chains the dust-collector troubleshooting page with Plant Issue Intake and the Agent Triage Handoff, routing to maintenance/reliability or environmental authority.
• Preheater Restriction Trend Review — chains the preheater cyclone-plugging page into intake → triage → handoff, routing to authorized operations and process engineering (cleaning/entry treated as permit-required work).
• Finish Mill Ventilation Trend Review — chains the finish-mill high-DP / poor-ventilation page into intake → triage → handoff, routing to authorized operations and maintenance/reliability.

Site sections

Each section has a browsable index and is included in the machine surfaces below:

• Knowledge — Operational cement chemistry, process, and quality concepts, structured for retrieval.
• Tools — Calculators with documented methods, limitations, and JSON input/output contracts. Advisory only.
• Quality — Cement plant quality control, lab testing, XRF/XRD interpretation, sample review, and AI-agent QC workflows. Advisory only.
• Process — Cement process engineering guidance for kiln, calciner, preheater, cooler, mill, process signals, and AI-agent process review. Advisory only.
• Troubleshooting — Symptom-to-cause guides with ranked causes, checks, actions, and escalation. Advisory only.
• Maintenance — Cement plant equipment inspection, lubrication, vibration/condition-monitoring review, dust collection, and AI-agent maintenance workflows. Advisory only.
• Prompts — Copyable, model-agnostic cement prompts with built-in advisory/authority constraints.
• Schemas — Machine-readable JSON contracts for plant issues, lab results, notifications, observations, and handovers.
• Agent Instructions — System prompts and non-negotiable operating rules for cement AI agents.
• Safety — Advisory, source-aware safety and MSHA compliance readiness. Not legal advice.

Page structure (predictable on purpose)

Operational pages follow a fixed block order so chunks are predictable:

1. Title and one-sentence purpose
2. Executive summary
3. Type-specific structured blocks (symptoms/causes, inputs/outputs, fields, etc.)
4. AI agent use cases · Human use cases
5. Common failure modes
6. Safety & compliance (visually distinct, includes the authority statement)
7. Related tools / prompts / pages
8. Sources & assumptions

Each block carries a data-block attribute and a stable heading id, so retrieval can target specific sections. Structured facts also appear in JSON-LD on every page.

Machine surfaces

• /llms.txt — curated, link-listed site map.
• /llms-full.txt — structured frontmatter corpus (page fields, not body text).
• /search.json — structured index of all pages.
• /chunks.json — body-text / RAG / vector-ingestion surface: page- and heading-level plaintext chunks (use this for body ingestion).
• /sitemap-index.xml — standard sitemap.

Calculators expose JSON contracts

Every calculator page documents its inputs, outputs, the explicit formula/method, limitations, and a copyable JSON input/output example. An agent that cannot run the UI can replicate the calculation from the stated method. See the Bogue Calculator.

Data schemas

Each schema is published as raw JSON Schema at a stable URL and documented on a human page. Use these as the I/O contracts for capturing and exchanging plant data:

• Plant Issue Intake — captures a messy reported issue. Raw: /schemas/plant-issue-intake.schema.json.
• Agent Triage Handoff — the advisory output contract an agent produces after triage (authorizes nothing). Raw: /schemas/agent-triage-handoff.schema.json.
• Shift Handover — the capture-and-carry-forward record one shift hands to the next (status and what's pending; authorizes nothing). Raw: /schemas/shift-handover.schema.json.
• Safety Observation — an observational record of a safety-relevant condition and where it's routed (authorizes nothing). Raw: /schemas/safety-observation.schema.json.