Concept Design
Focus: what need must the application satisfy, and which independent concepts and synchronizations
can fulfill it? Run only on explicit $concept-design invocation. Deliver the model, then continue
into PRD or implementation only when already authorized.
Model
A concept is a coherent behavioral unit designed for one purpose; pages, entities, and code
modules are only candidate clues.
- A concept purpose is an evaluable need explaining why one concept exists.
- The application purpose is the outcome a product should create through concept selection and
composition; it is not the sum of concept purposes.
- An operational principle (OP) is a representative, discriminating scenario showing how
behavior fulfills the concept purpose.
- State and actions define allowed behavior through invariants, preconditions, effects, and
result cases.
- A synchronization connects completed concept actions to subsequent calls as an application
rule.
- A misfit is a mismatch between designed behavior and the actual need.
The required argument is: contract supports OP; OP fulfills concept purpose; selected concepts and
synchronizations support application scenarios; scenario outcomes fulfill application purpose.
Composition must preserve each concept's allowed behavior. Facts require sources; label inferences
and unresolved decisions.
Design Loop
- Establish facts — Identify beneficiaries, application purpose, current state, desired
outcome, and constraints. In an existing system, trace actual entry points, state ownership,
failure paths, and tests. Separate current from desired behavior.
- Define candidates — Read
references/spec-format.md. Clarify terms and write the purpose,
OP, minimum state, and complete actions. Test meaning with concrete scenarios; represent external
identity through type parameters.
- Review arguments and seams — Read
references/criteria.md. Test the contract/OP argument and
counterexamples, then specificity, completeness, independence, and familiarity. Record a reasoned
seam decision for every candidate.
- Test composition — Read
references/sync-notation.md. Starting from application purpose and
end-to-end scenarios, select and instantiate concepts; define entry, binding, response,
concurrency, and failure behavior. Check under- and over-synchronization and derive both
synchronization and product-dependency diagrams.
- Revise and deliver — Correct evidenced misfits using the adjustment moves in the criteria.
Preserve unresolved assumptions with evidence and impact; block only the dependent portion.
Output
## Application Purpose and Scenarios
<users, purpose, current state, outcome, constraints; sources/inferences/open decisions> <end-to-end
scenarios: condition → actions and syncs → observable result → purpose; misfits>
## Concepts
<purpose, state, actions, OP, optional queries/notes per references/spec-format.md> Argument: <why
contract supports OP and result fulfills purpose; counterexamples/open points> Seam:
<specificity/completeness/independence/familiarity conclusion and reasons>
## Synchronizations
<app/include/sync grouped by entry point or rule responsibility>
## Synchronization Diagram and Product Subsets
<when → rule → then; where reads marked separately> <A → B means including A requires B; MVP>
## Exclusions and Open Decisions
<candidate/action/assumption, conclusion, source, impact>
Concept sections remain independent of other concept definitions. Put application context in notes
and coordination in synchronizations. Signatures, result cases, and state relations form the
synchronization interface; an OP is representative rather than exhaustive.
Completion requires evidence for both concept and application purposes, parseable
includes/actions/queries/parameters/outputs/bindings, explicit success and refusal behavior where
responses are required, loop and exclusion policies, faithful multi-source/multi-target/query edges,
and an MVP closed over entry points, remaining rules, dependencies, and resources. For a first full
example read references/example-reserving.md; for source definitions read references/sources.md.
1---2name: concept-design-23description:4 Designs Daniel Jackson concepts, purposes, operational principles, state, actions, and5 synchronizations only when the user explicitly invokes $concept-design. Use to turn verified needs6 into an independent concept model and tested application composition.7metadata:8 source: https://skillmd.com/skills/ontology-of-everything/concept-design-29 language: en10 translation_of: concept-design-cn11 openclaw:12 homepage: https://github.com/ontology-of-everything/concept-skills/tree/main/skills/en/concept-design13---1415# Concept Design1617Focus: what need must the application satisfy, and which independent concepts and synchronizations18can fulfill it? Run only on explicit `$concept-design` invocation. Deliver the model, then continue19into PRD or implementation only when already authorized.2021## Model2223A **concept** is a coherent behavioral unit designed for one purpose; pages, entities, and code24modules are only candidate clues.2526- A **concept purpose** is an evaluable need explaining why one concept exists.27- The **application purpose** is the outcome a product should create through concept selection and28 composition; it is not the sum of concept purposes.29- An **operational principle (OP)** is a representative, discriminating scenario showing how30 behavior fulfills the concept purpose.31- **State and actions** define allowed behavior through invariants, preconditions, effects, and32 result cases.33- A **synchronization** connects completed concept actions to subsequent calls as an application34 rule.35- A **misfit** is a mismatch between designed behavior and the actual need.3637The required argument is: contract supports OP; OP fulfills concept purpose; selected concepts and38synchronizations support application scenarios; scenario outcomes fulfill application purpose.39Composition must preserve each concept's allowed behavior. Facts require sources; label inferences40and unresolved decisions.4142## Design Loop43441. **Establish facts** — Identify beneficiaries, application purpose, current state, desired45 outcome, and constraints. In an existing system, trace actual entry points, state ownership,46 failure paths, and tests. Separate current from desired behavior.472. **Define candidates** — Read `references/spec-format.md`. Clarify terms and write the purpose,48 OP, minimum state, and complete actions. Test meaning with concrete scenarios; represent external49 identity through type parameters.503. **Review arguments and seams** — Read `references/criteria.md`. Test the contract/OP argument and51 counterexamples, then specificity, completeness, independence, and familiarity. Record a reasoned52 seam decision for every candidate.534. **Test composition** — Read `references/sync-notation.md`. Starting from application purpose and54 end-to-end scenarios, select and instantiate concepts; define entry, binding, response,55 concurrency, and failure behavior. Check under- and over-synchronization and derive both56 synchronization and product-dependency diagrams.575. **Revise and deliver** — Correct evidenced misfits using the adjustment moves in the criteria.58 Preserve unresolved assumptions with evidence and impact; block only the dependent portion.5960## Output6162```markdown63## Application Purpose and Scenarios6465<users, purpose, current state, outcome, constraints; sources/inferences/open decisions> <end-to-end66scenarios: condition → actions and syncs → observable result → purpose; misfits>6768## Concepts6970<purpose, state, actions, OP, optional queries/notes per references/spec-format.md> Argument: <why71contract supports OP and result fulfills purpose; counterexamples/open points> Seam:72<specificity/completeness/independence/familiarity conclusion and reasons>7374## Synchronizations7576<app/include/sync grouped by entry point or rule responsibility>7778## Synchronization Diagram and Product Subsets7980<when → rule → then; where reads marked separately> <A → B means including A requires B; MVP>8182## Exclusions and Open Decisions8384<candidate/action/assumption, conclusion, source, impact>85```8687Concept sections remain independent of other concept definitions. Put application context in notes88and coordination in synchronizations. Signatures, result cases, and state relations form the89synchronization interface; an OP is representative rather than exhaustive.9091Completion requires evidence for both concept and application purposes, parseable92includes/actions/queries/parameters/outputs/bindings, explicit success and refusal behavior where93responses are required, loop and exclusion policies, faithful multi-source/multi-target/query edges,94and an MVP closed over entry points, remaining rules, dependencies, and resources. For a first full95example read `references/example-reserving.md`; for source definitions read `references/sources.md`.