How It Works Architecture Operators Guard Companies About Activate
Infrastructure

Patent-protected
infrastructure.
Built from the
inside out.

NorixPlatform is not a feature set. It is an architectural position. Every design decision was made around a single question: when something goes wrong, can the operator prove what they knew, what they did, and when they did it?

01
Layer One

Operational Notice Record

The staff-facing layer. Community managers, maintenance coordinators, leasing staff, and contracted guards all operate here.

Every entry requires a location designation. Every entry is time-stamped automatically. Every entry captures the initial response taken. Staff identifiers are attached to every record.

The canonical action is Log Documented Notice. The language is precise because the legal word that governs multifamily duty is notice. Layer 1 is where that chain begins.


02
Layer Two

Encrypted Incident Archive

System-owned. Not accessible through the operational interface.

Layer 2 holds the pattern record across the property over time. Condition frequency by location. Response action documentation by staff. Portfolio-level visibility across every deployed property.

A single notice

Establishes awareness of a condition at a specific location on a specific date.

A pattern of notices

Establishes that the operator managed foreseeability systematically. That distinction matters in litigation.


03
Layer Three

Encrypted Evidence Bundle

The EEB is created intentionally. Never automatically. It requires a deliberate decision by the operator and legal counsel.

Before an EEB is shared, the receiving party acknowledges three things:

01 Correlation is not attribution
02 The system provides no determinations
03 The receiving party retains full discretion

The controlled disclosure protocol creates its own record. The operator can show not just what was documented but how it was disclosed and to whom.

Structural Requirement

Location designation
is mandatory.

Every documented notice requires a location designation before submission. This is not a user preference. It is a structural field.

Common Area

Lobbies, corridors, common spaces. Carries a distinct duty weight under multifamily law.

Parking Structure

Garages, surface lots, access points. Separate duty consideration from interior spaces.

Amenity Space

Pool, gym, clubhouse, rooftop. Each carries a specific invitation and responsibility profile.

Location designations are configured at the property level during onboarding. The system requires operators to think in locations because duty law thinks in locations.

Advisory Layer

Live Language Advisory.

The platform includes an advisory layer that flags documentation language that could create Fair Housing exposure and presents an alternative phrasing. Staff choose. The system records what was chosen.

The advisory layer never blocks an entry. It never rewrites staff language. It is advisory only. The operator's judgment governs. The platform makes sure that judgment is informed.

Fair Housing Architecture

Structural by design.

The system documents conditions and locations. Never individuals. Never behavior. Never residents by name.

This is not a policy commitment. It is the architecture. There is no field in the system that accepts individual identification in the operational layer. The separation is structural. It cannot be done the wrong way.

U.S. Patent No. 11,830,346 B2 · Patents Pending

The patent.

NorixPlatform operates on issued U.S. Patent No. 11,830,346 B2 with additional patents pending. The patent covers the foundational architectural separations that define how private-property operational communication infrastructure functions.

This is not a feature patent. It is an infrastructure patent. Anyone attempting to replicate how NorixPlatform's systems communicate across private-property boundaries is operating inside issued patent claims.

Activate