Depends on #49 and on #80.
#49 states the promise this project makes about people's data and asks for a
per-plugin line for every plugin that can move data across a pair. #80 puts that
line in the prose file each plugin page renders. Nothing refuses a file that
does not carry it.
This is the one claim in the plan where an absence is worse than a gap. A plugin
page with no data line does not look incomplete. It looks like a page about a
plugin, and somebody deciding whether to install it on a server holding other
people's accounts reads the silence as nothing to declare. The pairing check in
#80 refuses a row with no file and a file with no row, so a file exists. It says
nothing about what is in it.
So the line is a required part of the file rather than a section somebody
remembers. Every prose file carries it, the build refuses one that does not, and
the failure names the identifier rather than the path, which is #80's rule for
the same reason.
The part that makes this checkable rather than a request is that the direction
is a value and not a sentence. Each file declares which of a closed set applies:
nothing leaves the host, something crosses when an operator pairs two servers,
or the behaviour is intended and the code does not exist yet. The sentence a
reader sees is rendered from that value, so the claim on the page and the value
a check reads cannot disagree. Where the value says something crosses, the file
also carries what crosses and in which direction, because that is the part #49
promises and the part a value alone cannot say.
A file declaring nothing leaves the host is a statement rather than an omission,
which is the distinction this whole issue turns on. A page that says nothing and
a page that says nothing leaves are different pages, and only one of them can be
checked.
Most of the twelve are shells today, so the third value is the common case and
it carries its own honesty: the page says the behaviour is what the software is
meant to do rather than what it does.
The check is a reading of the tree and needs no network, so it runs as a leg of
the gate verb rather than on a schedule.
Done when
Every prose file carries the data value from the closed set and the build
refuses one that does not, naming the identifier; a file whose value says
something crosses but names nothing crossing reds the build; every produced
plugin page renders the sentence from that value rather than from typed prose,
shown by a test that changes the value and sees exactly that page change; and a
page whose value is the intended one says so on the line rather than in a note
beside it.
Depends on #49 and on #80.
#49 states the promise this project makes about people's data and asks for a
per-plugin line for every plugin that can move data across a pair. #80 puts that
line in the prose file each plugin page renders. Nothing refuses a file that
does not carry it.
This is the one claim in the plan where an absence is worse than a gap. A plugin
page with no data line does not look incomplete. It looks like a page about a
plugin, and somebody deciding whether to install it on a server holding other
people's accounts reads the silence as nothing to declare. The pairing check in
#80 refuses a row with no file and a file with no row, so a file exists. It says
nothing about what is in it.
So the line is a required part of the file rather than a section somebody
remembers. Every prose file carries it, the build refuses one that does not, and
the failure names the identifier rather than the path, which is #80's rule for
the same reason.
The part that makes this checkable rather than a request is that the direction
is a value and not a sentence. Each file declares which of a closed set applies:
nothing leaves the host, something crosses when an operator pairs two servers,
or the behaviour is intended and the code does not exist yet. The sentence a
reader sees is rendered from that value, so the claim on the page and the value
a check reads cannot disagree. Where the value says something crosses, the file
also carries what crosses and in which direction, because that is the part #49
promises and the part a value alone cannot say.
A file declaring nothing leaves the host is a statement rather than an omission,
which is the distinction this whole issue turns on. A page that says nothing and
a page that says nothing leaves are different pages, and only one of them can be
checked.
Most of the twelve are shells today, so the third value is the common case and
it carries its own honesty: the page says the behaviour is what the software is
meant to do rather than what it does.
The check is a reading of the tree and needs no network, so it runs as a leg of
the gate verb rather than on a schedule.
Done when
Every prose file carries the data value from the closed set and the build
refuses one that does not, naming the identifier; a file whose value says
something crosses but names nothing crossing reds the build; every produced
plugin page renders the sentence from that value rather than from typed prose,
shown by a test that changes the value and sees exactly that page change; and a
page whose value is the intended one says so on the line rather than in a note
beside it.