Notes¶
Migration records, audits, and reference material that explain the current state of the codebase without defining the canonical architecture.
- Asset Collection System Design
- Generic Story-Layer Framework for Managing Asset Collections
- Executive Summary
- Architectural Layers
- Core Concepts
- Design: AssetCollection Base
- Design: AssetWallet (Countable)
- Design: AssetInventory (Unconstrained Discrete)
- Design: ComponentManager (Constrained Discrete)
- Mixin Pattern for Owners
- Usage Examples
- Migration Path
- Open Design Questions
- Success Criteria
- Conclusion
- Credentials Interaction and Picking-Game Pattern
- Problem Statement
- Core Insight
- What the Scratch Iterations Established
- Why the Old Scene / Challenge Model Should Not Return
- Recommended v38 Shape
- Start Smaller Than “Papers Please”
- Generic Pattern: Picking Game with Hints
- What the Generic Layer Actually Needs
- Domain Concepts Worth Preserving
- What to Drop from the Older Iterations
- Example v38 Mental Model
- Proposed Implementation Order
- Summary
- Command Payload Widget Review Appendix
- Interaction Vocabulary Review Appendix
- Mu-Affordances and Microconcepts
- Sandbox Hubs as Fanout Operators
- Media resurrection plan (
tangl.media) - Migration Notes
- Audit Notes
- Reference Notes