Customer and site boundaries come first.
Access must follow the customer, site, role, and responsibilities assigned to a person. Our requirement for Assist is to work within those boundaries when finding records or helping with a request.
AI SAFETY & HUMAN CONTROL
Your infrastructure supports real operations. Our standard for S.P.E.C.T.R.A. Assist is useful assistance within defined limits, supported by evidence and accountable people.
BOUNDARIES BY DESIGN
These are design and release requirements. They describe the standard we are building toward, rather than certify the capabilities of a live deployment.
Access must follow the customer, site, role, and responsibilities assigned to a person. Our requirement for Assist is to work within those boundaries when finding records or helping with a request.
A conversation must not grant additional access or bypass required authorization. The application must enforce the limits on which information and actions are available to each person.
Original evidence and change history should remain available when information is updated. People need a way to review AI-assisted work, correct mistakes, and understand the evidence behind a reported result.
AI assistance needs clear limits and accountable human oversight. Authorized people must be able to pause AI actions and retain control of the work when a situation requires their attention.
ILLUSTRATIVE EXAMPLE
Suppose someone asks whether a connection can be removed. A label or an AI summary alone cannot establish everything that depends on it. The relevant records, their currency, and the field conditions all matter.
Understand which documents and recorded observations inform an answer.
Make gaps, conflicts, or unverified conditions clear to the person deciding.
Use qualified judgment and the authorization appropriate to the work.
AI-assisted information supports a decision. The people responsible for the site still need to understand the consequences of the work.
Hypothetical scenario illustrating our approach; not a customer case study or a demonstration of live automation.
TESTED CLAIMS / CLEAR EXPECTATIONS
Each public safety claim should connect to an implemented control and a verification test. We distinguish our design commitments from the safeguards verified for a particular release.
Explore AssistThese pages describe LAYER1’s philosophy and design commitments for Assist. Capability availability and verified safeguards will be documented for each release.
START WITH YOUR SITE
Talk with LAYER1 about your infrastructure, access requirements, and the information your people need to work from.