Praxis Core Component Runtime Profiles
Use this skill when a component owner must describe which concrete JSON input
shapes are safe to materialize and which effects those shapes may attempt. A
runtime profile is owner-authored evidence for host policy; it never grants
authorization or replaces backend capabilities.
Canonical Owner And Source Audit
@praxisui/core owns the public model and resolver. Inspect:
projects/praxis-core/AGENTS.md
src/lib/models/component-runtime-profile.model.ts
src/lib/services/component-runtime-profile.service.ts and spec
src/lib/models/component-doc-metadata.interface.ts
src/lib/services/component-metadata-registry.service.ts and spec
src/lib/ai/component-registry-ai-capabilities.ts
src/public-api.ts
Then inspect the owning component metadata/profile specs and the real host
policy. Current reference consumers include CRUD, Dynamic Form, List, Table,
Page Builder, the AI registry generator, and Dynamic Page Studio.
Contract Boundary
ComponentDocMeta.runtimeProfiles is the component owner's declaration.
ComponentRuntimeProfileService resolves the first profile whose complete
structural constraints match the supplied inputs and reports mismatches.
audience: 'public-untrusted' names the audited trust boundary; it does not
turn arbitrary public JSON into trusted config.
effects must enumerate the complete effect set for the matched shape.
effects: [] means local-only behavior.
- A host evaluates its own execution policy and resolves current backend
capabilities independently. Profile match is necessary evidence where the
host requires it, never sufficient authorization.
Do not infer safety from component id, selector, labels, prompts, example names,
or the absence of visible buttons. Do not maintain a host-owned allowlist that
redefines the owner's constraints or effects.
Author A Profile
- Inventory the actual runtime reads, writes, navigation, persistence, global
actions, hooks, renderers, URLs, and compatibility fallbacks for the input
shape.
- Classify existing support before adding a public field. Prefer an owner
profile over a Studio/host-local policy only when the component can state the
effect truth canonically.
- Give the profile a stable component-scoped id and the narrowest audited
audience.
- Close the input shape with explicit constraints. Use
$ and keys-subset
for bounded records, wildcard paths for arrays, and allow/deny operators for
values that change effects. Missing nested values must not accidentally pass
an allowlist.
- Declare every possible effect with canonical operation ids, exact HTTP
methods, resource-path inputs, suffixes, and fallback roles. A fallback is
still an effect and still requires host/backend permission.
- Publish through the owning
ComponentDocMeta; preserve profiles through
defensive registry cloning, generated component docs, registry ingestion,
AI grounding, and public package exports where those consumers need them.
- Update the component runtime so a safe profile is behaviorally true. A
metadata-only claim that runtime can escape the declared shape fails review.
Reference Profiles
- CRUD
public-local-inspect-only requires
metadata.interactionMode='inspect-only', inline data, volatile persistence,
no resource paths/actions/forms/open modes/hooks, a bounded Table config, and
effects: []. Residual create/view/edit/delete events must fail closed.
- Local Table/List/Form profiles require local data or a closed static config
and prohibit unreviewed URL-, renderer-, hook-, or persistence-bearing keys.
- Remote-read profiles enumerate schema/filter/get compatibility attempts and
keep capability resolution outside the profile.
These are patterns to inspect, not aliases to copy between libraries. Each
component owner must publish the effect truth for its own runtime.
Proof
Prove three paths:
- Happy: a closed owner-authored input matches the expected profile and the
runtime performs only its declared effects.
- Risk: a required input is absent or one constraint fails; resolution returns
no match plus useful mismatches without falling back to a broader profile.
- Adversarial: extra keys, unsafe renderers/URLs/hooks, remote paths in a local
profile, or manually dispatched CRUD actions are rejected and produce no
undeclared network/navigation/persistence/global-action effect.
Minimum Angular gates:
npm run test:core -- --include=projects/praxis-core/src/lib/services/component-runtime-profile.service.spec.ts --include=projects/praxis-core/src/lib/services/component-metadata-registry.service.spec.ts
npm run build:praxis-core
Add the owning component metadata/runtime specs and one real policy consumer.
For public registry changes, run npm run generate:registry:ingestion and
validate the projected entry. For Studio execution-policy changes, run its
focused service/network-policy specs and e2e/dynamic-page-studio.spec.ts when
browser behavior changed.
Review public API, README/JSON API docs, registry assets, Studio examples, and
host guidance. State explicitly when a derived artifact is unaffected.
Companion Skills
praxis-core-component-registry-contracts: registry identity, cloning, and projection fidelity.
praxis-angular-public-api-governance: exported model/service and direct-consumer proof.
praxis-crud-runtime-openmodes, praxis-list-runtime-data, praxis-table-runtime-data, and praxis-form-schema-runtime-modes: owner runtime truth.
praxis-ai-registry-ingestion: generated component/AI registry projection.
praxis-landing-dynamic-page-studio: public Studio policy and user-facing proof.
1---2name: praxis-core-component-runtime-profiles3description: "Use when authoring, resolving, auditing, projecting, or enforcing Praxis `ComponentRuntimeProfile` contracts: public-untrusted component execution, structural input constraints, declared runtime effects, CRUD inspect-only, Table/List/Dynamic Form safe profiles, registry projection, or Dynamic Page Studio execution policy. Do not use for ordinary component registry lookup without runtime-policy impact."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-core-component-runtime-profiles6---78# Praxis Core Component Runtime Profiles910Use this skill when a component owner must describe which concrete JSON input11shapes are safe to materialize and which effects those shapes may attempt. A12runtime profile is owner-authored evidence for host policy; it never grants13authorization or replaces backend capabilities.1415## Canonical Owner And Source Audit1617`@praxisui/core` owns the public model and resolver. Inspect:1819- `projects/praxis-core/AGENTS.md`20- `src/lib/models/component-runtime-profile.model.ts`21- `src/lib/services/component-runtime-profile.service.ts` and spec22- `src/lib/models/component-doc-metadata.interface.ts`23- `src/lib/services/component-metadata-registry.service.ts` and spec24- `src/lib/ai/component-registry-ai-capabilities.ts`25- `src/public-api.ts`2627Then inspect the owning component metadata/profile specs and the real host28policy. Current reference consumers include CRUD, Dynamic Form, List, Table,29Page Builder, the AI registry generator, and Dynamic Page Studio.3031## Contract Boundary3233- `ComponentDocMeta.runtimeProfiles` is the component owner's declaration.34- `ComponentRuntimeProfileService` resolves the first profile whose complete35 structural constraints match the supplied inputs and reports mismatches.36- `audience: 'public-untrusted'` names the audited trust boundary; it does not37 turn arbitrary public JSON into trusted config.38- `effects` must enumerate the complete effect set for the matched shape.39 `effects: []` means local-only behavior.40- A host evaluates its own execution policy and resolves current backend41 capabilities independently. Profile match is necessary evidence where the42 host requires it, never sufficient authorization.4344Do not infer safety from component id, selector, labels, prompts, example names,45or the absence of visible buttons. Do not maintain a host-owned allowlist that46redefines the owner's constraints or effects.4748## Author A Profile49501. Inventory the actual runtime reads, writes, navigation, persistence, global51 actions, hooks, renderers, URLs, and compatibility fallbacks for the input52 shape.532. Classify existing support before adding a public field. Prefer an owner54 profile over a Studio/host-local policy only when the component can state the55 effect truth canonically.563. Give the profile a stable component-scoped id and the narrowest audited57 audience.584. Close the input shape with explicit constraints. Use `$` and `keys-subset`59 for bounded records, wildcard paths for arrays, and allow/deny operators for60 values that change effects. Missing nested values must not accidentally pass61 an allowlist.625. Declare every possible effect with canonical operation ids, exact HTTP63 methods, resource-path inputs, suffixes, and fallback roles. A fallback is64 still an effect and still requires host/backend permission.656. Publish through the owning `ComponentDocMeta`; preserve profiles through66 defensive registry cloning, generated component docs, registry ingestion,67 AI grounding, and public package exports where those consumers need them.687. Update the component runtime so a safe profile is behaviorally true. A69 metadata-only claim that runtime can escape the declared shape fails review.7071## Reference Profiles7273- CRUD `public-local-inspect-only` requires74 `metadata.interactionMode='inspect-only'`, inline data, volatile persistence,75 no resource paths/actions/forms/open modes/hooks, a bounded Table config, and76 `effects: []`. Residual create/view/edit/delete events must fail closed.77- Local Table/List/Form profiles require local data or a closed static config78 and prohibit unreviewed URL-, renderer-, hook-, or persistence-bearing keys.79- Remote-read profiles enumerate schema/filter/get compatibility attempts and80 keep capability resolution outside the profile.8182These are patterns to inspect, not aliases to copy between libraries. Each83component owner must publish the effect truth for its own runtime.8485## Proof8687Prove three paths:88891. Happy: a closed owner-authored input matches the expected profile and the90 runtime performs only its declared effects.912. Risk: a required input is absent or one constraint fails; resolution returns92 no match plus useful mismatches without falling back to a broader profile.933. Adversarial: extra keys, unsafe renderers/URLs/hooks, remote paths in a local94 profile, or manually dispatched CRUD actions are rejected and produce no95 undeclared network/navigation/persistence/global-action effect.9697Minimum Angular gates:9899```bash100npm run test:core -- --include=projects/praxis-core/src/lib/services/component-runtime-profile.service.spec.ts --include=projects/praxis-core/src/lib/services/component-metadata-registry.service.spec.ts101npm run build:praxis-core102```103104Add the owning component metadata/runtime specs and one real policy consumer.105For public registry changes, run `npm run generate:registry:ingestion` and106validate the projected entry. For Studio execution-policy changes, run its107focused service/network-policy specs and `e2e/dynamic-page-studio.spec.ts` when108browser behavior changed.109110Review public API, README/JSON API docs, registry assets, Studio examples, and111host guidance. State explicitly when a derived artifact is unaffected.112113## Companion Skills114115- `praxis-core-component-registry-contracts`: registry identity, cloning, and projection fidelity.116- `praxis-angular-public-api-governance`: exported model/service and direct-consumer proof.117- `praxis-crud-runtime-openmodes`, `praxis-list-runtime-data`, `praxis-table-runtime-data`, and `praxis-form-schema-runtime-modes`: owner runtime truth.118- `praxis-ai-registry-ingestion`: generated component/AI registry projection.119- `praxis-landing-dynamic-page-studio`: public Studio policy and user-facing proof.120