How mikelevins/folio2 works
Main Architecture Overview
a) Core Components Layer:
• "as" and "make" subsystems at the foundation level as they are fundamental utilities
• Them as hexagonal ports/adapters since they're generic functions used across the system
b) Data Structures Layer:
• Their relationships with connecting lines
c) Advanced Features Layer:
• Series and taps at the top level
• Their dependencies on lower layers
Component Relationships
External Dependencies (Bottom Layer)
[Alexandria] [FSet] [SERIES] [Closer-MOP]
• ↑ ↑ ↑
Core Utilities (Foundation)
[as] ←→ [make]
• ↑
Data Structures (Middle Layer)
• ↑
Advanced Features (Top Layer)
[series] → [taps]
Additional Elements
Include:
• Version information
• External dependency versions
• Package naming conventions (net.bardcode.folio2)
Integration Points
Highlight:
• How the components integrate with Common Lisp's standard libraries
• Integration points with FSet and SERIES
• Extension points for custom implementations
Data Flow
Typical data flow patterns:
• Type conversion flows through 'as'
• Construction patterns through 'make'
• Series transformation chains
• Tap data source connections
Remember to include notes about the optional nature of various components and how they can be loaded independently, as this is a key feature of the system's design.