LEISSONCREATIVE

All systems / agronutikas

AgroNutikas Design System v8.1

Design rules for seven surfaces and field-entry states using local sample data. V8.1 rules, V9 pilot images and production behaviour are separate evidence layers.

Showcase: Design System v8.1Material status: Design reference

Observed means a dated check of a public or versioned artifact. Design reference describes a rule or prototype. Proposal does not establish production behaviour. Each inline marker points to its specific source.

One product, distinct work contexts

A field entry, a dense operator workspace and a client-facing website need different levels of information. AgroNutikas Design System v8.1 treats seven surfaces separately while connecting their vocabulary, states and provenance rules. For a client, that means 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 · v8.1 rulebook · reviewed [2] Design reference · v8.1 rulebook · reviewed

The field-entry question is simple: what happened, what was saved and what must the person do next? The v8.1 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. [3] Proposal · v8.1 rulebook · reviewed

Full source references
  • [1] design-8-1-reference · AgroNutikas Design System Rulebook v8.1, commit 64ecdd23f8f4ba23b1fba87758f836cdfd2886df
  • [2] seven-surface-matrix · AgroNutikas Design System Rulebook v8.1, section 15
  • [3] field-entry-states · AgroNutikas Design System Rulebook v8.1, sections 02/23/25; local illustrative data

A field-entry specimen

Sample data · a local field-entry illustration derived from v8.1 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. [2] Proposal · v8.1 rulebook · reviewed Every state presents a word, an icon and colour together. [1] Design reference · v8.1 rulebook · reviewed

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. [2] Proposal · v8.1 rulebook · reviewed

Full source references
  • [1] design-8-1-reference · AgroNutikas Design System Rulebook v8.1, commit 64ecdd23f8f4ba23b1fba87758f836cdfd2886df
  • [2] field-entry-states · AgroNutikas Design System Rulebook v8.1, sections 02/23/25; local illustrative data
Sample data · v8.1 field-view rule illustration · no real field connection

Four fixed examples show status, next action and evidence limit. This page does not save or submit a field entry.

Highlight one state

Allowed

Sample field A · task type and date are filled in.

Next action
Review the entry. No real record is saved here.
Rule
Illustrative rule: task type and date are present. §25.05 defines the display order of state and action.
Evidence limit
Local example; no production rules-engine decision has been verified.

Warning

Sample field A · entered amount needs checking against its source.

Next action
Compare the amount with its source before continuing.
Rule
Warning remains visible as word and icon · §02.
Evidence limit
The amount threshold is not farm data or a verified production rule.

Blocked

Sample field A · the task date is missing in this example.

Next action
Add the date and review the entry again.
Rule
Illustrative rule: a missing date pauses the entry. §25.05 defines display order.
Evidence limit
The block illustrates a rule; it is not a real account or legal decision.

Offline

Sample field A · an example of lost connectivity.

Next action
Continue composing a draft; this page neither saves nor syncs it.
Rule
“No connection. Save on device.” · §23 reference wording.
Evidence limit
Local state illustration; on-device storage and later sync have not been tested.

Decisions and rules

The seven surfaces start with different jobs. Marketing web uses warm light ground, Archivo headings, proof-led sections and one invitation to explore the pilot; the field app uses a dark data surface, visible sync state and a gloved primary action. Sharing a brand does not require these surfaces to share density or one component. These are v8.1 surface rules, not a claim that both have equal production maturity. [2] Design reference · v8.1 rulebook · reviewed [1] Design reference · v8.1 rulebook · reviewed

The investor view is a dense trust surface, with confidentiality and data timestamps beside the figures. Admin/Ops is a separate operator workspace where dense 40–44 px rows, navigation groups and decision factors support review; 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 · v8.1 rulebook · reviewed

Print/PDF uses a light paper surface and labels that remain legible in grayscale rather than hover or dark-screen colour differences. Slides and video use a dark presentation stage where motion supports the message and reduced motion has a static path. Social uses platform-specific aspect ratios and a brand overlay on approved imagery instead of a generic campaign template. These are v8.1 export and presentation rules, not client files published by this page. [2] Design reference · v8.1 rulebook · reviewed [1] Design reference · v8.1 rulebook · reviewed

An allowed field-entry state lets the person continue; a warning asks for an additional check; a block explains the reason and a recoverable path. Offline “saved on device” remains visible until sync, while a conflict asks for comparison instead of silently overwriting. This is a local specimen state contract, not proof that the production app always completes those transitions. [3] Proposal · v8.1 rulebook · reviewed

The field screen presents state first, then context, next action and evidence when needed. It has one primary action; a control intended for gloved field use targets at least 56 px. Marketing web and operator density are separate decisions, not scaled-down copies of the field view. [1] Design reference · v8.1 rulebook · reviewed [2] Design reference · v8.1 rulebook · reviewed

Status cannot depend on hue alone: a word and icon remain visible alongside colour. Map and data views need understandable source, time and a boundary between actual and forecast information. Estonian remains the field product's source vocabulary; the English on this portfolio page explains the system to international clients. [1] Design reference · v8.1 rulebook · reviewed

Full source references
  • [1] design-8-1-reference · AgroNutikas Design System Rulebook v8.1, commit 64ecdd23f8f4ba23b1fba87758f836cdfd2886df
  • [2] seven-surface-matrix · AgroNutikas Design System Rulebook v8.1, section 15
  • [3] field-entry-states · AgroNutikas Design System Rulebook v8.1, sections 02/23/25; local illustrative data

Evidence and limits

The v8.1 rulebook, CSS tokens and V8 mobile and tablet references support selected design rules and examples. They do not establish current AgroNutikas-APP production behaviour, real field data or the maturity of every component. [1] Design reference · v8.1 rulebook · reviewed All field-entry data in this deep view is sample data. [2] Proposal · v8.1 rulebook · reviewed

An older case gallery contains V9 pilot-package images whose capture dates are unverified. This v8.1 deep view does not use them as v8.1 screens or dated production proof. Versions and data layers remain separate until the images' provenance is checked. [3] Design reference · Case gallery · reviewed

Full source references
  • [1] design-8-1-reference · AgroNutikas Design System Rulebook v8.1, commit 64ecdd23f8f4ba23b1fba87758f836cdfd2886df
  • [2] field-entry-states · AgroNutikas Design System Rulebook v8.1, sections 02/23/25; local illustrative data
  • [3] v9-pilot-images · AgroNutikas case gallery, V9 pilot package; capture date unknown

A useful next step

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, provenance labels and verification questions; production integrations require separate scope. [1] Design reference · v8.1 rulebook · reviewed [2] Proposal · v8.1 rulebook · reviewed

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 · v8.1 rulebook · reviewed

Full source references
  • [1] design-8-1-reference · AgroNutikas Design System Rulebook v8.1, commit 64ecdd23f8f4ba23b1fba87758f836cdfd2886df
  • [2] field-entry-states · AgroNutikas Design System Rulebook v8.1, sections 02/23/25; local illustrative data

Back to systems · llms.txt