Skip to content

.harness-known-constraints.md

Latest commit

 

History

History
46 lines (33 loc) · 1.78 KB

.harness-known-constraints.md

File metadata and controls

46 lines (33 loc) · 1.78 KB
Raw

Known harness constraints

This file records the repository visibility and GitHub plan constraints detected when harness init last ran.

Detection

  • Tier: public
  • Detected at: 2026-05-13T21:04:47.214Z
  • Repository: henrik-me/agent-harness

tier is one of public, private-free, private-pro, private-team, private-enterprise, or unknown.

Disposition

A disposition is only needed for private-free repositories because GitHub-side branch protection is unavailable there.

What each disposition means

  • discipline-only — operate without GitHub-side branch protection. Rely on team discipline, the canonical sub-agent briefing preamble's no-commit rule, and the harness's check-clickstop and check-workboard linters. The harness itself used this disposition for its mainline while private-free.
  • upgrade-pro — upgrade the repository owner to GitHub Pro so private repos can use branch protection. Re-run harness init after the upgrade to refresh constraints.tier to private-pro.
  • flip-public-when-ready — defer the decision but plan to make the repo public. After flipping visibility, re-run harness init to refresh the recorded constraints.

How to re-evaluate

When your repo's visibility or plan changes, re-run harness init (it's idempotent) or manually edit constraints in harness.config.json and update this file. See INSTRUCTIONS.md section ## Re-evaluating private-tier disposition for the operational checklist.

Why this file exists

LRN-001 and LRN-002 record that the harness itself discovered the private-free branch-protection limitation during CS01 close-out. This artifact makes that constraint visible during consumer init so downstream projects can choose a clear disposition before the limitation interrupts setup.