Premise 2: Content is small. A 500-word blog post renders fine in Markdown. A 3,000-word agent-generated implementation plan with architecture decisions, trade-off tables, and code samples does not. Past about 100 lines, Markdown becomes a wall of text. No navigation, no collapsible sections, no way to jump to the part you care about. Thariq’s observation is blunt: “Nobody really reads a Markdown file longer than 100 lines.”

for best results pipe rg --json output to delta: this avoids parsing ambiguities that are inevitable with the output of git grep and grep

diff-so-fancy strives to make your diffs human readable instead of machine readable

landing: content intended mostly for human consumption, such as an object description and links to primary information (e.g., an image file or a spreadsheet), to alternate versions and formats, and to related information; from “landing page”, this is intended to support a browsing experience of an abstract overall view of the object.

I would say it's text when interpreted as text/plain it's human readable. Otherwise it's binary. That is, binary = for machines only.

I couldn't find a definition of text except that text means absence of binary data. This is weak - so I would follow your definition - A text file is a file which can be read by a human.

Try to make the Dockerfile easy to understand/read.

The additional content is only relevant for human readability. The machine, on the other hand, ignores this addition. Thus it is possible to express the rules in a grammatically correct way on the one hand and to give them a semantic context on the other.

Rules formulated with openVALIDATION are thus at the same time a formal, machine-processable specification, but also a documentation that is easy for people to understand.

The rules recorded in natural language are readable not only by humans but also by the computer and therefore no longer need to be programmed by a software developer. This task is now taken over by openVALIDATION.

substitute /one space or more/ for /newline/ globally

Read the code! No, really. I wrote this code to be read.

‘Programs are meant to be read by humans and only incidentally for computers to execute.’

Some of the verbs implemented by systemctl are designed to provide a high-level overview in a human readable format. All that information is available over dbus, and/or journalctl, systemctl show. We could provide that information in json format, but there's a second problem. Information and format of information printed by e.g. systemctl status is not stable. Since the output is not suitable for programmatic consumption anyway, there's no need to provide it in a machine readable format.

RDFa is intended to solve the problem of marking up machine-readable data in HTML documents. RDFa provides a set of HTML attributes to augment visual data with machine-readable hints. Using RDFa, authors may turn their existing human-visible text and links into machine-readable data without repeating content.

It does, however, provide the --porcelain option, which causes the output of git status --porcelain to be formatted in an easy-to-parse format for scripts, and will remain stable across Git versions and regardless of user configuration.

Parsing the output of git status is a bad idea because the output is intended to be human readable, not machine-readable. There's no guarantee that the output will remain the same in future versions of Git or in differently configured environments.