Computation belongs close to context
Systems should remain useful without a required network, account, or provider.
Manifesto / Revision 0.1
We cultivate systems that can account for themselves.
Software becomes infrastructure when people can inspect its boundaries, reproduce its evidence, and continue its stewardship.
Eight commitments
Memory is part of the machine
Past execution can improve recovery and understanding when it remains inspectable and bounded.
Evidence travels with the claim
Benchmarks name hardware, workload, commit, protocol, and limitations.
Refusal is a valid result
Ambiguous inputs and exhausted budgets should produce refusal rather than guesses.
Negative results stay visible
A failed approach can prevent repeated work and must remain in the record.
Performance never outranks correctness
Speedups preserve declared numerical, security, and durability invariants.
Open means governable
Roles, decisions, rights, security, and succession must be legible.
Stewardship should outlive origin
Durable commons require institutions able to survive any one company or person.
What follows
The record is part of the product.
Research ledgers, decision records, release receipts, known-limit registers, and transfer records allow an outsider to determine the state of the work.
A commons is credible when someone outside its founding circle can verify the project and earn authority within it.