# Governance

## Status

This repository is an initialized public scaffold governed by the proposed [NIN Knowledge Commons Doctrine](DOCTRINE.md) and [Operational Playbook](PLAYBOOK.md). Its existence does not establish an operating Commons service, reviewer council, institutional authority, marketplace, hosted RAG system, certification, accreditation, clinical validation, or permission to process PHI.

## Precedence

The following control in descending order when applicable:

1. law, professional duties, and binding institutional policy;
2. the current NIN–NAIO Master Directive and EDENA requirements;
3. artifact-specific licenses, rights, and authorization records;
4. the [Doctrine](DOCTRINE.md);
5. the [Operational Playbook](PLAYBOOK.md);
6. namespace, review, and publication records created under those authorities.

When authorities conflict, the more protective applicable boundary controls until a named human authority resolves the conflict.

## Decision model

> **Contributors propose. Reviewers verify. Institutions authorize. Nurses steward.**

AI may draft, classify provisionally, compare, test mechanically, and surface conflicts. It may not approve itself, promote publication state, grant authority, activate a pack, or authorize consequential use.

## Current public ceiling

- D0 only;
- Green and bounded Yellow only;
- Observe and Draft, with Recommend only where bounded Yellow controls are present;
- adults only for any future initial contribution process;
- no PHI, confidential institutional content, patient-specific tools, competency determinations, or autonomous actions.

Orange content is held. Red-P is prohibited. Red-E is outside ordinary Commons publication.

## Change control

Material changes to authority, risk scope, data classes, action modes, creator ownership, minor participation, payment, surveillance, institutional use, Orange publication, or conformance claims require explicit founder judgment and the applicable review process.

Every accepted implementation change must identify exact bytes, tests, unresolved findings, licensing effects, deployment state, and rollback or incident implications.
