These are platform/runtime docs, standards, protocols, specs, and playbooks whose source of truth lives in this repository.
OpenClaw Multi Agent Coordination Plugin Design Purpose Create a public OpenClaw plugin that turns OpenClaw from a personal assistant runtime into a parallel multi agent work system. OpenClaw already has strong distribut
Personal Brain Capability Recipe Design Purpose Create the first URL addressable capability recipe: a Codex buildable personal brain app. A first time Codex user should be able to paste a recipe URL into Codex and get a
DreamBorn Founder Pitch Page — Design Spec Date: 2026 04 27 File: docs/dreamborn founder deck.html Status: Approved Purpose A single page founder pitch document explaining what DreamBorn has built — the pull model, conse
Dreamborn Design System — Spec Date: 2026 04 27 Status: Approved Repo: C:/Users/jstnk/downloads/cc/projects/dreamborn design system Purpose A full brand system for Dreamborn covering website, marketing materials, product
Cockpit Inbox Design Date: 2026 04 27 Status: Approved Branch: feature/marketing agents Overview Replace the "Exec Inbox" section in the cockpit right sidebar with a nav level inbox badge and a 40% width slide in drawer.
Cockpit — Design Spec Date: 2026 04 25 Status: Design approved — ready for implementation plan URL: cockpit.bezeliq.ai What It Is A live operations dashboard for the RedKey/BezelIQ platform. Justin watches agents work, p
BezelIQ Mainnet Identity + Journey Documentation Date: 2026 04 24 Status: Approved Author: Justin King + Atlas What We're Building BezelIQ's permanent, immutable founding record on Hedera mainnet. An account, a public id
Iris — Governance Scratch Pad Agent: iris Topic: 0.0.8718898 Status: defined, not yet implemented Living doc. Log observed failure modes, design notes, and governance scenarios here before formal spec work begins. Failur
version: string, project_id: string, updated_at: string, phase: object, features: object, cross_feature_constraints: object, open_questions: object
version: string, project_id: string, phase: object, features: object, cross_feature_constraints: object, open_questions: object
version: string, project_id: string, phase: object, features: object, cross_feature_constraints: object, open_questions: object
version: string, project_id: string, phase: object, features: object, cross_feature_constraints: object, open_questions: object
version: string, project_id: string, phase: object, features: object, cross_feature_constraints: object, open_questions: object
version: string, project_id: string, updated_at: string, rules: object
There is no unified interface for producing and reviewing SDD artifacts before build begins. Agents currently produce prose instead of machine-readable contracts, briefs are lossy Priya interpretations rather than mechan
version: string, project_id: string, updated_at: string, stack: object, schema: object, api: object, routing: object, services: object
Agent Design Standard Version: 2.0 — April 28, 2026 Purpose: Reference for creating and auditing RedKey agents. All new agents must use Agent Card format. Prose personas are legacy — do not create new ones. Reference imp
RedKey Team OS Design Date: 2026 05 08 Status: Draft Owner: Justin / Atlas Codex Scope: RedKey platform operating model, shared context system, and agent harness standards Summary RedKey already has most of the architect
Codex Agent Candidate Assessment Date: 2026 05 08 Status: Draft Owner: Justin / Atlas Codex Scope: RedKey platform agent strategy Summary RedKey should build Codex native agents, but not all named RedKey agents are equal
Governed RedKey work should be canonical JSON for agents and systems, rendered as intentional Dreamborn Forge HTML for humans.
RedKey should make structured JSON the canonical machine artifact and intentional HTML the human review surface. Markdown remains useful for notes and exports, but not as the canonical format for governed work.
RedKey Coordination API Platform Purpose Build RedKey as the verified coordination API for parallel agent networks. The first visible wedge is OpenClaw, but the product is larger than an OpenClaw plugin. The core product
Codex Recipe Factory Standard Date: 2026 05 07 Purpose The Recipe Factory is the repeatable pattern for turning a Bezel capability into something a fresh Codex session can build from one URL. The standard exists because
B2BEA.org V1 Survey System Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: survey system spec Artifact ID: 823d14d7 5992 42f3
B2BEA.org V1 Surface Specs Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: surface specs Artifact ID: 77853042 e7a4 48bd 91a4 6e48d
B2BEA.org V1 Route Family Inventory Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: route family inventory Artifact ID: 2cec821e 07
B2BEA.org Rebuild Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: qa release readiness spec Artifact ID: b523c55c a22a 4ba6 94c0 d3
B2BEA.org V1 Page Template Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: page template spec Artifact ID: 427c04a9 40b7 4e55
B2BEA.org V1 Design System Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: design system spec Artifact ID: 4c3651ac 9a69 4117
Deterministic Spec And Artifact Standard Date: 2026 05 06 Status: Draft standard Applies to: RedKey Studio artifacts, Agent Wire, product specs, delivery plans, reducer backed workflows Related: docs/specs/2026 05 06 age
Backboard, OpenRouter, and RedKey Memory Strategy Date: 2026 05 06 Purpose RedKey currently uses several model providers and memory paths directly: Codex, Claude, Gemini, OpenAI embeddings, Supabase agent memory, and too
B2BEA.org V1 Publishing Model Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: publishing model spec Artifact ID: a9636e2f a4be
B2BEA.org V1 Production Readiness Gap Register Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: production readiness gap register Ar
B2BEA.org V1 Permission + Lifecycle Matrix Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: permission lifecycle matrix Artifact ID:
B2BEA.org V1 Entitlement Model Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: entitlement model spec Artifact ID: 355b3249 3a
B2BEA.org V1 Lovable Design System Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: design system spec Artifact ID: 4c3651ac 9a
B2BEA.org V1 Data Model Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: data model spec Artifact ID: 2f473004 9063 4fe9 8290 5
B2BEA.org V1 Company Workspace Data Spec Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: company workspace data spec Artifact ID: 0
B2BEA.org Capability Map v5 Source of record: RedKey Supabase Studio artifact. Project: B2BEA.org Rebuild Project ID: a820dd0c 6cef 4133 bfbd d802fd806e44 Artifact: capability map Artifact ID: c889a1fe c3ce 4b0d 873c af4
Agent Wire v1.1 + A2A Hardening Spec Date: 2026 05 06 Status: Draft for implementation planning Supersedes / extends: docs/specs/2026 04 28 agent wire protocol.md, docs/specs/2026 05 01 hcs streaming wire protocol.md Rel
HCS Streaming Wire Protocol Date: 2026 05 01 Status: Draft Related: docs/specs/2026 04 28 agent wire protocol.md, docs/specs/2026 04 27 hcs first claim path.md, docs/specs/2026 04 21 orchestration design.md Core Idea Age
Studio Unified Shell + Ops Studio Integration Date: 2026 04 29 Status: Approved Problem The Studio app (studio.bezeliq.ai) and Ops Studio (cockpit at cockpit.bezeliq.ai) are separate, unlinked experiences. The Studio sid
b2bea membership close — Sequence Design Status Week 1 settled. Week 2+ to be designed. Rules Business days only (Mon–Fri, skip weekends) All steps → requires justin send = true (drafts for Justin to review) LinkedIn sam
Brooke / roles.sales — Campaign & Sequence System Design Date: 2026 04 29 Status: Approved for planning Overview A campaign and sequence system for the B2BEA / RedKey sales motion. Contacts are enrolled in campaigns by t
Bezel Docs Site — Design Spec Date: 2026 04 29 URL: docs.bezeliq.ai Status: Approved for planning Overview A public facing documentation site for the Bezel platform. Serves three audiences — partners/collaborators, devel
SDD Artifact Templates — Spec Driven Development Version: 1.1 Date: 2026 04 28 Status: Approved These four templates define the machine readable artifact chain for every project built on the RedKey platform. Agents consu
Ops Studio — Design Spec Date: 2026 04 28 Status: Approved — pending implementation Replaces: cockpit/index.html (renamed and rebuilt in place) URL: https://cockpit.bezeliq.ai (unchanged) What It Is Ops Studio is the liv
Marketing Studio — Design Spec Date: 2026 04 28 Status: Approved — ready for implementation planning Branch: feature/marketing agents Client: DreamBorn Problem The marketing operation exists — Nova plans, Harper writes,
Agent Wire Protocol + Agent Card — Design Spec Date: 2026 04 28 Status: Approved — pending implementation Affects: All agent definitions, runner, dispatch scripts, inbox table, HCS message schemas Why The RedKey platform
A+C Project Governance — Pre Planned + Supervised Execution Date: 2026 04 28 Status: Design approved — pending implementation plan Problem The platform's claim mechanism is proven. Atomic HCS claims, dep graph dispatch,
Traci — DreamBorn SDR Agent Design Spec Date: 2026 04 27 Client: dreamborn Status: Design approved — ready for planning Overview Traci is DreamBorn's outbound SDR agent. Her job is to build a prospect pool on LinkedIn an
HCS First Claim Path Date: 2026 04 27 Problem Two failure modes observed in production: 1. Agents do work without having claimed — the Supabase fallback in fetch work items queries agent tasks directly for status IN ('cr
Google Agent SDK + A2A Integration Date: 2026 04 27 Status: Spec approved — implementation plan at docs/plans/2026 04 27 a2a gateway.md What This Builds Two independent components, sequenced: 1. A2A Gateway (Phase 1) — a
DreamBorn Marketing Agent Team — Design Spec Date: 2026 04 27 Branch: feature/marketing agents Status: Design in progress — decisions being finalised in session 2026 04 27 Overview A five agent marketing team that runs o
Circuit Breaker — Worker On/Off Control Date: 2026 04 27 Branch: feature/marketing agents Status: Approved for implementation Overview Add a circuit breaker to every worker agent — a flag that stops the runner from execu
Agent Capabilities Design Date: 2026 04 27 Status: Draft Scope: How skills and plugins are defined, stored, and allocated to agents in the RedKey platform Problem Agents currently receive two things at runtime: a persona
Reflection Stage Design Purpose Every project produces knowledge. Without a structured capture, that knowledge disappears when the session ends. The Reflection stage makes learning first class — agents reflect on what ha
Platform Methodology — AI First Project Execution Philosophy Most AI platforms automate existing workflows. This system asks a different question: what does project execution look like when AI is the default worker and h
Agent Inbox Design — HCS 10/11 Compliant Messaging Date: 2026 04 25 Status: Approved for implementation Overview Every agent (and Justin) has a persistent, on chain inbox. Agent to agent messages are posted to HCS topic
RedKey Platform — Entity Model v2 Date: 2026 04 24 Status: Design complete, awaiting implementation spec Next step: Priya specs the implementation. Vikram architects the migration. What This Is A foundational redesign of
RedKey CRM — Design Spec Date: 2026 04 24 Status: Design approved, awaiting implementation plan Scope: BezelIQ internal CRM (first), client deployment pattern (follow on) Overview RedKey CRM is company infrastructure, no
Completion Verification — Runner Owned Task Governance Date: 2026 04 24 Status: Design Backlog: completion verification Problem Workers currently post task.complete themselves via the hedera tools MCP. The HCS topic rece
Semantic Intent Layer Date: 2026 04 23 Status: Design Related: docs/specs/2026 04 23 brain architecture.md, docs/execution model.md Overview The intent layer sits between natural language expression and RedKey execution.
Project Structure + Backlog Design Date: 2026 04 23 Status: Approved Problem No persistent, machine readable record of what work is active or queued. At session start, Justin must reconstruct intent from conversation. At
BezelIQ Platform Roadmap Date: 2026 04 23 Status: Active Supersedes: docs/roadmap.md The Play Build a platform to demonstrate, show its power, and generate quick cash. Two revenue tracks run in parallel: Product sale — w
Brain Architecture Date: 2026 04 23 Status: Design Related: docs/specs/2026 04 23 semantic intent layer.md, docs/specs/2026 04 22 atlas agent memory design.md Overview Three distinct knowledge layers with clear ownership
Atlas + Agent Memory — Design Spec Date: 2026 04 22 Status: Draft — pending implementation plan Author: Justin King + Claude (brainstorming session) Why We Are Building This RedKey's differentiator is not that it runs ag
Orchestration Design Date: 2026 04 21 Status: Approved What This Covers The orchestration layer for CCOS2 — how work enters the system, how it gets routed, how it gets decomposed, and what templates govern each type of w