tinysocs-external-positioning

Check the claim against the banned/quotable/internal-only validation numbers table and the reproducibility standard. A public number must trace to a specific run artifact, git commit, and pack version, and the public dashboard must reflect the same run being quoted.

State the triad exactly: 19 rules enabled in the pilot base pack 2026.27, 39 defined in the C# engine, and 89 including the 50-rule Python roadmap catalogue. Never say 89 rules without qualifying that only 19 run detections in a shipping install.

No, 88.9% is internal-only as of 2026-07-11. Its source doc requires targeted runs for four environment-limited rules first, and the stale public dashboard showing 53.85% must be rebuilt before the number ships externally.

No. Pricing is locked until after the first cohort of customer conversations, with no price numbers permitted in any doc, schema, or page. Only competitors' own public list prices may appear in the comparison matrix.

Do not use it to rebuild the public validation dashboard, define evidence standards for new detection rules, decide change-control scope, or explain rule engine mechanics. Those belong to the validation-publication, validation-and-QA, change-control, and detection-engineering skills respectively.