Belongs on the storefront
Ecosystem summaries, product highlights, repo role descriptions, mobile entry explanations, and selected public links.
How the layers fit together
This page is the v1 ecosystem skeleton. Its job is to explain the major layers, clarify repo roles, and show which surfaces are public-facing versus internal/operator-oriented.
1. Public storefront
`davidlifschitz.github.io` is the discovery and explanation layer. It routes visitors, highlights key surfaces, and explains the system without replacing GitHub as the detailed technical source.
2. Operator shell
ScheduleOS is the operator-facing shell. It receives work, helps structure requests, routes them using shared capability concepts, and surfaces queue and result state.
3. Mobile layer
ShortcutForge is the fast mobile front door. It handles capture, one-tap triggers, and simple return flows, while routing deeper interpreted workflows into ScheduleOS.
4. Execution backend
Delegated execution systems perform the heavier work once a task has been routed out of the shell layer.
5. Memory and context
Context and artifact lookup surfaces enrich routing, review, and later explanation layers.
6. Product and research surfaces
Public-facing tools, experiments, and research verticals sit on top of the architecture and give visitors concrete surfaces to explore.
Public versus internal
Belongs elsewhere
Raw issue queues, sprint execution details, backend implementation internals, and deeper technical artifacts that are better suited for GitHub.
Repo role map
davidlifschitz.github.io
Public discovery and explanation layer.
ScheduleOS
Operator-facing intake, routing, and monitoring surface.
ShortcutForge
Fast mobile capture and trigger surface that complements ScheduleOS.
What is placeholder in v1
This page is intentionally a content and structure skeleton. The layer descriptions, role map, and public/internal boundaries are real. The copy, visuals, richer product examples, and more polished navigation will be refined in a later storefront design sprint. For live metrics, use the dashboard.