Open Questions¶
This is the single source of truth for unresolved, decision-pending questions at the company level. Other documents should link here rather than duplicating or re-litigating these questions in their own text — see document-metadata-standard.md.
Questions¶
| ID | Question | Why it matters | Owner | Status |
|---|---|---|---|---|
| OQ-001 | What is the final public brand for the Digital Products venture? | "Digital Products" is an internal working name only; public-facing material, domains, and trademarks depend on this being resolved. | Founder | Decided — "Devonside Labs", see ADR-0009. Visual identity (logo, lockups, favicons) remains open, tracked separately. |
| OQ-002 | Does this company repository remain documentation-centric, or does it become a monorepo containing implementation code? | Determines repository structure, tooling, and where future contributors look for code vs. governance. See repository-boundaries.md. | Founder / Repository Maintainer | Open |
| OQ-003 | Does the Shelfery implementation live in this repository or a separate repository? | Affects repository boundaries, CI/CD setup, and access control once code exists. | Founder / Venture Lead (Shelfery) | Decided — separate repository (pantryplus), see ADR-0010. |
| OQ-004 | Do Digital Products implementations live in this repository or elsewhere? | Same as OQ-003, for the Digital Products venture. | Founder / Venture Lead (Digital Products) | Open |
| OQ-005 | What GitHub organization and remote location will this repository (and any related repositories) use? | Affects collaboration, backup, and CI. | Founder | Decided (for now) — origin is configured at https://github.com/brokenlyre/devonshire-digital.git, the Founder's existing personal GitHub account (also used by the pantryplus implementation repo). See OQ-017 for the separate, still-open question of migrating to a dedicated Devonshire Digital LLC org later. |
| OQ-006 | What is the final repository visibility? | Currently assumed private (see assumptions-register.md AS-002); would need explicit confirmation before any future public use. | Founder | Decided — private by default, see ADR-0008 (approved 2026-07-11). Revisit via a new ADR if any specific content is later opened publicly. |
| OQ-007 | What are the final licensing terms, if any, for this repository or any part of it? | Currently assumed no OSS license / proprietary; affects any future external contribution or code release. | Founder | Decided — no OSS license, proprietary/all-rights-reserved, see ADR-0008 (approved 2026-07-11). Precise legal-reviewed notice language remains open — see NOTICE.md. |
| OQ-008 | Should document owners be named individuals rather than roles? | Current model is role-based (e.g. "Founder", "Repository Maintainer"); a growing team may need named accountable individuals per document. | Founder | Open |
| OQ-009 | What are the specific review cadences for each document type, beyond the default annual/quarterly conventions? |
review_cycle values are currently generic defaults; specific documents may need tighter or looser cadences. | Repository Maintainer | Open |
| OQ-010 | What is the Notion synchronization approach, if any? | Notion is management-only today and does not override Git (see git-and-notion-responsibilities.md); a future sync mechanism is explicitly not implemented yet. | Repository Maintainer | Open |
| OQ-011 | What are the final Devonshire company brand guidelines? | Affects docs/company/brand-architecture.md and all public-facing material. | Founder | Open |
| OQ-012 | What is the final Shelfery brand approval (name, identity, tone)? | Shelfery's brand direction is currently provisional (see assumptions-register.md AS-007). | Founder / Venture Lead (Shelfery) | Open |
| OQ-013 | What is the first Digital Products product priority? | Digital Products is a venture umbrella; no specific first product has been prioritized yet. | Founder / Venture Lead (Digital Products) | Open |
| OQ-014 | What product-support channels will be offered to customers? | Affects customer-trust commitments and support-related claims in any commercialization material. | Founder | Open |
| OQ-015 | What is the customer-data retention policy? | No customer data is currently collected, but any future product handling customer data needs a retention policy before launch. | Founder / Security and Privacy Reviewer | Open |
| OQ-016 | Should "Devonside" be reused as a naming-family prefix for future ventures (e.g., a hypothetical "Devonside Studios" or "Devonside Analytics"), beyond the "Devonside Labs" brand already adopted for the Digital Products venture? | The Founder has flagged intent to potentially reuse "Devonside" as a naming family across future, not-yet-created ventures. No such ventures exist yet and none are being registered by this question. Per ADR-0005, a shared naming root would not itself create a shared visual identity or umbrella brand — each future venture using it would still make its own independent brand-architecture decision — but the naming-family intent is worth recording now so it isn't reinvented or contradicted when the next venture is created. | Founder | Open |
| OQ-017 | Should Devonshire Digital LLC repositories move to a dedicated GitHub organization (rather than the Founder's personal brokenlyre account), and should an LLC-representative account (rather than a personal account) administer it? |
Raised 2026-07-11 when settling OQ-005: the Founder wants to use the personal account for now but flagged that a dedicated org with LLC-level administration may be warranted later, e.g. for cleaner separation of personal and company assets, multi-person access control, or a more official public-facing presence if any repository is ever made public. | Founder | Open |
Status values¶
- Open — no decision has been made yet.
- Decided — resolved; the Notes/linked decision record should be referenced and this row updated rather than deleted, to preserve the history of what was asked and when it was answered.
How to use this register¶
Link to a specific row (e.g. OQ-002) from any document that depends on the outcome, rather than
restating the open question inline. When a question is decided, update this table and add a
pointer to the decision record (typically an ADR).