@decantr/content 3.8.0

package/archetypes/recipefork-recipe-authoring.json

@@ -0,0 +1,216 @@
+{
+  "$schema": "https://decantr.ai/schemas/archetype.v2.json",
+  "id": "recipefork-recipe-authoring",
+  "role": "auxiliary",
+  "version": "1.0.0",
+  "decantr_compat": ">=2.0.0",
+  "name": "Recipefork Recipe Authoring",
+  "description": "Dual-mode recipe authoring workspace for Recipefork with Simple Mode and Chef Mode editing, drafts, hydrated editing, a shared structured ingredient editor, safe simple-to-chef conversion, hierarchical instruction groups, optional plating presentation, inline cookbook assignment, cooking tips, and rich recipe stories.",
+  "tags": [
+    "recipes",
+    "authoring",
+    "chef-mode",
+    "editor",
+    "drafts",
+    "2026"
+  ],
+  "classification": {
+    "triggers": {
+      "primary": [
+        "recipefork recipe editor",
+        "chef mode recipe editor",
+        "dual mode recipe form",
+        "advanced recipe authoring"
+      ],
+      "secondary": [
+        "structured ingredient editor",
+        "instruction group editor",
+        "recipe story editor",
+        "hydrated recipe edit"
+      ],
+      "negative": [
+        "browse",
+        "analytics"
+      ]
+    },
+    "implies": [
+      "drafts",
+      "image-upload"
+    ],
+    "weight": 1,
+    "tier": "recommended"
+  },
+  "pages": [
+    {
+      "id": "create",
+      "patterns": [
+        {
+          "pattern": "recipefork-recipe-mode-switch",
+          "preset": "split",
+          "as": "mode-switch"
+        },
+        {
+          "pattern": "recipefork-recipe-metadata-form",
+          "preset": "authoring",
+          "as": "recipe-metadata"
+        },
+        {
+          "pattern": "recipefork-simple-recipe-editor",
+          "preset": "standard",
+          "as": "simple-editor"
+        },
+        {
+          "pattern": "recipefork-chef-ingredients-editor",
+          "preset": "structured",
+          "as": "chef-ingredients"
+        },
+        {
+          "pattern": "recipefork-chef-instruction-editor",
+          "preset": "hierarchical",
+          "as": "chef-instructions"
+        },
+        {
+          "pattern": "recipefork-presentation-editor",
+          "preset": "ai-assisted",
+          "as": "recipe-presentation"
+        },
+        {
+          "pattern": "recipefork-cooking-tips-editor",
+          "preset": "bullet-editor",
+          "as": "cooking-tips"
+        },
+        {
+          "pattern": "recipefork-recipe-story-editor",
+          "preset": "expandable",
+          "as": "recipe-story"
+        },
+        {
+          "pattern": "recipefork-cookbook-assignment",
+          "preset": "inline-assignment",
+          "as": "cookbook-assignment"
+        }
+      ],
+      "default_layout": [
+        "mode-switch",
+        "recipe-metadata",
+        "cookbook-assignment",
+        "simple-editor",
+        "chef-ingredients",
+        "chef-instructions",
+        "recipe-presentation",
+        "cooking-tips",
+        "recipe-story"
+      ],
+      "shell": "recipefork-top-nav"
+    },
+    {
+      "id": "edit",
+      "patterns": [
+        {
+          "pattern": "detail-header",
+          "preset": "standard",
+          "as": "edit-header"
+        },
+        {
+          "pattern": "recipefork-recipe-metadata-form",
+          "preset": "authoring",
+          "as": "recipe-metadata"
+        },
+        {
+          "pattern": "recipefork-simple-recipe-editor",
+          "preset": "standard",
+          "as": "simple-editor"
+        },
+        {
+          "pattern": "recipefork-chef-ingredients-editor",
+          "preset": "structured",
+          "as": "chef-ingredients"
+        },
+        {
+          "pattern": "recipefork-chef-instruction-editor",
+          "preset": "hierarchical",
+          "as": "chef-instructions"
+        },
+        {
+          "pattern": "recipefork-presentation-editor",
+          "preset": "ai-assisted",
+          "as": "recipe-presentation"
+        },
+        {
+          "pattern": "recipefork-cooking-tips-editor",
+          "preset": "bullet-editor",
+          "as": "cooking-tips"
+        },
+        {
+          "pattern": "recipefork-recipe-story-editor",
+          "preset": "expandable",
+          "as": "recipe-story"
+        },
+        {
+          "pattern": "recipefork-cookbook-assignment",
+          "preset": "inline-assignment",
+          "as": "cookbook-assignment"
+        }
+      ],
+      "default_layout": [
+        "edit-header",
+        "recipe-metadata",
+        "cookbook-assignment",
+        "simple-editor",
+        "chef-ingredients",
+        "chef-instructions",
+        "recipe-presentation",
+        "cooking-tips",
+        "recipe-story"
+      ],
+      "shell": "recipefork-top-nav"
+    }
+  ],
+  "page_briefs": {
+    "create": "Recipefork's authoring entry point. Starts with a dual-mode switch between Simple Mode and Chef Mode, but both modes now share the same structured ingredient authoring surface. Chef Mode remains the hard blocker: grouped instruction sets, step imagery, timing, ingredient-step linkage, optional plating presentation, cooking tips, drafts, cookbook assignment, and rich stories must all be expressible without loss.",
+    "edit": "Hydrated edit surface for existing recipes. Editing must round-trip every Chef Mode field: stable ingredient IDs, instruction groups, step images, required ingredient links, derived timing, optional plating presentation, cooking tips, story HTML, cookbook assignment, and draft-versus-published state. Simple recipes should hydrate into the same structured ingredient editor without losing their original ingredient lines, and support safe conversion into Chef Mode in place for drafts or via draft-copy for published recipes."
+  },
+  "features": [
+    "simple-mode",
+    "chef-mode",
+    "drafts",
+    "image-upload",
+    "hydrated-editing",
+    "structured-ingredients",
+    "hierarchical-instructions",
+    "presentation",
+    "cooking-tips",
+    "mode-conversion",
+    "rich-story",
+    "autosave",
+    "cookbook-assignment"
+  ],
+  "dependencies": {
+    "patterns": {
+      "recipefork-recipe-mode-switch": ">=1.0.0",
+      "recipefork-recipe-metadata-form": ">=1.0.0",
+      "recipefork-cookbook-assignment": ">=1.0.0",
+      "recipefork-simple-recipe-editor": ">=1.0.0",
+      "recipefork-chef-ingredients-editor": ">=1.0.0",
+      "recipefork-chef-instruction-editor": ">=1.0.0",
+      "recipefork-presentation-editor": ">=1.0.0",
+      "recipefork-cooking-tips-editor": ">=1.0.0",
+      "recipefork-recipe-story-editor": ">=1.0.0",
+      "detail-header": ">=1.0.0"
+    },
+    "styles": {}
+  },
+  "suggested_theme": {
+    "ids": [
+      "recipefork",
+      "clean"
+    ],
+    "modes": [
+      "light",
+      "dark"
+    ],
+    "shapes": [
+      "rounded"
+    ]
+  }
+}

