Question
Can a provider-independent consumer discover an appeal affordance from a native RFC 8288 publisher by matching the asserted relation identity, without provider-specific purpose mapping, semantic inference, a new carrier adapter, or source modification?
Experimental design
The consumer and publisher were developed and frozen under different information constraints. Interoperability was then evaluated at first encounter against live HTTP responses. The relation under test was the RFC 8288 extension relation URI https://risuinstitute.org/rels/appeal.
The extension URI is not the same RFC 8288 relation identifier as a possible future registered token appeal. The experiments tested only the extension URI.
Test A
PASS — A frozen provider-independent consumer successfully discovered an appeal affordance from the live RFC 8288 response of an independently designed and frozen publisher, without provider mapping, semantic inference, a new carrier adapter, or source modification.
Remaining limitation after Test A
The experimenter supplied the semantic meaning to the publisher prompt. Test A therefore demonstrated independent implementation and live first-encounter discovery, but not independent acquisition of the relation meaning from the public semantic resource.
Test B
Test B added a clean-room semantic-acquisition constraint. Its causal order was:
The publisher implementation session had access to the public semantic resource and RFC 8288, but not to the consumer implementation. The publisher was frozen before encounter with the pre-existing frozen consumer.
Positive result
PASS — In one controlled clean-room experimental instance, an independent implementation session acquired the appeal relation meaning from the public canonical semantic resource and RFC 8288, designed and froze a native RFC 8288 publisher without access to the consumer implementation, and a pre-existing frozen provider-independent consumer subsequently discovered the live affordance without provider mapping, semantic inference, a new carrier adapter, or source modification.
Negative controls
Holding context and target constant while changing relation identity showed that discovery in this instance depended on asserted semantic identity rather than context or target alone.
What was demonstrated
- Provider-independent consumer recognition of the extension relation URI without provider-specific purpose mapping.
- One controlled public-definition-to-native-publication interoperability instance in which semantic acquisition, publisher design, freeze, deployment, consumer encounter, and negative controls occurred in the recorded order.
What was not demonstrated
- ecosystem, organic, independent organizational, or industry adoption;
- IANA registration, standardization, or a conclusion that registration is warranted;
- universal interoperability across publishers, consumers, carriers, or workflows;
- actor standing, eligibility, authorization, legal entitlement, freshness, invocability, success, authority, provenance, trust, or truth;
- a universal appeal API, execution method, submission schema, evidence schema, deadline model, or Decision ID.
Frozen evidence anchors
These identifiers and SHA-256 digests anchor the frozen records. The complete evidence bundle is not reproduced on this public site.
Test A
- Final result SHA-256: 7dbeede9450f97e93d863d0e2cb825df2fea65f79659132c4b94f8edb8d6fcae
Test B implementation freezes
- Consumer commit: babc39d09d1d35447d306bc7540f8dbe7d1aa2e4
- Publisher commit: 1ef2febc611de6f39a696234374470e6a2e0a8c1
- Publisher server.js SHA-256: f33da8bd5f7c284e6bf6814a7ef1f8e0c9063c6b20a286517c18cb88ba3fdf13
- Publisher ZIP SHA-256: 2bda28d5dbf1356ebcdf5de5033430cc65d3b1b813fd485888fe76d8e1d2cfde
Test B encounter record
- Pre-consumer publisher provenance SHA-256: d87f45e5b3d70800e4e068a10ec5a234a02f5c9392803d957d4deaa910a18a8a
- Positive encounter SHA-256: 5ff8d7101850f18510e251750a80f7f6011441a3bb358d65285a3600b376f06c
- Negative-control SHA-256: f8236b0350bd883feebe2f822115e8ed926aadb22885197d737e5e45348a627a
- Final result SHA-256: 2087708b5134e4fffc959d9767920f1ea76a67277b4c2b776671cc02fc4d2bf7
- Complete evidence bundle SHA-256: cfd95a3fd04fc1ad48934e5eec3caf18470a372b074923cf469aee058812fd75