Governance and versions

Brandbook edition 0.24: approved universal two-sided price card 1.0 for season 26/27 registered. Large logo, highlighted Classic kit, adjacent instructor and service panels, and a QR with outer margins. The library includes a native two-page 90 × 50 mm CDR, PDF with 3 mm bleed, previews and complete kit. Text is outlined; CDR verified by reopening. A4 and A3 releases are retained.

Brandbook edition 0.23: print kit 1.0 added for Laplandia guests with 15% off on presentation of a guest card. Two native CDR files — portrait A4 and landscape A3 — include 3 mm bleed and outlined text. The library provides previews, a complete ZIP, instructions and checksums. Colours are RGB with embedded sRGB; convert to CMYK using the printer’s profile at output. Previous approved releases are retained.

Brandbook edition 0.22: universal landscape A3 price list 1.0 approved for season 26/27. The library includes a 300 dpi PNG, JPG and complete source archive. Rental occupies the left two-thirds, with services and offers in the right column. The hotel discount is replaced by ‘One call and everything is OK!’. Approved A4 1.0 is retained as a separate release.

Brandbook edition 0.21: Laplandia price list 1.0 approved in portrait A4. The asset library preserves approved revision v6 as PNG, JPG and a source archive with prices and used assets. Document templates includes guidance and direct links to this release. Issue a new version for tariff or design changes, retaining the approved original.

The first catalogue stage covers Laplandia. Models and lengths are separate from branch offers with manually entered tariffs. Hour limits and checkout time belong to each branch. Carts are saved separately, and history keeps the original estimate. Product imagery, seasons and assortment are illustrative for now; other branches follow in subsequent stages.

The owner is responsible for strategy, promises and network standards. The brand steward maintains guidelines, sources and version history. The branch lead applies the rules on every shift. The shift lead handles exceptional service issues.

Design owns visual materials and templates; development owns tokens, components and the portal. The owner acts as brand steward when no separate steward is assigned. Shift contacts are held in each branch’s operational directory.

Use the current guide and asset library in daily work. Do not change the logo, palette or shared promises at branch level. Update addresses, hours, contacts, assortment and real photographs in designated fields.

Record corrections through repository changes: reason, affected sections and assets, revised rule and branch action. The brand steward checks RU/EN and releases a new edition. Replaced files leave the active library and remain in history.

6 October 2026 · 0.9: all 23 sections audited, shared Manrope and print rules, application tables and verification scenarios. Applications 1.0 provides 33 RU/EN masters, five Mobi poses and team forms. The catalogue finds assets by task, section and format; the design system shows working inputs, errors, states and a dialog. Branch leads receive order, preparation, training and quality forms; suppliers receive dimensions, editable fields and sources.

6 October 2026 · 0.8: Layout 1.0 — fluid shell, 4/8/12 columns, spacing scale and six compositions. Live specimens show actual width, density and guides; the capability matrix identifies browser enhancements. CSS, JSON, standalone RU/EN HTML, SVG grids, instructions and a reproducible kit are available. Website primitives use a single registry.

6 October 2026 · 0.7: Typography 1.0 — Manrope for RU/EN, 12 type roles, a local web font and five desktop weights. The library includes custom-text specimens, prices, tabular figures and enlargement checks; WOFF2, TTF, CSS, DTCG JSON, RU/EN PDFs, licence and sources are available. The website uses the new typeface; branches and suppliers receive shared typesetting and print rules.

6 October 2026 · 0.6: Colors 1.0 — seven brand colours, 20 theme, contrast and accent modes, and independent semantic states. The library includes live website tokens, examples, search and contrast checks, CSS, DTCG JSON, RGB/CMYK ASE, GPL, SVG, RU/EN PDF and a source kit. Branch applications use fixed identity colours; user accents change only the interface.

6 October 2026 · 0.5: SkiMobile Icons 1.0 — 143 symbols, 11 groups, original sport pictograms and shared colour and motion rules. The library includes static and animated SVG, transparent PNG, collections, sprite, sources and licences. The interface uses shared icon components.

6 October 2026 · 0.4: Logo Motion 1.0 — entry, rider carves, exit and full sequence. The library offers web and editing formats with sound and alpha; static logos 1.0 are retained. All public sections are active network instructions.

Each update states what changed and what the branch must do. The lead briefs the team, replaces old materials and records adoption. Staff learn any change to a guest promise before it is used.

1. Learn the meaning of SkiMobile and the three commitments. Find the brand book, branch addresses and responsible contact.
2. Practise fitting and comfort checks. Explain items, period, cost and delivery terms in your own words. Demonstrate preparation and an item readiness record.
3. Role-play delay, replacement, price dispute and condition complaints. Identify the responsible person and next step. The branch lead checks these scenarios before independent work.

1. Record name, resort, address, format, contacts, hours and service provider. Assign a branch lead and shift lead.
2. Check preparation, fitting, handover and returns. Put period, pricing, replacement, delivery and extension rules in the operational price list. Train the team on service scenarios.
3. Apply logo, colour, sign, uniform and wayfinding rules. Check entrance and price readability. Match map listings, QR codes and the website to current contacts.
4. Walk through the guest journey from enquiry to return. Record issues, assign owners and resolve blockers before opening. The lead records branch readiness.

Staff assign every enquiry: record the task, pass it to the shift lead and tell the guest the next contact. An authorised lead decides compensation and exceptions; record the decision, reason and outcome.

The brand book version identifies the shared guideline edition. Kits have independent versions: Logo, Colors, Typography, Layout and Applications 1.0. Copy corrections do not rename old kit files; changes to geometry, tokens or exports release a new kit with a new catalogue and checksums.

Change records contain the reason, new rule, affected applications and branch action. Do not overwrite an externally distributed file under the same version; history directs replaced materials to the current edition.

1. Provide the task, target application, current kit, languages, permitted fields and responsible contact. For print, add dimensions, quantity, material and printer profile.
2. Receive editable sources, final exports, font licences and image provenance. Verify facts, contacts, sources, readability, proofs and actual links.
3. Record the version and network action; leads confirm replaced applications and staff briefing.

Email recipients, SMTP and the Telegram bot are configured through server environment variables. Until configured, the form shows a device-local save. Both live channels are verified before publication. Partial-success retries use only the remaining channel.

The server journal keeps an identifier, checksum and channel results outside the public directory and Git. Catalogue, cart and guest history remain local; a team member confirms availability, handover, return and payment.