Every reusable capability I've identified across OPUS products, scored by how much un-extracted value sits there. 10 = extract today. Append-only — past entries superseded but never edited.
Fracture potential: this is the most reusable framework in the studio; 3 connectors are stubbed, but the contract is solid — extract before fixing
Fracture potential: de-religify branding → @opus-studio/brand-safety-api. Same engine, sold as B2B brand-safety for ad-tech, K-12 ISPs, compliance platforms.
Fracture potential: @opus/domain-interpreter npm package. 12K+ lines of showcase brands extracted as separate data file. Revenue-generating cross-product feature.
Fracture potential: @opus/domain-interpreter npm package. 12K+ lines of showcase brands extracted as separate data file. Revenue-generating cross-product feature.
Fracture potential: makes the operator's existing Claude Code subscription the canonical LLM tier for every OPUS product. Reduces studio-wide LLM spend toward zero. Dual-mode: paid fallback fires automatically when bridge unavailable.
Fracture potential: This entry is the moment the value ledger transitions from wishlist to accounting system. Every future LLM call in the studio can be benchmarked against these baseline numbers.
Fracture potential: With provider (cap-013) + consumer (this) both shipped, wire-001 is the FIRST end-to-end cross-OPUS capability flow in the studio's history. The value ledger formally transitions from wishlist to accounting.
Fracture potential: products.ts can become @opus-studio/products npm package — single source of truth feeding every OPUS product
Fracture potential: @opus/relay as gRPC service; cross-product device management plane
Fracture potential: merge with autocmo's tier-aware router → @opus-studio/llm-router as the canonical version. Currently 2 separate implementations.
Fracture potential: convert OneAPIKey into the canonical internal cost-allocation hub for the studio (the OPUS API Tax Router proposal)
Fracture potential: single canonical LLM router for OPUS; current state = 4+ implementations
Fracture potential: resolves fracture-007 (4/7 family members stub) for kosher-classifier specifically. Activation = set AI_INFERENCE_ENABLED=true + ONEAPI_KEY in env. ~$0.0003/domain at scale.
Fracture potential: this is the multiplier asset the directive called out. ~250 keys * 3 languages locked under one type-safe catalog. Doubles or triples addressable audience without rebuild.
Fracture potential: the strongest unrealized OPUS asset (@opus/brandsafe potential) is now one boolean away from running. Local mode = $0 marginal cost via bridge.
Fracture potential: package as @opus-studio/llm-router; sells as standalone SaaS for any Anthropic SDK user
Fracture potential: abstract Persona's YAML schema beyond Android — same primitive could simulate web sessions or voice calls
Fracture potential: this is a real governance breakthrough most studios lack. Extract as ADR + reference template.
Fracture potential: @opus/play-publisher. Every OPUS product with an Android target reinvents this.
Fracture potential: the studio's first economic layer. Recursive feedback per Master Prompt section 2.
Fracture potential: this is the multiplier: every future content unit ALEF publishes can reach the trilingual audience without rebuild. Russian and Hebrew were latent demand for OPUS Studio's domestic Israeli market.
Fracture potential: This script is the enforcement of the most important lesson of the project. Until today, no machine-checked what visitors actually saw. Now a 30-line script gates every deploy.
Fracture potential: the Potemkin-site failure becomes mechanically impossible. CI runs verify-deploy + i18n-lint + typecheck on every push; if drift, GitHub annotation surfaces it before operator's next session.
Fracture potential: first stake in the ground for real visual identity. Same pattern applies to all OPUS sites that today live in pure-mono aesthetic.
Fracture potential: single hero mark today. v2 could be a generative variant per-section (different ring counts/colours/speeds) tied to data state.
Fracture potential: AlefLoop is data-driven imagery — same approach (real-numbers-as-visual) could become the recurring pattern across pages. Each data page could have its own loop diagram pulled from its source.
Fracture potential: extract as @opus-studio/i18n; lighter than next-intl, no router coupling
Fracture potential: the pipeline pattern is more valuable than any single agent. Document as ADR, publish as exposure unit
Fracture potential: @opus-studio/saas-kit; opinionated starter for any product wanting multi-tenant + Stripe
Fracture potential: Build Mode currently proposes diffs but never patches. Wire it to actually patch + open PR = step-change in admin productivity.
Fracture potential: @opus-studio/anomaly; signal-grading framework reusable anywhere there's a metric
Fracture potential: @opus-studio/domain-valuator; sellable as standalone API
Fracture potential: every new OPUS product saves ~80% boilerplate; old products gain a normalized observability/security baseline
Fracture potential: no competitor exists; ~5000 synagogues in Israel + diaspora long tail; 1-2 days to ship as @opus/hilula-engine
Fracture potential: first time ALEF iterates on its own visual presentation autonomously. Pattern is repeatable: dispatch critic, capture, implement, ledger.
Fracture potential: This is the single biggest UX feature gap from critique 001 (7/10 impact). With ~85 indexed items, the site moves from indie-polished to Stripe-caliber discoverability.
Fracture potential: This mistake is a category-level mistake. It exposes the entire class of 'I'm not seeing what users see' failures and forces a process change.
Fracture potential: first of 5 migration patches actually applied. Pattern repeatable for annoying-secretary, wizetube, bizforge, autocmo when operator is ready.
Fracture potential: closes the autonomy loop the directive demanded ('תן לזה לרוץ אוטומטית'). From this commit forward, every Claude Code session ends with a verified-live deploy if the data changed.
Fracture potential: directly answers the operator's directive 'תעשה את האתר ידידותי למשתמש עם אפשרות להעמקה'. Pattern is reusable for any OPUS product that has a data-dense UI — wherever raw output meets a non-expert visitor.
Fracture potential: StatusSparkbar pattern reusable on /mistakes (lesson effectiveness). Arc diagram pattern reusable on any future origin→consumer dataset.
Fracture potential: lift as @opus-studio/observability; one-line setup for any product
Fracture potential: @opus/vercel-deployer; useful for any product that auto-creates and ships micro-sites
Fracture potential: document as ADR; extract to @opus-studio/mode-isolation
Fracture potential: per-marketplace optimized AI copy as a service for any product selling on multiple channels
Fracture potential: hero product for smarts-domains; could become a public API
Fracture potential: forest defense signaling — turn isolated incidents into ecosystem-wide hardening
Fracture potential: market is opaque (Yad2/Madlan dominate listings; AI-valuation shallow). Components already exist across 3 OPUS products. 2-3 weeks to ship.
Fracture potential: reusable across any OPUS product needing trilingual; LangProvider is decoupled and type-safe (Strings interface enforces full coverage)
Fracture potential: three completed rounds (001, 002, 003) prove the loop is repeatable. Maintenance.ps1 already detects >=7d staleness and surfaces the prompt. ALEF can run this autonomously going forward.
Fracture potential: realizes the master directive 'if translation missing, use Bridge to fill'. Dry-run mode reports gaps without API calls. Pattern is reusable for any OPUS product with i18n needs.
Fracture potential: first deliberate funnel on the site. If audience metrics show high bounce on data pages, /start-here is where to A/B the framing.
Fracture potential: could add filter/sort controls, status timeline per proposal, and an explicit 'adoption velocity' counter (proposals-per-week shipped).
Fracture potential: pattern reusable for status_set on /wires (ui-002) and time_series on /timeline. Component currently inline; could be extracted to a Histogram component when second consumer arrives.
Fracture potential: general previous_state pattern. Same shape could anchor a 'last 7 days' chart, weekly newsletter content, or anomaly detection on counts.
Fracture potential: same depth pattern applicable to Stat tiles on /now and /lab. Header trim was overdue.
Fracture potential: prevents studio-wide drift between products
Fracture potential: the studio's resting EKG — catches products being neglected before chronic damage compounds
Fracture potential: the same i18n map pattern is reusable for any future hand-written chronicle in the studio
Fracture potential: first self-improvement loop wired into the maintenance heartbeat. Pattern repeatable for any audit cycle (security, accessibility, perf).
Fracture potential: Term component built and ready; not yet wired into manifesto/timeline prose because those strings are flat i18n catalogs. Next iteration: a markdown-to-React renderer that auto-detects glossary keys.
Fracture potential: establishes the precedent that every animation must respect this query. Future audit rule could flag any animate-/transition- class on an element without an exception comment.
Fracture potential: low individually but useful when bundled into @opus-studio/pwa-kit
Fracture potential: first end-to-end shipped change driven by ALEF analysis. 32 → 34 products in catalog. Compounds with wire-001 (each new product is a candidate consumer/provider).
Fracture potential: doctrine-as-code: the validator is the enforcement. Until now, missing translations could be merged silently. Now they fail.
Fracture potential: closes the only remaining production URL gap. Once deployed, n50.io always works.
Fracture potential: low - utility component, but unlocks future deep-link routes
Fracture potential: closes 3 of the 7 search-UX gaps critique_003 identified. Remaining 4 (recent/pinned, mobile density, RTL input, Tab nav) deferred to round 004.