package/archetypes/recipefork-recipe-detail.json

@@ -0,0 +1,139 @@
+{
+  "$schema": "https://decantr.ai/schemas/archetype.v2.json",
+  "id": "recipefork-recipe-detail",
+  "role": "primary",
+  "version": "1.0.0",
+  "decantr_compat": ">=2.0.0",
+  "name": "Recipefork Recipe Detail",
+  "description": "Recipefork's recipe detail surface with hero imagery, summary/actions, Chef Mode ingredient and instruction displays, optional plating presentation, dynamic cooking tips, public provenance attribution, owner-only branch analytics, and comments, all under the shared Recipefork top-nav shell.",
+  "tags": [
+    "recipes",
+    "detail",
+    "chef-mode",
+    "comments",
+    "2026"
+  ],
+  "classification": {
+    "triggers": {
+      "primary": [
+        "recipefork recipe detail",
+        "chef mode recipe page",
+        "recipe detail with comments"
+      ],
+      "secondary": [
+        "recipe hero page",
+        "fork provenance recipe",
+        "recipe comments"
+      ],
+      "negative": [
+        "catalog",
+        "admin"
+      ]
+    },
+    "implies": [
+      "sharing",
+      "comments",
+      "reactions",
+      "forking"
+    ],
+    "weight": 1,
+    "tier": "recommended"
+  },
+  "pages": [
+    {
+      "id": "recipe-detail",
+      "patterns": [
+        {
+          "pattern": "hero",
+          "preset": "image-overlay",
+          "as": "recipe-hero"
+        },
+        {
+          "pattern": "detail-header",
+          "preset": "standard",
+          "as": "recipe-summary"
+        },
+        {
+          "pattern": "recipefork-fork-provenance",
+          "preset": "lineage-card",
+          "as": "recipe-provenance"
+        },
+        {
+          "pattern": "recipefork-chef-ingredients-display",
+          "preset": "scaled",
+          "as": "chef-ingredients"
+        },
+        {
+          "pattern": "recipefork-chef-instructions-display",
+          "preset": "hierarchical",
+          "as": "chef-instructions"
+        },
+        {
+          "pattern": "recipefork-presentation-display",
+          "preset": "numbered-steps",
+          "as": "recipe-presentation"
+        },
+        {
+          "pattern": "recipefork-cooking-tips-display",
+          "preset": "bullet-list",
+          "as": "cooking-tips"
+        },
+        {
+          "pattern": "comment-thread",
+          "preset": "sidebar",
+          "as": "recipe-comments"
+        }
+      ],
+      "default_layout": [
+        "recipe-hero",
+        "recipe-summary",
+        "recipe-provenance",
+        "chef-ingredients",
+        "chef-instructions",
+        "recipe-presentation",
+        "cooking-tips",
+        "recipe-comments"
+      ],
+      "shell": "recipefork-top-nav"
+    }
+  ],
+  "page_briefs": {
+    "recipe-detail": "Recipefork's recipe detail page is equal parts showcase and utility: hero imagery at the top, rich summary/actions, then the actual cooking content. Chef Mode recipes should preserve scaled ingredients, hierarchical instructions, optional plating presentation, and immediate-parent/root-original attribution for all viewers. Recipe-specific cooking tips replace generic filler. Branch metrics, fork-history inspection, and descendant branch timelines are owner-facing analytics rather than public browsing defaults."
+  },
+  "features": [
+    "sharing",
+    "comments",
+    "reactions",
+    "forking",
+    "chef-mode",
+    "presentation",
+    "cooking-tips",
+    "lineage",
+    "branch-analytics"
+  ],
+  "dependencies": {
+    "patterns": {
+      "hero": ">=1.0.0",
+      "detail-header": ">=1.0.0",
+      "recipefork-fork-provenance": ">=1.0.0",
+      "recipefork-chef-ingredients-display": ">=1.0.0",
+      "recipefork-chef-instructions-display": ">=1.0.0",
+      "recipefork-presentation-display": ">=1.0.0",
+      "recipefork-cooking-tips-display": ">=1.0.0",
+      "comment-thread": ">=1.0.0"
+    },
+    "styles": {}
+  },
+  "suggested_theme": {
+    "ids": [
+      "recipefork"
+    ],
+    "modes": [
+      "light",
+      "dark"
+    ],
+    "shapes": [
+      "rounded"
+    ]
+  }
+}

