Route kits
These are shapes for discovery, not packaged claims or fixed prices. Each route is adapted to the organisation's systems, authority, users, Norway-facing conditions, and evidence needs.
For public websites or portals where people cannot locate the right service, understand the next step, or recover from an error. Map intent, information architecture, approved language, accessibility, analytics boundaries, search foundations, and a maintainable publishing route.
For work trapped between inboxes, spreadsheets, CRM records, documents, and vendor systems. Establish the system of record, transitions, permissions, retries, duplicate protection, exception queues, and operator visibility.
For research, retrieval, classification, drafting, or internal support where source quality and human review matter. Bound the accessible data, build evaluation cases, surface citations or source context, and provide fallback when a model cannot answer safely.
For applications that are difficult to deploy, restore, understand, or safely modify. Inventory dependencies, protect current data, reproduce the important failure, fix the narrowest risk, and leave an observable release and rollback route.
Norway field overlay
Language ownership, representative formats, consent behavior, data vendors, NOK journeys, identity dependencies, accessibility, performance, review timing, and support are selected from the real operating context. They are not a country-name layer added at the end.
If none fits, describe the workflow and let the fit check determine whether another approach is responsible.