Start here

Pick the system or task you're working on, then follow the relevant reading path. This section also explains the terminology, sources and safety labels used in the wiki.

On this page

Overview#

Physical security integrations cross disciplines that use the same words differently. A camera, door controller, BMS gateway, message broker, and cloud API may all expose an “event,” yet differ on delivery, ordering, acknowledgement, retention, identity, and time. These pages establish the shared vocabulary and evidence rules needed before protocol detail.

Reading order#

How to use this knowledge base
Scope and boundaries
Verification and safety
Glossary and conventions
Choose a route in learning paths
Read the protocol landscape, then the relevant foundation and protocol pages

What this wiki helps with#

Correct classification: electrical interface, data link, transport, media format, application protocol, profile, API, and product are kept distinct.
Integration decisions: pages call out actors, trust boundaries, state models, failure semantics, version scope, and migration concerns.
Defensible claims: facts that can change are dated and sourced close to the claim.
Safe failure: advice accounts for physical effects, degraded modes, and independent life safety functions.
Maintainability: one canonical page per topic, controlled metadata, relative links, explicit gaps, and scheduled review.

Useful shortcuts#

Need	Go to
Understand where a protocol sits	Architecture and layering
Design an event integration	Events, state, commands, and time
Reason about authentication	Identity, authentication, and authorisation
Understand certificates	TLS, PKI, and certificates
Review physical interfaces	Serial and field interfaces
Check evidence quality	Source policy
Contribute a correction	Contribution guide

Return to the root index.