package/archetypes/recipefork-social.json

@@ -0,0 +1,103 @@
+{
+  "$schema": "https://decantr.ai/schemas/archetype.v2.json",
+  "id": "recipefork-social",
+  "role": "auxiliary",
+  "version": "1.0.0",
+  "decantr_compat": ">=2.0.0",
+  "name": "Recipefork Social",
+  "description": "Recipefork's public discovery feed with engagement-aware recipe ranking, event filters, followed-creator cues, fork-depth/root lineage badges on cards, and a preview-card community activity rail.",
+  "tags": [
+    "recipes",
+    "social",
+    "feed",
+    "activity",
+    "2026"
+  ],
+  "classification": {
+    "triggers": {
+      "primary": [
+        "recipefork feed",
+        "recipe activity rail",
+        "community recipe feed"
+      ],
+      "secondary": [
+        "recipe publishing feed",
+        "follow activity",
+        "food social timeline"
+      ],
+      "negative": [
+        "admin",
+        "analytics"
+      ]
+    },
+    "implies": [
+      "social",
+      "reactions",
+      "comments",
+      "follows"
+    ],
+    "weight": 0.9,
+    "tier": "recommended"
+  },
+  "pages": [
+    {
+      "id": "feed",
+      "patterns": [
+        {
+          "pattern": "filter-bar",
+          "preset": "standard",
+          "as": "feed-filters"
+        },
+        {
+          "pattern": "recipefork-recipe-card",
+          "preset": "feed",
+          "as": "recipe-grid"
+        },
+        {
+          "pattern": "recipefork-activity-feed",
+          "preset": "preview-cards",
+          "as": "community-activity"
+        }
+      ],
+      "default_layout": [
+        "feed-filters",
+        "recipe-grid",
+        "community-activity"
+      ],
+      "shell": "recipefork-top-nav"
+    }
+  ],
+  "page_briefs": {
+    "feed": "Recipefork's discovery home after landing: a recipe-first feed with newest-versus-trending controls on the left and a linked community activity rail on the right. Trending should consider more than forks alone: recent reactions, comments, saves, branch-variation counts, and affinity to followed cooks all inform the ordering. Cards can reveal fork depth and rooted lineage without overwhelming the browsing experience."
+  },
+  "features": [
+    "social",
+    "activity-feed",
+    "comments",
+    "reactions",
+    "follows",
+    "forking",
+    "engagement-ranking",
+    "lineage-cues"
+  ],
+  "dependencies": {
+    "patterns": {
+      "filter-bar": ">=1.0.0",
+      "recipefork-recipe-card": ">=1.0.0",
+      "recipefork-activity-feed": ">=1.0.0"
+    },
+    "styles": {}
+  },
+  "suggested_theme": {
+    "ids": [
+      "recipefork"
+    ],
+    "modes": [
+      "light",
+      "dark"
+    ],
+    "shapes": [
+      "rounded"
+    ]
+  }
+}

