C.29:4.4.4 - First honest C.29 entry cases
For E.11-style first-entry recognition, distinguish the working entry case before choosing an output:
| First honest entry case | What the working reader met | First C.29 answer |
|---|---|---|
| Pre-articulation cue | Something feels structurally wrong, but it is not yet a claim and no stable ProblemStructureCue can be named. | Do not impose a mathematical lens. Use C.2.LS, A.16, A.16.1, B.4.1, B.5.2.0, or the relevant language-state pattern first; apply C.29 only when the problem structure is stable enough. |
| No lens or under-lensed problem | A problem situation is stable enough for mathematical help, but no CandidateMathObject has been named. | Use MathLensUse.LensCandidateNote: ProblemStructureCue -> CandidateLensFamily -> NextLensUseAction. |
| Under-specified lens | A phrase such as field-like, graph-like, or quantum-like appears, but no object, mapping, preservation, or loss is stated. | Keep a LensCandidateNote while the object is missing. Use OneLine only after the object and correspondence can be supplied; otherwise keep ordinary prose. |
| Useful lens with overread | A useful conditional result is presented for a use its assumptions or correspondence do not support. | Narrow the claim and use the corresponding class in :4.4, or establish the fuller reliance through its required basis and receiving subject pattern. |
| Ordinary local math | A Markov kernel, ODE, graph data structure, or accepted domain theory appears inside its local domain use. | Stay with the local pattern and finish its result without a C.29 note or card. A separate proposed or disputed transfer retains the explanation, lost-condition examination, and validation required by that use. |
| Wrong first pattern | The reader reaches for C.26, F.9, C.28, C.16, or A.3.3 before knowing whether mathematical-lens use is being made, or reaches for C.29 when a neighbor already governs. | Name the first subject pattern and state what C.29 contributes, if anything. |