C.27:2 - Forces

1. Cheap recognition versus costly overformalization. The state, rate, and intervention-sensitive distinction must be visible in a minute. Most temporal prose must remain outside C.27.
2. Effort profiles versus derivative words. Real interventions can be impulses, scheduled pushes, feedback policies, adaptive regimes, brakes, pauses, coasting periods, or redirections. The useful question is what input occurs over which window, not whether the prose says acceleration.
3. Resistance without fake physics. Lag, queue pressure, habit, coordination cost, technical debt, service demand, physical inertia, or another domain-local resistance can matter. None becomes a new mass or force kind.
4. Rhythm without a rhythm ontology. C.27 consumes an exact C.27.TA claim. Cross-bearer phase, synchronization, coupling, or entrainment appears only when the receiving use relies on that independently established relation.
5. Readable practice versus hidden claim inflation. Ordinary actor and practice wording should stay readable. Exact System, assignment, authority, Work, causal, benchmark, promise, and assurance details appear only when the current claim relies on them.
6. Preservation versus copied neighboring schemas. Rare uses need exact trigger questions, but C.27 should cite the result of C.16, C.28, G.9, C.26.3, or another direct pattern instead of reproducing its schema.
7. Value neutrality versus acceleration bias. C.27 must allow acceleration, deceleration, braking, redirecting, coasting, pausing, stabilizing, recovering, sustaining, widening, and narrowing without deciding which is valuable.