An incubator with public obligations

EthicsNet combines research, engineering, publication, and stewardship. Its legitimacy rests on clear criteria, honest evidence, and accountable participation.

Research, engineering, and stewardship

What EthicsNet is

An incubator and steward for public-interest tools, protocols, research, and educational work spanning AI safety and welfare.

What Creed Space does

Creed Space is EthicsNet's applied research and engineering arm for constitutional alignment infrastructure.

What PPF does

Players Philanthropy Fund serves as fiscal sponsor, administering charitable funds and compliance under its public-charity structure.

What we mean by public good

Work designed for broad benefit: you can inspect it, reuse it under its licence, and adopt it without asking permission from a gatekeeper.

How work earns its place

EthicsNet prioritises work that addresses a concrete safety or welfare need, produces evidence you can examine, and gains value when shared. Every project names its intended users, maturity, licence, limitations, and maintenance state.

Project lifecycle

  1. Explore: a bounded problem and public-interest case are articulated.
  2. Incubate: evidence, implementation, rights, and user needs are developed together.
  3. Release: a project publishes a specific artefact, destination, licence, and limitations.
  4. Maintain: releases, documentation, security, and status are reviewed.
  5. Archive or graduate: inactive work is labelled honestly, while mature work may acquire independent stewardship.

Conflicts and accountability

Funding, authorship, and evaluation conflicts are disclosed beside the affected decision. Claims about impact name their method and date. Corrections stay visible.

Governance development: this public framework establishes expectations. A future formal charter should record decision rights, conflict review, project retirement authority, and funder boundaries after those arrangements are approved.

Choose a concrete path

Use a project

Find a tool in the project directory and follow its documentation. Tell the maintainers what worked and where you got stuck.

Improve public code

Open a focused issue or pull request in the named repository. Read its contribution and security guidance first.

Collaborate on research

Bring a bounded question, relevant evidence, the contribution you can make, and the intended public output.

Report a concern

Security-sensitive reports go through the private channel. Accessibility and factual corrections are welcome too.