n8n4Runr
Projects

4Runr Project / AI Systems

Active

4Runr OS

Small agents.
One intelligent system.
Your hardware.

A local operating system for coordinated networks of specialized AI agents.

The agent

Think intelligent script.

Each agent has one job. It checks. It decides. It follows a protocol. Then it reports back.

Example — Infrastructure Monitor

  1. Check

    Is the service responding?

  2. Decide

    Is this temporary or an outage?

  3. Protocol

    Retry → Diagnose → Warn → Recover → Escalate

  4. Report

    Return the result to the system.

The agent handles the local job.

The system

One agent sees a problem.

The system sees the pattern.

Direction

Network Agent

Unusual traffic

Service Agent

Response time increasing

Security Agent

Repeated authentication failures

Main Agent / Orchestrator

This may be one incident, not three unrelated events.

Agent = local decision

Orchestrator = system-level understanding

Governed intelligence

Intelligence needs boundaries.

Giving AI the ability to act is different from giving it the ability to answer.

Direction

  1. 01Agent observations
  2. 02Orchestrator
  3. 03Proposed decision
  4. 04Jackel Kernel
  5. 05Allow / Refuse
  6. 06Shield
  7. 07Controlled action

Sentinel

The system doesn't just execute. It observes itself.

Jackel Kernel

Jackel decides what authority the system should allow.

  • Governance
  • Context
  • Permissions
  • Policy
  • Risk
  • Allowed actions

Shield

AI proposes. 4Runr verifies. Then the system acts.

Sentinel

The system doesn't just execute. It observes itself.

The bigger bet

Not one enormous AI doing everything.

Many small agents doing specific things well.

The future of agents may be hundreds of small pieces of intelligence embedded throughout real systems.

One watches infrastructure.

One watches security.

One watches communication.

One watches operations.

Each reports upward. One system understands what they mean together.

  1. Agents do the work

  2. Orchestrator sees the system

  3. Jackel governs decisions

  4. Shield protects execution

  5. Sentinel watches everything

  6. User-controlled hardware

The user's own machine becomes the execution environment. Agents stay close to the systems they are responsible for. Different models can be used depending on the job.

Current state

The platform exists. The product path is still being proven.

Built / Foundation

  • CLI
  • TUI
  • Server architecture
  • Docker execution environment
  • Foundational security systems

Current objective

  • Make one complete agent work

Direction

  • One working agent
  • Several agents
  • Coordinated network of agents

Current objective

Make one complete agent work.

  1. Define a job

  2. Launch the agent locally

  3. Detect something real

  4. Make a decision

  5. Interact with orchestration and governance

  6. Execute an authorized protocol

  7. Report the result

Then we make that path take minutes.