Thursday, January 22, 2015

Proposal: Scalability

Self-killed. Failed by Kevan.

Adminned at 23 Jan 2015 22:59:10 UTC

If the ruleset contains the text:

A Mission is Completed if all of its Team chooses Repair.

A Mission Fails if it is not Completed 72 hours after the time of the Alert’s posting, or if no less than two Team members have not chosen Repair. When a Mission Fails, and every 72 hours after that, the Severity of its System is incremented once.

Change it to:

A Mission is Completed if all of its Team chooses Repair. When a Mission is Completed, the Severity is decremented once..

A Mission Fails if it is not Completed 72 hours after the time of the Alert’s posting, or if at least 50% of the Team rounded down, and at least 1 Team member, has not chosen Repair. When a Mission Fails, and every 72 hours after that, the Severity of its System is incremented once.

Comments

_Fox_:

22-01-2015 03:30:03 UTC

oops

Kevan: he/him

22-01-2015 09:31:22 UTC

Why “oops”?

Kevan: he/him

22-01-2015 23:00:07 UTC

against Not sure that the scaling adds anything, and it still has the fail-immediately-anyway bug. Decrementing on success is a nice thought, but weak in practice - you’d only ever need it for systems that have already failed, and they’re going to keep failing every 72 hours no matter what you do.

A fine first proposal, though.

_Fox_:

23-01-2015 04:42:39 UTC

Yeah. That is a pretty big bug.

_Fox_:

23-01-2015 04:42:53 UTC

against