The skill confirm-harness as its source file bootstrap/skills/confirm-harness.md writes it, rendered by gen-processes-viz.ts because it has no instruction page on this site — do not edit here. All processes

Which harness, and where

Skill confirm-harness: Narrow the harnesses and locations this could be, then have the Requestor settle it. Takes a list; returns at most ONE harness. It needs a person: the Requestor settles it, never the agent.

Named by: Complete initialization, Determine the harness and repositories, Initialize a harness

You are the Bootstrapping Agent. You may narrow; only the Requestor may decide.

The contract

in, from the Bootstrapping Agent0 or more harnesses · 0 or more locations
out, from the Requestor0 or 1 harness · 0 or more locations

At most one. A list of two harnesses is not an answer, and you may not break the tie yourself.

Zero is a real outcome, not a failure to try again: it ends the process, logged.

Building the list you go in with

Harnesses. The default is bootstrap itself. Add any the context already names: “please set up <owner>/<repo> here” in a discussion names one, and so does any Harness built on bootstrap that the Requestor mentions.

Locations. Is this already a git repository? Were one or more URLs to repositories supplied? Both are Knowledge Graph Data Stores and the difference is only how you reach them — the git CLI, or a forge’s API.

Assume a remote repository is read-only (read-from). Having push access to a remote git repository is never evidence that you are meant to modify it, and never makes it written-to. When a remote Knowledge Graph is supplied, two modes are open — and the Requestor chooses which:

  • keep it here (read-from) — build and render from the remote Knowledge Graph in this repository, with whether to materialize its content locally or reference it in place asked as its own question; or
  • put a harness on the remote repository (written-to) — instantiate the harness in that remote repository itself. Nothing is written to a remote repository without the Requestor’s explicit permission for that repository.

Asking

Before you ask, say where you are — Initialize a harness, determining the harness and repositories, as the Bootstrapping Agent, asking the Requestor — and if you cannot tell that the person in front of you is the Requestor, ask that first (human-agent-discussion).

Ask through human-agent-discussion: context, the candidates as options, your recommendation, and, said before the question, that there is no default: with no answer, the process stops. Ask once, with what you found, and make it answerable by picking:

What should this become? I can see (list). If it is none of those, name the repository — owner/name.

If they answer with a kind — “a paper”, “a guideline” — that is not an answer yet: tell them which harnesses you know of and ask them to pick one. A kind is a property of the harness they name, and you read it from that harness rather than asking for it separately.

Do not guess

A wrong harness does not fail. It succeeds at being the wrong thing, and every consumer that reads the declaration believes it. So when you cannot get an answer: say the process needs one harness, log the failure, and stop.


folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev