Home /Modules/vm/CHALLENGE-REPORTS-MANAGER.md

CHALLENGE-REPORTS-MANAGER.md

lib/vm/CHALLENGE-REPORTS-MANAGER.md · 31 line(s) · markdown

<p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela/sleela-vm-creator-logo-001.jpg" alt="SLeeLa VM Creator" width="100%"></p>

Challenge Manager and Reports Manager

Challenge Manager

The Challenge Manager provides declared, bounded diagnostic challenge probes and canaries. It does not inject arbitrary hidden executable payloads. A challenge may be installed locally or on an explicitly authorized remote SLVM target through existing capability, certificate, security, and resolver controls.

When a declared system state or binary result matches its condition, the manager emits a ConditionObserved event. Authorized delivery may use a registered listener, computer identity, IP/port endpoint, or messaging endpoint. Remote delivery is authenticated, capability-scoped, auditable, and resolver-aware.

Editions

Reports Manager

Reports Manager provides authorized observation of system input, output, messages, and system records. Records are converted into named binary output objects and routed through the IQ/system-output path. Named binary objects are typed data records, not executable payloads.

Authorized records can be forwarded through a messaging API. Stream authorization, object identity, sequencing, destination authorization, and audit policy apply.

Common flow

System -> capability/security boundary -> challenge or report record -> named binary object -> IQ/output routing -> authorized listener or messaging API.

Build integration

The package build is available with make -C lib/vm and from the repository root with make vm. The Compiler Manager contract is reviewed before VM package objects are considered ready for assembly; the build does not silently change the declared VM inventory.