01
Use the mathematical association precisely
The word Affine gives a technically informed audience a reason to look more closely, but it does not explain the whole product. A future owner should state what the proposed tool actually does and avoid implying that every spatial operation is an affine transformation. A simple geometric illustration can introduce the theme, provided it is labelled as an illustration rather than a benchmark or implemented feature. The naming advantage is the connection to a recognisable field of ideas. The supporting explanation must still distinguish the field, the proposed use and any later verified implementation.
02
Choose what Core is central to
Core can suggest a reusable library, a shared workspace or a foundational learning sequence. Those are different promises, so the first presentation should choose one as its lead rather than combine all three into an imaginary product suite. If the offer is a library, documentation and small examples would be central. If it is a workflow tool, the user journey and supported handoffs would matter more. For an educational product, the progression of lessons would define the experience. The name has room for these readings, but a launch message needs a specific centre of gravity.
03
Let a diagram explain a relationship
A visual identity could use coordinate frames, connected points or a simple shape shown in two positions. Those elements have a natural relationship to the name and can remain legible on a documentation page or a compact application header. A diagram should explain one relationship at a time instead of layering symbols to look technical. Labels can identify the original and transformed views without suggesting that a picture proves anything about a future engine. This approach gives AffineCore a coherent visual vocabulary while leaving the actual product interface and approved artwork open for development.