A conversation with an AI

Fred Slane

5 August 2026

Following a planning meeting for a panel on open space standards development, I “Googled” a few questions. As has become common, Googling will result in an AI response. In this case the responding AI was Gemini, by Google.

Prompt: What industries use voluntary consensus standards?

Voluntary consensus standards are used across many technical sectors to guide safe product design, manufacturing, and testing. Government agencies like the U.S. Environmental Protection Agency and the FDA frequently adopt them instead of writing unique government rules. [1, 2, 3, 4, 5]

Major Industries Using Standards

• Medical Devices & Healthcare: Manufacturers use ISO, IEC, and AIAA AND ASTM rules to prove product safety and performance for market clearance.
• Construction & Architecture: Builders and engineers rely on codes for energy use, materials strength, and structural safety.
• Manufacturing & Consumer Goods: Factories use standards for testing product durability, toy safety, and chemical limits.
• Information Technology & Telecom: Tech firms follow joint consensus rules for data security, wireless equipment, and networking compatibility.
• Energy & Utilities: Power and oil groups use technical benchmarks for equipment testing, emissions control, and plant safety. [2, 3, 6, 7, 8]

Would you like to know about a specific standards organization (like AIAA, ASTM, ISO, or NFPA) or how a particular industry applies these rules?

[1] https://www.epa.gov

[2] https://www.greenlight.guru

[3] https://incompliancemag.com

[4] https://obamawhitehouse.archives.gov

[5] https://www.newpig.com

[6] https://www.epa.gov

[7] https://www.youtube.com

[8] https://www.intertekinform.com

Prompt: What industries do not use voluntary consensus standards?

Virtually no industry is entirely exempt from voluntary consensus standards, but several sectors actively avoid or reject them in favor of proprietary, specialized, or strict government-mandated rules. Instead of using open, consensus-driven systems like ISO or ANSI, these fields operate differently due to extreme secrecy, hyper-niche requirements, or rapid evolution. [1, 2, 3, 4, 5]

Sectors That Avoid Voluntary Consensus Standards

• National Defense & Classified Intelligence: Highly sensitive military programs rely on proprietary Military Standards (MIL-STD) or top-secret internal metrics rather than open, public consensus standards to maintain strategic advantages. [6]
• Cutting-Edge Artificial Intelligence & Tech R&D: Frontier tech fields (like quantum computing or generative AI models) move too quickly for traditional standard-developing organizations, choosing to rely on internal company benchmarks or de facto proprietary standards. [7]
• Art, Craft, & Artisanal Goods: Fine art, bespoke fashion, luxury goods, and hand-crafted items rely entirely on individual creativity and proprietary techniques rather than unified industry benchmarks.
• Nuclear Energy Core Operations: While standard utilities use voluntary consensus rules, core nuclear safety and weaponry rely almost exclusively on strict, top-down government mandates (like the Nuclear Regulatory Commission) because the risk of failure is too high for voluntary frameworks. [2, 8]
• Early-Stage Biotech & Proprietary Therapeutics: Deep tech and gene-editing startups pioneering brand-new scientific methods bypass consensus standards simply because the technology does not exist yet to build a consensus around. [7]

Common Reasons an Industry Rejects or Bypasses Them

• Speed of Innovation: Traditional consensus standards take years to publish, while fast-moving tech industries will leave them behind in months.
• Proprietary Edge: Companies chasing market dominance prefer to lock users into their own ecosystems rather than build compatible, open-source architectures.
• Extreme Safety Risks: When the public interest is at risk, federal regulators will completely step in and mandate unique government metrics rather than waiting for private-sector agreements. [7, 9, 10, 11]

If you are evaluating a specific business model, let me know:

• What product or service are you focusing on?
• Are you trying to determine if you need to comply with a particular framework?
• Do you want to see an example of a de facto standard that replaced a consensus one?
•  

I can provide the exact regulatory context or competitive standard environment for your situation.

 [1] https://www.newpig.com

[2] https://www.iacet.org

[3] https://www.iacet.org

[4] https://www.trilinkftz.com

[5] https://drexel.edu

[6] https://eureka.patsnap.com

[7] https://www.nist.gov

[8] https://www.nationalacademies.org

[9] https://www.epa.gov

[10] https://obamawhitehouse.archives.gov

[11] https://emergingtechpolicy.org

Prompt: The space industry is rapidly becoming more commercial, with more participants and substantial growth. How will companies benefit by developing and using voluntary consensus standards?

