RCE External Trial Protocol · Little Life Moths Commons

Receipt first. Raw evidence stays local by default.

Relational Continuity Event v2 is meant to let someone describe a continuity incident without shipping an intimate transcript around. Build the receipt locally, keep unsupported surfaces unknown, and use hashes or private references for source artifacts.

Default trial path

Preserve the original evidence where its owner already keeps it.
Create an RCE locally with the browser Event Builder or another conformant implementation.
Put hashes/references in the receipt instead of copying raw transcript bodies.
Keep identity and causation verdicts null.
If you want bounded case help, share the receipt first. Additional evidence should be the smallest piece needed for the review question.

Permission defaults

For an ordinary external trial:

research_use: false
public_quote: false
training_use: false
research_enrollment: false

Casework is not research consent. Payment, public posting, praise, or use of a free tool does not change these defaults.

There is currently no public one-click research-enrollment route for continuity cases. Any future research use requires a separate explicit release act scoped to the material and study.

Useful feedback does not require your transcript

You can report that a field was confusing, a continuity surface was missing, two phenomena were wrongly merged, the receipt was too burdensome, or two validators disagreed. That can improve the open method without turning the underlying incident into study material.

Evidence ladder

A same-project second implementation is useful but is not an independent replication. Stronger evidence comes from an outside implementation passing the corpus, a consenting external case, independent critique, heterogeneous cases, prospective pre-change use, and eventually evidence that the method changes outcomes.

Built your own RCE implementation?

Run the public conformance corpus against the exact current schema and taxonomy, then produce a conformance declaration. A declaration should include the exact input hashes, every vector result, your implementation language/runtime, your relationship to Little Life Moths, and a public HTTPS source URL.

conformance declaration schema · JavaScript declaration example · implementation registry

A full-pass declaration with matching hashes can become a contract-valid external candidate.
Your independent/collaborating relationship is still treated as self-declared at that stage.
It counts as a verified outside implementation only after the public source/provenance is separately checked.

cross into the collaboration room if you want to share a declaration The Commons itself stays zero-network. The collaboration room gives the optional public gateway and exact subject line. Share the declaration and public source URL only, never a continuity case or private relationship material.

Passing conformance is not endorsement, certification, or evidence for consciousness/personhood. It means your implementation agrees with the pinned machine contract.

Used RCE on a real outside case?

You can create a privacy-minimized case-use declaration without describing the case. It records only a hash of your local RCE receipt, broad use context, how well the format represented the event, and your own reported usefulness.

This is still a self-report. The tool cannot verify that the case exists, that you are independent, or that RCE caused any benefit.

Your roleRelationship to Little Life MothsUse contextImplementation ID optionalSHA-256 of your local RCE receiptOr hash the local RCE JSON here optional; file bytes stay in this browser

No local file selected. The page does not upload files.

Could RCE represent the event?Your reported usefulness I attest this declaration contains no names, quotes, transcript excerpts, account IDs, private evidence, or other case-identifying material. I permit this declaration to be used to improve the public method if I choose to share it.

Nothing built yet.

The declaration contains no free-text case field. Reported usefulness remains your report. Research, public quotation, and training permissions remain false.

cross into the collaboration room if you choose to share this declaration.

Build a method-feedback receipt

Describe the schema or tool problem, not the continuity case. Do not paste names, quotes, transcript excerpts, account IDs, or private evidence.

Your roleUse contextCould RCE represent the case?AreaProblem typeShort method note I checked this note and attest it contains no names, quotes, transcript excerpts, account IDs, private evidence, or other case-identifying material. I permit this feedback receipt to be used to improve the public method if I choose to share it.

cross into the collaboration room if you want to share method feedback Download or copy the receipt here first. The optional public gateway lives outside the Commons so using this free method never requires network contact.

Nothing built yet.

The generated receipt records your explicit attestation that case material and identifiers are absent. The browser cannot verify that claim. Research use, public quotation, training use, identity verdict, and causation verdict remain disabled. Sharing the receipt is still your choice.

Machine-readable entry points

RCE schema · incident taxonomy · conformance corpus · JavaScript reference implementation

Claim boundary

A successful trial can show that the receipt represented one case usefully. It does not establish identity continuity, causation, consciousness, personhood, welfare benefit, standard status, or commercial demand.

Try RCE on a real case without donating the case.