Enhance documentation structure and clarify project domain; add new directories for architecture, contracts, and extensions; update roadmap and open questions with resolved decisions and clarification plans.

2026-05-23 10:16:51 -05:00
parent c797a946c1
commit bf20d2a347
8 changed files with 95 additions and 5 deletions
@@ -25,6 +25,19 @@ Out of scope for early phases:
 - Moderation and trust policy.
 - Search and discovery.

+## Project Domain Baseline
+
+Current product definition:
+
+- A project is a defined work process.
+- Core project structure includes materials/ingredients, required tools, and ordered step-by-step instructions.
+- Steps may include embedded media hosted on this instance or linked from external sources.
+- Projects may include external canonical links (for example homepage, repository, or source publication).
+- Explicit project versioning is preferred and will be part of the domain model.
+- The project model is composable: a minimal core plus optional domain-specific extensions.
+- Domain-specific detail (for example knitting patterns/yarns, 3D print profiles/STLs, electronics BoM data) should be representable without being mandatory for all instances.
+- First-party FeDIY focuses on a stable extension mechanism rather than implementing every niche schema directly.
+
 ## Client and Front-End Strategy

 The server exposes a stable, documented HTTP API as its primary interface. The bundled web UI is a first-party client of that same API — it receives no privileged server-side access that a third-party client could not also use.
@@ -68,6 +81,7 @@ Bundled web UI:
 - Separate local canonical records from imported federated records.
 - Preserve source metadata for remote content and actor provenance.
 - Track object lifecycle states to support idempotent federation processing.
+- Persist project data as core fields plus extension payloads so instances can tailor domain detail without fragmenting the base model.

 ## Federation Strategy