PANIM ADAM — Gray-Zone Discernment

PANIM ADAM is the fourth of the four Chayyot — the face of the human, gray-zone discernment. It activates when the other three Chayyot have run and the action is not clearly blocked but carries conflicting signals. It does not decide. It elucidates: composing a structured Beiur report that enables human judgment rather than substituting for it.

What PANIM ADAM does

PANIM ADAM is the composition layer. It receives the output verdicts from NESHER, SHOR, and ARYEH and runs a single deterministic rule tree to produce one of five decisions: ALLOW, CAUTION, ESCALATE, BLOCK, or INDETERMINATE.

When the decision is ESCALATE, PANIM ADAM also generates a structured Beiur report — a machine-readable record of which classifier triggered escalation, why, and what human review should produce. The Beiur is not a block. It is a structured elucidation: the minimum information a supervisor needs to make a real decision, not a refusal posing as one.

Install

Zero runtime dependencies. No model downloads, no service calls, no telemetry. The TypeScript build ships as both ESM and CJS with full type declarations.

Quick start

Pass the upstream verdicts from NESHER, SHOR, and ARYEH. Null means the classifier was skipped (output or scope not provided). PANIM ADAM composes them deterministically.

import { compose } from '@reshimu/panim-adam'

const result = compose(
  {
    nesher: { level: 'CRITICAL' },
    shor:   { level: 'PARTIAL' },
    aryeh:  null
  },
  'migrate production database',
  'scheduled maintenance window'
)

// result.decision                      === 'ESCALATE'
// result.beiur.recommendation          === 'DEFER'
// result.beiur.triggeredBy[0].chayyah  === 'NESHER'
// result.beiur.summary                 — human-readable escalation notice
// result.reasons                       — per-chayyah explanation array
// result.reasoning                     — compact machine trace: "NESHER=CRITICAL·SHOR=PARTIAL→ESCALATE"

The beiur field is non-null only when decision === 'ESCALATE'. For all other decisions it is null. The Beiur is filed — not generated speculatively — because the escalation already happened.

Decision table

The rule tree is deterministic. Same inputs always produce the same output. Priority runs top to bottom: the first matching rule wins.

The Beiur report

The word beiur (בֵּיאוּר) means elucidation — the act of making something clear that was previously opaque. The Beiur report is not a refusal. It is structured evidence for a human reviewer: which classifier triggered, what specifically caused it, what the recommendation is, and a plain-language summary of what happened and why human review is required.

The recommendation field is one of APPROVE, DENY, or DEFER. It is PANIM ADAM's structured suggestion — not a decision. The supervisor who reads the Beiur makes the decision.

Full reference

The complete reference — the full Beiur schema, every composition rule, integration with the Atzmut OS MCP server, and the architectural notes — lives in the PANIM ADAM README on GitHub.

The Architecture of Velocity essay describes PANIM ADAM as the function every organization rediscovers after a catastrophic drift: the recognition that some decisions are structurally irreducible to predicates, and that escalating with a structured elucidation — rather than a binary block — is itself the alignment work. This package instantiates that function as a deterministic, zero-dependency library. PANIM ADAM is the fourth of the four Chayyot — the Bearers of the Throne. For the theological and architectural depth, read The Chayyot as Validators.