git:20260903.ecbd52c to git:20260926.09b7c01

---

name: open-point-process-runner

description: Validates and analyzes one registered Open against current evidence.

---

# open-point-process-runner

## Goal

Give decision support for one Open. Investigate until the Return is complete; do not over-search.

## Preconditions

- An Open is one unresolved question that matters to the current slice.

- It belongs to one registry lens. Blocking says whether unresolved work

prevents closure.

## Inputs

Require: facts path; one Open. A project evidence scope may also be supplied.

Analyze only the input Open.

## Cognition

Input terms carry the meanings defined in these units.

| Term | Unit |

|---|---|

| facts | `../../references/cognition/fact.md` |

| Open `lens`, registry lens | `../../references/cognition/lens.md` |

| KW row the Open's `basis` names | `../../references/cognition/kw-ruler.md` |

Two options rest on them: `already-answered` holds when the fact set

states the question; `out-of-slice` holds when the substance belongs to

another lens or to no lens of this slice.

## Analyze

1. Decision support possible → `open`; else `blocked`. Stop if `blocked`.

Do not infer.

2. If `open`: explain without assumed context. Options must differ in

action, consequence, or trade-off. Reword, already-answered, and

out-of-slice are options.

## Return

- `blocked`: exception. Cases: missing input; missing evidence.

`reason` is free text.

- `open`: `issue`, `evidence`, 2–5 `options`, `lean`.

- Use one of the two shapes below.

```json

{

"status": "blocked",

"reason": "facts path is missing"

}

```

```json

{

"status": "open",

"reason": "still unresolved",

"issue": "Acceptance for this open is still unspecified.",

"evidence": ["F-1"],

"options": [

{"id": "A", "action": "Land a close"},

{"id": "B", "action": "Reword the question"},

{"id": "C", "action": "Treat facts as already answering it"}

],

"lean": "A"

}

```

## Boundaries

- Read-only; do not write facts, Opens, Batches, or workflow state.

- No user interaction, disposition, or queue movement.

- Depend only on supplied inputs and the Cognition units.

- Substantive input changes require a fresh invocation.

- Failure has no side effects.