データベースの現在状態

A third independent official Recipe, from a second publisher, gives salt-preserved wakame as 15g before washing and soaking. The recurring pre-treatment identity is now stronger, while the only published canonical Variant remains explicitly desalted; Food identity, source amount, consumed-weight conversion, shopping, and nutrition remain separated without guessing.

A fourth independent official Recipe reproduces the exact Kikkoman fourfold-concentrated mentsuyu Product at 100 ml. Exact Product identity is recurrent, while generic Food relation, Product conversion, shopping identity, and Product-specific nutrition remain separately pending because current generic/MEXT targets cannot preserve concentration and composition.

A fresh fourth official Recipe isolates grated ginger tube at 2cm and production preserves the numeric centimetre amount. An affected garlic Recipe still resolves only because its own row explicitly states 2cm (2g); generic cross-Food or cross-Product centimetre conversion remains unsupported.

A second independent official reuse Recipe separates cucumber pickle, onion pickle, and retained pickle brine. The source-backed boundary is now explicit, but canonical Food/Variant identity, prepared-piece conversion, shopping identity, brine composition, and nutrition remain separately pending rather than being guessed from generic pickles, vinegar, or a separately displayed KANTAN-SU Product.

A fifth independent official Recipe confirms the exact Product surface at 大さじ3. The approved BWS executable has been recovered, but its access-token projection is missing, so Product-to-generic-Food review, conversion, shopping identity, and runtime nutrition remain separately pending.

A second independent official Recipe reproduces the exact Kikkoman Gumen soy-milk tantan Product at 1袋. Exact Product identity is now supported, while inner-pouch conversion, outer-package shopping quantity, generic Food identity, Product-specific nutrition, attribution, and Adaption remain separate pending relations.

Exact Product identity and official composition are now supported by the official Product page and two production-imported official Recipes. Product-to-Food identity, conversion, shopping, runtime nutrition, and Recipe-specific Adaption applicability remain separate pending relations because the canonical exact-Product surface and approved production credential runner are unavailable.

An official Recipe uses source-explicit 味の素 Product at 3 shakes. Generic candidates exist, but the runtime correctly requires a reviewed Product mapping and leaves Food, conversion, shopping, and nutrition pending.

An official Recipe uses source-explicit reduced-sodium salt Product やさしお in two ingredient rows. No reviewed Product-to-Food mapping or composition target exists, so Food, shopping, and nutrition remain pending without guessing ordinary salt.

A fresh official Recipe uses a source-explicit branded whole-soybean soy sauce at 2.5 tablespoons. Generic soy sauce is available, but the runtime correctly keeps the Product unresolved without a reviewed Product-to-Food mapping.

An official Recipe uses 40g of a branded tarako paste with explicit Product identity and direct grams, but no reviewed generic Food or Variant target is available; raw tarako is not assumed to be compositionally equivalent.

An official Recipe uses a branded tomato-garlic dressing, but candidate generation only exposes raw tomato identities. The runtime correctly leaves the Product unresolved rather than treating a processed dressing as tomato.

A source-explicit branded tomato beverage has only raw-tomato and lycopene candidates. The runtime correctly leaves it unresolved rather than treating a processed drink as raw tomato.

A public Recipe can contain multiple named ingredient branches paired with separate method branches; the importer now defers merged shopping and nutrition, while canonical branch selection/modeling remains unsupported.

A fresh Umios household recipe repeats a bracketed A marker across five sauce ingredients, but the current source contract retains each ingredient independently and does not define whether that decoration should become linking query group metadata.

Post-v1 long-tail relation gap: food_identity for 揚げ油.

Post-v1 long-tail relation gap: food_identity for ingredient-71aef61d-0d05-4e9d-adea-151379f91a9b.

Post-v1 long-tail relation gap: food_identity for 鶏むね肉.

Relation coverage gap: relation_missing for canonical_recipe_cooking_links.

Post-v1 long-tail relation gap: recipe_process_missing for fixed_corpus_without_candidate_process.