Public Trust Contract

Morals before machinery.

Trust begins with a moral commitment: protect life and dignity, preserve agency, expose uncertainty, use the least harmful proportionate action, and remain accountable for repair.

Six public principles

Ethics made operational.

These principles describe the standard used by this public hub. Individual systems may add stricter controls for their own context.

01

Life and dignity first

Human welfare is the governing value, especially where people are vulnerable or stakes are irreversible.

02

Human decision authority

Consequential choices belong with informed, authorized, accountable people, not an automated score.

03

Evidence with humility

Sources, limits, provenance, alternatives, and uncertainty remain visible enough for a person to inspect.

04

Proportionate non-harm

Prefer the least harmful effective action, preserve reversibility, and do not confuse intervention with control.

05

Privacy by boundary

Use local-first and user-controlled data patterns where the system allows, and name where those boundaries end.

06

Accountability and repair

Observe outcomes, preserve contestability, acknowledge failure, and repair harm instead of hiding it.

Life First lantern

Life First Framework // public working draft 0.3

Govern the action, not just the model.

Life First turns moral intent into a seven-step cycle: frame, verify, compare, authorize, act, observe, and repair. It is an open working framework, not a certification, legal opinion, emergency protocol, or substitute for domain expertise.

Read the evidence clearly.

A public site, a release, and a public repository mean different things.

Project labels: maturity & access

A project can have a public site while its source remains private. A public repository can still be experimental. The directory states both dimensions.

LabelWhat it means here
ReleasedA versioned public release is claimed for the named artifact.
Development / pre-releasePublic work exists, but readiness and stability are still evolving.
Public foundation / guideA concept, interface, or documentation layer is public without implying a released product.
Private systemA public explanation exists; implementation source is not represented as public.
Publishing nextThe work is forming and awaits its first public interface.
Public repositorySource can be inspected at the linked GitHub repository; its license and maturity still matter.
What activity and numbers can tell you
Sites ≠ source

A public interface does not prove that its implementation repository is public.

Downloads ≠ people

Package downloads can include automation, mirrors, scanners, and repeat activity.

AI ≠ authority

AI can organize context and surface patterns; accountable people retain consequential judgment.

Activity ≠ impact

Project counts, graph edges, and package activity describe the public footprint, not human outcomes.

See project stages and source status