Projects
A real project rarely belongs to only one space.
It may begin as a question in the Lab, become an experiment in the Workshop, and later operate as a working system in Works. Projects are the bridges that connect those states.
Canonical Project
An operational system for small businesses that connects booking, scheduling, CRM, notifications and bounded AI without making AI the system's identity.
Routine business operations are fragmented across messaging, scheduling, CRM and manual follow-up.
Small-business economics, existing communication habits, reliability requirements and the need to preserve human control.
Deterministic operational runtime with bounded AI used only where interpretation is required.
A working system architecture connecting operational workflows with human-centered interaction.
The correct abstraction level matters more than the fashionable stack.
Applied Systems
These systems are real parts of the work, but their canonical project entities are still being structured.
A reusable web production architecture that separates content, localization, editing, presentation and deployment while preserving the identity of each site.
Applied across Alena Portfolio, a musician site and parts of Nexus Epiphany.
A controlled knowledge-operations system for evolving project knowledge without bypassing provenance, conflict handling or human judgment.
Implemented around staged mutation, matching, conflict handling and controlled execution.
Project Model
Research questions, experiments and operational systems can all belong to the same project. The project layer exists to preserve those relations instead of flattening the work into portfolio cards.