As the commercial space sector shifts away from legacy, government-dominated monopolies, developing and adopting voluntary consensus standards provides a powerful operational and financial edge for private space companies. Rather than relying on outdated military protocols or hyper-customized setups, companies using uniform baselines from organizations like AIAA AND ASTM International and ISO unlock several distinct business advantages. [1, 2, 3, 4]

1. Drastically Lowering Supply Chain Costs

• Commercial Components: Standards allow companies to safely use commercial off-the-shelf (COTS) parts instead of sourcing slow, multi-million dollar, custom-engineered gear. [5]
• Manufacturing Scale: Standardizing physical interfaces (like satellite buses, cargo bays, and rocket fuel valves) means suppliers can mass-produce hardware, lowering costs across the board. [5]
•  

2. Streamlining Regulatory Approvals

• Fast-Track Compliance: Regulatory agencies like the Federal Aviation Administration (FAA) operate under modern, performance-based frameworks (such as 14 CFR Part 450) that explicitly accept established industry consensus standards as an approved means of compliance. [6, 7]
• Global Market Expansion: Aligning hardware with recognized international standards helps companies secure rapid export approvals and foreign orbital slot licensing without redesigning their tech stack for every country. [2, 5]

3. Enabling Plug-and-Play Interoperability

• In-Space Servicing Ecosystems: The growth of complex orbital logistics—such as refueling, robotic assembly, and rendezvous and proximity operations (RPO)—requires cross-company docking compatibility. Organizations like CONFERS are setting consensus baselines so a satellite from Company A can smoothly interface with a service vehicle from Company B.
• Unified Data Protocols: Standardized data messaging (e.g., standard ISO orbit data messages) makes it easy for private tracking Networks, ground stations, and satellite operators to exchange data instantly. [2, 8, 9, 10, 11]

4. Maximizing Safety and Mitigating Risk

• Securing Space Sustainability: Following consensus standards for space debris mitigation (such as ISO 24113) helps space firms actively shield their hardware from catastrophic orbital collisions.
• Human Spaceflight Safety: Standardized liftoff, structural, and life-support metrics reduce the likelihood of high-profile accidents that could prompt harsh, industry-stifling political crackdowns. [8, 12, 13, 14, 15]

5. Boosting Investor and Insurer Confidence

• Predictable Risk Pricing: Space insurance underwriters penalize unproven, purely proprietary tech; adopting industry-wide standard testing protocols allows companies to negotiate significantly lower premium rates.
• Investment Readiness: Venture capital and private equity groups favor companies that rely on mature, standardized engineering principles, as it reduces overall operational risk and yields a faster, more predictable time-to-market. [2]

Are you looking at this from a strategic hardware development angle, or are you navigating a specific space regulation? Let me know:

• What specific domain are you targeting? (e.g., small satellites, heavy launch vehicles, orbital habitats, or space tourism)
• Do you want examples of current active standards committees you can join to help influence these rules? [2, 4, 14, 16, 17]

 [1] https://space.commerce.gov

[2] https://space.commerce.gov

[3] https://www.brookings.edu

[4] https://www.AIAA and ASTM.org

[5] https://www.aia-aerospace.org

[6] https://www.faa.gov

[7] https://www.faa.gov

[8] https://www.iso.org

[9] https://knowledge.bsigroup.com

[10] https://www.sciencedirect.com

[11] https://www.ronsped.it

[12] https://spacenews.com

[13] https://share.ansi.org

[14] https://aerospace.org

[15] https://spacexstock.com

[16] https://www.aia-aerospace.org

[17] https://www.faa.gov

Prompt: The space industry is rapidly becoming more commercial, with more participants and substantial growth. What are the risks to companies by developing and using voluntary consensus standards?

While voluntary consensus standards offer immense benefits, the process of developing and adopting them introduces significant strategic, financial, and legal vulnerabilities for commercial space companies. Navigating a consensus-driven environment requires balancing open collaboration with a company's unique competitive advantages.

1. Risk of IP Exposure and Technology Leakage

• Forced Disclosure: Participating in standards development organizations (SDOs) requires engineers to discuss technical requirements openly, which can inadvertently expose proprietary engineering methods to direct competitors.
• FRAND Licensing Traps: If a company’s patented technology becomes integrated into an industry standard, they are often legally forced to license that intellectual property under Fair, Reasonable, and Non-Discriminatory (FRAND) terms, severely capping potential licensing revenue. [1]

