Concept Guardrails
Focus: do existing specifications state module contracts clearly and correspond to facts and derived
maps? Run only on explicit $concept-guardrails invocation. The workflow adapts
wyx v0.26.0 under MIT (LICENSE.upstream); specifications use
this repository's Jackson dialect while runtime scripts retain upstream behavior.
Authority Model
CONCEPT.md defines purpose, state, actions, and operational principle; optional notes hold
application context.
SYNCS.md records app/include/sync coordination for application purposes and scenarios;
when/where/then define rules and // flow: groups them.
PIPELINE.md records sources, stages, outputs, invariants, triggers, and data boundaries without
replacing synchronizations.
ARCHITECTURE.md is a derived navigation map. Product dependencies come from the overall PRD, not
synchronization edges.
- Backfill reconstructs evidenced contracts from implementation; drift compares implementation with
contract. Neither proves fitness for purpose.
Specification coverage does not prove design correctness, and an accurate map does not prove code
conformance. Label inferred purposes; never use an ideal OP to justify an observed defect.
Modes
Use $concept-guardrails <mode> [path-or-description]. A path means backfill, a description means
create, and no argument means discover candidates. Start with audit when the mode is absent or the
project has no specifications.
| Mode |
Output and required reference |
audit |
Read-only coverage and command plan: references/audit.md |
concept |
Concept candidates or CONCEPT: references/concept.md |
drift |
Read-only drift report: references/drift-detection.md |
pipeline |
Pipeline candidates or PIPELINE: references/pipeline.md |
sync |
Coordination candidates or SYNCS: references/sync.md |
map |
Derived maps: references/map.md |
Route complex modeling to concept-design, confirmed-model transcription to concept-prd, and
fitness/independence/composition review to concept-audit.
Constraints
- Read specifications, implementation, and project conventions first. Mark current defects during
backfill; update specifications before implementation for confirmed new behavior.
- Present a draft or diff before unapproved writes. Complete already-authorized creation or repair;
ask only for unresolved model choices or expanded scope. Discovery lists candidates; read-only
audits do not write history or fixes.
- Keep one authoritative specification per concept, its PIPELINE beside it, cross-concept pipelines
in the composition layer, and one SYNCS per synchronization package grouped by flow. Rebuild
derived maps after specification changes when authorized.
- Before creating or reading CONCEPT/SYNCS or checking pipeline interfaces, read
references/spec-format.md. Use independent sections, named inputs/outputs, result-case matching,
and query bindings. Write operational principle; read legacy principle and signatures
compatibly.
- Mark legacy wyx interactions, dependencies, known coupling, dispatching, coordination graphs, and
sync: sections for migration rather than mixing dialects. When authorized, rewrite
CONCEPT/SYNCS/PIPELINE together while preserving triggers, bindings, effects, and failure
semantics.
Completion means the selected mode's definitions, relations, and references are evidenced; backfill
distinguishes facts, inference, and open decisions; reports name scan scope and repair direction;
maps are rebuilt from content rather than timestamps. For automatic injection read
references/hooks-runtime.md: hooks list specifications, flag staleness, and inject PIPELINE data
boundaries but do not validate semantic seams.
1---2name: concept-guardrails-23description:4 Runs concept-spec guardrails in audit, concept, drift, pipeline, sync, or map mode only when the5 user explicitly invokes $concept-guardrails. Use to create, backfill, compare, or map colocated6 concept specifications.7compatibility:8 File read/write and Grep/Glob; optional boundary-injection runtime requires Claude Code hooks and9 jq10metadata:11 source: https://skillmd.com/skills/ontology-of-everything/concept-guardrails-212 language: en13 translation_of: concept-guardrails-cn14 author: ontology-of-everything15 version: "0.32.0"16 openclaw:17 homepage: https://github.com/ontology-of-everything/concept-skills/tree/main/skills/en/concept-guardrails18---1920# Concept Guardrails2122Focus: do existing specifications state module contracts clearly and correspond to facts and derived23maps? Run only on explicit `$concept-guardrails` invocation. The workflow adapts24[wyx v0.26.0](https://github.com/jlifyio/wyx) under MIT (`LICENSE.upstream`); specifications use25this repository's Jackson dialect while runtime scripts retain upstream behavior.2627## Authority Model2829- `CONCEPT.md` defines purpose, state, actions, and operational principle; optional notes hold30 application context.31- `SYNCS.md` records app/include/sync coordination for application purposes and scenarios;32 when/where/then define rules and `// flow:` groups them.33- `PIPELINE.md` records sources, stages, outputs, invariants, triggers, and data boundaries without34 replacing synchronizations.35- `ARCHITECTURE.md` is a derived navigation map. Product dependencies come from the overall PRD, not36 synchronization edges.37- Backfill reconstructs evidenced contracts from implementation; drift compares implementation with38 contract. Neither proves fitness for purpose.3940Specification coverage does not prove design correctness, and an accurate map does not prove code41conformance. Label inferred purposes; never use an ideal OP to justify an observed defect.4243## Modes4445Use `$concept-guardrails <mode> [path-or-description]`. A path means backfill, a description means46create, and no argument means discover candidates. Start with audit when the mode is absent or the47project has no specifications.4849| Mode | Output and required reference |50| ---------- | ---------------------------------------------------------- |51| `audit` | Read-only coverage and command plan: `references/audit.md` |52| `concept` | Concept candidates or CONCEPT: `references/concept.md` |53| `drift` | Read-only drift report: `references/drift-detection.md` |54| `pipeline` | Pipeline candidates or PIPELINE: `references/pipeline.md` |55| `sync` | Coordination candidates or SYNCS: `references/sync.md` |56| `map` | Derived maps: `references/map.md` |5758Route complex modeling to `concept-design`, confirmed-model transcription to `concept-prd`, and59fitness/independence/composition review to `concept-audit`.6061## Constraints6263- Read specifications, implementation, and project conventions first. Mark current defects during64 backfill; update specifications before implementation for confirmed new behavior.65- Present a draft or diff before unapproved writes. Complete already-authorized creation or repair;66 ask only for unresolved model choices or expanded scope. Discovery lists candidates; read-only67 audits do not write history or fixes.68- Keep one authoritative specification per concept, its PIPELINE beside it, cross-concept pipelines69 in the composition layer, and one SYNCS per synchronization package grouped by flow. Rebuild70 derived maps after specification changes when authorized.71- Before creating or reading CONCEPT/SYNCS or checking pipeline interfaces, read72 `references/spec-format.md`. Use independent sections, named inputs/outputs, result-case matching,73 and query bindings. Write `operational principle`; read legacy `principle` and signatures74 compatibly.75- Mark legacy wyx interactions, dependencies, known coupling, dispatching, coordination graphs, and76 `sync:` sections for migration rather than mixing dialects. When authorized, rewrite77 CONCEPT/SYNCS/PIPELINE together while preserving triggers, bindings, effects, and failure78 semantics.7980Completion means the selected mode's definitions, relations, and references are evidenced; backfill81distinguishes facts, inference, and open decisions; reports name scan scope and repair direction;82maps are rebuilt from content rather than timestamps. For automatic injection read83`references/hooks-runtime.md`: hooks list specifications, flag staleness, and inject PIPELINE data84boundaries but do not validate semantic seams.