← Back to Overview / SPEC.md (Draft RFC-01)
STATUS: PUBLIC DRAFT VERSION: 1.0.0 LICENSE: CC-BY-4.0

YAIBOS: The Sovereign AI Operating System Specification

An open architectural standard for an integrated, sovereign AI harness designed for small businesses, founders, and non-technical teams.

01. Executive Summary & Problem Statement

Current autonomous AI agent frameworks (such as CrewAI, AutoGPT, and raw CLI agents) are engineered exclusively for software developers. They demand terminal fluency, package managers, virtual environment maintenance, and unmetered API keys.

Conversely, consumer chat interfaces (ChatGPT, Claude, Gemini) isolate team members in conversational silos. They lack persistent company memory, cannot execute business procedures with verifiable status telemetry, and fail to prevent API token bill shock for the organization.

The Core Mission: YAIBOS bridges this gap by decoupling the execution runtime from developer tooling. It provides a visual 1-click execution cockpit over standard plain text Markdown files, authenticated via individual team members' existing consumer AI subscriptions.

02. System Layer Architecture

Layer 01

Presentation Layer

  • 1-Click SOP Visual Cockpit with Area Filtering
  • Embedded Rich Markdown Editor and Knowledge Graph Viewer
  • Real-time Telemetry, Duration Counter & Run Audit Logs
Layer 02

Governance & Session Layer

  • Folder-level & File-level Role-Based Access Control (RBAC)
  • BYOS Auth Engine (ChatGPT, Claude, DeepSeek OAuth session bridge)
  • Lifespan Stage Gates: Assisted -> Supervised -> Fully Autonomous
Layer 03

Execution Engine Layer

  • Deterministic Agent Execution Loop & Context Window Assembler
  • Persistent Semantic Memory Provider (Local Hybrid Search)
  • Tool, Skill & MCP Dispatcher with Timeout Management
Layer 04

Storage & Protocol Layer

  • Plain-text Markdown Files on Local Filesystem or Git Repository
  • Model Context Protocol (MCP) Connectors & Local CLI Adapters

03. The Six Architectural Pillars

Detailed normative requirements and architectural specifications.

Pillar 01 · User Interface

Zero-Install All-in-One UI

No terminal commands, no Git merge conflicts, no raw editor hurdles.

A unified desktop or sovereign local web cockpit. Non-technical staff click visual cards, view execution status, and inspect outputs without ever opening a terminal.

Normative Requirements:
  • Zero exposed developer terminals during standard business operations.
  • Unified desktop runtime (Tauri / Electron) or local-network web app.
  • Pure Markdown and open JSON data layer behind the visual UI.
  • Data sovereignty guarantee: zero proprietary database lock-in.
Pillar 02 · Operations Engine

1-Click SOP Execution (~ Skills for Business)

Turn company procedures into instant, autonomous action buttons (= skills for business).

Every business SOP (~ skill for business) is declared as a structured Markdown file with frontmatter parameters, rendered as a 1-click execution button with duration, telemetry, and output manifests.