2. Strategic Slowdowns and Bureaucracy

• The Speed Penalty: Reaching a true consensus among dozens of competing international stakeholders takes years. Fast-moving startups risk missing critical market windows if they wait for a formal standard to finalize before building their hardware.
• Design Paralysis: Committing to an evolving standard can lock a company into design iterations that become obsolete before the standard is officially published, wasting valuable engineering hours.

3. Competitor Maneuvering and Market Leveling

• Stifling Unique Advantages: Standards naturally democratize technology. By standardizing a breakthrough interface, a pioneering company effectively erases its own unique technological moat, allowing late-entering competitors to build compatible products cheaply.
• Committee Capture: Larger, legacy aerospace companies often dedicate entire departments to packing SDO committees. These giants can manipulate the standard's criteria to favor their own existing supply chains, intentionally pricing out or designing out nimbler startups.

4. Premature Technical Lock-In

• Freezing Innovation: Solidifying a standard too early in a technology's lifecycle (such as in-space manufacturing or lunar power beaming) can institutionalize subpar engineering practices, forcing the entire industry to build around an inefficient baseline.
• Compliance Over Optimization: Engineers may prioritize strictly meeting a consensus standard's checkbox requirements over pushing the envelope on system performance, payload capacity, or weight reduction.

5. Hidden Costs of Compliance and Auditing

• SDO Paywalls: Participating in committees, purchasing standard documentation, and hiring certified compliance managers represents a massive overhead cost that disproportionately strains early-stage space ventures.
• Expensive Validation: Proving compliance often requires third-party testing, qualification, and specialized cleanroom verification, adding millions of dollars to a launch vehicle or satellite development cycle.

If you are weighing whether to join a space standards committee or adopt an existing framework, let me know:

• What specific technology are you developing? (e.g., docking mechanisms, laser communications, or orbital refueling systems)
• Are you trying to protect a specific proprietary advantage from your competitors?

I can help you analyze a strategy to participate in standards development while shielding your core innovations.

 [1] https://www.youtube.com

Prompt: It appears that there is a fine balancing act a company must perform to wisely participate in voluntary standards development and standards use. How can that balancing act be described for a company's short, mid and long term development?

A commercial space company can navigate this balancing act by viewing voluntary consensus standards not as a rigid rulebook, but as a dynamic risk-management tool. The strategy must evolve across short, mid, and long-term horizons to match the company’s shifting priorities from survival to market dominance.

---

⏳ Short-Term (Years 1–3): Lean Survival & Strategic Shielding

In the early stages, a company’s primary goals are speed-to-market, capital conservation, and protecting its core intellectual property (IP).

• The Balancing Act: Consume standard components; strictly hide your core IP.
• Standards Use Strategy: Heavily adopt existing, mature standards for non-differentiating hardware (e.g., standard fasteners, power voltages, or telemetry protocols). This minimizes engineering overhead and maximizes your limited budget.
• Development Strategy: Stay away from active Standards Development Organizations (SDOs) in your core innovation areas. If your breakthrough is in active orbital refueling, do not join committees discussing it yet. Build your proprietary "secret sauce" in total isolation to maintain your technological moat.
• The Risk to Manage: Over-customization. Designing every single bolt or software protocol from scratch will drain your venture capital before you ever reach the launchpad.

---

⏳ Mid-Term (Years 3–5): Scaling, Influence, & Market Alignment

As the company achieves its first successful launches or deployments, the focus shifts to scaling production, lowering supply chain costs, and clearing regulatory hurdles.

• The Balancing Act: Influence the rules without giving away the blueprint.
• Standards Use Strategy: Use standards as a weapon to clear regulatory bottlenecks. For example, adopt established FAA or ISO baselines to fast-track your launch licenses and lower your space insurance premiums.
• Development Strategy: Selectively send senior engineers to join key SDO committees (like AIAA AND ASTM or CONFERS). Your goal here is defensive: ensure that your competitors do not write a standard that outlaws your specific architecture or favors their own supply chain.
• The Risk to Manage: Committee capture and IP leaks. Ensure your engineers are highly trained in IP protection so they only share performance requirements (e.g., "the docking ring must withstand X force") rather than implementation details (e.g., how your proprietary software calculates the alignment).

---

⏳ Long-Term (Years 5+): Market Leadership & Ecosystem Lock-In

As a mature market leader, the goal shifts to defending your market share, driving industry-wide interoperability, and shaping the future regulatory landscape.

