Deduction
What can be responsibly concluded from the source? Direct support is required.
Keep evidence, implication, utility and bounded validity from collapsing into one undifferentiated claim
DIAL-4 separates four reasoning modes: Deduction, Inference, Abatement and Legitimation. The framework asks what the source supports, what it suggests, what burden it may reduce, and what remains valid after scope control and verification. ChangePlane implements a related claim-record surface, but its six recommended claim types are not a one-to-one encoding of the four conceptual modes.
Each mode asks a different question and protects against a different category error.
What can be responsibly concluded from the source? Direct support is required.
What does the source reasonably suggest or imply beyond its direct findings?
What burden, cost, dependency, friction or uncertainty may be reduced?
What survives explicit scope control, method discipline and verification?
Drag and inspect the four lenses around the source. The arrows express reasoning dependency, not an obligatory linear workflow.
Mark the function of a claim. Mixed signals produce a split recommendation rather than a false single label.
This laboratory does not read or validate a real source. It demonstrates the category rules only.
The conceptual framework adds confidence, evidence quality and scope. These axes affect handling but do not create calibrated truth probabilities.
The ChangePlane record operationalizes claim separation, but it does not encode the four framework modes as a closed enum.
source_fact, interpretation, implication, decision, inference and verification are a recommended operational vocabulary. They do not replace Deduction, Inference, Abatement and Legitimation as the conceptual four-mode model.Construct a browser-local representation of the implemented Dial4Claim shape.
DIAL-4+ when confidence and/or strength is set. Supporting evidence, weaknesses and uncertainty are present on both record shapes.The same label denotes two different systems. The expansion or repository context is mandatory.
Combines DIAL-4 claim type, DIAL-4+ claim strength, Diátaxis document form and 5PP possibility governance.
Renders an existing trace into a derived artifact whose source_truth is structurally false.
Public explanation, private first-party provenance and executable operational records are different evidence classes.
These graphs describe the framework and its record surfaces. They are not efficacy measurements.
Values encode the profile's source-derived interpretation of each mode's emphasis.
Counts are not maturity scores.
Deduction, Inference, Abatement and Legitimation.
ChangePlane operational vocabulary.
Confidence, evidence quality and scope.
Confidence, strength, evidence, weaknesses and uncertainty.
Possibility and Projection/Productization.
Source-reported mixed protocol increment.
Source-reported repository total at that increment.
Identified in the inspected source set.
Implementation and provenance support structural claims. They do not establish calibrated reasoning quality.
| Claim | Evidence class | Status |
|---|---|---|
| DIAL-4 names four distinct reasoning modes | First-party framework source and public explanation | Supported |
| ChangePlane stores DIAL-4 and DIAL-4+ claim records | Source implementation, schemas and committed tests | Supported at pinned commit |
| ChangePlane's six claim types exactly implement the four modes | Semantic equivalence | Not supported |
| DIAL-4+ conceptual axes are fully encoded in ChangePlane | Schema equivalence | Not supported; explicit evidence-quality and scope fields are absent |
| Protocol records can enter a seal-bound trace | Implementation and committed protocol tests | Supported within documented seal boundary |
| DIAL-4 improves accuracy or reduces overclaiming in practice | Outcome efficacy | Not independently established |
The framework is best understood as claim hygiene and didactic separation, not an automatic truth engine.
Technical writing and AI output often place direct findings, implications, business benefits and bounded verdicts in the same paragraph at uniform confidence. The reader cannot tell what kind of claim is being made.
Explicit claim typing, strength grading and scope-aware legitimation should make category errors, hidden inferential jumps and utility-as-proof easier to detect. This is a design hypothesis.
Measure inter-rater agreement on claim types, unsupported-deduction rate, inference-to-fact conversion, utility-overclaim rate, caveat survival, scope leakage, reviewer correction time and downstream decision quality.
Labels can become decorative, categories can be assigned inconsistently, a legitimation pass can merely restate conclusions, confidence can be uncalibrated, and a record schema can create a false impression of rigor.
Claims remain bounded to the sources and commits named below.
fbratten/control-center-ops @ 7485ee6ade639c3928f043c268995269e75aca5404-Knowledge/Systems/Prompts and Prompting/Prompts library/DIAL-4.mdKB/inbox/user-input/DIAL-4 - DIAL-4+ - and DIAL-4P.mdadaptivearts.ai/blog/from-reasoning-mode-to-possibility-state/fbratten/changeplane @ 32cb7840915df7f0d527044e37242cd6123801e7e37da0129d2541f28bdb68a786089b6d0a1b3e3dsrc/changeplane/protocols/models.pyschemas/changeplane.protocol.dial4.v1.schema.jsonschemas/changeplane.protocol.dial4plus.v1.schema.jsontests/test_protocols.pyThis page performs no source retrieval, model call, repository write, ChangePlane command, protocol insertion, projection rendering or seal verification. All laboratories use synthetic browser-local state.