Dead Star Labs

How we build

Five rules, and the shipped behaviour that keeps them.

Principles are cheap. Each one below names the product behaviour that substantiates it; if a rule ever loses its last piece of evidence, it should be deleted rather than left standing as decoration.

  1. Private by default

    Software should not require surrendering unnecessary information. The default is the least data that still makes the thing work.

    Evidence

    • The Dark Index catalogues on your device, with no account and no usage analytics
    • Same Ground browse resources and reach a crisis line with no legal name, documents, or location

  2. Useful without a signal

    Core functionality should survive bad connectivity whenever the problem allows it. Connectivity is a convenience, not a precondition.

    Evidence

    • SteadSense the emergency packet and the homestead record stay readable with no connection at all
    • The Fish-Assist plans generate offline from cached data
    • The Dark Index collection access works offline

  3. Explain the answer

    When software makes a recommendation, you should be able to see the rule that produced it and where that rule came from, before you act on it.

    Evidence

    • The Fish-Assist every recommendation shows the rule behind it and that rule's source
    • SteadSense task rankings carry reason codes, and guidance carries its provenance

  4. Don't invent certainty

    If the system does not know something, saying so is a feature. A confident wrong answer is worse than no answer, and in some domains it is dangerous.

    Evidence

    • SteadSense declines canning parameters, doses, wild-food identification, and water safety rather than guessing
    • The Fish-Assist says when it does not know a waterbody instead of inventing one

  5. Your data stays useful

    Exports belong in ordinary formats, and nobody should be trapped inside an application. Leaving should be as supported as arriving.

    Evidence

    • The Dark Index the whole catalogue exports to CSV or JSON, in the free core rather than behind a tier

These rules are enforced, not admired.

The same instinct runs through the site you are reading: colorways are machine-tuned until they provably clear WCAG AA, a button cannot exist without a destination, and the deploy fails if a page starts making a request it promised not to make.

How decisions get made