Overview
Pmaster-dev follows a hybrid software model that combines open-source collaboration with protected proprietary technology.
The goal is to:
- Encourage community innovation
- Maintain transparency and trust
- Protect intellectual property
- Support enterprise and commercial growth
The ecosystem is divided into three layers:
Pmaster-dev Ecosystem
|
------------------------------------------------
| | |
v v v
Open Source Source Available Proprietary Community Layer Controlled Layer Private Layer
- Open Source Layer
Purpose
Open-source projects allow developers, organizations, and communities to collaborate, improve software, and build integrations.
Examples:
open-source/
├── SDKs ├── API clients ├── Documentation ├── UI components ├── Design systems ├── Developer tools └── Integration examples
Possible projects:
VR4DEAF UI
Open:
- Accessibility components
- Deaf-first design patterns
- Frontend utilities
- Design tokens
PinkSync SDK
Open:
- Event formats
- API clients
- Integration examples
- Developer documentation
Developer Tools
Open:
- CLI utilities
- Testing tools
- Templates
- Automation helpers
- Source-Available Layer
Purpose
Source-available projects provide transparency while protecting commercial use and controlled distribution.
Examples:
source-available/
├── Advanced workflows ├── Enterprise modules ├── Admin dashboards ├── Deployment systems └── Integration packages
Characteristics:
- Source code may be visible
- Contributions may be accepted
- Commercial rights may require permission
- Usage is controlled by license terms
- Proprietary Layer
Purpose
Private technology protects the core business value, security, and customer-specific systems.
Examples:
private/
├── AI systems ├── Enterprise platform logic ├── Security architecture ├── Customer integrations ├── Billing systems ├── Private datasets └── Internal algorithms
Example Product Separation
VR4DEAF
Open:
- Accessibility components
- Public resources
- Developer documentation
Protected:
- Enterprise platform
- Agency workflows
- Customer systems
- Compliance integrations
PinkSync
Open:
- SDKs
- Event specifications
- Basic integrations
Protected:
- Internal infrastructure
- Enterprise routing
- Advanced automation
360Magicians
Open:
- Developer tools
- Examples
- Framework utilities
Protected:
- AI agents
- Model orchestration
- Private knowledge systems
- Business automation logic
GitHub Organization Structure
Pmaster-dev
├── Open Source │ │ ├── vr4deaf-ui │ ├── pinksync-sdk │ └── developer-tools │ ├── Source Available │ │ ├── workflow-modules │ ├── enterprise-connectors │ └── admin-components │ └── Proprietary │ ├── vr4deaf-platform ├── pinkflow-engine └── 360magicians-core
Repository Requirements
Every repository should define:
README.md LICENSE SECURITY.md ARCHITECTURE.md CONTRIBUTING.md
The README should state:
Project Visibility: (Open Source / Source Available / Proprietary)
License: Applicable License
Contribution Rules: How developers participate
Commercial Use: Allowed or restricted
Strategic Model
The ecosystem follows an open-core approach:
Open Foundation
↓
Community Adoption
↓
Trusted Platform
↓
Enterprise Features
↓
Sustainable Revenue
Principles
Build in Public Where Possible
Share:
- Standards
- Tools
- Documentation
- Accessibility improvements
Protect What Creates Long-Term Value
Protect:
- User data
- Security systems
- Enterprise workflows
- AI intelligence
- Proprietary integrations
Maintain Trust
Every project should clearly communicate:
- Who owns it
- How it can be used
- How contributions work
- What is open or restricted
Pmaster-dev operates as an engineering ecosystem where open collaboration and proprietary innovation coexist.