Back to all
Planned

Automation triggers

A condition-to-action engine is designed as a separate bounded context.

Defendy control panelPlanned
Interface not presented as live

This capability is on the roadmap, so the site shows its status instead of inventing a finished control.

Roadmap

What is included

  • Not presented as generally available
  • Will be documented after production verification

Admin problem

A clear rule instead of guesswork

An administrator needs to configure the capability once, see its actual status and understand the expected result.

  • Designed for backward compatibility
  • Feature-flagged delivery
  • Status shown transparently

How it works

Status controls the interface

The direction is documented, but no finished control is shown before implementation.

Expected action

A visible result

Defendy does not perform this as a generally available capability yet.

Source of truth

Verifiable product status

We do not publish unverified scale or availability claims. These paths are the evidence for this status.

  • docs/target-architecture-v2/03-bounded-contexts.md

Documentation

Related guides