The Harness

Actions

Reaches GitHub

publish the branch

Ever had a branch pushed straight to main by mistake?

Pushing local commits up to GitHub, where the rest of the mechanism can finally see them.

Performed by: Developer

create a task issue

Ever opened a ticket that turned out to have zero plan behind it?

Opening the Issue that a task exists as — its scope, its reasoning and its dependencies, written down before anyone starts.

Performed by: Planner

open a pull request

Ever gotten a PR with no explanation of what it does or why?

Proposing finished work for review, carrying the account of what changed and which intent it came from.

Performed by: Developer

revise a pull request

Ever seen a PR quietly gutted after it already passed review?

Editing a pull request after it exists — its code, its title or its description, whether or not review already happened.

Performed by: Developer, Planner

grant a waiver

Ever had someone bypass a rule just by typing the right words?

Deliberately excusing a rule for one case — an authority the mechanism grants to a person, never to an agent.

Performed by: Principal

Stays local

commit the work

Ever had a commit land that plain doesn't build?

Recording a change locally — the last moment it costs nothing to catch a mistake.

Performed by: Developer

author the brief

Ever started a task with no clear idea of what "done" means?

Dispatching one intent as instructions someone can execute: what to build, what is out of scope, and what done means.

Performed by: Planner

produce the verdict

Ever gotten a review that was really just a rubber stamp?

Judging finished work against the brief it came from, and saying plainly whether it passes.

Performed by: Reviewer, Security Reviewer

post the provenance comment

Ever needed to know exactly what shipped, and why, six months later?

Writing the permanent record of a merged task — what shipped, from what intent, checked by whom.

Performed by: Archivist

write the retrospective

Ever finished a big chunk of work with nobody writing down what was learned?

Closing out a finished phase of work by recording what actually happened and what it taught.

Performed by: Tranche Archivist

create the milestone

Ever had a Milestone whose title quietly became the only place a version lived?

Declaring a product goal as a Milestone — free-text title, prose goal, an optional Release: field as the version's sole authority, and an optional list of which tranches serve it.

Performed by: Architect