Memory
Operator direction (2026-10-08): custom pieces (UK phone bot, UK vector search, etc.) assembled on demand — NOT shipped as general features but pulled together when a user decides "i need to do this" and their LLM assembles the way. Consequences recorded: (1) demand-driven catalog — composition requests ARE the roadmap signal; every unmet "i need this" is a logged gap prioritizing what to build; (2) "UK-" qualification on examples is R0 doing its job (where_done sovereignty baked into piece identity); (3) custom pieces authored by us (model may propose/scaffold, humans author+classify+pin — trust tier intact); (4) novel compositions flow through the existing one-click approval gate, then graduate: private composition vs published safe-way needs governance (who reviews before a user-built way becomes everyone's way — OPEN); (5) flywheel: intents → compositions → custom pieces → richer catalog → more satisfiable intents. [Digest: 53df278b-50a4-44ed-a3d2-156dfa06cc37]
Tags: custom-pieces, ondemand, flywheel, roadmap, project:redaction-kernel, kind:semantic, rolled-up — Source: mcp — 2026-10-08 14:17:02 UTC