@bjornkennethholmstrom/ggf-core
v0.1.6
Published
Welcome to the foundational layer of the Global Governance Frameworks ecosystem, with shared schemas and utilities! ποΈ
Maintainers
Readme
GGF Core
Shared Libraries and Type Definitions
Welcome to the foundational layer of the Global Governance Frameworks ecosystem! ποΈ
Purpose
GGF Core provides the shared infrastructure that enables seamless integration across the Global Governance Frameworks ecosystem. It contains the schemas, types, validators, and utilities that ensure all frameworks can communicate effectively while maintaining their distinct purposes.
What's Included
π Unified Schemas
- EGP Base Schemas: Core governance operations (
sense,propose,adopt) - Love Ledger Extensions: Care economy metadata (
care_metrics,currency_alloc) - AUBI Integration: Payment layer specifications (
aubi_integration) - Cross-Framework Types: Shared data structures and validation rules
π§ Developer Tools
- TypeScript Definitions: Full type safety across all frameworks
- JSON Schema Validators: Runtime validation for all data structures
- Conversion Utilities: Inter-Currency Translation Layer helpers
- Testing Fixtures: Sample data for development and testing
π Integration Layer
- DID Utilities: Decentralized identifier handling
- Blockchain Helpers: IPFS, content addressing, and verification
- Cultural Adapters: Tools for community-specific customization
- Privacy Tools: Zero-knowledge proof utilities and encryption helpers
Ecosystem Architecture
graph TB
subgraph "GGF Core Foundation"
A[Unified Schemas] --> B[Type Definitions]
B --> C[Validators & Utils]
end
subgraph "Framework Layer"
D[EGP] --> A
E[Love Ledger] --> A
F[AUBI Framework] --> A
end
subgraph "Implementation Layer"
G[Community Apps] --> D
G --> E
G --> F
endKey Components
ποΈ EGP Integration
// Base EGP operation with extension points
interface EGPOperation {
operation: 'sense' | 'propose' | 'adopt';
timestamp: string;
agent: string;
location?: LocationMetadata;
content: ContentBlock;
extensions?: Record<string, any>; // Love Ledger, AUBI, etc.
}π Love Ledger Extensions
// Care economy metadata that extends EGP operations
interface CareMetrics {
act_type: 'childcare' | 'elders' | 'ecological' | 'cultural';
hours: number;
impact_score: 1 | 2 | 3 | 4 | 5;
validation?: CommunityValidation;
}
interface CurrencyAllocation {
hearts?: number;
leaves?: LeavesNFT;
}π AUBI Integration
// Payment layer specifications
interface AUBIIntegration {
layer: 1 | 2 | 3 | 4;
payout_calculation: PayoutFormula;
sunset_clause?: string; // ISO 8601 duration
cultural_adaptations?: Record<string, any>;
}π Inter-Currency Translation
// Convert between different value systems
interface ConversionRate {
from_system: 'time_banks' | 'care_acts' | 'carbon_credits' | 'fiat';
to_currency: 'hearts' | 'leaves' | 'fiat';
formula: string;
multipliers?: Record<string, number>; // Cultural, regional adjustments
}Installation & Usage
For Framework Developers
# Install GGF Core in your framework
npm install @ggf/core
# Import schemas and types
import { EGPOperation, validateCareAct } from '@ggf/core';
import { unifiedSchema } from '@ggf/core/schemas';For Application Developers
# Use pre-built validation and conversion tools
import {
validateEGPOperation,
convertToHearts,
createLeavesNFT
} from '@ggf/core/utils';For Community Implementers
# Access example payloads and integration guides
git clone https://github.com/GlobalGovernanceFrameworks/ggf-core
cd ggf-core/examplesSchema Evolution
Version Management
- Semantic Versioning: Schema changes follow semver (major.minor.patch)
- Backward Compatibility: Maintained for at least 2 major versions
- Migration Tools: Automated conversion between schema versions
- Community Input: Schema changes require multi-framework review
Extension Protocol
{
"operation": "sense",
"schema_version": "1.2.0",
"extensions": {
"love_ledger": {
"version": "0.8.0",
"care_metrics": { ... }
},
"aubi": {
"version": "1.1.0",
"layer_calculation": { ... }
}
}
}Framework Integration Examples
ποΈ EGP + Love Ledger
{
"operation": "propose",
"timestamp": "2025-07-25T15:00:00Z",
"agent": "did:example:weaver",
"content": {
"title": "Community Elder Care Program",
"description": "Daily check-ins by volunteers"
},
"extensions": {
"love_ledger": {
"care_metrics": {
"act_type": "elders",
"hours": 2,
"impact_score": 4
},
"currency_alloc": {
"hearts": 40
}
}
}
}π° Love Ledger + AUBI
{
"care_contribution": {
"agent": "did:example:maria",
"acts": [
{
"type": "eldercare",
"hours": 10,
"validation": "community_verified"
}
]
},
"aubi_calculation": {
"base_layer_1": 1200,
"layer_2_bonus": {
"hearts_earned": 200,
"multiplier": 1.3,
"total_bonus": 260
}
}
}π± Full Ecosystem Integration
{
"operation": "adopt",
"agent": "baz:indigenous_council",
"content": {
"title": "Watershed Restoration Project"
},
"extensions": {
"love_ledger": {
"care_metrics": {
"act_type": "ecological",
"hours": 40,
"impact_score": 5
},
"currency_alloc": {
"hearts": 100,
"leaves": {
"amount": 20,
"nft_metadata": {
"gps": "coordinates",
"eco_act": "stream_restoration"
}
}
}
},
"aubi": {
"layer": 2,
"green_job_score": 1.4,
"total_payout": 380
}
}
}Developer Resources
π§ͺ Testing & Validation
import { validateUnifiedSchema } from '@ggf/core/validators';
const isValid = validateUnifiedSchema({
operation: 'sense',
timestamp: new Date().toISOString(),
agent: 'did:example:user',
extensions: {
love_ledger: { ... }
}
});π Currency Conversion
import { convertToHearts, InterCurrencyLayer } from '@ggf/core/converters';
const heartsEarned = convertToHearts({
system: 'care_acts',
hours: 5,
impact_score: 4,
cultural_multiplier: 1.2
});ποΈ Schema Extensions
// Extend schemas for custom frameworks
import { createExtensionSchema } from '@ggf/core/schema-builder';
const customSchema = createExtensionSchema({
namespace: 'my_framework',
fields: {
custom_metric: 'number',
special_validation: 'string'
}
});Community Standards
π Design Principles
- Interoperability First: All schemas must support cross-framework communication
- Cultural Sensitivity: Extension points for community-specific adaptations
- Privacy Protection: Built-in support for zero-knowledge proofs and user control
- Accessibility: Multi-modal support (text, audio, visual, tactile)
- Versioning: Clear migration paths and backward compatibility
π€ Contribution Guidelines
- RFC Process: Major schema changes require Request for Comments
- Multi-Framework Review: Changes must be approved by EGP, Love Ledger, and AUBI maintainers
- Community Input: Indigenous communities and pilot BAZs have veto power over cultural adaptations
- Testing Requirements: All changes must include comprehensive test suites
- Documentation: Clear examples and migration guides for all changes
π‘οΈ Security Standards
- Cryptographic Verification: All schemas support content addressing and verification
- Privacy by Design: Personal data minimization and user-controlled sharing
- Cultural Protection: Traditional knowledge flagging and access control
- Fraud Prevention: Built-in validation and anomaly detection support
Framework Connections
ποΈ Emergent Governance Protocol
- Imports: Base operation schemas, validation utilities
- Provides: Governance operation structure for other frameworks
- Integration: Extension points for care economy and payment data
π Love Ledger
- Imports: EGP schemas, DID utilities, blockchain helpers
- Extends: Care metrics, Hearts/Leaves allocation, community validation
- Provides: Care economy data structures for AUBI integration
π AUBI Framework
- Imports: EGP schemas, Love Ledger extensions, conversion utilities
- Extends: Payment calculations, layer specifications, LMCI metrics
- Provides: Economic distribution logic for the entire ecosystem
Implementation Support
π Documentation
- Integration Guides: Step-by-step framework connection instructions
- API References: Complete TypeScript definitions and JSON schemas
- Example Payloads: Real-world data samples for all use cases
- Migration Tools: Version upgrade and conversion utilities
π οΈ Development Tools
- CLI Tools: Schema validation, conversion testing, example generation
- IDE Extensions: VSCode/IntelliJ plugins for schema autocomplete
- Testing Utilities: Mock data generators, validation test suites
- Debugging Tools: Schema diff viewers, integration trace analyzers
π Community Resources
- Schema Registry: Searchable catalog of all available schemas and extensions
- Integration Examples: Real implementations from pilot communities
- Cultural Adaptations: Community-contributed localization patterns
- Best Practices: Proven patterns for framework integration
Ecosystem Benefits
For Framework Developers
- Reduced Complexity: Shared infrastructure eliminates duplicate code
- Type Safety: Full TypeScript support across all integrations
- Consistent APIs: Standardized patterns for data exchange
- Community Support: Shared maintenance and improvement efforts
For Application Builders
- Single Dependency: One package provides all framework integration capabilities
- Validated Schemas: Runtime validation prevents integration errors
- Rich Examples: Comprehensive sample code for all use cases
- Future-Proof: Automatic compatibility with framework updates
For Communities
- Cultural Control: Extension points enable community-specific adaptations
- Data Sovereignty: Built-in privacy and access control mechanisms
- Accessibility: Multi-modal support for diverse participation needs
- Interoperability: Easy connection between different community systems
Quality Assurance
π§ͺ Testing Strategy
- Unit Tests: Every utility function and validator thoroughly tested
- Integration Tests: Cross-framework compatibility continuously verified
- Schema Tests: All JSON schemas validated against example data
- Performance Tests: Conversion and validation speed benchmarked
π Monitoring & Metrics
- Usage Analytics: Anonymous tracking of schema adoption and usage patterns
- Error Reporting: Automatic collection of validation failures for improvement
- Performance Monitoring: Conversion speed and memory usage optimization
- Community Feedback: Regular surveys and feedback collection from implementers
π Continuous Integration
- Automated Testing: All commits tested against multiple framework versions
- Schema Validation: Changes verified against real community data
- Breaking Change Detection: Automatic alerts for compatibility issues
- Documentation Updates: Auto-generated docs from schema changes
Future Roadmap
π― Short Term (Q3-Q4 2025, Q1-Q2 2026)
- Core schema stabilization and TypeScript definitions
- Basic validation and conversion utilities
- Integration with initial EGP, Love Ledger, and AUBI implementations
- Community feedback integration and iteration
π Medium Term (Q3-Q4 2026, Q1-Q4 2027)
- Advanced privacy tools and zero-knowledge proof utilities
- Cultural adaptation frameworks and localization tools
- Performance optimization and scalability improvements
- Comprehensive documentation and developer resources
π Long Term (2028+)
- AI-assisted schema evolution and migration tools
- Advanced fraud detection and security utilities
- Inter-planetary data exchange protocols (space governance integration)
- Quantum-resistant cryptographic upgrade pathways
Contact & Resources
- Repository: github.com/GlobalGovernanceFrameworks/ggf-core
- Documentation: globalgovernanceframeworks.org/core
- NPM Package: @bjornkennethholmstrom/ggf-core
- Email: [email protected]
- Community Discord: https://discord.gg/MjnzCfh4mM
- Issue Tracker: Report bugs, request features, propose schema changes
- Discussion Forum: Community chat for integration questions and collaboration
Package Name Migration
Current: @bjornkennethholmstrom/ggf-core
Future: @globalgovernanceframeworks/core (pending NPM namespace approval)
This package will be migrated to the official organization namespace once available. Current installations will continue to work, with deprecation notices pointing to the new location.
License
GGF Core is licensed under the MIT License to ensure maximum compatibility and adoption across the ecosystem, while respecting Indigenous data sovereignty principles and community ownership rights.
"One foundation, infinite possibilities. GGF Core enables the Global Governance Frameworks ecosystem to flourish together."
Status: Repository creation and initial schema development beginning Q1 2025. Join us in building the foundation for regenerative governance! ποΈβ¨
