Platform detection
Flowpane stores customer declaration and independent observation separately. Observation can support bounded guidance; it does not overwrite the declaration or establish which system/plugin manages an artefact.
How detection works
During the first governance check, Flowpane analyses:
- HTML meta tags — the
generatormeta tag - Response headers — server and powered-by indicators
- Asset paths — CSS/JS paths indicating specific platforms
- HTML patterns — structural patterns characteristic of specific platforms
Selection boundary
The detector derives content, commerce, frontend and delivery evidence independently. A persisted compatibility primary requires vendor-valid, non-conflicting evidence at confidence 0.65 or above and is selected content, then commerce, then frontend. Delivery is never eligible. Material same-dimension conflicts suppress selection.
Confidence level
Confidence belongs to the selected primary, not the combined technology stack. Low-confidence, delivery-only, conflict, blocked and acquisition-failure outcomes do not create a new platform observation.
Correcting the platform
If the customer declaration is wrong, change it in Site metadata. A high-confidence mismatch between declaration and observation produces generic guidance without changing factual artefact status or scoring.
Joomla and WordPress connections are supported in reviewed environments; access and management depend on the Site entitlement and current capabilities.