Passes the checks
The input meets the rules you configured. Your application still applies its own operating and safety controls before acting.
SSX_AEGIS / PYTHON SDK
0.2.0 · BETA · PRIVATE ACCESSCheck the data before your software acts on it.
The SSX_AEGIS Python SDK checks where a reading came from, whether it makes sense, and whether the requested action is allowed. It keeps the result and the reasons, so your team can review what happened.
FOUR SEPARATE CHECKS
Check the sender and signature, and look for old or repeated records.
Compare the reading with expected conditions and the source’s track record.
Check who is asking and what they have permission to do.
Apply your team’s rules for approval, limits, and recovery.
THE DECISION RECORD
Each result explains which checks passed and which did not. Connecting these results to a machine or application takes separate integration work.
The input meets the rules you configured. Your application still applies its own operating and safety controls before acting.
Keep the reading on screen for someone to review. Do not let it trigger an automatic response.
A required check failed. Keep the result and the reason so your team can investigate.
A read-only pilot checks inputs and records results without controlling your system. For example, compare its assessment of a machine alert with the operator’s decision before considering automation.
The SDK’s linked record history and signed checkpoints help reviewers spot changes to saved decisions. They do not prove that the original reading was accurate.
PRIVATE CLIENT ACCESS
The SDK and its documentation are private. Approved clients receive them under a written SSX360 license, with access and support agreed directly.
Pick one type of input, such as a sensor alert or a software request. Agree what a good result looks like and who will review it.
Agree the license, price, delivery, and support. We share client materials through a private channel.
Run a read-only pilot alongside your existing checks. Review the results together before deciding on a wider rollout.
PRIVATE ACCESS
Describe the data coming in, the action it could trigger, and who reviews it today. We’ll discuss a small pilot and the work needed to connect it.
Keep the first message non-sensitive. Licensing, delivery, and commercial terms are agreed directly.