Sentence Start Numbers Composition Rule Checker
Simple explicit sentence-start digit flag versus caller style choice; quotes/signs, year exceptions, sentence segmentation and rewriting omitted.
Description
Sentence Start Numbers Composition Rule Checker: return starts with ascii digit, caller style review.
A style rule may treat a sentence beginning with a numeral differently from other number occurrences. This check targets the start of the supplied text.
This tool returns starts with ascii digit, caller style review. Use the stated units and model convention when interpreting these fields.
When to use this tool
Use this tool when the supplied inputs match the specific operation described above and you need a repeatable result under its stated convention.
- Check the supported input and output contract against an existing calculation or observation.
- Use the complete example to confirm units, selector spelling and result interpretation.
How to use the tool and how it works
- Enter every field in the input table using the stated units and the exact supported selector spelling where applicable.
- Run the tool. Correct input errors before interpreting an output.
- Read the result fields below; use accompanying flags and the stated sign, boundary or model convention when interpreting a number.
Ignore leading whitespace and test whether the next character is an ASCII digit. Request style review only when such a start is present and the caller does not allow it.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sentence | Sentence. | Text |
| callerAllowsDigitStarts | Caller allows digit starts. | true or false |
| Output field | Interpretation |
|---|---|
| result | Object containing the following named result fields. |
| result.startsWithAsciiDigit | Starts with ascii digit flag under the exact conditions described above. |
| result.callerStyleReview | Caller style review flag under the exact conditions described above. |
{
"input": {
"sentence": "12 people arrived.",
"callerAllowsDigitStarts": false
},
"output": {
"result": {
"startsWithAsciiDigit": true,
"callerStyleReview": true
}
}
}Limitations and assumptions
- The tool does not identify sentence boundaries or recognize every Unicode numeral.
- Every declared field is required and unexpected fields are rejected. Numeric inputs must be finite; input errors are distinct from a valid false result or an explicitly qualified output.
- Extremely large inputs and nonfinite or excessively large outputs are rejected. List positions reported by the tool use zero-based indices unless stated otherwise.
Alternative or Complementary methods
Check the underlying observations, units and conventions independently before using the result in a larger workflow. The tools listed below address nearby tasks; compare their inputs and scope before substituting one for this operation.
References
Similar or alternative tools
- acronym first use spelled out rule checker
First-use acronym checks need an explicit full name and exact house-style form.
- cherry picked start date trend splice warning checker
Selected and full-window trends can differ in sign.