CSC – Glossary & Vocabulary Rules¶
A governance document defining stable terminology and linguistic constraints for the Cognitive Signal Chain (CSC)
1. Purpose¶
This document defines the controlled vocabulary used across CSC documentation.
Its purpose is to:
- prevent semantic drift over time
- avoid overloaded or ambiguous terms
- ensure consistency across pedals and governance docs
This is a linguistic constraint document, not a glossary for teaching others.
2. Core Principle¶
Language shapes cognition; unstable language destabilizes systems.
CSC therefore treats vocabulary as a first-class design concern.
3. Canonical Terms¶
The following terms have specific, fixed meanings within CSC and must not be redefined implicitly.
Cognitive Signal Chain (CSC)¶
A personal system of ordered cognitive subsystems (“pedals”) that enforce distinct thinking modes when designing systems.
Pedal¶
A CSC subsystem that:
- enforces exactly one cognitive mode
- has explicit inclusion and exclusion rules
- produces inspectable artifacts
Cognitive Mode¶
A constrained thinking posture that determines what kinds of mental operations are allowed or disallowed.
Examples:
- exploratory
- structural
- adversarial
- translational
Artifact¶
An explicit, inspectable output produced by a pedal.
Artifacts are the only mechanism by which context travels between pedals.
Bypass¶
The intentional skipping of a pedal for a given pass, with acknowledged risk.
Re-entry¶
Returning to an earlier pedal after downstream work reveals a flaw.
Drift¶
Gradual erosion of constraints, roles, or boundaries that reduces CSC effectiveness.
4. Reserved Terms (Use with Care)¶
The following terms may be used, but require precision:
- System: an intentional construct optimized for specific decisions
- Constraint: a non-negotiable rule that creates power
- Failure: an observable breakdown CSC exists to prevent
- Misuse: predictable degradation when a system is applied incorrectly
These terms must be grounded in concrete examples when used.
5. Forbidden or Discouraged Terms¶
The following terms are discouraged or forbidden due to vagueness or overload:
- alignment
- clarity (without specification)
- best practice
- framework (unless explicitly defined)
- maturity
- culture (without operational meaning)
Use of these terms requires explicit definition or replacement.
6. Naming Rules¶
When introducing new concepts or pedals:
- Names must describe function, not aspiration
- Avoid metaphor-only names without explanation
- Avoid branded or motivational language
If a name cannot survive literal interpretation, it is suspect.
7. Pedal Naming Convention¶
Pedal names should:
- end with “GPT”
- reflect the primary object of control
- avoid overlap with other pedals
Examples:
- Sensemaking GPT
- Assumption Excavator GPT
- Red Team / Misuse GPT
8. Documentation Language Rules¶
Across CSC documents:
- Prefer declarative statements over persuasive language
- Avoid promises of outcomes
- State assumptions explicitly
- Name tradeoffs and risks
Tone should remain neutral, precise, and non-performative.
9. Drift Detection via Language¶
Language drift signals system drift when:
- terms are used interchangeably without justification
- new euphemisms replace existing terms
- metaphors begin to replace definitions
Such changes should trigger a Consistency & Drift Audit.
10. Relationship to CSC¶
This document:
- stabilizes meaning across the CSC repository
- reduces cognitive load when navigating docs
- prevents slow semantic erosion
CSC relies on disciplined language to remain coherent and inspectable.
End of CSC Glossary & Vocabulary Rules.