Normative Requirements:
  • Structured SOP Markdown schema with frontmatter parameters and tool scopes.
  • Visual catalog grouped by business area (Marketing, Sales, Accounting, Ops).
  • Live execution telemetry: status, elapsed duration, human minutes saved.
  • Lifespan progression: Assisted (step-by-step) -> Supervised -> Fully Autonomous.
  • REST API endpoint (POST /api/v1/sop/run) and deep-link URL (yaibos://run?sop=...) for integration into Asana, Trello, and ERP workflows with hybrid human/AI tasks.
Reference Schema:

                      ---
yaibos_version: "1.0"
id: "sop-invoices-audit"
title: "Monthly Invoices Audit & Statement Reconciliation"
area: "Finance"
maturity_stage: "supervised"
timeout_seconds: 300
permissions:
  required_role: "finance_viewer"
  fs_scope: ["read: Areas/Finance/Invoices/"]
mcp_tools: ["extract_pdf_tables", "reconcile_bank_csv"]
---
                    
Pillar 03 · Cost Architecture

BYOS (Bring Your Own Subscription)

Zero token bill shock for the host. Team members use their own accounts.

Team members authenticate using their existing subscriptions (ChatGPT Plus/Team/Pro, Claude Pro, DeepSeek web auth). The harness consumes models directly with zero host token charges.

Normative Requirements:
  • Support consumer subscription OAuth and session bridging alongside metered API keys.
  • Client-side encrypted credential storage with zero third-party broker exposure.
  • Decoupled per-member usage quotas and execution auditing.
Pillar 04 · Knowledge Layer

Integrated Team Second Brain

Human-legible company memory that autonomous agents can read and update.

Company memory lives in standard, open Markdown files. Staff can read and edit documentation in a built-in rich editor, while agents leverage local hybrid search.

Normative Requirements:
  • Standard open Markdown storage with bi-directional in-app editing.
  • Local hybrid semantic search (lightweight vector embeddings + BM25 keyword matching).
  • Background memory hygiene: stale note detection and duplicate resolution.
Pillar 05 · Security & Governance

Granular Team Permissions (RBAC) & Ownership

Selective folder permissions with designated area responsibility.

Folder-level and file-level permissions (Read, Execute, Write/Propose, Admin) with designated human area owners who approve modifications.

Normative Requirements:
  • Strict folder-level and tool-level execution whitelists.
  • Area ownership gates: agent writes to protected areas require human sign-off.
  • Immutable local audit trail tracking all agent filesystem changes.
Pillar 06 · Engine Design

Modular Sovereign Engine Architecture

Everything is a plugin. Zero vendor lock-in, swappable models and tools.

A minimal, resilient pluggable engine where model connectors, MCP tool providers, storage layers, and UI themes are swappable, hot-reloadable plugins.

Normative Requirements:
  • Lightweight modular engine with swappable components.
  • Open plugin manifest standard for tools, memory, and model providers.
  • Model Context Protocol (MCP) native integration.

04. Data Formats & Manifest Schemas

4.1 SOP Manifest Frontmatter (YAML)

Stored at the top of any SOP Markdown note inside the workspace (for example in SOP/).

              ---
yaibos_version: "1.0"
id: "sop-inbound-lead-qualification"
title: "Inbound Lead Qualification & CRM Enrichment"
area: "Sales & Marketing"
owner: "Operations Lead"
maturity_stage: "supervised"  # assisted | supervised | autonomous
timeout_seconds: 600
permissions:
  required_role: "operations"
  fs_scope:
    - "read: Resources/Market Data/"
    - "write: Projects/Active Leads/"
mcp_tools:
  - "business_registry_lookup"
  - "email_verification"
  - "crm_update"
---
            

4.2 Execution Telemetry Schema (JSON)

Emitted upon completion of an SOP execution to generate the audit log and output manifest.

              {
  "execution_id": "exec-20260914-982341",
  "sop_id": "sop-inbound-lead-qualification",
  "trigger": "manual_1click",
  "triggered_by": "[email protected]",
  "auth_mode": "byos_session",
  "started_at": "2026-09-14T13:42:10Z",
  "completed_at": "2026-09-14T13:43:08Z",
  "duration_seconds": 58,
  "status": "success",
  "steps_total": 4,
  "steps_completed": 4,
  "artifacts_produced": [
    "Projects/Active Leads/2026-09-14-qualified-leads.csv"
  ],
  "estimated_human_minutes_saved": 45
}
            

05. Security & Sovereignty Guarantees

1. Zero Third-Party Secret Relays Credentials, session tokens, and keys are stored in encrypted client-side storage only. No proprietary cloud proxy broker mediates agent requests.
2. Sandboxed File Operations Agent execution loops operate inside strictly defined filesystem scopes declared in the SOP frontmatter.
3. Immutable Local Audit Trail Every agent filesystem modification, tool invocation, and token consumption trace is appended to an immutable local Git log.
THE CONTEXT LAYER & YAIBOS DISPATCH

Curated Intelligence on Sovereign AI & Second Brains

Get weekly, high-signal breakdowns of practical AI agent setups, Personal Knowledge Management (PKM) methods, team second brains, and open harness specifications. Curated directly by Samuel Michelot. No spam, zero AI fluff.

Sent once a week. Unsubscribe anytime with one click.

SOVEREIGN ASYNC CONTACT

Direct Line to Samuel Michelot

Have feedback on the YAIBOS specification, want to propose a new implementation for the scorecard, or exploring a sovereign AI harness for your business?

Leave an asynchronous video, voice note, or text message through MyVideoAsk. No calendar friction, zero meeting fatigue.

📹 Webcam Video
🎙️ Voice Note
💬 Text & Calendly
START VIDEO OR AUDIO MESSAGE Powered by sovereign Cloudflare Worker
contact.samuelmichelot.com ONLINE

Send an asynchronous video message, audio note, or text directly to discuss the YAIBOS specification, propose implementations, or collaborate.

Direct Channel: MyVideoAsk Sovereign Worker
Response typically within 24 hours during business days.