traq sounds precise, calm, deliberate, understated and engineered.
Governing Rule.
Anchor before adjective. Mechanism before promise. Evidence before claim.
Use.
- short, concrete sentences;
- named systems and visible actions;
- collect, forward, understand, monitor, check and decide;
- direct acknowledgement of limits;
- one idea per statement or frame.
Avoid.
- hype, urgency and superlatives;
- vague transformation language;
- unlock, revolutionize, dominate and supercharge;
- heroic founder narratives;
- competitor attacks;
- technical explanation without a customer decision attached.
The voice should be confident without dominance, technical without inaccessibility, and restrained without becoming anonymous.
Writing Mechanics.
Write traq in lowercase, including headings and labels. Give each statement one clear idea. Prefer a named action, mechanism or evidence item over a broad adjective. Keep uncertainty visible when it affects the meaning. Use meaningful line breaks without stranding connecting words.
Collect, forward and understand name the current mechanism. Use monitor, check, match and compare only for actions the product actually performs today.
Example Distinction.
Avoid "100% accurate tracking" without evidence. A statement about comparing two named outputs is more specific, but it still needs evidence that the comparison exists in the current product. A restrained tone does not make an unsupported claim true.