Execution Order
Syntax 1.5.0 preserves top-level operation order. This removes ambiguity when
imports, local blocks, extensions, and replacements target the same value.
Resolution Sequence
flowchart LR
A["@meta"] --> B["@inherit"]
B --> C["@use"]
C --> D["local blocks"]
D --> E["@extend"]
E --> F["@override"]
F --> G["validate"]
G --> H["format"]
Diagram shows recommended organization, not a fixed phase reordering. Resolver executes declarations in actual source order after metadata.
Composed Source Graph
Resolver selects operation semantics from the complete reachable graph, not
only the entry file. Inherited files, top-level imports, and inline composed
operations. Inherited files, top-level imports, inline composed skills, and
inline @use declarations carried by @extend bodies are inspected before
resolution. If any reachable source declares syntax 1.5.0 or uses an ordered
operation feature, the composed graph uses declaration order. A lower-version
entry file remains valid, but PS018 reports the ordered-operation requirement
at its source location.
If no reachable source requires ordered operations, pre-1.5 projects retain
legacy phase ordering. The resolver does not reject mixed-version composition;
it applies ordered semantics and leaves PS018 to request a syntax upgrade.
Order Changes Results
@meta { id: "ordered-operations" syntax: "1.5.0" }
@standards { testing: ["Use Jest"]}
@override standards.testing { ["Use Vitest"]}
@extend standards { testing: ["Require integration tests"]}Final value:
testing: ["Use Vitest", "Require integration tests"]Reversing @extend and @override discards the extension because replacement
runs later.
Rules
@overridetarget must exist when operation runs.@extendtarget should exist before extension.- A block name may appear only once per file; a second block with the same name in one file is a PS048 error. Same-name blocks from
@inheritand@usemerge by name in declaration order. - Imported source values use import merge policy before later operations.
- Sealed skill properties remain protected regardless of operation order.
- Older syntax using
@overridestill resolves deterministically, but PS018 requests syntax1.5.0.
Review Checklist
- Read declarations from top to bottom.
- Record target value after every operation.
- Confirm replacement occurs only where intended.
- Run
prs validate --strict. - Inspect generated changes with
prs compile --dry-runorprs diff.