package/archetypes/registry-browser.json

@@ -0,0 +1,121 @@
+{
+  "$schema": "https://decantr.ai/schemas/archetype.v2.json",
+  "id": "registry-browser",
+  "role": "primary",
+  "version": "1.1.0",
+  "decantr_compat": ">=2.0.0",
+  "name": "Registry Browser",
+  "description": "Public content browsing for a design registry. Search, filter, and explore patterns, themes, blueprints, archetypes, and shells.",
+  "tags": [
+    "registry",
+    "browser",
+    "search",
+    "content",
+    "explore"
+  ],
+  "classification": {
+    "triggers": {
+      "primary": [
+        "registry",
+        "browse",
+        "explore",
+        "catalog"
+      ],
+      "secondary": [
+        "search",
+        "filter",
+        "patterns",
+        "themes",
+        "blueprints"
+      ],
+      "negative": []
+    },
+    "implies": [],
+    "weight": 0.9,
+    "tier": "recommended"
+  },
+  "pages": [
+    {
+      "id": "homepage",
+      "default_layout": [
+        "search-filter-bar",
+        "registry-discovery-cta-grid",
+        "content-card-grid"
+      ],
+      "shell": "top-nav-main",
+      "notes": "Registry landing for builders. Hero search plus a discovery CTA grid, featured blueprints, and showcase-forward discovery."
+    },
+    {
+      "id": "browse",
+      "path": "/browse",
+      "default_layout": [
+        "search-filter-bar",
+        "content-card-grid"
+      ],
+      "shell": "top-nav-main"
+    },
+    {
+      "id": "browse-type",
+      "path": "/browse/[type]",
+      "default_layout": [
+        "search-filter-bar",
+        "content-card-grid"
+      ],
+      "shell": "top-nav-main"
+    },
+    {
+      "id": "detail",
+      "path": "/[type]/[namespace]/[slug]",
+      "default_layout": [
+        "content-detail-hero",
+        "json-viewer"
+      ],
+      "shell": "top-nav-main"
+    },
+    {
+      "id": "profile",
+      "default_layout": [
+        "detail-header",
+        "content-card-grid",
+        "activity-feed"
+      ],
+      "shell": "top-nav-main",
+      "notes": "Public user profile showing published items and activity."
+    }
+  ],
+  "page_briefs": {
+    "homepage": "Registry landing for app-builders. Search remains the hero, but the page should quickly orient users toward official blueprints, discovery CTA cards, and live showcases rather than analytics. Quick-start actions should be visually strong, clearly interactive, and owned by a dedicated discovery pattern instead of page-local runtime styling. Use one consistent public-shell inset rhythm and keep every section purposeful.",
+    "browse": "Search-first browsing page. The filter bar should expose search, type, source, and sort only. Cards should lead with title, type, description, and source line. Remove operator-facing trust chips from browse entirely and keep the layout calm, editorial, and easy to scan.",
+    "browse-type": "Filtered registry view for a single content type. Same search/source/sort rhythm as the main browse page, pre-filtered to the selected type. Type identity should remain strong without creating visual clutter.",
+    "detail": "Content detail page. Hero content is intent-first, with quick-start guidance, human-readable source identity, and trust surfaces that explain why an item matters. Recommendation, showcase, and verification signals belong here, not on browse cards.",
+    "profile": "Public profile showing avatar, username, bio, and published item count with the same curated shell spacing as the rest of the registry browser. Published content cards should match browse-card hierarchy, including thumbnail, type chip, source line, and simpler metadata."
+  },
+  "features": [
+    "search",
+    "pagination"
+  ],
+  "shells": {
+    "top-nav-main": "Top navigation bar with main content area"
+  },
+  "dependencies": {
+    "patterns": {
+      "search-filter-bar": "^1.0.0",
+      "registry-discovery-cta-grid": "^1.0.0",
+      "content-card-grid": "^1.0.0",
+      "content-detail-hero": "^1.0.0",
+      "detail-header": "^1.0.0",
+      "json-viewer": "^1.0.0",
+      "namespace-badge": "^1.0.0",
+      "activity-feed": "^1.0.0"
+    },
+    "styles": {}
+  },
+  "suggested_theme": {
+    "ids": [
+      "luminarum"
+    ],
+    "modes": [
+      "dark"
+    ]
+  }
+}

