Appearance

Operational Protocols ​

Arkhein's operational protocols ensure that the system maintains integrity, security, and reliability while providing powerful cognitive capabilities.

Safety & Sovereign Integrity ​

Silo Guard (Security) ​

The Silo Guard enforces a strict Managed Folders Boundary. All file operations (read, write, list) are filtered through realpath normalization and boundary checks. This prevents path traversal attacks and unauthorized file access.

Self-Healing Integrity ​

Arkhein uses a self-healing protocol to maintain the accuracy of its memory.

  • Drift Detection: Lightweight disk signatures for autonomous sync.
  • Shadow Rebuilds: Zero-downtime vector indexing using shadow directories and atomic swapping.
  • HealSiloJob: Automatically triggered to reconcile disk-to-database drift.

Agent Lifecycle & Visibility ​

Earthbeat Monitor ​

The Earthbeat Monitor provides real-time visibility into Arkhein's multi-pass background pipeline. Users can monitor indexing progress, reasoning stages, and tool execution states.

Task Registry ​

The Task Registry maintains a persistent system_tasks table for tracking long-running background processes (e.g., seeding a large folder). This ensures work is never lost if the application is restarted.

Agent Workspace ​

Each reasoning task occurs within a durable on-disk Scratchpad workspace. This provides a clear audit trail of the agent's intermediate work and allows for physical validation of its reasoning.

Concurrency & Reliability ​

Re-entrant Locking ​

Arkhein uses partition-isolated locking with exponential backoff. This ensures high-concurrency safety for database and vector index operations without deadlocking the UI.

Smart Model Matching ​

To ensure zero-config reliability, Arkhein uses tag-lenient model matching. It will attempt to resolve requested models (e.g., mistral) to their local equivalents (e.g., mistral:latest) automatically.

Debug Checklist ​

  1. Managed Folders: Confirm directory is authorized and accessible.
  2. Knowledge SSOT: Check the knowledge table for correct row counts and metadata.
  3. Vektor Integrity: Verify the vector.bin exists and matches model dimensions.
  4. Task Status: Check the Task Registry for stalled or failed background jobs.
  5. Logs: Review storage/logs/laravel.log for execution trace and SLM errors.