Keep roles, workflows, skills, tools, briefs, and plans distinct. A workflow is reusable method guidance in a canonical WORKFLOW.md package. A skill is bounded reusable instruction in SKILL.md. A deterministic tool performs an operation; it neither confers permission nor accepts its subject. A brief binds the present work. An ad hoc plan can be useful without being registered as a reusable workflow. Repetition is a reason to consider method development, not authority to amend an active method silently. Root entry · Runtime contract

Discover before loading. Inspect the effective catalog's name, description, origin, compatibility, and collision status, then load only the selected entrypoint and stage resources. Unqualified workflow lookup uses project, user, then bundled precedence. Preserve the full selected identity—kind, source, source-root ID, and name—through execution and replay. For example, the current App/Piping loop explicitly selects the bundled chirality-root local-graph methods. A later same-name discovery cannot replace that selection silently. Runtime contract, libraries and catalogs · Workflow index

For setup, retain the effective preparation skill and its actual origin. The Root index also carries a workflow with that basename; preserving the kind prevents an accidental substitution. In the App, available skills come from Codex's native discovery, including project, user, and bundled origins. An index entry or a historical selection does not establish the bytes supplied to the present run. Root reference tools and current source packages likewise do not prove a consumer's adoption or production qualification. Root entry · Runtime contract · Project setup

Legacy TaskSkill and unqualified converted workflow names use the explicit compatibility mapping. A source-qualified workflow identity preserves its historical workflow and bypasses that alias conversion. Retired named agents are mapped through compatibility records; they are not reintroduced as standing roles. Record what was supplied and what resolved. If historical bytes cannot be recovered, report that limit instead of replaying today's same-name file as though it were the original. Runtime contract, workflow packages

Before creating or revising any reusable workflow, load create-workflow from the intended library basis. Establish purpose, applicability, inputs, outputs, decisions, checks, recovery, and destination. A small method may need one file. Keep run-specific private facts and permissions in briefs. A project/user method request does not authorize changing the bundled library. Use existing revision mechanisms and preserve prior content before an accepted replacement. Root entry · Create a workflow

In the App authoring path, prepare .chirality/workflow-drafts/<name>/WORKFLOW.md under the project or user root, with needed resources inside the draft package. The human inspects it, requests changes in chat, and registers the reviewed bytes through the Workflows panel. Do not write straight into the live catalog as a substitute for review, claim an unobserved registration, or automatically run the new method. Another host presents the complete method and resource inventory for explicit acceptance before registration through available tools. Create a workflow

Validate metadata, folder/name agreement, resource containment, links, and intended source identity; walk through a representative success and interruption. Distinguish that walkthrough from execution evidence. Bundled Root authoring separately updates the catalog and generated index under its authorized scope and checks. Runtime discovery or reference-tool success does not establish production provider qualification. Skills and tools need the same care with provenance, scope, actual availability, and applicable ownership, even though their packaging differs. Create a workflow · Runtime contract

Domain methods deserve their own source treatment. domain-decomp preserves source admission, fidelity, atomization, category/knowledge-type meaning, disagreement, and independent examination. DOMAIN/KTY material is outside the PROJECT/SOFTWARE Scope-of-Work conversion standard. Research work should identify its accepted snapshot, retrieval basis, bounded question, independently checked evidence, and recoverable return through the selected method. Neither a retrieved passage nor a generated knowledge artifact becomes a validated engineering equation by being indexed. Domain decomposition · Research orchestration · Scope-of-Work standard §1 · Piping source rules