Brand Kit / Editorial Style Guide
Purpose
Section titled “Purpose”To ensure consistent communication across whitepapers, project documentation, marketing materials, and public-facing content.
It standardizes terminology, tone, and style to reflect CodecFlow’s identity as an innovative, reliable execution engine for robotics and AI, emphasizing technical precision, adaptability, and real-world problem-solving.
About CodecFlow
Section titled “About CodecFlow”CodecFlow is the execution engine for robotics, providing a unified platform that enables adaptive AI agents to operate seamlessly across cloud, edge, desktop, and robotic hardware. It addresses the limitations of traditional automation, such as brittle scripts that fail with UI changes or environmental shifts, by leveraging Vision-Language-Action (VLA) models to create intelligent, reusable Operators.
These Operators perform tasks through a perceive-reason-act cycle, allowing robots and AI systems to handle real-time decision-making, low-latency execution, and integration with resources like compute, payments, and simulations. Key offerings include Fabric for orchestrating distributed workloads, OPTR for runtime management, and x402 for native payments within workflows.
CodecFlow powers a machine economy where robots can autonomously perceive, decide, act, and settle costs, unlocking applications in manufacturing, household automation, and beyond. The ecosystem includes an Operator Marketplace for sharing skills and $CODEC tokens for incentivizing contributions.
Writing Guidelines
Section titled “Writing Guidelines”- Prioritize clarity and structure: Use short paragraphs, bullet points, and numbered lists for technical explanations to improve readability. Break complex ideas into digestible sections, starting with high-level overviews before diving into details.
- Incorporate visuals: Enhance explanations with diagrams, screenshots, videos, or images where relevant, as seen in content about latency comparisons or architectural pillars. See the “Brand Kit Resources” section for relevant materials.
- Back claims with evidence: Support statements about capabilities (e.g., 10x lower latency) with specific examples, metrics, or references to real-world applications.
- Use active voice: Focus on what CodecFlow enables or solves (e.g., “Fabric routes compute to the nearest servers”) instead of passive constructions.
- Inclusivity: Address a technical audience (developers, robotics engineers) while remaining accessible to broader stakeholders, avoiding unnecessary jargon but defining terms on first use.
Critical Style Conventions
Section titled “Critical Style Conventions”- Always refer to the platform as CodecFlow (one word), not CODEC, Codec Flow, or variations.
- Use Vision-Language-Action (VLA) models with hyphens; abbreviate as VLA after first mention.
- Capitalize proper nouns for key components: Operators, Fabric, Machine Layer, System Layer, Intelligence Layer, Operator Marketplace, Compute Marketplace.
- Refer to the token as $CODEC (with dollar sign prefix).
- Use en dashes (–) for ranges or compound terms like “sim-to-real transfer” or “cross-embodiment learning.”
- For cycles or processes: “perceive-reason-act cycle” (hyphenated, lowercase unless starting a sentence).
- Technical terms: Maintain consistency, e.g., “low-latency” (hyphenated), “real-time” (hyphenated), “on-device execution” (hyphenated for compound modifiers).
- Links: Embed or footnote sources in the first comment below the main body of a post (so a posts reach is not reduced by the Twitter/X algorithm)
What to Avoid
Section titled “What to Avoid”- Overly promotional hype: Steer clear of unsubstantiated claims like “revolutionary” without evidence; focus on factual benefits and problem-solving.
- Redundancy: Do not repeat phrases unnecessarily; ensure each section adds value.
- Ambiguity: Avoid vague terms like “better” without qualifiers (e.g., specify “10x faster response time”).
- Vendor-specific bias: Emphasize decentralization and avoidance of lock-in, without disparaging competitors.
- Overly complex sentences: Break up long run-ons; aim for sentences under 25 words where possible.
- Inconsistent formatting: Do not mix styles (e.g., always use bullets when making lists, not asterisks for one and bullet points for another).
Tone and Voice
Section titled “Tone and Voice”- Professional, insightful, and forward-thinking, blending technical depth with practical optimism.
- Position the platform as a problem-solver in robotics and AI, highlighting gaps in current systems (e.g., deployment challenges) while showcasing solutions without arrogance.
- Content should feel authoritative yet approachable, inspiring confidence in CodecFlow’s infrastructure for real-world autonomy.
- Use a collaborative tone that invites engagement (e.g., “If this resonates, reach out”), emphasizing community, innovation, and scalability.
Content Types with Examples
Section titled “Content Types with Examples”- Technical Explanations/Articles: In-depth breakdowns of concepts, using threads or sections with bullets.
Example: “VLAs unify vision, language, and action into a single learning loop… This is where robotics is today.” (From posts on VLA models and deployment gaps.)
Detailed explanation of VLAs’ role in bridging the deployment gap in robotics, including unification of vision, language, and action. https://x.com/codecopenflow/status/2014601997455130876
In-depth overview of the x402 payment protocol and its integration with CodecFlow for AI agents. https://x.com/codecopenflow/status/1982024337235345878
- Announcements/Updates: Concise highlights of features or events, often with media.
Example: “Fabric delivers 10x lower latency… from 600ms down to 50ms.” (Include metrics and visuals like videos.)
Announcement of $CODEC going live on MachineDEX, with integration details for the optr SDK. https://x.com/codecopenflow/status/1969758581714280528
Update on x402 integration possibilities and future billing explorations for CodecFlow services. https://x.com/codecopenflow/status/1982024337235345878
- Quotes and Commentary: Repurpose external content with added insights.
Example: Quoting a report on Physical AI, then explaining CodecFlow’s role: “This is what we’ve been building at CodecFlow… OPTR keeps that loop stable.”
Commentary on @oyhsu’s insights into robotics advances, with quotes and CodecFlow’s focus on deployment gaps. https://x.com/codecopenflow/status/2014601997455130876
- Use Case Summaries: Bullet-point lists of applications.
Example: “Robots at CES 2026: - Boston Dynamics Unveils Atlas… - NVIDIA announces new open AI models…” (Curate industry news with CodecFlow context.)
Use case for operators controlling onchain machines with telemetry and rewards on peaq. https://x.com/codecopenflow/status/1969758581714280528
- Guides/Tutorials: Step-by-step instructions in docs.
Example: “Training Operators: Use no-code demonstration… or SDKs to integrate APIs.” (From docs on Operator creation.)