{
  "title": "AlefOS Blog",
  "url": "https://alefos.ai/blog",
  "jsonUrl": "https://alefos.ai/blog/index.json",
  "rssUrl": "https://alefos.ai/rss.xml",
  "lastUpdated": "2026-07-29",
  "categories": [
    {
      "name": "Founder Notes",
      "description": "Notes about why AlefOS is being built and what the product is meant to protect.",
      "count": 1
    },
    {
      "name": "Product",
      "description": "Product explanations grounded in the public AlefOS surface and current documentation.",
      "count": 2
    },
    {
      "name": "Engineering",
      "description": "Technical notes about the public architecture, MCP access model and operating boundaries.",
      "count": 1
    },
    {
      "name": "Operational AI",
      "description": "Practical distinctions between AI output and durable operational context.",
      "count": 1
    },
    {
      "name": "Guides",
      "description": "Readable paths for using AlefOS with existing work systems and public documentation.",
      "count": 1
    }
  ],
  "articles": [
    {
      "slug": "why-alefos-exists",
      "title": "Why AlefOS Exists",
      "description": "AlefOS exists because work does not fail only when a conversation is lost. It fails when context, commitments and next actions stop travelling together.",
      "excerpt": "The real problem is not finding one message. It is preserving the useful state of work across calls, messages, meetings and the actions that follow.",
      "category": "Founder Notes",
      "tags": [
        "operational memory",
        "work context",
        "decisions",
        "follow-up"
      ],
      "author": {
        "name": "AlefOS",
        "role": "Product and engineering notes"
      },
      "publishedAt": "2026-07-29",
      "updatedAt": "2026-07-29",
      "readingTime": 2,
      "featured": true,
      "coverImage": {
        "src": "https://alefos.ai/resources/articles/why-alefos-exists/cover.svg",
        "alt": "Calls, messages and meetings converging into an AlefOS operational memory briefing.",
        "width": 1600,
        "height": 900
      },
      "heroImage": {
        "src": "https://alefos.ai/resources/articles/why-alefos-exists/hero.svg",
        "alt": "Detailed visual of dispersed calls, messages and meetings becoming shared operational memory.",
        "width": 1600,
        "height": 900
      },
      "ogImage": "https://alefos.ai/resources/articles/why-alefos-exists/og.png",
      "url": "https://alefos.ai/blog/why-alefos-exists",
      "jsonUrl": "https://alefos.ai/blog/why-alefos-exists.json"
    },
    {
      "slug": "ai-summaries-are-not-operational-memory",
      "title": "AI Summaries Are Not Operational Memory",
      "description": "A summary describes an event. Operational memory connects events, people, decisions, promises and next actions over time.",
      "excerpt": "Useful AI output is not enough when the work continues after a single call or meeting. AlefOS treats continuity as the product surface.",
      "category": "Operational AI",
      "tags": [
        "AI summaries",
        "memory",
        "context",
        "continuity"
      ],
      "author": {
        "name": "AlefOS",
        "role": "Product and engineering notes"
      },
      "publishedAt": "2026-07-29",
      "updatedAt": "2026-07-29",
      "readingTime": 2,
      "featured": false,
      "coverImage": {
        "src": "https://alefos.ai/resources/articles/ai-summaries-are-not-operational-memory/cover.svg",
        "alt": "A one-off AI summary separated from a connected AlefOS operational timeline.",
        "width": 1600,
        "height": 900
      },
      "heroImage": {
        "src": "https://alefos.ai/resources/articles/ai-summaries-are-not-operational-memory/hero.svg",
        "alt": "Detailed visual comparing a one-off AI summary with connected operational memory over time.",
        "width": 1600,
        "height": 900
      },
      "ogImage": "https://alefos.ai/resources/articles/ai-summaries-are-not-operational-memory/og.png",
      "url": "https://alefos.ai/blog/ai-summaries-are-not-operational-memory",
      "jsonUrl": "https://alefos.ai/blog/ai-summaries-are-not-operational-memory.json"
    },
    {
      "slug": "from-conversations-to-action",
      "title": "From Conversations to Action",
      "description": "Turn conversations into action means connecting calls, messages, meetings and context to decisions, missions and human validation.",
      "excerpt": "AlefOS treats conversation as the beginning of work, not the final artifact. The useful outcome is a next action that still has its context.",
      "category": "Product",
      "tags": [
        "missions",
        "calls",
        "meetings",
        "human validation"
      ],
      "author": {
        "name": "AlefOS",
        "role": "Product and engineering notes"
      },
      "publishedAt": "2026-07-29",
      "updatedAt": "2026-07-29",
      "readingTime": 2,
      "featured": false,
      "coverImage": {
        "src": "https://alefos.ai/resources/articles/from-conversations-to-action/cover.svg",
        "alt": "A structured flow from conversations to context, decision, mission and validated action.",
        "width": 1600,
        "height": 900
      },
      "heroImage": {
        "src": "https://alefos.ai/resources/articles/from-conversations-to-action/hero.svg",
        "alt": "Detailed visual showing conversations becoming context, decisions, missions and validated actions.",
        "width": 1600,
        "height": 900
      },
      "ogImage": "https://alefos.ai/resources/articles/from-conversations-to-action/og.png",
      "url": "https://alefos.ai/blog/from-conversations-to-action",
      "jsonUrl": "https://alefos.ai/blog/from-conversations-to-action.json"
    },
    {
      "slug": "why-ibox-was-built",
      "title": "Why IBOX Was Built",
      "description": "IBOX was built for messages that need interpretation, priority and context, not for another generic inbox.",
      "excerpt": "A raw message can be too long, too vague or too easy to misread. IBOX turns the useful work state into a briefing that can connect to actions and context.",
      "category": "Product",
      "tags": [
        "IBOX",
        "messages",
        "briefings",
        "context"
      ],
      "author": {
        "name": "AlefOS",
        "role": "Product and engineering notes"
      },
      "publishedAt": "2026-07-29",
      "updatedAt": "2026-07-29",
      "readingTime": 2,
      "featured": false,
      "coverImage": {
        "src": "https://alefos.ai/resources/articles/why-ibox-was-built/cover.svg",
        "alt": "A raw message being transformed into an AlefOS IBOX briefing with context and next actions.",
        "width": 1600,
        "height": 900
      },
      "heroImage": {
        "src": "https://alefos.ai/resources/articles/why-ibox-was-built/hero.svg",
        "alt": "Detailed visual showing raw messages, tone and priority becoming an IBOX briefing.",
        "width": 1600,
        "height": 900
      },
      "ogImage": "https://alefos.ai/resources/articles/why-ibox-was-built/og.png",
      "url": "https://alefos.ai/blog/why-ibox-was-built",
      "jsonUrl": "https://alefos.ai/blog/why-ibox-was-built.json"
    },
    {
      "slug": "building-an-mcp-first-operational-system",
      "title": "Building an MCP-First Operational System",
      "description": "AlefOS exposes operational context to AI assistants through MCP while keeping permissions, tenants and human validation central.",
      "excerpt": "MCP is an access layer for authorized capabilities. In AlefOS, it should make business context readable without turning every AI suggestion into unchecked execution.",
      "category": "Engineering",
      "tags": [
        "MCP",
        "permissions",
        "tenants",
        "ChatGPT",
        "AI assistants"
      ],
      "author": {
        "name": "AlefOS",
        "role": "Product and engineering notes"
      },
      "publishedAt": "2026-07-29",
      "updatedAt": "2026-07-29",
      "readingTime": 2,
      "featured": false,
      "coverImage": {
        "src": "https://alefos.ai/resources/articles/building-an-mcp-first-operational-system/cover.svg",
        "alt": "ChatGPT and other assistants accessing AlefOS through an MCP permission layer.",
        "width": 1600,
        "height": 900
      },
      "heroImage": {
        "src": "https://alefos.ai/resources/articles/building-an-mcp-first-operational-system/hero.svg",
        "alt": "Detailed visual of assistants using a permissioned MCP layer to reach AlefOS capabilities.",
        "width": 1600,
        "height": 900
      },
      "ogImage": "https://alefos.ai/resources/articles/building-an-mcp-first-operational-system/og.png",
      "url": "https://alefos.ai/blog/building-an-mcp-first-operational-system",
      "jsonUrl": "https://alefos.ai/blog/building-an-mcp-first-operational-system.json"
    },
    {
      "slug": "alefos-works-with-the-tools-you-already-use",
      "title": "AlefOS Works With the Tools You Already Use",
      "description": "AlefOS is designed to unify context above existing work tools where providers are available, rather than requiring every team to replace its systems first.",
      "excerpt": "The practical path is to connect signals from existing calls, messages, meetings and groups into one operational layer without inventing unavailable integrations.",
      "category": "Guides",
      "tags": [
        "providers",
        "integrations",
        "calls",
        "meetings",
        "WhatsApp"
      ],
      "author": {
        "name": "AlefOS",
        "role": "Product and engineering notes"
      },
      "publishedAt": "2026-07-29",
      "updatedAt": "2026-07-29",
      "readingTime": 2,
      "featured": false,
      "coverImage": {
        "src": "https://alefos.ai/resources/articles/alefos-works-with-the-tools-you-already-use/cover.svg",
        "alt": "Existing work tools feeding authorized context into AlefOS.",
        "width": 1600,
        "height": 900
      },
      "heroImage": {
        "src": "https://alefos.ai/resources/articles/alefos-works-with-the-tools-you-already-use/hero.svg",
        "alt": "Detailed visual of existing work channels feeding the AlefOS context layer.",
        "width": 1600,
        "height": 900
      },
      "ogImage": "https://alefos.ai/resources/articles/alefos-works-with-the-tools-you-already-use/og.png",
      "url": "https://alefos.ai/blog/alefos-works-with-the-tools-you-already-use",
      "jsonUrl": "https://alefos.ai/blog/alefos-works-with-the-tools-you-already-use.json"
    }
  ]
}