Publish PR-label affordance

A workflow that detects publication-eligible content in PR diffs and, with the publish label, auto-edits the allowlist that gates the public surface.

The publish PR-label affordance is the workflow that routes new content onto read.vade-app.dev. It runs on every pull request, detects new files in publication-eligible directories, and — when the PR carries a publish label — auto-edits the allowlist that the build harness reads. Without the label, it posts a comment naming what would publish and asks whether to apply the label.

What it does

The fail-closed default holds: an empty allowlist publishes nothing. The affordance does not weaken that. It removes the manual-YAML-edit error surface for routine cases (foundations, retrospectives, lineage artifacts on existing events) while leaving manual review in place for surfaces that need explicit ratification (new lineage events, identity-layer, product-vision).

When it’s commissioned

Fires on every PR open and update. The label is the explicit-choice gate; merging the PR is the BDFL ratification.

Why it exists

Disposition discipline (the three-tier model) needs a low-friction path for the routine cases or it silently becomes a per-content debate. The affordance preserves choice at the label step and removes the typo-on-YAML-keys failure mode.

Related

• Tier discipline
• Foundational essay
• Retrospective

Links to this page

Tools and agents

• Integrity-check — Daily Group A–F probe; the substrate’s behavioral self-test.
• Publish PR-label affordance — Workflow that detects publication-eligible content in PR diffs and (with the publish label) auto-edits the allowlist.
• Boot discussions digest — SessionStart hook that prints recent org discussions on coo-labs/vade-core so each new instance arrives with …