01
Contain the problem, not just the alert
When independent signals agree, an approved policy can coordinate a bounded response—then compare the reported result with what was intended.
STONEHALL ONE · COORDINATED PROTECTION
Water where it shouldn’t be.One response, already underway.
Moisture, flow, and household state became one verified response.
- MoistureWater detected
- Main flow4.8 gal/min continuous
- Home stateAway · 32 minutes
Stonehall correlatesLikely leak · Kitchen supplyWater Protection · Approved
Approved responseClose compatible main valve
PRODUCT DEFINITION
The brain behind
the connected home.
Stonehall One is a pre-launch intelligence and coordination controller for professionally designed properties. It is intended to learn from available system behavior, suggest useful policies, coordinate approved actions, and keep the reported outcome in view.
Specialist systems keep doing the work they do best. Stonehall does not silently create high-impact rules, certify third-party equipment, or make every property behave the same way.- SHARED CONTEXT
One model of the property
Available device states are related to rooms, routes, equipment, utilities, and household modes so separate products can contribute to one useful situation.
- LEARNED ASSISTANCE
Suggestions before automation
Stable patterns can become evidence-backed proposals that show the systems affected, the exceptions preserved, and what would need approval before anything changes.
- TRUSTED EXECUTION
Approved behavior, clear receipts
Commissioned policies coordinate compatible systems within explicit bounds. Reported outcomes and unresolved exceptions stay visible instead of disappearing inside separate apps.
HOW IT OPERATES
A home that gets better
over time.
Stonehall can turn stable patterns into reviewable policies, then coordinate only what has been approved. Each outcome either produces a clear receipt or leaves an exception visible.
- 01
OBSERVE
The property becomes legible.
Available device states are normalized and related to the rooms, equipment, people, permissions, and dependencies established during commissioning.
- 02
LEARN
Stable patterns become evidence.
Where enabled, repeated system behavior and manual adjustments can reveal a consistent pattern without turning one unusual event into a rule.
- 03
PROPOSE
The assistant drafts what could help.
A proposal explains the evidence, affected systems, timing, exceptions, safety bounds, and how the result would be checked.
- 04
APPROVE + COORDINATE
Permission becomes defined behavior.
Once reviewed and approved, deterministic triggers and guards coordinate compatible systems. The assistant does not improvise inside the control loop.
- 05
VERIFY + REFINE
The result closes the loop.
Reported states, credential use, and unresolved exceptions stay visible. Outcomes can inform a new proposal, but active policies never silently rewrite themselves.
Active high-impact policies do not silently rewrite themselves. Internet service, vendor clouds, subscriptions, manufacturer interfaces, and third-party policies can still affect availability.
LEARNED ASSISTANCE · 01 OBSERVE
It notices the routine
before you program it.
Repeated system behavior becomes evidence, not a command. Stonehall drafts what could help and waits for approval.
01 · OBSERVE
The home notices what repeats.
Across repeated evenings, device states begin forming a stable sequence.
01 · OBSERVE
A pattern becomes evidence.
After the dog comes in, four doors lock, downstairs lights go dark, and the upstairs settles.
02 · UNDERSTAND
It finds the exception.
On Tuesdays, one household member returns later through the mudroom.
02 · PROPOSE
A useful policy is drafted.
The proposed Night Close shows every system, timing rule, exception, and verification step.
03 · APPROVE
You approve the boundaries.
Nothing changes from observation alone. The policy becomes active only after review.
03 · COORDINATE
Then the ordinary runs itself.
Locks, lights, climate, access, and the pet route move together inside the approved rules.
03 · VERIFY
And the result stays visible.
Reported states confirm what finished and keep any unresolved exception in view.
CORE CAPABILITIES
The value is what
the home finishes.
Protection, learned assistance, resource management, trusted access, security, and service become more useful when the property can coordinate the whole outcome.
Protection paths depend on commissioned sensors, controls, readback, and safety boundaries.
02
A home that gets better over time
Stable patterns across available system events can become useful proposals before the household has to think about programming them.
03
Use resources around real priorities
Compatible energy, water, irrigation, climate, battery, and vehicle systems can coordinate around utility periods, commissioned watering windows, weather, reserve targets, and departure needs.
04
Give service access without opening the home
Assigned credentials can be limited by schedule, entrance, route, alarm partition, and equipment scope, then expired after the door or gate reports closed.
05
Security that knows what belongs
Access, camera, motion, network, schedule, and property-state signals can be correlated so an approved response reflects the situation instead of one isolated alert.
06
Carry the issue through recovery
Equipment context, response history, a service brief, scoped access, and post-service reported states can remain together instead of becoming five disconnected handoffs.
PRODUCT INSPECTION
A permanent place
for the home’s intelligence.
Stonehall One is pre-launch. This view separates established product responsibilities from engineering targets and the property-specific decisions made during commissioning.
“Confirmed” identifies a current product role or boundary—not an unpublished hardware specification.
- ConfirmedA current product responsibility or boundary.
- Pre-launch targetCurrent pre-launch engineering intent.
- Property-confirmedValidated for the commissioned property.
- To be finalizedPending engineering or launch policy.
EQUIPMENT-ROOM CONTEXT
Designed to live with the infrastructure.
Stonehall One is intended for professional equipment-rack placement, giving the property’s coordination logic a deliberate, serviceable home away from living spaces.
- Pre-launch targetInstallation format
- The current pre-launch target is a 1U format for professional rack placement.
- Property-confirmedEquipment location
- The appropriate rack and equipment location are selected during the property review.
- To be finalizedInstallation requirements
- Final mounting, ventilation, power, and network requirements remain pending engineering.
COMPATIBILITY EVIDENCE
Compatibility is proven by behavior,
not a logo.
Stonehall reviews how each system can participate, what the coordination should accomplish, and how the finished behavior will be validated in the property.
Property reviewFit is determined from the exact property and equipment.
Interface-dependentParticipation requires an available, validated connection path.
Pre-launch targetIntended behavior remains subject to engineering and validation.
Review by system family
Use Tab to enter the filters, then the arrow keys to move.
Showing 13 coordination paths across all system families
Scroll horizontally to compare the evidence fields
| Coordination path | Example behavior | Commissioning validation | Status |
|---|---|---|---|
| Lighting & livingCoordinated atmosphere and comfort, shaped around the rooms people actually use. | |||
| Lighting and shade scenes | A supported evening scene can adjust selected lighting and shades together while familiar room controls remain available. | Confirm exact equipment and interface access; test scene recall, manual overrides, timing, and recovery after an interruption. | Property review |
| Climate and occupancy context | Available occupied or away state can inform supported comfort settings without replacing equipment-level safeguards. | Confirm writable control points, equipment limits, manual priority, restoration behavior, and the intended room-by-room scope. | Interface-dependent |
| Audio and room routines | Supported audio zones may participate in arrival, entertaining, or wind-down routines as one part of a wider scene. | Confirm zone availability, account and network dependencies, startup behavior, volume boundaries, and a quiet fallback state. | Interface-dependent |
| Security & networkUseful context from supported access, awareness, and network systems—without blurring safety boundaries. | |||
| Scoped service access | An assigned credential may be limited to an approved window, entrance, route, and alarm partition, then expired after the configured closeout state. | Confirm owner authorization, credential lifecycle, door or gate readback, relock guards, privacy expectations, and independent access operation. | Interface-dependent |
| Security context and response | Available door, motion, camera-derived, schedule, and property-state signals can be correlated before an approved lighting, retention, or notification response runs. | Review event sources, privacy expectations, false-trigger handling, notification boundaries, and independent security operation. | Property review |
| Network service visibility | The commissioning target is a clearer service picture for selected network-dependent systems and their known dependencies. | Define monitored equipment, access permissions, useful service states, outage behavior, and who should receive an exception. | Pre-launch target |
| Energy & utilitiesSupported resource signals can inform routines while equipment and safety controls retain authority. | |||
| Peak demand and reserve priorities | Available tariff periods, meter state, battery reserve, and weather context may coordinate supported flexible loads while preserving commissioned priorities. | Confirm the state source, allowed control scope, equipment safeguards, manual controls, restart behavior, and an appropriate fallback. | Interface-dependent |
| Mobility and charging context | Where charging state is available, it may participate in arrival, away, or energy-aware routines without replacing load planning. | Review the installed charger, available account or interface path, property load plan, electrician requirements, and owner priorities. | Property review |
| Water and irrigation windows | Compatible irrigation may follow commissioned local watering windows while available forecast and soil conditions adjust eligible schedules. | Confirm the authoritative schedule source, address and region, controller interface, landscape constraints, manual override, and how rule changes are reviewed. | Property review |
| Utility exception awareness | Available water, power, or equipment signals may contribute to a configured alert or property response. | Validate the source, notification path, escalation rules, network dependency, and the continued independence of certified protection. | Interface-dependent |
| Property infrastructureThe coordination, commissioning, and service layer that makes the finished experience understandable. | |||
| Equipment-room coordination | Stonehall One is intended to provide a defined coordination point while connected specialist systems continue their own core operation. | Confirm equipment location, rack fit, power, network, thermal conditions, service access, and the final engineered controller requirements. | Pre-launch target |
| Schedules and property modes | Configured home, away, arrival, or quiet modes can coordinate eligible systems while preserving explicit manual overrides. | Review time and location assumptions, transition rules, manual priority, exception handling, and recovery after restart. | Property review |
| Commissioning record and handoff | Accepted routines, dependencies, and operating boundaries can be documented as part of the commissioned property experience. | Agree the system inventory, responsible parties, routine acceptance checks, owner handoff, and any ongoing care scope. | Property review |
Compatibility is confirmed during a property review. These examples describe possible coordination—not vendor certification, endorsement, or guaranteed availability. Exact behavior depends on equipment, software versions, available interfaces, permissions, licensing, network conditions, region, and commissioning.
TRUSTED AUTONOMY
Autonomy,
with clear limits.
Stonehall acts only inside commissioned policies the household can understand, approve, and reverse.
- What the policy permits
- Named triggers, affected systems, timing, exceptions, permissions, timeouts, and failure behavior are defined before the policy becomes active.
- What Stonehall checks
- Available device readback and related sensor states can show what completed, what did not, and when manual attention is still needed.
- What remains independent
- Certified life-safety functions, emergency response, specialist-system protections, provider responsibilities, and manual control stay with the systems designed for them.
TECHNICAL DETAILS
Specific where it matters.
Honest where it varies.
Pre-launch information
Stonehall One is still being finalized. Hardware, software, features, installation requirements, included services, availability, and appearance may change before launch. Fields not listed as final remain pending engineering.
- System role
- A dedicated intelligence and coordination controller for a professionally designed Stonehall property experience.
- Core operation
- Relates available system states through a commissioned property model, supports evidence-based suggestions, and coordinates approved policies across compatible systems.
- Control experience
- Assistant proposals, approved automatic behavior, receipts, exceptions, keypads, apps, and alerts are shaped during design and commissioning for the selected systems.
- Local behavior
- Selected core coordination can be designed to run locally. Remote access, notifications, vendor-cloud connections, and optional AI features may still require internet service and remain subject to their providers.
- Target format
- Pre-launch target: 1U rack format for placement in a professional equipment rack. Final mechanical design remains pending engineering.
- Physical details
- Final dimensions, weight, and materials are pending final engineering.
- Platform & I/O
- Final power requirements, ports, compute platform, and storage specification are pending final engineering.
- Connectivity & scale
- Final supported protocols, radios, and system capacity are pending final engineering and software validation.
- Qualification & coverage
- Environmental ratings, certifications, and warranty terms are pending final engineering, testing, and launch policy.
- Installation
- Targeted for professional equipment-rack placement in an appropriate equipment location selected during the property review.
- Power & network
- Final requirements are pending engineering, then confirmed from the controller configuration, equipment location, network design, and connected systems.
- Commissioning
- Stonehall maps rooms, equipment, dependencies, supported connections, control paths, readback, and policy boundaries; validates key outcomes; and documents the finished experience.
- Property fit
- New construction, renovation, and existing properties are assessed individually; the appropriate scope differs by site.
- System families
- Lighting and shades; climate and air; access and security; audio and video; energy, water, irrigation, mobility, utility, and other property systems where supported.
- What is assessed
- Exact equipment, software and firmware versions, network access, manufacturer interfaces, geography, licensing, and account permissions.
- Existing equipment
- Compatible systems can remain. Replacement or additional interface hardware is recommended only after the property review.
- Third-party services
- Availability and behavior can change with manufacturer software, APIs, vendor clouds, subscriptions, policies, internet service, or product support.
- Product status
- Stonehall One is pre-launch. Hardware, software, features, included services, regional availability, and appearance remain subject to change.
- Data handling
- Data paths and retention depend on the final deployment and connected platforms. They are reviewed as part of system design.
- Updates
- Update and maintenance requirements are established for the commissioned configuration and may include third-party dependencies.
- Ongoing care
- Stonehall Care is selectively available. Support, refinement, service scope, and cadence are confirmed separately for each property.
- Safety boundary
- Stonehall One is not an emergency-monitoring or life-safety system, and coordinated responses cannot guarantee prevention of damage, loss, injury, or interruption. Certified safety systems and emergency services remain independent.
Exact capabilities are documented for each commissioned property. Nothing on this page replaces a compatibility review or final system design.
View the complete technical recordPROPERTY FIT
Start with what the home
can sense and control.
A useful system begins with the actual home graph: installed equipment, available history, control paths, readback, household priorities, and the boundaries that should never be crossed.
01
EXISTING INTEGRATED HOME
Capable systems. Fragmented experience.
Relevant when lighting, climate, access, audio, video, network, or other installed systems are capable but do not behave as one property.
STONEHALL REVIEWS
- Exact models, versions, accounts, and available interfaces
- Network, equipment-room, licensing, and access conditions
- What can remain, what needs an interface, and what may need to change
02
RENOVATION
Coordinate before the property closes back up.
Relevant when an active project creates room to rationalize controls, infrastructure, and responsibilities while changes are still practical.
STONEHALL REVIEWS
- Systems to retain, replace, relocate, or add
- Rack, network, power, cabling, and equipment access
- Trade coordination, project timing, and commissioning gates
03
NEW CONSTRUCTION
Design the coordination layer from the start.
Relevant when the intended property experience can be defined across disciplines before individual systems are selected and commissioned.
STONEHALL REVIEWS
- Plans, system scopes, and intended property routines
- Responsibility and connection boundaries between specialists
- Commissioning, handoff, documentation, and care requirements
PROPERTY FIT REVIEW
See what Stonehall could learn and coordinate here.
Stonehall maps the available signals, controllable systems, household priorities, policy boundaries, and measurable opportunities before recommending a design.
- Map signals, controls, and readback
- Identify protection, resource, access, and care opportunities
- Define the first approved, measurable outcomes