Lucine – Cognitive Continuity in Human–AI Systems
Fast catch-up, visible memory, and agency over time.
Continuity case study for long-running AI collaboration, focused on visible memory, consent, fast catch-up, and user agency.
Benjamin Monteiro
I work across the line of a thing: how it is named, built, used, trusted, delivered, and maintained.
My work connects naming, product logic, interfaces, AI-assisted workflows, and operational structure. The aim is to show what each choice affects, not just how the finished thing is positioned.
The work below starts with the three entry points, then opens the case studies behind the strongest proof.
Working range
Cross-disciplinary systems for teams, products, brands, tools, and services that need coherence across more than one layer.
Work categories
Browse by medium first, then open the case-study shelf for the decisions, constraints, and outcomes behind the work.
Interfaces, AI continuity, information architecture, and tool surfaces for complex products.
Physical goods, materials, prototypes, product trust, ecommerce, and campaign flow.
Story, identity, storefront rhythm, launch assets, trust cues, and Jansberg pathways.
Depth shelf
These pages show the context, constraints, and decisions behind the work that needs more than a short category preview.
Open case-study shelfFast catch-up, visible memory, and agency over time.
Continuity case study for long-running AI collaboration, focused on visible memory, consent, fast catch-up, and user agency.
One trusted direction cue instead of a full map.
Assistive · Product · SystemsWearable navigation concept for moments when one trustworthy cue is safer than a full map, focused on direction, reassurance, and low cognitive load.
Comfort-led interaction, pacing, and thumb zones.
UX · Human FactorsInteraction framework for low-friction interfaces, focused on ergonomic reach, soft state changes, ambient legibility, and tactile reassurance.
Emotional memory with clear recall boundaries.
AI · Systems · UXAI memory concept for emotionally meaningful continuity, focused on layered recall, healthy forgetting, and legible consent.
Stable decisions under volatile conditions.
Systems · AI · BehaviourDecision-system study for high-volatility contexts, focused on clarity signals, risk pacing, and behaviour safeguards.
Visible state, drift tracking, and cognitive pacing.
AI · Systems · EthicsCognitive architecture study for oriented AI interaction, focused on drift tracking, visible continuity, emotional pacing, and safe collaboration.
Next step
Start with the archive for proof, or contact me directly for product, UX, AI-system, physical-product, or website work.
Product · Systems · Space
I am based in Knivsta, between Uppsala and Stockholm, and I work across digital products, physical making, brand surfaces, and early business structure.
That range matters in the work: choices made in naming, interface, production, or launch are felt later in cost, delivery, use, trust, and maintenance.
Working posture · index 01
Many projects are given a narrow name too early. A website is also a sales process. A product is also cost, production, storage, trust, and use. An AI tool is also memory, consent, failure, and recovery.
The useful work is to map the fuller shape before deciding what should be made.
Typical outputs include interaction maps, service flows, prototype plans, naming options, launch structures, or a plainer account of what the project actually is.
My practice moves between digital product design, physical prototyping, research synthesis, and the systems that connect them. I enjoy projects where interface, behaviour, and environment influence each other rather than living in separate boxes.
Some weeks look like Figma, workshops, user flows, and decision framing. Other weeks look like CAD, 3D printing, sewing, rough spatial tests, and material checks.
I keep those modes close because each one catches a different kind of mistake before the project becomes expensive to change.
Systems practice · index 02
The practice stays cross-medium on purpose: screen decisions, material decisions, and service decisions all reveal different parts of the same project.
/identity/origin
I observe how people adapt around imperfect systems: how they carry things, move through spaces, avoid confusion, and build small personal routines around products that almost fit.
The useful moment is often where a product can become quieter by respecting behaviour already there.
/designer/interaction
I design interactions around sequence, state, feedback, and expectation.
The interface should teach through structure: placement, sequence, state, and feedback before relying on explanation.
/systems/clarity
I trace relationships, frame edge cases, and identify which decisions will affect the most other parts of the project.
The surface carries more weight when the underlying logic has already been found.
/practice/making
I move between sketches, flows, prototypes, CAD, and quick physical tests when the concept needs to be understood from more than one angle.
Physical making sharpens product judgement. Materials, seams, scale, balance, and wear reveal constraints that a screen can hide too easily.
/space/environment
Rooms, movement, objects, and sequence all teach behaviour before any text appears. I treat space as another interface layer.
The same sequencing logic often translates directly into product and service structure.
/future/direction
I am best suited to consulting, special projects, founding design work, and experimental projects where the brief is still open.
The strongest fit is work where the team needs direction, structure, and practical next steps before a final surface.
Direction · index 03
Terrain turns the portfolio into a spatial map so projects can be explored by relationship instead of only by page order.
Terrain is a working experiment in portfolio navigation. It gives case studies, ideas, and project branches a visible relationship to each other.
It is useful when a visitor wants to browse by theme, compare related projects, or return to a specific thread later.
It also gives the information architecture a visible test when a linear list is not enough.
Strong products become easier to use over time. They preserve context, recover gracefully, and avoid punishing the user for learning in public.
Calm does not mean empty. It means each element earns its place and the product feels steady under use.
This is a design standard, not a visual style.
Strong work often sits where the boundaries are not clean: a product that needs a brand, a brand that has to survive production, an interface that changes how the service runs.
The point is not to cover more disciplines for its own sake. It is to make decisions that can hold from idea to delivery.
The best projects still leave room for discovery, but they do not pretend that discovery is separate from cost, use, or consequence.
Experimental interface studies for motion, interaction, visual systems, and AI-assisted design patterns. Terrain is the main live example: a spatial way to navigate complex work without losing orientation.
A navigable view of connected projects, decisions, and working systems. Move through the atlas without losing the wider structure around each piece of work.
Built for orientation. Explore the guided view, use the map directly, or see how the system was made.
Design as observation, inquiry, and intentional invention.
I move from intent, fast internal iteration, and attention to real-world feedback.
A clear direction gives the first prototype something to test. External signals then decide what needs to change.
Drift is useful only when it refines the path without betraying the core intent.
I notice intention in artifacts – where care exists, where compromises show, and where people compensate unconsciously.
Useful signals include load spikes, workarounds, movement patterns, and places where intent and use drift apart.
The design work is to restore alignment before the mismatch becomes normal.
I use AI as a reflective tool to broaden thinking without surrendering judgment.
AI is useful for alternatives, blind spots, scenario mapping, and coherence checks.
It should expand the decision space without becoming the authority.
Business architecture
A person-first business creation practice for people who do not yet have the right business idea, concept, or structure. The work starts with the individual and shapes a business around them.
This is not generic consulting, generic idea generation, or a sales funnel. It starts with the person: strengths, weaknesses, energy, capital, constraints, reach, and desired way of living.
For people who do not yet know what to build and need an idea shaped around their strengths, constraints, and capacity.
For people with fragments or rough ideas who need the offer, audience, pressure, and first moves put into order.
For clients who want the model, operating demands, first steps, and tradeoffs worked through before they begin.
Based in Knivsta, Sweden – available for projects locally and remotely. For work inquiries, collaborations, or questions: