These are applications of the traq foundation and visual system. They do not imply that final templates for every format exist.
| Format | Guidance |
|---|---|
| Website | Follow the website brief for audiences, structure, page order and actions. Check product facts against current status, then structure a clear problem, mechanism, evidence and action. Use actual assets and meaningful headline breaks. |
| Sales deck / presentation | One argument per slide. Name the customer decision, show a current mechanism and support claims with supplied evidence. Keep diagrams inspectable and secondary text readable. |
| Document / review | Separate observations, evidence, interpretations and open questions. Make sources and decisions easy to scan. |
| Social / ads | One specific idea or evidenced problem per piece. Preserve lowercase naming, original assets and restrained language. Avoid invented results or broad transformation claims. |
| Product interface | Prefer direct, accurate operational labels; keep meaning understandable without colour. Use collected, forwarded, monitored or failed only when that state actually exists in the current product. |
| Founder communication | Explain practical context and limits; keep customer evidence and the product in front. |
| Internal doctrine | Use values, beliefs and principles to guide decisions. More declarative internal language does not become proof of a public product outcome. |
Application artwork, photography, icon family and motion rules remain unspecified where the package contains no approved reference. Use the same voice and identity across formats without inventing an approved template or fixed layout.