We build practical intelligence, software, and systems that remain grounded in the work people do every day.
Explore the intelligence applications that connect the EMPHOS ecosystem.
Clear intelligence tools for grounded, practical decisions.
Focused desktop software and platforms built for practical work—not subscription clutter.
Find the work, ideas, and long-range direction shaping the EMPHOS ecosystem.
Research and ideas built to inform practical decisions.
Learn about EMPHOS Group and the work shaping its long-term direction.
Practical products, disciplined research, and a connected portfolio.
Aletheia Core, Heinrich, FieldLine PDF, FieldLine Planner, RightNow, HAVEN, PRISM, and Shield — one connected EMPHOS ecosystem.
Shield is EMPHOS’s research direction for monitoring and security in connected environments. The aim is to bring events, context, and understandable controls together, so people can see what matters and decide what happens next.
Longer-term R&DCurrent focus: defining a bounded prototype.
Events with a source, time, and place.
What changed, what relates, and what is missing.
Review, acknowledgement, and authorized next steps.
A door opens. A reading changes. A device stops reporting. Each signal has a different meaning depending on where it came from, when it arrived, and what else was happening.
Shield explores how to turn that fragmented information into a coherent picture, with the evidence and choices close at hand.
Present the event and its source, rather than a conclusion without supporting information.
Relate timing, location, recent events, and the settings chosen for that environment.
Give the appropriate person a clear way to acknowledge, investigate, or hand over an event.
Keep notification and device-control permissions explicit, with a record of the decision.
The programme starts with a small set of defined inputs and review steps. These are the capabilities the research is intended to develop and evaluate.
Explore how authorized sensor and monitoring-system events can be collected into a consistent view.
Study how related events and the environment’s configured rules can make an alert easier to interpret.
Develop a review path that helps the responsible person assess an event and choose an appropriate follow-up.
Explore notifications and device interactions through explicit permissions and testable rules.
The proposed architecture gives each stage a specific role. Aletheia Core would support interpretation, while event handling, permissions, and approved actions have their own defined rules.
An authorized source supplies a signal with its time, location, and device status.
Related records and configured conditions help explain what changed and what needs review.
The responsible person can examine the evidence, check uncertainty, and select a next step.
An authorized notification or action is logged with its result and any outstanding follow-up.
Research will examine local processing, secure handoffs between devices, and how the experience behaves when an input or connection is unavailable.
These examples illustrate possible prototype scenarios. Each starts with a limited question and an explicit role for the person responsible for the environment.
An access-point event arrives outside the schedule configured for a property or workspace.
Check the event time, authorized access information, related signals, and whether the source is reporting normally.
Present the event to a designated reviewer, who can acknowledge it, add context, or notify a chosen contact.
A connected source reports a water, temperature, or other environmental change.
Compare recent readings, device condition, and the thresholds selected for that location.
Create a clear maintenance or investigation prompt, with the reading and source available for review.
An expected update has not arrived from a monitored source.
Show the last successful report, the affected area, and any known connectivity or maintenance information.
Ask the responsible person to check the device, so a missing connection remains visible in the overall picture.
Useful monitoring depends on more than identifying events. The research also needs to establish what people can see, what the system retains, and how they remain in control.
Define the information required for each use case, where it is processed, who can access it, and how long it is retained. Explore local processing and explicit choices for any remote access.
Keep the source and timing of an event available for inspection. Test how summaries distinguish observations, interpretations, missing inputs, and conflicting information.
Separate permission to view an event, notify someone, and control a connected device. Make access easy to review and revoke as people, roles, or circumstances change.
Measure missed events, unnecessary notifications, review time, and the outcome of a selected action. Include connectivity loss, delayed signals, and permission changes in prototype testing.
Shield’s intended place is between connected environments and the people responsible for them. Its integration research builds on the direction of the wider EMPHOS portfolio.
The intended model foundation for interpreting event information and helping explain it. Shield research would evaluate the model within specific monitoring workflows and their defined limits.
Explore Aletheia CoreThe desktop AI workspace. A possible Shield integration would provide a place to inspect events, understand their context, and manage review tasks through an authorized workflow.
Explore HeinrichThe mobile direction for Heinrich. Shield-related research could explore selected notifications, event review, and acknowledgement away from the desktop.
Explore the Heinrich AppThe ten-device hardware suite. HAVEN HOME’s household-hub concept is a natural setting to explore local coordination; other device connections would be defined and evaluated for their particular use cases.
Explore HAVEN HOMEShield remains a longer-term research programme. The next step is a bounded prototype with specified inputs, review steps, and testable behaviour.
Progression follows evidence from that work: integration quality, usability, permission control, and performance in the intended environment.
Choose a use case, its users, the available inputs, and the decisions the experience should help them make.
Connect the selected sources and develop an event record, context view, and explicit review path.
Test whether people can understand the information and use the controls, including when data or connectivity is incomplete.
Use the findings to establish supported integrations, operating requirements, documentation, and the work needed for a controlled pilot.
Next milestone: a documented prototype scope and evaluation plan for one defined monitoring use case.
We welcome conversations with device developers, property and facilities teams, and research partners. Bring a specific environment, the signals available there, and the decisions that need better support.
