Concept Audit
Focus: can the concept and application designs fulfill their respective purposes, and does the
implementation conform? Run only on explicit $concept-audit invocation and remain read-only.
Design can be reviewed without code; without specifications, review only observable code properties.
Mark conclusions unsupported by missing material as unverified.
Model
A concept is a behavioral unit designed for one purpose. A concept argument connects its purpose
to its operational principle (OP), state, and actions. An application argument connects the
application purpose to concept selection, synchronizations, and end-to-end scenarios. Conformance to
an unsuitable model does not establish fitness; successful OP tests do not prove the purpose, and
locally sound concepts do not prove the application purpose.
Review five dimensions:
- Fitness: behavior meets the real need under stated assumptions.
- Independence: concept definitions do not depend on other concepts; this repository also
requires concept modules not to reference one another.
- Composition: synchronizations coordinate public actions without expanding or corrupting
allowed concept behavior.
- Drift: implementation differs from a confirmed behavioral contract; distinguish omissions from
contradictions.
- Product subsets: each subset preserves its purpose, entry points, required synchronizations,
and resources.
Evidence means a fact supported by inspected requirements, models, code, or tests. Missing evidence
is not evidence of absence.
Audit
- Scope — Read
references/spec-format.md, requirements, concept and synchronization
specifications, the overall PRD, and staged links. With code, trace real entry points, calls,
state/schema, migrations, and tests. Record versions, terms, facts, inferences, coverage, and
gaps.
- Design arguments — State concept and application purposes. For every concept, test the
contract → OP → purpose argument and specificity, completeness, independence, and familiarity.
Review application selection and synchronizations against end-to-end scenarios. Novelty or
infrastructure identity alone is not a defect.
- Drift and independence — When code exists, use
references/drift-checklist.md to compare
signatures, outputs, invariants, state, and dependencies, including public calls, shared mutable
state, private access, and DTO/protocol leakage. Same-named local type parameters are not
semantic dependencies.
- Composition — Use
references/composition-checklist.md to trace each action and
synchronization from the application purpose. Check completion events, bindings, isolation,
failure, replay, loops, under-synchronization, and over-synchronization.
- Dependencies and subsets — Check product inclusion dependencies separately from code
restrictions. A product graph need not mirror a code graph.
- Aggregate — Cross-check includes, actions and queries, parameters, outputs, bindings, and
diagrams. Merge findings by root cause and report all five dimensions; an unexecuted check cannot
pass.
Report
# Audit Report <date>
Scope: <requirements/spec/code versions; verified and unverified material> Summary: <coverage,
finding count, severity>
| Proposition or finding | Scenario and evidence | Failed relation or assumption | Impact/severity | Fix route |
| ---------------------- | --------------------- | ----------------------------- | --------------- | --------- |
Coverage: <five dimensions and every concept, entry point, or rule group> Fix order: <merged root
causes, affected locations, current fix, dependencies>
Medium or higher severity needs current specification or code evidence; pure design review is a
specification-level projection. Separate missing OP tests from purpose failure. Without
implementation, do not report implementation violations. Attach a scenario to every under- or
over-synchronization claim.
Route model defects to concept-design, transcription/index errors to concept-prd, and code
violations to concept-implementation. Read references/sources.md when source definitions or
criteria must be verified. Do not write specifications, code, or history.
1---2name: concept-audit-23description:4 Audits concept and application design arguments and optional code conformance only when the user5 explicitly invokes $concept-audit. Read-only; use for purpose fitness, independence, composition,6 drift, and product-subset review.7metadata:8 source: https://skillmd.com/skills/ontology-of-everything/concept-audit-29 language: en10 translation_of: concept-audit-cn11 openclaw:12 homepage: https://github.com/ontology-of-everything/concept-skills/tree/main/skills/en/concept-audit13---1415# Concept Audit1617Focus: can the concept and application designs fulfill their respective purposes, and does the18implementation conform? Run only on explicit `$concept-audit` invocation and remain read-only.19Design can be reviewed without code; without specifications, review only observable code properties.20Mark conclusions unsupported by missing material as unverified.2122## Model2324A **concept** is a behavioral unit designed for one purpose. A concept argument connects its purpose25to its operational principle (OP), state, and actions. An application argument connects the26application purpose to concept selection, synchronizations, and end-to-end scenarios. Conformance to27an unsuitable model does not establish fitness; successful OP tests do not prove the purpose, and28locally sound concepts do not prove the application purpose.2930Review five dimensions:3132- **Fitness:** behavior meets the real need under stated assumptions.33- **Independence:** concept definitions do not depend on other concepts; this repository also34 requires concept modules not to reference one another.35- **Composition:** synchronizations coordinate public actions without expanding or corrupting36 allowed concept behavior.37- **Drift:** implementation differs from a confirmed behavioral contract; distinguish omissions from38 contradictions.39- **Product subsets:** each subset preserves its purpose, entry points, required synchronizations,40 and resources.4142Evidence means a fact supported by inspected requirements, models, code, or tests. Missing evidence43is not evidence of absence.4445## Audit46471. **Scope** — Read `references/spec-format.md`, requirements, concept and synchronization48 specifications, the overall PRD, and staged links. With code, trace real entry points, calls,49 state/schema, migrations, and tests. Record versions, terms, facts, inferences, coverage, and50 gaps.512. **Design arguments** — State concept and application purposes. For every concept, test the52 contract → OP → purpose argument and specificity, completeness, independence, and familiarity.53 Review application selection and synchronizations against end-to-end scenarios. Novelty or54 infrastructure identity alone is not a defect.553. **Drift and independence** — When code exists, use `references/drift-checklist.md` to compare56 signatures, outputs, invariants, state, and dependencies, including public calls, shared mutable57 state, private access, and DTO/protocol leakage. Same-named local type parameters are not58 semantic dependencies.594. **Composition** — Use `references/composition-checklist.md` to trace each action and60 synchronization from the application purpose. Check completion events, bindings, isolation,61 failure, replay, loops, under-synchronization, and over-synchronization.625. **Dependencies and subsets** — Check product inclusion dependencies separately from code63 restrictions. A product graph need not mirror a code graph.646. **Aggregate** — Cross-check includes, actions and queries, parameters, outputs, bindings, and65 diagrams. Merge findings by root cause and report all five dimensions; an unexecuted check cannot66 pass.6768## Report6970```markdown71# Audit Report <date>7273Scope: <requirements/spec/code versions; verified and unverified material> Summary: <coverage,74finding count, severity>7576| Proposition or finding | Scenario and evidence | Failed relation or assumption | Impact/severity | Fix route |77| ---------------------- | --------------------- | ----------------------------- | --------------- | --------- |7879Coverage: <five dimensions and every concept, entry point, or rule group> Fix order: <merged root80causes, affected locations, current fix, dependencies>81```8283Medium or higher severity needs current specification or code evidence; pure design review is a84specification-level projection. Separate missing OP tests from purpose failure. Without85implementation, do not report implementation violations. Attach a scenario to every under- or86over-synchronization claim.8788Route model defects to `concept-design`, transcription/index errors to `concept-prd`, and code89violations to `concept-implementation`. Read `references/sources.md` when source definitions or90criteria must be verified. Do not write specifications, code, or history.