Threshold / Sense → Infer
The door opens. That is all the threshold knows.
A door contact reports one change; motion may suggest that someone is there.
Calling it an arrival—and deciding who arrived—means combining separate signals into a story.
House route / Stop 01
City edge · one household · browser exhibition
A normal house, one layer at a time.
This is not a tour of imaginary gadgets. It begins with an ordinary house, then follows what its systems can sense, infer, remember, control, and explain. The last stop separates equipment that exists now from the combinations that remain a five-year scenario.
01 / Room Observatory
Interactive architectural study · renderer 01
The room is not a single intelligence.
The intelligence is scattered across sensors, models, memories, house rules, devices—and the people who live with them. Choose a verb to see what has to happen, and what the room should reveal, before we call it intelligent.
Stress-test the promise
Our starting room assumes one person, one vendor, and a working internet connection. Real homes rarely stay that simple. Change the conditions.
- 01SenseObserved capability
The room picks up sound, motion, light, temperature, and device state.
- 02InferObserved capability · current limits
Those signals become guesses: occupied, familiar, likely, unusual. Identity is a conclusion, not something a sensor simply sees.
- 03RememberObserved capability · current limits
Events, preferences, and profiles can linger—often without a clear view of what was kept or how to change it.
- 04DecideProposed safeguard
A person, rule, or model chooses: act, ask, wait, or do nothing.
- 05ActObserved capability
A permitted command changes what people see, hear, feel, or can access.
- 06ExplainProposed safeguard
People should be able to see what happened, why it happened, and who or what had permission.
- 07ForgetProposed safeguard
Deletion needs a clear target and limit. A receipt can confirm an action, but not that every copy—or every learned effect—is gone.
We use seven verbs to read the room. They are not a literal flowchart: real systems loop, revise, and let one action become the next signal.
H02 / Lived-in fieldbook
Six scenes from one imagined household · one ordinary night
One house,
one ordinary night.
The full-scale view places the technology in an actual neighborhood. These close views show where it touches ordinary life: at the front door, across a shared kitchen, at the table, and inside the household record.
-
Plate H02.1 / 18:14:07Project-created systems plate · measured illustration -
Plate H02.2 / 18:14:39CGI study · shared preferences Shared kitchen / Remember → Decide
The routine remembers one person. The kitchen already belongs to another.
One resident likes a bright hall. Someone already at the table wants the kitchen dim.
Both facts can be true. The system still has to decide whose comfort wins—or stop and ask.
-
Plate H02.3 / 18:14:48CGI study · four separate actions Across the house / Act
One command becomes four different changes.
Light, heat, media, and a lock each receive their own instruction.
Calling that “the room” hides the important part: every device can fail on its own, needs its own override, and leaves someone to deal with the result.
-
Plate H02.4 / After the changeCGI proposed safeguard · explanation and override At the table / Explain
If the room acts, it should be able to say why.
The explanation should survive the app.
A useful receipt would say what set the change off, which rule fired, what changed, and who authorized it. You should not have to hunt through someone else’s account menu to understand your own room.
-
Plate H02.5 / 02:14CGI study · a signal and its retained record Night hall / Sense → Remember
At 2:14 a.m., a small moment can become a long memory.
Walking down the hall is ordinary. Keeping a record of it is a choice.
A sensor may register a crossing. It does not know why it happened. The harder question is whether that moment should enter the household’s history—and for how long.
-
Plate H02.6 / Next morningCGI proposed safeguard · stopping and removing Utility wall / Explain → Forget
The exit is part of the room.
Turn it off. See what it kept. Delete the event. Know what deletion cannot promise.
Stopping the system and deleting its memory are different acts. A receipt can confirm that a named record was removed. It cannot prove that every copy—or every influence on a model—is gone.
02 / One minute, opened
Interactive event choreography · illustrative household sequence
One gesture.
Eight accountable events.
The feature begins with a room appearing to welcome someone home. Open that minute and the seamless gesture separates into signals, inferences, retained context, policy, commands, and consequences.
What it feels like
“The room welcomed someone home.”
One quiet gesture. No visible request.
60seconds
opened
Trace at rest. The complete sequence remains readable below.
-
Signals suggest activity in two places. Signals are not identities.
Responsible components · occupancy and audio sensing Open the sensing boundary -
Events are joined to a routine. This exact chain is not established by the sources.
Responsible component · hub or automation service Open the present assessment -
The system assigns meaning. “Familiar” is an inference, not an observation.
Responsible component · rule or model Inspect Infer -
A scenario preference appears. What was retained—and where?
Responsible component · profile or routine store Inspect Remember -
The returning preference conflicts with the room already in use. Whose rule applies?
Responsible component · household policy Open the shared-room conflict -
Separate commands leave the controller. Coordination does not supply judgment or consent.
Responsible components · hub and device interfaces Read the Matter 1.6 profile -
The room changed. The reason, scope, and override should remain visible.
Responsible component · accountable interface Inspect Explain
04 / Local until it is not
Interactive boundary plate · documented fragments, not one product
Local until it is not.
A feature can run locally while the rest of the chain reaches elsewhere. Follow the cuts to see where the evidence holds—and where we simply do not know.
-
Path A / Documented local
A task can be local. The system may not be.
Apple documents on-device models. Google documents local execution for some automations. These are separate records, not one pipeline.
- Not established
- Local generative household interpretation, complete offline behavior, or the location of every prompt, output, log, and telemetry stream.
- Network-cut result
- No whole-system result inferred.
-
Path B / Disclosed remote component
A remote component has a network edge.
Apple documents three server-based models running on Private Cloud Compute. Apple’s PCC requirements say request data must not be retained, including through logging or debugging, after a response; this is a vendor-stated boundary, not an independent audit or a feature-routing map.
- Network-cut result
- The generic remote segment is interrupted. No named feature inherits this state without documented dependency and fallback behavior.
-
Path C / Unstated
Silence is not local.
Google’s Gemini for Home report lists devices and services but does not state execution location, network dependency, offline behavior, or fallback for its named AI capabilities. Matter coordinates supported components; it does not supply one universal local/cloud architecture. Other unstated processing, account, telemetry, retention, and fallback boundaries remain unknown.
- Network-cut result
- Unstated behavior remains unknown before and after the network cut.
05 / The memory residue
Interactive deletion-path study · proposed safeguard
The record can go.
The residue remains a question.
Deleting one named record is not the same as erasing every trace. This diagram follows an illustrative request and marks what the receipt can—and cannot—prove.
All objects and uncertainties are shown. Trace the request to emphasize its named boundary.
- 01 / Inside illustrated scope
Raw event
Hallway occupied · 02:14Requested outcome: remove from the named visible-history store.
Illustrative target · not proof of storage architecture - 02 / Separate object
Derived preference
Prefer low light after midnightA related preference is a separate object. This diagram does not assert that one event created it.
Outcome not established - 03 / Separate object
Profile association
Routine associated with Resident ARemoving an event does not establish that a resident or household profile changed.
Outcome not established - 04 / Unknown
Possible learned influence
Prior update or tuning effect?No specific influence is established. The dotted path asks whether one exists and whether it can be reversed.
Existence and reversibility unknown - 05 / Proposed safeguard
Audit entry
Request H-0214 · scope statedAn accountability record would have its own purpose, access, and retention boundary.
Separate record - 06 / Limited proof
Deletion receipt
Visible-history event marked removedA receipt can report the named action. It cannot, by itself, prove what happened to backups, shared copies, profiles, or learned influence.
Proof limited to stated scope
A reasoning diagram—not a deletion guarantee. This is not a product trace, vendor architecture, legal determination, or claim that every pictured object exists in a named system.
Current evidence supports a narrower conclusion: local inference does not establish that telemetry, logs, backups, or outputs remain local; smart-home research documents users’ varied and sometimes unclear understanding of how household data was collected and used; lifecycle guidance makes end-of-life support a product concern.
Artificially.cloud’s notice describes this website’s own request-data boundary. It is not evidence about a household product.H03 / Five-year house
A conditional 2031 field study · evidence window 16 Oct 2026
The future lives in the utility room.
Five years is close enough that the studs, the budget, and the service call still matter. This is the same 3,500-square-foot house at the edge of the city—not a lab and not a billionaire compound. Most of it is ordinary. The speculative step is that real components begin to coordinate locally, explain what they did, and give way when someone disagrees.
- Current
A component or capability can be bought, deployed, or used now, though access and quality vary.
- Emerging
Real standards, products, or research systems exist; ordinary household availability is not established.
- 2031 forecast
A conditional design extrapolation for this exhibit—not an issued forecast, promised arrival date, or product claim.
01 / The working edge
The glamorous part is that the laundry gets folded. The credible part is everything bolted to the wall.
A single mobile robot shares the utility room with the systems that make the house work: heat pump, filtered air, water isolation, battery, wired network, local compute, and the old shelf where spare parts accumulate. In the garage, the Roadster charges like a car—not like a magic battery for the building.
Boundary: The robot is a five-year extrapolation from research systems, not a claim of safe unattended domestic competence. The Roadster is not shown powering the house; bidirectional support for that exact vehicle and installation would have to be verified.
RoomHeadset off
ViewInside the headset
02 / Spatial room
The headset comes off. The room still has to work.
Most days it is a spare room with a reading chair and somewhere to put your books. Put on the headset and a digital model of the household robot could appear in the clear floor area, ready to inspect without moving the real machine. The door, seating, and physical controls still matter. Someone should be able to interrupt, and taking the headset off should be enough to return to the room.
Boundary: Headsets and immersive media exist now. A socially graceful room that coordinates lighting, sound, safety, and household interruption is the forecast layer. No headset pose, room scan, or bystander recording should enter the household memory by default.
H03 / Evidence register
Twelve systems. Twelve places to stop pretending.
The image is a synthesis; the evidence is not. Each entry names what is real, what is still uneven, and the line this house does not cross.
-
One robot, with a job description.
Research robots can already chain manipulation tasks such as collecting and folding laundry. Here, one shared machine works in the utility room instead of following people through every room.
- Boundary
- A laboratory task is not proof of safe, reliable, unsupervised household work. Stairs, children, pets, clutter, wet fabric, maintenance, and recovery remain hard.
-
The outside robot stays outside.
A robotic mower follows a mapped work area while drip irrigation responds to weather and several soil readings. The lawn still has thin spots, leaves, and edges a person has to trim.
- Boundary
- A mower is a narrow-purpose appliance, not a second household robot. One soil probe cannot represent a whole property, and weather-aware watering still needs calibration and winter maintenance.
-
A dedicated VR area is mostly good architecture.
High-resolution stereoscopic video, spatial audio, hand tracking, passthrough, and room-scale experiences are available. The house adds the unglamorous pieces: clear floor space, a seated mode, a visible dock, washable face interfaces, acoustic control, and a physical way out.
- Boundary
- Fidelity is not comfort, shared presence, universal accessibility, or privacy. A room designed around one headset can become obsolete; the safe floor and ordinary controls should remain useful.
Apple Immersive Video technical overviewW3C WebXR Device APIApple Vision Pro privacy overview
-
The house can hear some things without calling home.
Fixed voice commands can run on modest local hardware; larger on-device models are arriving in consumer systems. The utility cabinet gives them power, cooling, storage, and an ordinary network cable.
- Boundary
- Local inference does not prove local logs, telemetry, backups, accounts, or outputs. Open-ended speech and multimodal reasoning need more compute than a handful of household commands.
Home Assistant local voice documentationApple on-device model research
-
The future is a shared vocabulary, not one brand.
Matter and Thread let more controls, sensors, locks, energy devices, cameras, and appliances describe themselves across ecosystems. Two border routers keep the low-power fabric from depending on one box.
- Boundary
- A published standard is not universal implementation. Commissioning, multi-admin behavior, firmware support, and feature depth still vary by product and platform.
Connectivity Standards Alliance: Matter 1.6Thread 1.4 feature paper
-
The Roadster charges. The house negotiates everything around it.
A home battery, heat-pump water heater, smart panel, solar inverter, and managed charger shift flexible loads without making the resident decode a utility tariff at dinner.
- Boundary
- Managed charging is not vehicle-to-home power. Grid programs, interconnection, equipment, and the exact car all determine whether bidirectional charging is possible.
U.S. DOE managed and bidirectional chargingTesla Powerwall operationTesla charging during an outage
-
The best automation prevents an ordinary bad day.
Particulate, carbon-dioxide, temperature, and humidity trends can change ventilation and filtration. Flow monitoring, point sensors, and a motorized main valve can catch some leaks before the basement becomes the story.
- Boundary
- Consumer sensors drift and cross-react; they are not clinical or regulatory instruments. Automatic valves can miss leaks or close by mistake, so testing, a manual lever, and a plumber still matter.
U.S. EPA low-cost indoor-air monitorsU.S. EPA leak and flow-monitoring guideMatter 1.3 water and energy devices
-
Permission becomes part of the wall.
Camera shutters, microphone power cuts, room-level permissions, local-only indicators, tactile switches, and a mechanical key sit where residents and guests can actually find them.
- Boundary
- NIST defines capabilities, not one master household cutoff. The unified privacy station shown here is a design proposal. A software mute is not the same as removing sensor power.
NIST IR 8259 Rev. 1Connectivity Standards Alliance: Aliro 1.0Apple accessibility features
-
The bedroom gets an off switch before it gets a sensor.
An opt-in bedside radar can estimate sleep and movement without a camera. A later system might notice an unusual fall-like event and ask before escalating to a named person.
- Boundary
- This is wellness support, not diagnosis or emergency certainty. Pets, bedding, another sleeper, room geometry, sparse radar returns, and consent all complicate the signal.
Google Research sleep/wake radar studyPrimary mmWave activity and fall study
-
The kitchen coordinates. It does not cosplay as a chef.
The induction range, hood, air system, washer, dryer, dishwasher, refrigerator, and water heater can expose state and energy use while retaining physical controls.
- Boundary
- Interoperability does not establish robot cooking, reliable food recognition, automatic shopping, or safe remote start. The resident can always run the machine now.
Matter 1.2 appliance supportMatter 1.3 kitchen, laundry, and energy support
-
The invisible house still needs labeled cable.
Fiber, Ethernet, a PoE switch, local storage, a small AI appliance, UPS, ceiling access points, and Thread border routers make the network a serviceable part of the building.
- Boundary
- Wi-Fi 7 adds capacity, not perfect coverage; 6 GHz attenuates quickly through walls. Critical fixed systems still benefit from wire, ventilation, updates, and a documented fallback.
-
The house fabricates the drawer clip, not the water pipe.
An enclosed desktop printer makes jigs, cable guides, adapters, and low-risk replacement parts. Electrochromic glazing and a matte e-paper panel quietly manage glare and household information without turning every surface into a screen.
- Boundary
- This is not a replicator. Printed gas, mains electrical, structural, medical, or pressure-bearing parts require qualification. Smart glass switches slowly, varies by climate, and should keep a conventional shade.
NIST additive-manufacturing qualification reportU.S. DOE electrochromic window overviewE Ink Spectra 6
06 / Time Spine
Related visions, separated by evidence.
Filter by time, then choose an entry to open its Evidence Margin. Keyboard: Tab enters the chronology; arrow keys move between visible entries. Everything is also readable in the list view.
Archive
When a work or idea entered the record
These are the dates when works appeared or events happened. They do not move as the present moves.
Now cut · 12 Oct 2026
A dated view of current evidence
This is what the evidence showed on 12 Oct 2026. It will age.
Research windows
Dates to check the evidence again
These are review dates, not promises about what arrives. No outcome, probability, or website timeline is forecast here.
07 / Comparison Shutter
One presence. Many systems.
Use the buttons to line the two readings up or pull their differences apart. The full comparison stays readable as text.
The rows align categories for inspection. Alignment does not make the imagined and observed systems equivalent.
Imagined / Editorial composite under review
One coherent presence
| Function | Continuous assistant and mediator |
|---|---|
| Capability | Conversation, memory, planning, action |
| Mechanism | Presented as a unified intelligence |
| Oversight | Often implicit or centralized |
| Social context | Everyday dependence is normalized |
Observed / Editorial composite under review
Many partial systems
| Function | Separate assistants, sensors, routines, and devices |
|---|---|
| Capability | Strong in narrow tasks; continuity varies |
| Mechanism | Fragmented models, services, and control layers |
| Oversight | User-configured, vendor-governed, inconsistently legible |
| Social context | Trust, privacy, reliability, and household negotiation remain unresolved |
08 / Horizon Window
What would change the view?
These dates are for returning to the evidence, not predicting an arrival. Each horizon names what would strengthen the case and what would weaken it. Any future forecast would go through a separate documented review.
Current posture
The uncertainty belongs in the exhibit.
Drivers and signposts
- Smaller local models with practical latency.
- Cheaper, lower-power sensing.
- Interoperable device standards.
- User-readable memory and permission controls.
Blockers and invalidators
- Reliability remains too inconsistent for household routines.
- Fragmented ecosystems prevent useful continuity.
- Regulation or public resistance restricts ambient sensing.
- Control remains opaque enough to erode household trust.
09 / Source Room
Provenance before polish.
This register gathers the sources the exhibition depends on most. We checked them against current primary or authoritative records; independent fact-checking and final editorial review are still required before publication.
- S-0012001: A Space OdysseyAFI catalog · Film record and 1968 release
- S-002Star Trek: The Next GenerationOfficial series record · 1987–1994
- S-002aThe Sound of Their VoicesOfficial Star Trek account · Computer voice and representative episodes
- S-003Smart HouseDisney catalog · Film record and official synopsis
- S-004Minority ReportAmblin official page · 2002 film; surveillance boundary case
- H-001The Computer for the 21st CenturyMark Weiser · Ubiquitous-computing vision
- H-003Design Principles for Intelligent EnvironmentsMIT AI Laboratory / AAAI · Primary prototype paper
- H-007Ambient IntelligencePhilips Research authors · TU Eindhoven bibliographic record
- H-006Scenarios for Ambient Intelligence in 2010EU ISTAG · Historical scenario exercise, not prediction
- E-001Matter 1.6 release notesConnectivity Standards Alliance · Released standard, not product adoption
- E-001aSmartThings Hub Platform certificationCSA · Matter 1.6 software-component certification; not availability proof
- E-001bMatter specification indexCSA · Matter 1.6.1 listed as latest 1.6.x version at cutoff
- E-002Third-generation Apple Foundation ModelsFirst-party on-device and PCC server-model architecture and evaluations
- E-002aPrivate Cloud Compute core requirementsVendor-stated request-data no-retention and no-logging boundary; not an independent audit
- E-003Gemini for Home platform reportVendor-reported capabilities; execution location, network dependency, and fallback unstated
- E-003aGoogle Home APIs Android release notesVendor-reported GA milestone and supported Matter versions
- E-003bGoogle Home APIs iOS release notesSome automations may execute locally; not evidence of local Gemini inference or complete offline behavior
- E-004Research Report: User Perceptions of Smart Home Privacy and SecurityNIST IR 8330 · Interviews about smart-home data understanding
- E-005Smart-home security and privacy perceptionsNIST SP 1343 · Survey of 401 U.S. users
- E-006Security and Privacy in Multi-User Smart HomesUSENIX Security · Month-long seven-household study
- E-007Enhancing smart home services among people with disabilitiesAssistive Technology · Qualitative study with 25 participants
- E-009Foundational Cybersecurity Activities for IoT Product ManufacturersNIST IR 8259 Revision 1 · Lifecycle and end-of-life guidance
What we still do not know
- Whose context wins?How much product language and account design still assumes a single owner?
- What survives a vendor?A room’s continuity is fragile if its memory cannot move, expire, or be independently audited.
- When is restraint measurable?What language can describe a system that correctly declines to act?
10 / Reading Room
Rooms That Notice.
The Intelligent Room is one exhibition and one editorial issue. Each story enters the same system from a different human question.
01 / Feature · 12 min
When the room begins to notice
02 / Visual essay
Seven verbs in an empty room
03 / Household study
A house with more than one person
04 / Exit manual
How to leave an intelligent home
A field guide to hidden seams, domestic memory, and the boundary between help and observation.
Read now ↗How sensing becomes judgment—and judgment becomes architecture.
In developmentGuests, children, workers, and the fiction of shared permission.
In developmentDeletion, deactivation, resale, portability, and the right to pull the plug.
In development