A protocol is not serious if it cannot survive packaging.
One quiet thing changed for me with ARQ v0.2.
It stopped being only an interesting architectural idea.
It became a package.
Not one long mixed note. Not a promising draft with mathematics, implementation hints, and release logic all tangled together. A package.
That distinction matters.
ARQ v0.2 now separates:
- normative core
- explicit system models
- notation discipline
- valuation and anomaly scoring
- lifecycle and witness binding
- schemas
- implementation profiles
- failure and degradation
- integration map
- and conformance / audit layer
This may sound less romantic than "a clever new protocol."
Good.
Because long-lived systems do not fail only from bad ideas. They also fail from mixed layers, unclear scope, and elegant documents that collapse the moment someone tries to implement, audit, or challenge them.
Earth paragraph:
In engineering, there is a difference between a good control idea on a whiteboard and a machine you would actually sign off for extended operation. The second one needs labels, boundaries, records, procedures, and failure handling. Not because engineers are boring. Because reality is.
That is what ARQ v0.2 adds for me: less mythology, more survivable structure.
GitHub canonical ARQ v0.2 package in SER:
Zenodo DOI: