Security and Operating Boundaries
Security depends on separating public documentation from private product material, limiting capabilities to approved scope, and keeping qualified people responsible for consequential engineering work.
Security principles
Product source, credentials, license material, customer data, and simulator files stay outside the website.
Modes, workspaces, authentication, and deployment policy restrict what can operate.
Only authorized project data required for the task enters the workspace.
Qualified personnel review inputs, assumptions, calculations, and simulator outputs.
Responsible use
- ✓Verify engineering basis
Check units, thermodynamics, specifications, constraints, and convergence.
- ✓Preserve formal processes
Do not replace HAZOP, SIL, management of change, process safety, or required sign-off.
- ✓Treat uncertainty explicitly
Missing sources, conflicting evidence, model mismatch, and unknown conditions require resolution.
Website analytics
- ✓Aggregate by default
The website operator uses Cloudflare zone analytics for request volume and approximate unique visitors without adding a visible counter to the site.
- ✓No custom visitor profiles
The website does not implement its own fingerprinting, advertising tracker, or per-visitor database.
- ✓Operational separation
Analytics and security telemetry remain in the Cloudflare account and are not committed to the website repository.
Infrastructure providers process request metadata to deliver and protect the site. The operator should keep the public privacy statement aligned with the analytics actually enabled.
Public website boundary
Anything shipped as HTML, CSS, JavaScript, text, or images is delivered to the visitor's browser. Sensitive product material must never enter the website project.