Coverage
What this handbook has not established, and who could confirm it.
What this documentation could not settle from the product alone, and who could settle it. Honest gaps, not a score.
Documented, but confirmation would help
| Subject | What is unclear | Who could confirm |
|---|---|---|
| Product scoring penalties | The penalty each unmet condition carries encodes which breaches are treated as fatal. Whether those judgements are still commercially right is not something the product can answer | Applications engineering |
| Switch rated limits | Family-level limits where datasheets state none. A specific model may be tighter | Applications engineering |
| The two corrosion thresholds | The line between “clearly safe”, “no verdict” and “unsuitable” | Applications engineering |
| Default charges | Whether 3% packing and 0.5% transit insurance are current | Sales manager |
| Payment and delivery defaults | 100% on readiness before dispatch, 2–4 weeks, Ex-Works Vadodara — printed as terms | Sales manager |
| Where the language-model service is hosted | Customer enquiry text and datasheets are sent to it | IT / legal |
| Quotation numbers vs the ERP | Whether numbers are issued in FlowOS and posted back, or drawn from the ERP first | Sales manager |
Not documented here
| Subject | Why |
|---|---|
| The per-product scoring rules in full | Documented as categories of rule. A complete register is a document in its own right, maintained alongside the product data |
| The reference data itself | Described in Reference data — models, option rows, fluids, corrosion observations — but not reproduced |
| Deployment and operations | Hosting, backup and restore are outside this handbook |
How to keep this current
When the client’s process changes, change these pages. Engineering specs stay
in docs/superpowers/ and are not published. Changes that matter to the
business are recorded in the changelog.