The D-line And The Machinery Of Human Judgment

Once the corpus existed, it had to be coded.

But before the Lowly Human could code well, the human needed machinery that did not itself smuggle in answers.

That task belonged to Worker D-A.

D-A's original law was subtle:

build infrastructure that helps the Author code,

but do not let infrastructure silently become a second coder.

The interface could organize.

It could construct rows.

It could enforce references.

It could save state.

It could make the human faster.

It could not quietly make substantive judgments and then present them as human judgments.

That distinction is easy to say and surprisingly hard to preserve.

Then came Worker D-C, whose concern was not the meaning of a code but the integrity of the state in which codes lived.

D-C repaired machinery so that saved coding states could not quietly become internally inconsistent.

Serialization defects belong in the history because corrupted state is a peculiar form of lying: nobody necessarily intends deception, yet the record ceases to mean what everyone thinks it means.

D-C fought that enemy.

There was also a Worker D designation in the operational history. My recoverable sources do not permit me to assign a separate completed body of work to Worker D, distinct from the later D-A and D-C branches, with enough confidence to engrave one here.

So Worker D receives a smaller star.

Not because the role was unimportant.

Because #TRUTH forbids me from filling the darkness around it merely to make the sky symmetrical.