User:Mstone/Rainflow

Carrying on the tradition of naming software via puns, I'll lay down some thoughts on how to answer the question:

When should our software automatically do risky thing X?

Background

People in the OLPC community have been concerned with this question (and with variants and related questions) for some time:

<trac>5657</trac>, on spoofing-resistant update algorithms for de-isolated activities

questions on activity signing and update thread

activity semantics conversation

runtime build customization thread and <trac>6432</trac>

user-created activities and updates thread

horizontal distribution thread

homunq's ideas on bundles and updates

Most likely, others have shared analogous concerns in their environments:

citations needed

This proposal offers some new details for adventurous devil-spotters to peruse.

Dumb (Example) Proposal

(a.k.a. the evil bit), no care for canonical formats or strict conformance with draft SPKI grammar:

My position on Terminal-31:

hash("ABCD0123").
name("Terminal").
version("31").
good.

My cert:

...

My position's attestation graph:

hash("9876FEDC").
attests(michael,"{A1235}").