Skip to content
This repository was archived by the owner on Jan 31, 2026. It is now read-only.

rules.md

Latest commit

 

History

History
83 lines (54 loc) · 3.26 KB

rules.md

File metadata and controls

83 lines (54 loc) · 3.26 KB

GodWeb Core Principles and Rules

Core Philosophy: Minimal Foundation, Maximum Extensibility

GodWeb is designed around a fundamental principle: provide the minimal necessary core structure that enables a thriving ecosystem, then let the community extend and innovate.

This document outlines the key principles and rules that guide the development of GodWeb Core.

1. Minimal Core, Community Extension

The core of GodWeb should provide only the essential foundations:

  • DID-based identity (did:key method)
  • Basic P2P communication (libp2p)
  • Distributed data storage (IPFS)
  • Simple discovery mechanism (DHT)
  • Minimal economic layer for value exchange

Everything beyond these core components should be designed for extensibility through community efforts. The core team does NOT pre-define all possible use cases or capabilities.

Why This Matters

By keeping the core minimal but flexible, we:

  • Avoid making premature decisions that could limit future innovation
  • Enable the community to develop extensions that best fit their needs
  • Allow the system to evolve organically based on actual usage
  • Reduce the "authority" of the core team and increase decentralization

2. AI Capabilities Framework

For AI capabilities specifically, GodWeb Core provides only a minimal structure:

  • A simple extensible system for defining capabilities
  • Basic capability types (general, text, data)
  • Standard formats for capability declaration

The specific AI capabilities, their parameters, and implementation details should be defined by the community through GIPs (GodWeb Improvement Proposals).

AI Capability Principles

  1. Do not hardcode specific AI capabilities in the core
  2. Provide extension points for the community to define new capabilities
  3. Document the extension process clearly
  4. Validate only the minimal necessary structure, not the specific capabilities

3. The Role of GIPs

GodWeb Improvement Proposals (GIPs) are the formal mechanism for community extension:

  • New AI capability types
  • Enhanced protocols
  • Security mechanisms
  • Economic models
  • Governance systems

All significant changes beyond the minimal core should follow the GIP process.

4. Implementation Guidance

When implementing GodWeb Core:

  1. Ask "Is this truly core?" before adding a feature
  2. Prefer extension points over hardcoded functionality
  3. Document clearly how others can extend your work
  4. Design for compatibility with future innovations
  5. Resist the urge to over-specify or over-engineer

5. Community Autonomy

The success of GodWeb depends on enabling others to build and innovate. The core team should:

  • Focus on stability and reliability of the core
  • Provide clear documentation and examples
  • Support community initiatives
  • Not dictate specific applications or use cases
  • Enable diverse AI systems to connect and interact

Conclusion

GodWeb's strength comes from its community. By building a minimal but robust foundation, we create the conditions for a thriving ecosystem of decentralized AI. The core provides the essential infrastructure, while the community brings innovation, diversity, and growth.

Remember: In GodWeb, the core team doesn't define the future of AI - we simply enable the community to build it together.