BMT-12.05 Executive Summary#
BlueMirror.tech | May 2026#
Beatrice Mensah runs a four-person software company in Nairobi that builds accessibility software for users with motor impairments. Her flagship product is a kitchen-task assistant for people with essential tremor and Parkinson’s. After two years selling it as a standalone application, she has concluded that distribution is the bottleneck. The product needs to reach users through a platform they already use, not through an app store they have to discover. The BlueMirror SDK is one of the platforms her team is evaluating. What she is verifying is whether the platform’s technical and governance commitments match the promises, and what the boundary is between an SDK skill her team would build and the BGO Context Shards her clinical advisors might create separately.
The SDK provides the tools and integration interfaces for third-party developers to build skills that operate within BlueMirror’s deployment. A skill is a unit of capability the agent layer can call. Skills integrate at the L-layer. The architecture’s separation of the H-layer (one slow, deliberative brain per subscriber holding the full context) and the L-layer (many fast, specialized hands executing one task each) is the load-bearing pattern. The developer’s skill operates as an L-layer hand: it receives a structured request from the H-layer, executes its task, and returns a result. It does not see the subscriber’s full MoC context. It receives a privacy-filtered context package containing exactly what the skill needs and nothing more.
The certification program is the platform’s safety and quality gate. Basic certification covers functional correctness, privacy posture, and platform interaction standards. Clinical certification, required for any skill making health-related recommendations, includes clinical advisory review, evidence documentation, and an FDA-jurisdiction determination. Medical certification, required for any skill meeting the medical device threshold, includes FDA clearance. Beatrice’s kitchen-task assistant falls into the clinical certification tier because it provides health-related guidance to users with movement disorders, even though it does not meet the medical device threshold.
The revenue-sharing model varies by certification level. Basic-certified skills receive 70% of subscriber-attributed revenue; the platform retains 30%. Clinical-certified skills receive 60%; the platform retains 40%, reflecting the additional cost of clinical advisory infrastructure and platform liability. Medical-certified skills receive 50%; the platform retains 50%, reflecting the regulatory and liability cost the platform carries. The platform’s share funds the infrastructure, safety review, certification program, and consumer protections that make the marketplace credible.
The marketplace is path-aware. A subscriber on Path A with a Local Pane sees skills that can run locally. A subscriber on Path F served by a Community Pane sees the same catalog, with execution location differing. The catalog is universal across paths. The platform’s runtime resolves the deployment-path question without the developer’s involvement.
The BGO and SDK boundary is the question Beatrice’s team has been working through. A BGO Context Shard is the captured expertise of an individual practitioner. The retired oncology nurse who creates a clinical trial navigation Shard from her twenty-three years of practice is a BGO Sage. The BGO economic model is forty-forty-twenty: forty percent to the Sage, forty percent to the platform, twenty percent to a viability fund that subsidizes subscribers who cannot pay retail. An SDK skill is a software product built by an organization. Beatrice’s company is a developer. The skill embodies the company’s collective work; no single individual is the methodology source. The distinction is entity type and intent, not content domain. For Beatrice’s team, the classification is clear. Her company is a developer. Her clinical advisors, if they wished to deploy their personal methodologies through Shards, would be Sages with separate Shard agreements. The two categories could coexist in the marketplace and could even be composable.
BlueMirror starts as a product. The thirteen concierge agents, the thirty domain models, the architectural substrate are all internal builds. The transition to platform happens when external developers build skills the internal team did not imagine. The kitchen-task assistant for users with tremor is one example. Each comes from a developer or a Sage who knows a domain better than BlueMirror’s team. The transition is gated by certification. The platform does not accept any skill that can be built; it accepts skills that pass the certification bar.
Beatrice’s evaluation concluded that the SDK was the right distribution path. The certification process would be longer than her team’s previous regulatory work but manageable within the company’s runway. The revenue model would scale better than the standalone application’s per-unit-sale economics. The platform’s commitments aligned with what her clinical advisors had been making about the product all along. The decision was to commit to the SDK as the primary distribution path and retire the standalone application within eighteen months of skill certification.
Read the full article at bluemirror.tech.