Noxgild
Security

Command Lifecycle

Understand how Noxgild records work from queueing through execution and final state.

Noxgild stores durable command state so a requested action does not become an unverified fire-and-forget operation.

Typical lifecycle states include QUEUED, CLAIMED, EXECUTING, SUCCEEDED, FAILED, and UNKNOWN.

The executor, worker, and policy checks determine how the command can proceed.

UNKNOWN is intentionally conservative: a consequential side effect may have happened, but Noxgild cannot safely prove the final state.

Do not blindly replay an UNKNOWN command. Verify the real-world result first.

Client Access Keys

Use scoped client credentials only for supported clients that cannot use the intended OAuth path.

Browser Trust Boundary

Understand why untrusted web content cannot silently authorize local Machine or Desktop actions.