How it works
Two paths in. One record out.
Ardyn either routes an operation your agent requests, or observes changes your systems already make. Both paths end in the same place: a receipt that separates what was claimed from what was observed.
Active and passive are separate on purpose.
Active execution
Your agent asks; Ardyn routes it
- An agent requests a capability.
- Ardyn selects the implementation and your connection.
- The provider performs the operation.
- Ardyn records the provider’s own observation and issues a receipt.
Passive observation
Your systems act; Ardyn watches
- You connect a system in observe-only mode.
- Ardyn reads the changes the provider reports.
- Nothing is executed on your behalf.
- Observations are recorded with the same receipt format.
The chain
Capability → implementation → connection → observation → receipt.
- 01
Capability
What can be done, independent of provider.
- 02
Implementation
The versioned pack that does it.
- 03
Connection
Your authorized account.
- 04
Observation
What the provider reported.
- 05
Receipt
The portable record of all of it.
ACTA across the lifecycle
ACTA is the state and evidence layer underneath. It supplies context to an operation before it runs — which connection, which scope, what came before — and receives evidence as it runs and after it finishes. It is not a log sink attached after the fact.