AgroNutikas Design System v9.0

A field entry, a dense operator workspace, a map view and a client-facing website need different levels of information. AgroNutikas Design System v9.0 is a consolidation release that treats nine surfaces separately: marketing web, field app, investor portal, Admin/Ops, print/PDF, slides and video, social, motion, and map/GIS. Their vocabulary, states and provenance rules stay connected, so a phone and a report are not forced into one compressed layout. This describes the design rules' scope, not the production maturity of every surface. [1] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

v9.0 does not redraw the system. Admin/Ops is now a fully specified surface with 15 screens, and four token layers have been added: motion, ops, map/GIS and editorial. No existing token value changed and v8.1 is preserved, so earlier work needs no colour migration. [3] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

The field-entry question is simple: what happened, what was saved and what must the person do next? The offline-state rule asks for a clear message and action even when the connection fails. The specimen illustrates that rule with local sample data; it does not measure production sync reliability. [4] Proposal · v9.0 rulebook · reviewed 17 Oct 2026

Sample data · a local field-entry illustration derived from v9.0 rules. Visitors can compare allowed, warning and blocked decisions with an example offline message. All four states, their rules, next actions and evidence limits remain visible without JavaScript; an active browser can highlight one state. This page does not save, submit or sync an entry. It must not be read as an actual farm decision or a live rules-engine response. [4] Proposal · v9.0 rulebook · reviewed 17 Oct 2026 Every state presents a word, an icon and colour together. [1] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

The specimen colours come from the field app's dark mode: deep earth #060807 with a green undertone, white headings and a green focus ring. v9.0 left these values unchanged. [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 When connectivity is absent, the message should say that the entry is saved on the device and offer a way to continue with a local draft. If another device edits the same record, a conflict needs a separate comparison; “saved on device” is not “synced to server”. These are example states from rulebook section 23, not confirmation of production sync. [4] Proposal · v9.0 rulebook · reviewed 17 Oct 2026

The specimen ends with a motion plate. Its table computes five durations in three audience perspectives, three timing curves are drawn from their control points, and only the stepper curve overshoots its target. An expandable lab lets you choose the audience, the curve and the motion scale and run a reveal of six field cards; under reduced motion the cards are in their end state at once. The values come from the motion system token file, not from the field app code. [3] Design reference · Motion token file · reviewed 18 Oct 2026

The marketing mood is a field manual. The ground is warm cream #FAFAF7 rather than pure white, because it causes less glare. Headings use Archivo, borders are 1.5 px lines in ink #0A1A0C, corners are sharp, the shadow is a 3 px ink offset and corner markers frame blocks as in a printed guide. That surface carries proof and one invitation to explore the pilot, not gloss. [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [3] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

The field app is the second mood: light grows from darkness. The ground is deep earth #060807 with a green undertone, not pure black; type is Outfit and Inter, cards have 18–24 px rounding and a soft bioluminescent glow replaces the shadow. The screen presents state first, then context, next action and evidence when needed. It has one primary action, and a control intended for gloved use targets at least 56 px. [1] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

The investor view is a dense trust surface, with confidentiality and data timestamps beside the figures. Admin/Ops is a separate operator workspace of 15 screens: welded hairlines, a 13 px base size and zero glow, because an operator reads a table, not a mood. It does not copy the field app's large controls. Both are reference surfaces, not a public data room or live operator data. [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [3] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

Print/PDF uses a light paper surface and labels that remain legible in grayscale. Slides and video use a dark presentation stage, and social uses platform-specific aspect ratios with a brand overlay on approved imagery. The editorial layer is a separate token layer for longer content. These are v9.0 export and presentation rules, not client files published by this page. [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [1] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

Status is always colour, icon and word together, never hue alone. Colours carry Estonian element names such as mets, talinisu, oht and muld, so design and field work share one vocabulary. An allowed field entry lets the person continue, a warning asks for an additional check and a block explains the reason and a recoverable path; a conflict is never silently overwritten. [1] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [6] Proposal · v9.0 rulebook · reviewed 17 Oct 2026

Motion durations are computed: a base value multiplied by a motion scale and a perspective scale. The farmer perspective runs at 0.66 times the duration and the investor perspective at 1.3 times, and the reduced-motion preference is honoured. On the map, a parcel status is always stroke, fill and legend word together, never fill alone; the gold selection colour stays distinct from status green, and source, time and the forecast boundary remain visible. [5] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

Contrast is computed with the WCAG 2 formula from the v9.0 token values. In marketing, field, ops and print modes every text-role pair reaches at least 4.5:1: body text on cream 11.0:1, muted text 6.7:1 and field app body text 16.4:1. One exception is stated openly: white text on the amber marketing button gives 3.2:1, so it is for large text only. [4] Observed · Contrast computation · reviewed 17 Oct 2026

The v9.0 rulebook and colors_and_type.css v9.0 are pinned by SHA-256 hashes; they support selected design rules, tokens and examples. They do not establish current AgroNutikas-APP production behaviour, real field data or the maturity of every component. [1] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [2] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 All field-entry data in this deep view is sample data. [5] Proposal · v9.0 rulebook · reviewed 17 Oct 2026 The system's documentation can also be browsed as an interactive platform: 14 chapters, 16 components in six groups as static previews, and role tokens in four modes (web, app, ops, print). [3] Design reference · Design-system documentation · reviewed 22 Oct 2026

Governance is part of the system: semantic versioning, migration guides, a design debt register of 12 items with 9 resolved and 3 open, a component maturity matrix, an AI implementation contract and a QA script list. They describe how the system is changed and checked; they are not a claim that every check is currently green in the product. [4] Design reference · v9.0 rulebook · reviewed 17 Oct 2026

An older case gallery contains V9 pilot-package images whose capture dates are unverified. The V9 pilot package and the v9.0 rulebook are different things, so we do not use those images as v9.0 screens or dated production proof. Versions and data layers remain separate until the images' provenance is checked. [6] Design reference · Case gallery · reviewed 24 Sept 2026

If your product spans several work contexts, we can map the states of one real journey, define rules for phone and wider screens and build a clearly labelled local specimen. Handoff includes a state vocabulary, control measurements, a contrast calculation, provenance labels and verification questions; production integrations require separate scope. [1] Design reference · v9.0 rulebook · reviewed 17 Oct 2026 [2] Proposal · v9.0 rulebook · reviewed 17 Oct 2026

When you contact us, describe a situation in which someone cannot tell whether work was saved or what to do next. We can start with that state and mark what is observed, what is reference and what still needs implementation. [2] Proposal · v9.0 rulebook · reviewed 17 Oct 2026