conformance-sweep-loop

Files (1)

• SKILL.md

SKILL.md (first lines)

# Conformance sweep loop

Use this procedure for class-wave repair inside the current authorized scope.
Universal execution, applicability, deadlines and result classification remain
with their rule owners. Compose $make-check for native command selection and
$verification-loop for evidence; this procedure introduces no raw-tool route.

1. Read the selected project's declarations, implementation owners, consumers,
   current WIP and native gate report. Establish the complete declared scope
   before classifying findings; tests, examples and scripts are not excluded
   merely because they are outside production source.
2. Group findings by shared cause. Select one owner-level correction with its
   complete consumer closure, reusing the existing lower-layer implementation.
   Remove pass-through wrappers, duplicated conversions and superseded paths.
   Apply the project's own typing and composition contract; this global skill
   does not impose FLEXT facade structure on another project.
3. Execute through the declared root repair/generation verbs. Resolve rule
   resources from their current typed catalog. Neither historical CLI selectors,
   personal rule directories nor an invented profiling command are inputs.
4. Exercise public behavior, generation fixed point and required native gates.
   CRG enriches discovery only when the selected host provides it and the task
   selects that integration; compose $crg through that host's public boundary.
   Its absence never authorizes another engine or substitutes for required proof.
5. Review and integrate the complete validated slice through the global Git
   contract. Keep one current candidate and retain causal evidence when a gate
   fails. Continue correction at its owner within the same authorized unit.

For a dependency defect, inspect the declared upstream revision before creating
another implementation. Upgrade only through the consuming project's upgrade
owner, then prove the installed artifact and interpreter identity. An assumed
stale cache does not justify unconditional cache deletion or another installer.

A live incident follows its selected runtime owner before a debt sweep. Read
status through that public surface; this skill grants no daemon restart,
activation, endpoint override or topology mutation.

From datacosmos-br/agents, MIT.

More from datacosmos-br/agents