package/archetypes/render-monitor.json

@@ -0,0 +1,114 @@
+{
+  "$schema": "https://decantr.ai/schemas/archetype.v2.json",
+  "id": "render-monitor",
+  "role": "auxiliary",
+  "version": "1.0.0",
+  "decantr_compat": ">=2.0.0",
+  "name": "Render Monitor",
+  "description": "Observe every render job in flight: queue, progress, GPU utilization, and live log streaming for diagnosing failed or slow video generations.",
+  "tags": [
+    "render",
+    "monitor",
+    "jobs",
+    "logs",
+    "queue",
+    "gpu",
+    "2026"
+  ],
+  "classification": {
+    "triggers": {
+      "primary": [
+        "render monitor",
+        "render jobs",
+        "render queue",
+        "job monitor",
+        "video renders"
+      ],
+      "secondary": [
+        "render logs",
+        "gpu jobs",
+        "render status",
+        "job observability"
+      ],
+      "negative": []
+    },
+    "implies": [
+      "logs"
+    ],
+    "weight": 0.6,
+    "tier": "recommended"
+  },
+  "pages": [
+    {
+      "id": "renders",
+      "path": "/renders",
+      "patterns": [
+        {
+          "pattern": "render-queue",
+          "preset": "list",
+          "as": "queue-list"
+        },
+        {
+          "pattern": "filter-bar",
+          "preset": "standard",
+          "as": "filters"
+        }
+      ],
+      "default_layout": [
+        "filters",
+        "queue-list"
+      ],
+      "shell": "sidebar-main"
+    },
+    {
+      "id": "render-detail",
+      "path": "/renders/:id",
+      "patterns": [
+        {
+          "pattern": "detail-header",
+          "preset": "standard",
+          "as": "job-header"
+        },
+        {
+          "pattern": "log-stream",
+          "preset": "standard",
+          "as": "live-logs"
+        }
+      ],
+      "default_layout": [
+        "job-header",
+        "live-logs"
+      ],
+      "shell": "sidebar-main"
+    }
+  ],
+  "page_briefs": {
+    "renders": "All-jobs dashboard. A horizontal filter bar at the top exposes status chips (queued, running, completed, failed), project selector, time range picker, and GPU-tier filter. Below, a render queue rendered as a full list shows each job row with thumbnail preview, project name, scene badge, progress bar with percentage, ETA, elapsed time, GPU label, and contextual actions (cancel, retry, download) aligned right.",
+    "render-detail": "Single render job focus view. Top region is a detail header with large preview thumbnail, job title, status badge, progress ring, key metrics (frames rendered, elapsed, ETA, GPU model), and action buttons (cancel, retry, download artifact). Below, a full-height live log stream component displays streaming stdout with timestamp gutters, severity color coding, auto-scroll lock, filter input, and copy/download controls."
+  },
+  "features": [
+    "render-monitoring",
+    "logs"
+  ],
+  "shells": {
+    "sidebar-main": "Sidebar navigation with main content area"
+  },
+  "suggested_theme": {
+    "ids": [
+      "carbon",
+      "neon-dark"
+    ],
+    "modes": [
+      "dark"
+    ]
+  },
+  "dependencies": {
+    "patterns": {
+      "render-queue": ">=1.0.0",
+      "filter-bar": ">=1.0.0",
+      "detail-header": ">=1.0.0",
+      "log-stream": ">=1.0.0"
+    },
+    "styles": {}
+  }
+}