Shelfery System Context (Placeholder — stale)¶
Note (2026-07-27): this placeholder predates Shelfery's actual implementation
(now a production app in the shelfery repository) and predates
ADR-0017,
which means this repository no longer holds Shelfery's product specification at
all — not even as a ventures/shelfery/product/ placeholder. Fully replacing this
document with a real system context (or an accurate "specification lives
elsewhere" pointer) is a separate task from the product-governance restructuring
that added this note. Content below is retained as-is; do not treat the
product/product-requirements.md paths it references as real.
This document is a deliberately minimal placeholder. No application architecture has been decided for Shelfery. There is currently no system context diagram, no defined set of components, no chosen technology stack, and no integration map, because none of those decisions have been made.
Why this is empty¶
Producing a real system context requires an approved product specification
describing what the product needs to do. Without that, any architecture
description written here would be invented rather than derived from real
requirements — which this venture's documentation is explicitly required
to avoid (see ventures/shelfery/AGENTS.md, section 6).
What triggers real architecture work¶
Real system-context and architecture work is expected to begin once a product
specification is defined and reviewed — that specification now lives entirely
in the shelfery implementation repository (see the note above), not under a
ventures/shelfery/product/ path here. At that point, this document should be
replaced with an actual system context description — the boundary of the
system, its major components, its external dependencies, and how it fits into
any broader Devonshire Digital technical environment, if applicable.
What to do if asked for architecture now¶
If asked to produce Shelfery architecture, check the shelfery implementation
repository's own docs/ai/architecture.md first — it likely already has one.
Treat this document's absence of one as a signal to look there, not to invent
an architecture to fill the gap here.