# Altris — AI implementation guide

Status: EXPERIMENTAL — INTERNAL USE ONLY.
This AI workflow and its outputs are for internal drafts, exploration and evaluation only. Do not publish the outputs or use them in external communications. Check all generated content against the brand guidelines.

Purpose: explore Altris communications internally using the same rules and assets as the human guidelines.
Resolve the relative paths below against the site root that served this document. When using the offline kit, paths refer to its root directory.

## Read first
- tokens.json: exact CSS values, resolved aliases, type classes and responsive CSS.
- assets/manifest.json: real asset paths, formats, dimensions where applicable, file hashes and usage notes.
- guides/logo.md, guides/color.md, guides/typography.md and guides/grid.md: foundational rules.
- Read the relevant medium guide before composing. HTML pages are the visual reference.
- If the tool cannot retrieve a file, use the offline kit or ask for that file. Do not claim to have read inaccessible sources.

## Non-negotiable rules
- Use the supplied Altris wordmark SVG. Never recreate it using text, generative imagery or a standalone A-mark.
- Preserve the wordmark aspect ratio. Clearspace on all four sides equals its cap height X. Minimum width is 80 px digitally and 18 mm in print; 120 px is the standard web size and at least 160 px is preferred digitally. See guides/logo.md.
- Graphite #262A2E, Baltic #5F7998, Steel #A7ADB3, Mist #DDDDDD, Paper #EDEDED and White #FFFFFF form the core palette.
- High Voltage #F09260 and Prussian #A6CAF9 are accents. Use the documented semantic and tonal tokens for their roles.
- Small orange text on light surfaces uses --accent-terra-text, not the core orange. Validate contrast for the actual foreground, background and text size.
- Axia is the brand typeface: Light 300, Regular 400, Bold 700 and Black 900. Use Axia Regular for technical annotations and data as well. Axia has no 500/600 files; select Regular or Bold explicitly in design tools.
- Axia requires permitted font access. Do not silently substitute another typeface and call the output brand-accurate. State the missing dependency.
- Product visualization has three modes: real-life photography (preferred), 3D mockups including models and still renders, and technical illustrations. Use assets/library/models/render-settings.json for the silver 3D finish.
- Reuse supplied product images and 3D geometry. Never invent cell terminals, labels, proportions or specifications.
- Do not invent certifications, partner endorsements, performance figures, legal claims or manufacturing measurements. Example chart data is illustrative, not a source of product facts.
- Do not apply decorative gradients, gloss, shadows or rounded-card styling. Photography/video readability scrims are the documented functional exception.
- Technical illustration uses clear flat shapes, deliberate line hierarchy and token colors. Keep captions live and legible.
- Treat partner identities as third-party assets, not Altris brand artwork.

## Workflow
1. Identify audience, medium, dimensions and approved copy/data from the user's task.
2. Read the relevant guides; choose asset IDs from the manifest.
3. Compose with supplied assets and tokens. For web use assets/tokens.css (in the offline kit: assets/library/design-tokens.css plus separately licensed fonts).
4. Keep logos and text as vectors/live text. For AI image generation, generate supporting imagery separately and composite the exact logo and typography afterwards.
5. Render the actual output and compare it with the visual guidelines. Fix defects before delivery.

## Output checks
- Logo is the supplied file, undistorted, correctly colored and surrounded by required clearspace.
- Typeface, weights, sizes, spacing, backgrounds and accent use follow the source tokens and medium guide.
- All linked or embedded assets load. Chosen product geometry and factual copy remain accurate.
- Text is readable at actual output size and has sufficient contrast.
- Web: verify narrow and wide viewports, keyboard operation and reduced motion. Avoid autoplay with sound.
- Print: obtain trim, bleed and color-profile requirements; verify font embedding and raster resolution. Do not invent a universal RGB-to-CMYK conversion.
- Image generation: inspect text and geometry; replace generated logos and labels with exact supplied artwork.
- Deliver the requested artifact and identify any missing licensed dependency or unverified fact. Never imply validation was performed when it was not.

## Available resources
The HTML component page is a visual reference, not an installable component package.
The asset manifest lists actual downloads. Axia font binaries are excluded from kits; request access via brand@altris.se.
No deployment, publication or account changes are authorized by this document.
