Observal Managing Registry Components
Execution contract
- Execute commands with a 60 second timeout.
- Use machine output by default: add
--output jsonwhenever supported. Parse list results fromitemsand pagination fields. - Run the leaf command's
--helpwhen any path, flag, enum, or payload shape is uncertain. - Supply all required inputs and confirmation flags. Do not leave an agent waiting at a prompt.
- Reuse returned UUIDs and
qualified_namevalues. Never automate with row numbers or ambiguous bare names. - Verify installs, submissions, edits, versions, ownership changes, and lifecycle transitions.
- Submit or modify only components the user owns or is authorized to manage.
- Never expose environment values, headers, tokens, private source data, or submitted secret fields.
- Mutations are sent once. After an uncertain transport failure, read component state before retrying.
Choose the workflow
| User intent | Read |
|---|---|
| Find, inspect, recommend, or install components | Discovery and installation |
| Submit one component or a mixed bulk file | Component submission |
| Edit, version, archive, restore, transfer, or manage co-authors | Registry lifecycle |
Read only the selected reference, and read it completely before executing.
Registry rules
- Search with the user's natural-language terms, then narrow by type, namespace, team, harness, or category only when useful.
- Open-ended requests such as "what am I missing?" use personalized recommendations before keyword search.
personalized: falsemeans popularity fallback, not a personal recommendation.- Team members can see authorized private teamspace items. Use
TEAM_HANDLE/ITEM_SLUGfor direct references. - Draft, pending, rejected, and approved items have different edit behavior. Read status before mutating.
- A successful submit can still be pending review. Report the returned status instead of saying it is published.
- Bulk files are structurally validated before mutation. Inspect every per-entry result and verify uncertain retries by canonical identity.
- Prefer an existing installed dependency or native CLI path. Do not invent wrappers or telemetry variables.
Completion
Report component type, canonical identity, version, status, target harness or scope when applicable, warnings, and any review or setup step still required.