← Back to Platform

Airlock & MUNX Protocol Visa

Cryptographic Swarm Governance

Overview

Autonomous agents require strict Identity and Access Management (IAM). Multinex utilizes MUNX Protocol Visa (Verified Identity & Sovereign Authorization) to grant cryptographically verifiable clearance to agents, managed via a Git-native Airlock bridge.

Airlock & MUNX Protocol Visa Topology

[ Enterprise PM Tool ] (Jira/Linear)
         │
         ▼ (Webhook)
[ Airlock Sync Engine ] ──> Translates ticket to Markdown (.md)
         │
         ▼
[ Local Board Directory ] <── [ Diplomat Agent (L3 Clearance) ]
                                - Reads markdown task
                                - Executes tool logic
                                - Generates payload
                                     │
[ Governance Gateway ] <─────────────┘
  - Checks IPFS for MNXS-ID
  - Verifies Ed25519 signature
  - If valid: Commit execution
  - If invalid: Revoke VISA / Terminate thread
ARCHITECTURAL CONSTRAINT: THE I/O BOTTLENECKAirlock utilizes Git-tracked Markdown for absolute auditability. However, Git commits are disk I/O heavy. Attempting to use Airlock for high-frequency, intra-swarm communication (Micro-Messaging) will result in severe Git history bloat and immediate system degradation.
RECOMMENDED SOLUTION: THE BIFURCATED ROUTING STRATEGY
  1. Macro-Governance (Airlock): Use Airlock strictly for initial task assignment. Translate a Jira/Linear ticket into an air-gapped Markdown file. The human supervisor signs this file, granting the lead agent a MUNX Protocol Visa to begin the multi-hour project block.
  2. Micro-Messaging (M.A.R.S Redis): Once authorized, the lead agent spawns a swarm. All high-velocity communication (e.g., thousands of sub-task negotiations per minute) transitions to the M.A.R.S Redis Pub/Sub bus. This keeps chatter entirely in-memory with zero disk latency.
  3. Final Egress (Shield + Airlock): Upon completion, the "Diplomat" agent aggregates the final result. The outbound payload passes through the Multinex Shield firewall for redaction, and the sanitized summary is committed back to the Airlock as a single Git state change.

The Execution Path

  1. Task Sync: The Airlock bridge continuously pulls tickets from Jira and drops them into an air-gapped markdown directory.
  2. Checkout: A Diplomat Agent reads the task. To execute a system command (e.g., writing to a protected database), the agent must sign the request payload using its private Ed25519 key.
  3. Verification: The system checks the signature against the agent's public MNXS-ID registry.
  4. Audit: Every commit to the codebase or database is tagged with a Git Trailer: MUNX-VISA-SIG: <ed25519_hash>, ensuring perfect attribution.