القائمة
Mental model for an application as the concrete selection and realization boundary of the product chain.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Mental model for a sealed service whose context and authorship narrow toward operation handlers.
Mental model for locating work in RAWR's blueprint kinds while keeping semantic direction, ownership, and structural proof distinct.
Mental model for Nx as the repository graph and scheduler while project owners retain their qualified build and verification work.
Mental model for one conventional installed Oclif application that owns CLI identity while commands retain qualified capability boundaries.
Mental model for a first-party Oclif command plugin as one host-composed terminal projection on public package boundaries.
Mental model for inert reusable support that carries no product, runtime, or projection authority.
| name | habitat-app-frame |
| description | Mental model for an application as the concrete selection and realization boundary of the product chain. |
An app turns declared capability into one concrete product assembly. It owns plugin membership, provider and profile selection, stable configuration binding, role choice, and the executable entrypoint.
resource -> provider -> service -> plugin -> app
|
v
runtime realization
The app selects; it does not redefine. Resource contracts remain neutral, providers retain implementation ownership, services retain domain truth, and plugins retain projection ownership. App-owned context flows downward through those public faces so each lower boundary receives only what it needs.
The package-backed shell may expose bin/, but host-specific details belong to
a narrower app blueprint. Entrypoints stay thin: they select one declared
composition and start it rather than reconstructing providers, services, or
plugin surfaces by hand.
app, composition, entrypoint, profile, realization, role, selection