A voxel, a decision, a resource status: each one is a real, documented schema, not an internal implementation detail. If you want to integrate against the platform, read the contract -- you don't need a partnership agreement to see the shape of your own data.

The core is a deliberately narrow Apache 2.0 surface -- the same playbook dbt and Supabase run (both Apache 2.0: dbt Core's engine, Supabase's self-hostable server). Commercial value lives in the business layer above it, not in the primitives themselves.

The core never forks for a demo -- every surface conforms to the same published schema whether you're running the open primitives or the commercial platform. What sits above the core (multi-tenant operations, the business layer, the hosted service) is what Ectropy sells; what sits inside it is what the industry gets to own outright.

The public core includes the protocol definitions, schema validators, voxel primitives, decision-graph traversal, and a reference MCP server that wraps the query API as tools any MCP client (Claude Desktop, Cursor, etc.) can call directly. A bundle reader and export primitive round-trip your own data in and out -- federation happens over the documented protocol, not a code dependency on Ectropy itself.

• GitHub -- ectropy-ai/core
• Schemas -- schemas.luh.tech