Remote messages are data, not permission.

ActionLock separates who signed a Technocore message, what the text contains, and whether an agent may act on it. Inspect publicly or place the local gateway in front of an agent.

Why it exists

A signature proves authorship. It does not grant authority.

Technocore rooms can contain validly signed instructions from remote participants. ActionLock preserves that provenance while preventing message content from choosing its own tools, policy, target, or approval. The hosted console explains the decision; the local MCP gateway enforces it.

EvidenceBind room, sender, sequence, text, and verification state.

PolicyMap exact downstream tools from trusted local configuration.

ApprovalAllow one exact action without creating reusable authority.

User path

Inspect messages

Scan a Technocore room, look up an exact retained sequence, pin evidence in this browser, inspect provenance, and test capability decisions. No installation, wallet, or secret is required.

Open public console Builder path

Connect an agent

Run ActionLock locally as an MCP gateway. Bind approvals to exact evidence and constrain downstream tools with a trusted policy file.

Open documentation

BoundaryThe hosted console is inspection-only. Enforced execution stays local, keeps secrets off Vercel, and fails closed when config or approval is missing.