Compatibility & pilots
What TT-o is, exactly.
TT-o (TasteTuner-origin) is the ingredient-origin-process-sensory layer of the Ajinomatrix ecosystem: a raw material becomes a sensory-intelligent object that can travel between origin, lot, process, recipe, MP6 sensory profile and storytelling timeline.
AJNV4 compatibility
The AJNV4 export follows the docs/recipe-format.md portable recipe graph exactly, so it is quasi-injectable into POST /api/v2/graph/tastetuner/save with a minted version_id:
| TT-o concept | AJNV4 representation |
|---|---|
| Cocoa lot (with origin, harvest, quality tests) | ingredient node · payload.label + full metadata under payload.tto (shadowing Ingredient / IngredientLot / LotOriginDetail / Supplier from ingredient_service) |
| Pod opening, fermentation, drying, roasting… | process nodes · duration_s, payload.temperature, inline processEvents (START/END); sensory snapshots per lot under payload.tto.sensorySnapshots |
| Each lot’s process history (fermentation, drying, roasting…) | One process chain per lot — per-lot temperature and notes preserved, so the two-vintage experiment keeps its meaning |
| Chocolate 72 % (per vintage) | One intermediate node per lot (Chocolate A / Chocolate B) |
| Comparative millésime tasting | Shared tasting process consuming both chocolates → serve node |
| Stage order · lot consumption · outputs | Edges with UPPERCASE roles: PRECEDES, CONSUMES, PRODUCES (quantities, unit_id, yield_pct) |
Rule: TT-o never redefines base graph vocabulary. Everything TT-o adds — origin, evidence, confidence, sensory targets — rides inside payload.tto extension objects, so a future AJNV4 module can adopt or ignore them without breakage.
MP6 experimental sensory projection
mp6.experimental.tto.v0.1 projects the final tasting snapshot onto MP6’s six dimensions (taste, smell, texture, sight, temporal, psychosensory) and carries the full stage-by-stage series separately. Temporal tasting points (attack → aftertaste) were not recorded and are therefore not synthesized: the file exports temporal_capture_status: "not_recorded" — genuine temporal capture is the job of MP6 Recorder in a real project. Origin is preserved as reported / inferred / missing; this is an experimental sensory projection, not yet a canonical .mp6.
JRF experimental projection
jrf.experimental.tto.v0.1 follows Ajinoverse recipe-file conventions: title, ingredients (lots with origin metadata), processes (stages with duration and temperature), serve state, tasting notes with descriptors, and recommended next actions. A compatibility_notes field states exactly what remains to align with canonical JRF.
What is demo-ready vs experimental
| Element | Status |
|---|---|
| Illustrative cocoa demonstrator, workspace editing, millésime timeline, vintage radar, empty-project pathway | Demo-ready (dataset explicitly illustrative) |
| TT-o project import/export (round-trip, validated, provenance preserved) | Native |
| AJNV4 portable graph export (per-lot process paths) | File handoff — format-faithful; live AJNV4 import test pending |
| MP6 export | Experimental sensory projection — canonical MP6 Validator alignment pending; temporal tasting not synthesized |
| JRF export | Experimental projection — canonical JRF validator alignment pending |
| TasteTunerPublic · Chef Paradous · Ajinoverse | Workflow links — human next steps, not API integrations |
| Backend, auth, Supabase, AI calls, lab integration, chemical prediction | Out of scope for v0.1.1 by design |
Where TT-o fits — the Ajinoverse loop
TT-o is the origin layer of Ajinoverse: capture the ingredient and its process history here, carry its sensory identity into MP6, its transformation into JRF/AJNV4.3, and validate the resulting product with people through TasteTunerPublic. Not every project traverses every tool — each has one clean responsibility.
Source → Structure → Sense → Create → Test → Learn. View the complete Ajinoverse → Explore culinary application with Chef Paradous →
Pilot path
1 · Cocoa Sensory Mapping Sprint
€2,500 – €7,500 · 2–3 weeks
Stages to monitor, data to collect, first MP6 template, 1–2 pilot use cases, beta protocol (Colombia / Brussels / 2027).
2 · Harvest / Fermentation / Roasting Pilot
4–6 weeks
One origin, two harvest moments or two fermentation/roast profiles; structured comparison, temporal profile, monitoring recommendations.
3 · Millésime Cocoa Experience
storytelling layer
MP6 Timeline Player visualization for luxury / Michelin / education / commercial differentiation.