20-agent-draft

All node tools/apexctl.mjs ... commands are package-root relative: run them from the packaged skill root, or invoke that script by explicit path.

Agent 1 — Draft (Child Workflow)

Purpose

• Generate the initial APEXlang draft artifact from the provided inputs with minimal token/context usage.

Inputs

• target_type
• intent
• data_contract
• styling? (none by default)
• output_path? (defaults to applications/app_###/ for page/component scope)
• server_side_condition? (structured object from master workflow)

<authority_rules>

• Shared prompt contract: references/workflows/apexlang/prompt-contracts.md
• Follow the hierarchy, rule IDs, intermediate artifacts, and stop conditions defined there.
• If a phase-specific note conflicts with that contract, the shared contract wins. </authority_rules>

<task_scope>

• Generate the initial APEXlang draft artifact from the provided inputs.
• Use templates and governance to choose the exact emitted shape; do not widen scope or invent fallback artifacts.
• Follow the posted rules and workflow first. Do not guess while a higher-precedence rule source still provides an unanswered next step. </task_scope>

<allowed_sources>

• Templates: Use templates/** only; never invent attributes or UT classes.
• Pattern lookup order: For page-scoped work, load the matching family under templates/page-examples/** first, then the narrower supporting family under templates/**.
• Target-app isolation: For app-scoped work, read the resolved target app only for integration facts such as ids, aliases, navigation entries, breadcrumb entries, and artifact paths. Do not derive reusable patterns, layout conventions, naming conventions, or DSL structure from any applications/** tree unless the user explicitly requests cross-app comparison, migration, parity, or example lookup.
• Schema contract: When assets/component-attributes.json defines the component, treat it as the repo-safe subset for that covered shape. Draft only blocks/properties allowed by that subset unless direct compiler validation or compiler metadata for the active runtime proves otherwise. If template prose/examples disagree, treat the template as defective and do not copy the unsupported attribute.
• Exact-match template shortcut: Reuse a canonical template directly only when the component family and variant, parent context, nesting shape, and conditional mode already match, and the change is limited to safe instance substitutions such as labels, names, ids, aliases, and SQL text.
• Compiler-truth escalation: If no exact-match template exists, or the edit introduces a new property, nested block, enum token, slot, template option, or layout attribute, query compiler-backed truth with tools/query-valid-props.mjs before drafting. If compiler-backed truth cannot be resolved, emit Missing Inputs instead of inventing syntax.
• Compiler-truth evidence: Draft output must be eligible for node tools/apexctl.mjs apexlang compiler-truth audit --app-path <temp_app_path> --verify-component-attributes. Record the planned audit evidence path in the parallel contract payload.
• Authority order: For APEXlang shape decisions, direct compiler validation or compiler metadata outranks assets/component-attributes.json, which outranks template prose and examples. </allowed_sources>

<exact_match_policy>

• Follow EXACT_MATCH_TEMPLATE_REQUIRED_001.
• Reuse a canonical template directly only when the component family and variant, parent context, nesting shape, and conditional mode already match, and the change is limited to safe instance substitutions such as labels, names, ids, aliases, and SQL text. </exact_match_policy>

<compiler_truth_contract>

• Follow COMPILER_TRUTH_EVIDENCE_REQUIRED_001.
• If no exact-match template exists, or the edit introduces a new property, nested block, enum token, slot, template option, or layout attribute, query compiler-backed truth with tools/query-valid-props.mjs before drafting.
• When compiler-truth escalation is triggered, emit a Compiler Truth Evidence section before the Generation Plan or APEXlang artifact. For each affected component family, record the exact query-valid-props command, checked scope, conclusion, and emitted decision.
• Draft output must be eligible for node tools/apexctl.mjs apexlang compiler-truth audit --app-path <temp_app_path> --verify-component-attributes. Record the planned audit evidence path in the parallel contract payload.
• Local validator success does not replace compiler-truth evidence for a structural edit. </compiler_truth_contract>