Choosing a Home
When a promising idea appears, do not begin by minting another Composition. Begin with the truth that must survive the work. Workflow owns the law; this page is the practical routing test.
The shortest routing test
| What actually changed? | Give it this home |
|---|---|
| another customer, host, credential set, or local configuration | a Deployment of an existing Product |
| another concrete job the operator needs to finish | a use case supported by a Product |
| another profession, market promise, default set, or support envelope | a Product identity or immutable revision, according to whether the stable operator promise changed |
| another repeatable score under the same application owner | a Pattern and immutable Scroll revisions |
| another vertical, region, provider, or form factor under the same records, authority, recovery, and finish judgment | an exact owner-qualified profile |
| another UI, report, device view, or public explanation | a projection, with its own presentation owner |
| another engine, API, transport, capture surface, or implementation mechanism | an exact Provider, Animator/Connector, adapter, or client integration, plus a typed package Contribution through the owning Extension Domain when registration is required |
| an already-settled result from another owner | an exact typed record, artifact, observation, or receipt reference |
| one live result must coordinate the lifecycle and settlement of several application owners | a Suite |
| genuinely new durable records, judgment, effects, outcomes, and recovery reused beyond one Product, client, or deployment | a candidate Composition |
Profile is not one global LychD entity. Name its owner and kind—such as a Workshop service
profile, Reach deployment profile, or Animator capability profile—and pin its exact revision. A
profile remains valid only while the owning records, authority, recovery, and honest terminal
judgment remain unchanged.
“Translate this” is normally a versioned Translation Spell or an owner-declared transformation, not a Composition by itself. Language Edition is a Composition because a timed-language edition adds durable source/segment alignment, casting, spoken performance, captions, dialogue conform, acceptance, and recovery. Website interface localization remains a Frontend catalogue concern. Shared language machinery does not merge those owners.
One idea end to end
Suppose the idea is “help a garage diagnose cars and find parts”:
- Mechanic is the proposed Product operators recognize.
- “Choose the next diagnostic test” is one supported use case.
- The durable technical service case belongs to the Workshop candidate and its passenger-vehicle service profile.
- One configured installation for one garage would be a Deployment.
- An already-settled part requirement can be referenced by Scavenger; only one live coordinated diagnostic-and-acquisition promise needs a Suite.
A curated Portfolio, not a closed universe
The first-party Portfolio should grow more slowly than Products, use cases, profiles, and Deployments. That pressure preserves comprehensible owners; it is not a numerical cap. A cap would reward god-Compositions that absorb unrelated records and safety laws merely to keep the count small.
Before promoting a candidate, answer all of these:
- What durable application record exists after chat history is gone?
- Which judgments and policies belong to that record rather than to a provider or Product?
- What can finish, refuse, remain unknown, partially settle, restart, and recover?
- Which existing office already owns the truth, if any?
- Why is a Pattern, profile, Product, projection, Extension Domain or package Contribution, Provider, or typed reference insufficient?
- What is the smallest fixture that can falsify the proposed boundary?
- Which independently motivated Products or use cases corroborate reuse?
Two independent consumers are strong evidence, not a quota. A single compelling reference case may reveal a valid owner; two decorative Product wrappers do not.
Reuse without making a god
Keep a profile when vocabulary and rules vary but the same record lifecycle, authority, recovery, and terminal judgment still make sense. Split the owner when those invariants diverge.
- Workshop may gain another trade profile only while one technical service case and honest disposition still govern it.
- Homestead remains coherent while place custody and household provision own the work; a foreign professional operation does not become Homestead merely because it occurs on the property.
- Familiar remains coherent while one admitted body's capabilities, safety, stop law, and bounded task settlement remain shared. A body class with different emergency and recovery law may deserve another owner.
- A generic “casework” helper is not automatically a Composition. Broker, accounting, legal, and municipal cases keep separate judgment unless evidence proves one root lifecycle rather than a union schema with a vague name.
An unresolved ownership need stops at study
A Product or use-case study may reveal necessary truth for which no accepted Composition yet exists. Record that as an unresolved ownership need; never let the Product temporarily own it.
Classify it before proposing a new Composition:
- If an external system is already authoritative, integrate through a typed contract.
- If a client owns bounded UI or device-local presentation state, keep it at the client boundary.
- If LychD needs durable application truth with distinct judgment, effects, finish, and recovery, develop a candidate Composition study.
Until the need resolves to an exact external authority or accepted Composition revision, affected use cases remain candidate or unsupported. The Product must not claim them as supported, and no Invocation depending on the missing truth may be admitted as a supported Product path.
From study to matter
Product/use-case study exposes a need
→ candidate Composition tests the owner and defeat conditions
→ Portfolio acceptance establishes design truth
→ source enters only with an executable first-party contract
→ State of Work records what is actually delivered
A placeholder package does not advance that sequence. Today there is no live Composition store, Product catalogue, Product selector, or Suite executor, so speculative source stubs would create topology without executable truth.
Next, learn how accepted owners assemble into Products and Suites, or return to the Portfolio.