Examples
These examples apply FTL to real Fenexity-style technical prose. Each one shows a “before” version and a controlled “after” version, and explains what changed.
Example A — vague adjective
Before
The edge solution is more robust.After
The edge controller continues to enforce the site power limit if the cloud connection is unavailable.What changed: the vague comparative “more robust” was replaced with a specific behavior (FTL-W08).
Example B — ambiguous term
Before
The charger reports its status.After
The EVSE reports its operational status.What changed: “charger” is ambiguous (EVSE, charging station, connector, power electronics). The revised version is only valid if EVSE is genuinely the intended concept (FTL-W15).
Example C — modality
Before
The service should keep the last valid plan.After, if normative
If the optimizer is unavailable, the service MUST retain the last valid charging plan.What changed: the condition moved before the action (FTL-W04). The author must explicitly decide whether this is a requirement; the rewriting tool must not invent MUST (FTL-W11).
Example D — quantity
Before
The battery has a capacity of 400.After
The battery has a nominal energy capacity of 400 kWh.What changed: the quantity and unit are explicit (FTL-W09), and the semantic type (energy capacity, not charge capacity) is named.
Example E — intent
Before
The dispatcher needs a button to start charging manually.Structured interpretation
Request:
Provide manual charging control.
Inferred intent:
Enable the dispatcher to recover charging operations when automatic control does not
produce the required operational state.
Status:
The inferred intent requires validation.What changed: the mechanism (a button) is separated from the intent, which is marked as inferred (FTL-W12).
Example F — meeting summary
German source
Wir wollen eigentlich nur vermeiden, dass morgens irgendein Bus nicht rauskommt,
weil er nicht genug geladen ist.Controlled summary
Customer intent:
Avoid missed morning departures caused by insufficient vehicle charge.
Open definition:
The required departure-readiness criteria are not yet defined.What changed: the summary preserves intent and explicitly marks what is still undefined, instead of inventing a requirement.