Programming
Experiments
Small programs constructed from theoretical distinctions. Each experiment asks what must become observable when a claim is translated into states, transformations, constraints, interventions, and trajectories.
An experiment asks where it stops working.
Aspect Relegation
When can an explicitly controlled operation disappear into automatic execution, and what forces it back into explicit control?
Admissible Degradation
How much damage can a system absorb while preserving the conditions required for legitimate continuation?
Continuation
What can reachable trajectories tell us that inspection of the present state cannot?
Repair and Difference
Can a repair restore immediate function while destroying distinctions required for future behavior?
Refusal
What changes when refusal is represented as an explicit state transition rather than as missing output?
Replay
What information must an event history preserve for reconstruction to remain semantically adequate?
Defeat
How does policy-relative defeat differ computationally from the structural existence of an attack?
No Scalar
Which distinctions disappear when multidimensional standing is compressed into a single score?
Projection
What properties survive when a richer object is exposed through a restricted interface?
Unfinishedness
Can deliberately retained attachment points increase future reachability compared with completed structures?
Smoothness
When does smooth observable behavior conceal discontinuity or divergence in the process producing it?
MEM|8
What becomes observable when transformation is decomposed into explicit POP, REFUSE, BIND, TRANSFORM, VERIFY, and COLLAPSE operations?
Each program should identify its theoretical claim, operational interpretation, manipulated variables, observable state, expected relationship, competing interpretation, and embarrassment condition. An interactive result is evidence about the implementation before it is evidence about the theory.