Demo: Document Process Sentinel demo assumptions

[smithaldon1]

Purpose

Make clear what the demo proves and what it does not prove.

Acceptance Criteria

• Docs explain the demo detection rule.
• Docs explain the synthetic nature of the data.
• Docs explain that this is not production validation.
• Docs explain that recommendations require human review.
• Docs identify post-demo improvements.

Dependencies

Expected demo detection behavior and detection copy polish.

Out of Scope

• Full Process Sentinel architecture rewrite.
• Validation package.
• Real plant deployment guidance.

Test Plan

• Run make docs if available.
• Manually verify documented assumptions match the current rule behavior.
• Confirm post-demo language aligns with ROADMAP non-goals.

Documentation Impact

Update docs/demo/ or Process Sentinel docs with demo assumptions and limitations.

Suggested Labels

demo-critical, process-sentinel, documentation

Milestone

Demo Ready

Parent Epic Link

#119

Recommended Project Status

Ready

Demo Critical

Yes

[smithaldon1]

UI/UX demo planning pass note: this issue appears mostly satisfied by the current checkout through services/process-sentinel/README.md, docs/DEMO_RUNBOOK.md, and the manufacturer/Workbench demo runbooks, which now document simulator-backed data, deterministic rule assumptions, advisory recommendations, and post-demo limitations.

Recommended next action: verify the current docs on the target branch after PR #172/#178 settle, then close this issue if no additional Process Sentinel assumption copy is missing. Do not create a duplicate UI copy issue; use #175 for broader demo-safe terminology.