How formalism-labs/classico works
Main Components Structure
a) Core Libraries Layer (Bottom):
• Paella (Python)
• Shibumi (Bash)
• Cetara (C/C++)
• Golani (Go)
• WD40 (Rust)
• Jasmine (JavaScript/TypeScript)
• Posh (PowerShell)
• Bento (Ruby)
b) Build Tools Layer (Middle):
• mk (GNU Make framework)
• cmake modules
c) Executable Scripts Layer (Top):
• bin/ (utility scripts)
• sbin/ (administrative scripts)
Component Relationships
• Dependency flows between components
• Script interaction patterns
• Platform-specific variations
Key Architectural Elements
a) Platform Abstraction:
• osnick (OS/platform identification)
• Architecture detection
• System capability detection
b) Automation Facilities:
• Build automation
• Testing frameworks
• Package management
• CI/CD integration
Specific Details
Annotations for:
• Cross-language interoperability
• Platform-specific behaviors
• Environment variable handling
• Script argument conventions
Integration Points
Highlight:
• CI/CD integration (.github/workflows)
• Container support (Dockerfile related components)
• Build system integration points
Build system flexibility
Key Relationships to Show:
• How scripts in bin/ utilize the various libraries
• How build tools (mk, cmake) interact with core libraries
• Platform detection and adaptation flow
• Cross-language communication patterns
• Component types
• Connection types
• Platform indicators
• Special symbols
Remember to indicate the extensibility points where new automation tools can be added and how they integrate with the existing infrastructure.