Concept Library · Archive / basic concept
The proposed use of Perfume Garden is to designed around a local-first manual path, Perfume Garden would help a user build linked notes, claims, questions, definitions, and relationships with inspectable structure.
Specific concept
This page describes a concept, not a finished product. Existing source language is retained where useful, while release, evidence and commercial claims remain separate.
Perfume Garden is an expansive Application Future Concept for a workflow that would designed around a local-first manual path, Perfume Garden would help a user build linked notes, claims, questions, definitions, and relationships with inspectable structure, built around a manual-first path rather than an opaque service.
A good fit for Perfume Garden is people who need to build linked notes, claims, questions, definitions, and relationships with inspectable structure; its defining use case centers on a persistent multi-project workspace with history, search, connected workflows, and reusable structures.
A completed use of Perfume Garden would target an inspectable personal knowledge network rather than an opaque auto-generated graph; it does not prove outcomes beyond that defined result.
Perfume Garden stands apart through a persistent multi-project workspace with history, search, connected workflows, and reusable structures; that mechanism shapes the actual activity.
Possible forms
These are format possibilities, not release plans. A derived guide, tool, game, product or business resource would get its own canonical identity and its own evidence and release state.
Independent resources
Concept ancestry can explain where work began without becoming a dependency graph for everything that follows.
If ICU later publishes a related guide, calculator, download, game, comparison, product profile or business resource, that resource owns its own URL, maturity, evidence and availability. It can remain useful even if this concept page is later merged, archived, redirected or retired.
Secondary provenance
The old universe hierarchy is preserved for traceability, not used as the main organizing structure of this page.
AU-G06-S01-PL01AU-G06-S01/concepts/au-g06-s01-pl01-perfume-garden/Perfume Garden
The proposed use of Perfume Garden is to designed around a local-first manual path, Perfume Garden would help a user build linked notes, claims, questions, definitions, and relationships with inspectable structure.
The proposed task flow would move through create or open a persistent workspace and capture a note; create several durable records or projects using the domain-specific information model; mark its type and source; use connected views to search, compare, link, and review history. The user would keep control of edits, assumptions, and the final result rather than depending on opaque automation.
A completed use of Perfume Garden would target an inspectable personal knowledge network rather than an opaque auto-generated graph; it does not prove outcomes beyond that defined result.
Perfume Garden begins with repeated manual records and projects. You can add only what you know and leave uncertain parts open until better information is available.
The organizing interaction is a persistent multi-project workspace with history, search, connected workflows, and reusable structures. The proposed application would expose the user’s inputs, revisions, and resulting record so the manual path remains understandable and usable.
The concept scope calls for the local task flow, editable records, review controls, and export or portability appropriate to expansive workspace. Optional external features do not count as working until verified.
A representative use case would enter real source material, move through create or open a persistent workspace and capture a note; create several durable records or projects using the domain-specific information model; mark its type and source; use connected views to search, compare, link, and review history, revise the result, and leave with an inspectable personal knowledge network rather than an opaque auto-generated graph.
A good fit for Perfume Garden is people who need to build linked notes, claims, questions, definitions, and relationships with inspectable structure; its defining use case centers on a persistent multi-project workspace with history, search, connected workflows, and reusable structures.
Perfume Garden stands apart through a persistent multi-project workspace with history, search, connected workflows, and reusable structures; that mechanism shapes the actual activity.
Perfume Garden is classified as a Planet because of its intended scope: expansive workspace. This depth label does not indicate release status, quality, or priority.
Perfume Garden stays within its stated scope. The application remains planned, and no cloud sync, collaboration, import, or external integration is presented as working until it is actually verified. This is a Future Concept, so no release, schedule, availability, or outcome is guaranteed.
If ICU later develops Perfume Garden, a representative working Demo could be defined and tested before any broader release. Any Demo would have to full the core task manually; a Full release could add verified depth without making optional external services mandatory. No Demo, Preview, or Full release is scheduled or promised by this catalog entry.
The illustration is concept artwork, not a product screenshot. It uses constellation-like relationships used sparingly, readable note surfaces, source cards, question trails, and reversible link maps to represent the proposed activity or experience.
Connected discovery
Editorial connections use public topics, collection structure and reviewed relationships. Every card explains why it appears.
Loading public connections…