name	hima-verdict
description	Independent critic that inspects work against the charter and seals a stage DONE_VERIFIED, PARTIAL, or BLOCKED.
stage	verify
source	base
mode	force

Purpose

Close the verify stage with an honest seal. hima-verdict is the critic — never the builder, never run in parallel with the builder — and it never self-declares completion on the same work it authored. It inspects the diff against the sealed charter (hima-charter) and the trial evidence (hima-trial), then renders one of three verdicts.

When to use

After hima-forge/hima-trial produce a candidate change and before any DONE claim.
Force at M+ criticality: no stage can be marked complete without a verdict seal.
Skip only at T/L criticality where a lightweight self-check is an acceptable substitute.

Steps

Load the charter (scenarios, acceptance criteria, criticality tags) and confirm it is sealed.
Re-run or read the trial evidence; do not trust a diff read alone — check tests actually ran.
Check each acceptance criterion individually; do not average partial passes into a pass.
Check Core/Shell boundary, type safety, and rule compliance against the project's disciplines.
Render the seal: DONE_VERIFIED (all criteria met + evidence collected), PARTIAL (useful work, named gap), or BLOCKED (missing authority/credential/external state).
Record the seal and its evidence trail so hima-stewardship can audit it later.

Done when

A verdict (DONE_VERIFIED / PARTIAL / BLOCKED) is recorded with the evidence it rests on, the critic identity is distinct from the builder identity, and no criterion was skipped silently.

Más de este repositorio

mismo repositorio

hima-admit

momomuchu/hima

Bootstrap a new project or catch up an agent on an existing one in minutes by reading vision/goals/state and scaffolding the minimum brain files.

2026-07-021

hima-blueprint

momomuchu/hima

Produce the structural plan — component boundaries, contracts, data flow — plus a lightweight decision record, from a sealed charter.

2026-07-021

hima-charter

momomuchu/hima

Formalize intent into a spec artifact (Gherkin scenarios, acceptance criteria, criticality tags) before any non-md file may change.

2026-07-021

hima-covenant

momomuchu/hima

Declare and audit the per-project disciplines (cadence, branching, testing, architecture, methodology) that the pluggable StageSkillMap resolves against.

2026-07-021

hima-forge

momomuchu/hima

Implement the minimum code to satisfy the charter's RED tests, one logical change per commit.

2026-07-021

hima-lookout

momomuchu/hima

Cited, multi-source research pass for H/C decisions or true blockers — converts findings into requirements, risks, and rejected alternatives.

2026-07-021

name	hima-verdict
description	Independent critic that inspects work against the charter and seals a stage DONE_VERIFIED, PARTIAL, or BLOCKED.
stage	verify
source	base
mode	force

Purpose

When to use

After hima-forge/hima-trial produce a candidate change and before any DONE claim.
Force at M+ criticality: no stage can be marked complete without a verdict seal.
Skip only at T/L criticality where a lightweight self-check is an acceptable substitute.

Steps

Load the charter (scenarios, acceptance criteria, criticality tags) and confirm it is sealed.
Re-run or read the trial evidence; do not trust a diff read alone — check tests actually ran.
Check each acceptance criterion individually; do not average partial passes into a pass.
Check Core/Shell boundary, type safety, and rule compliance against the project's disciplines.
Render the seal: DONE_VERIFIED (all criteria met + evidence collected), PARTIAL (useful work, named gap), or BLOCKED (missing authority/credential/external state).
Record the seal and its evidence trail so hima-stewardship can audit it later.

Done when

A verdict (DONE_VERIFIED / PARTIAL / BLOCKED) is recorded with the evidence it rests on, the critic identity is distinct from the builder identity, and no criterion was skipped silently.