• The Balancing Act: Turn your proprietary tech into the industry standard.
• Standards Use Strategy: Shift completely to a modular, plug-and-play architecture. Use industry standards to force your suppliers to commoditize their parts, which drives down your long-term manufacturing costs.
• Development Strategy: Aggressively lead SDO committees. Take your proven, field-tested proprietary interfaces and intentionally transition them into the official industry standard. By doing this, you force the entire industry to adapt to your technology stack, positioning your company as the central hub of the space ecosystem.
• The Risk to Manage: Technical stagnation. If you lock the industry into a standard that you wrote five years ago, you risk a nimbler, short-term startup bypassing the standard entirely with a disruptive, next-generation technology (e.g., laser comms completely displacing radio frequencies).

---

To help apply this framework directly to your business model, let me know:

• What sub-sector of the space industry are you operating in? (e.g., launch services, satellite components, or ground stations)
• What is your company's current maturity phase? (e.g., early seed-stage R&D vs. fully operational with existing contracts)

I can help map out a custom timeline of which specific standards committees to join or avoid based on your position.

Prompt: What are examples of de facto standards in the space industry?

De facto standards emerge through rapid market adoption, historical dominance, or sheer technological efficiency rather than through a formal voting process by a standards committee. In the space industry, these standard protocols dictate how companies build, launch, and operate hardware. [1, 2]

🚀 Hardware Form Factors

CubeSats (The 1U Form Factor): Originally developed by Stanford and Cal Poly as an educational framework, the standard 10x10x10 cm cube format is the absolute de facto structural baseline for the entire small satellite market. Satellite deployers, launchers, and components are universally manufactured to match these "U" measurements. [3]

PC104 Boards: For satellite internal computers and electronics architecture, the PC104 form factor (inherited from rugged terrestrial industrial computing) became a de facto standard for stacking boards cleanly inside small spacecraft before newer standards caught up.

🛰️ Commercial Launch Configurations

ESPA Rings: Developed initially for military payloads by Moog, the EELV Secondary Payload Adapter (ESPA) became the de facto industry adapter ring for rideshare missions. If a company manufactures a small satellite, they almost always ensure its separation mechanism mounts cleanly onto a standard ESPA port.

SpaceX Transporter Port Specs: Because SpaceX dominates the commercial rideshare market, their internal launch vehicle manifests, environmental testing criteria, and deployment mechanical interfaces have become de facto rules that small-sat startups must build toward if they want access to affordable orbits. [4]

💾 Data & Software Ecosystems

Linux in Flight Software: While legacy aerospace relied exclusively on proprietary, hyper-specialized real-time operating systems (like VxWorks), Linux has become a de facto operating system choice for private constellation operators and commercial rocket flight computers due to its vast developer pool and open flexibility.

TLEs (Two-Line Element Sets): Originally created by NORAD decades ago, this data format is the global de facto format used to track and communicate the orbital elements of objects in Earth's orbit. Despite its limitations compared to modern vector formats, almost all tracking software and tracking entities still ingest TLE data. [5, 6]

📡 Ground Stations & Frequency Allocation

SpaceX Starlink / User Terminals: In the consumer and commercial satellite internet market, the mass production and design of Starlink's phased array user terminals have created a de facto ecosystem standard for satellite-to-ground consumer connectivity.

The S-Band / X-Band Paradigms: While the International Telecommunication Union (ITU) controls formal spectrum allocations, the commercial space supply chain has forced de facto consensus on hardware pricing—meaning most small satellites use identical, off-the-shelf S-band radios for telemetry and X-band radios for high-speed data downlinks simply because those components are cheapest and easiest to source. [7]

Are you looking to design a subsystem that needs to fit into one of these established ecosystems, or are you trying to determine if your proprietary technology can overthrow a current de facto baseline? Let me know:

What specific aspect of space tech are you building? (e.g., satellite hardware, communication tech, or launch adapters)

Do you want to know how to ensure backward compatibility with these legacy de facto systems?

[1] https://aerospace.org

[2] https://www.linkedin.com

[3] https://www.spacesymposium.org

[4] https://spacenews.com

[5] https://dgi.wbresearch.com

[6] https://spacenexus.us

[7] https://orbitalradar.com

Unless otherwise noted, the blog posts are written by Frederick A. Slane, Executive Director of the Space Infrastructure Foundation. (c) Copyright Space Infrastructure Foundation 2026. Unlimited distribution with citation.