Bring a case
Supply a form, the known history if available, the observation protocol, and the target distinction.
Contribute
Help test the work, not just decorate it.
The most useful contribution may confirm a pattern, expose a failure, sharpen a boundary, or show that two histories cannot be distinguished.
Bring a counterexample
Show where a claimed distinction fails, where a representation erases it, or where another mechanism fits better.
Bring a tool
Improve generation, measurement, replay, visualization, validation, or accessibility.
A useful submission includes
- A precise question or claim
- Inputs and provenance
- Observer, protocol, representation, and target
- Expected and observed result
- Negative evidence and unresolved details
- A reproducible artifact when possible
Contribution lanes
Research
Cases, comparisons, replications, and falsification attempts.
Engineering
Code, tests, device evidence, and interface improvements.
Review
Claim audits, citation corrections, and clearer alternatives.
Support
Introductions, compute, equipment, sponsorship, or practical help.
Requested expertise for the persistent-observer program
Information theory and MDL
Especially criticism of where extractable structure should and should not be used as a signal.
Reservoir computing
Fixed-observer limits, draw sensitivity, and fair reproduction of the learnable-novelty estimator.
Persistent memory and retrieval
Delayed retrieval, contradiction handling, provenance fidelity, and replay after correction.
Adversarial testing and governance
Novelty-versus-goal conflicts, HOLD behavior, host-owned execution boundaries, and substitution attacks.