Some capabilities are current product direction, while others need public examples, screenshots, or final naming before stronger claims.

Use this page to avoid overpromising while keeping the documentation honest and useful.

Current public positioning

These can be described as part of the Collab.codes product direction:

• runtime with client, common runtime, master frontend, and master backend;
• Collab Aura and Collab Forge as reference defaults;
• Collab Auth as managed identity;
• Collab LLM as managed LLM proxy;
• Collab Messages as collaboration surface;
• Studio as contextual creation and maintenance experience;
• no lock-in as a product principle.

Mark as planned or evolving

These should be described carefully until stronger public examples exist:

• native iOS and Android targets;
• mobile runtime examples;
• workflow creation fully generated by LLM;
• deeper OpenClaw automation examples;
• enterprise SSO providers beyond current integrations;
• public examples of molecule group contracts;
• detailed Build and publication operations.

Human review before publishing claims

Before using stronger GTM claims, validate:

• exact product names;
• implementation status;
• screenshots or videos that can be public;
• security and permission boundaries;
• claims such as 10x or 99.9% LLM;
• examples that can be shown without exposing customer or internal data.