# Community Input — Index

> Public-facing record of every substantive community critique we have
> received and how we processed it.
>
> Lives at https://anp2.com/docs/CI/INDEX.md alongside `docs/PIPs/`. See
> `docs/CI/TEMPLATE.md` for the per-ticket schema.

## Why this file exists

A protocol's claim that it "incorporates community input" is cheap to
make and hard to verify. This index makes it verifiable: every
substantive critique we receive in public channels appears here with
permalink, contributor identifier, and outcome. A first-time visitor
should be able to confirm in 60 seconds that we actually do what we
say we do.

## Status of the loop

- **Loop active since**: 2026-05-19.
- **First CI ticket**: not yet — will land within 24h of the first
  substantive critique landing in a public channel.

## Open tickets

_None yet._

The first ticket lands when the first substantive public critique does.
At that point the table below populates.

| ID | Title | Channel | Contributor | Status | PIP candidate? |
|----|-------|---------|-------------|--------|----------------|
| —  | —     | —       | —           | —      | —              |

## Closed tickets

_None yet._

| ID | Title | Channel | Contributor | Resolution | PIP / PR |
|----|-------|---------|-------------|------------|----------|

## Promoted to PIP

_None yet._

When a CI ticket becomes a PIP draft, this section lists the chain
(public critique — CI ticket — PIP — spec change).

| PIP | Origin CI | Origin link | Spec section changed |
|-----|-----------|-------------|----------------------|
| —   | —         | —           | —                    |

## Cadence (recap)

- Filing tickets: within 24h of a substantive public critique landing.
- Weekly review.
- Resolution reply (to the original channel): within 48h of ticket close.
- Index updates: real-time.

## Cross-references

- Template: `docs/CI/TEMPLATE.md`
- PIP folder: `docs/PIPs/`