tama adaptive status

Reports adaptive autonomy policy, per-hook effective state, source identity, and telemetry transport status.

#Invocation

tama adaptive status [--json]

--json prints the same reading as one document instead of lines.

#Output and state

The first line reports automatic ceiling, lexical-frustration behavior, explicit-correction behavior, and repair autonomy. Each sorted hook line includes tier, mode, phase, recovered baseline, open-run length, source verification, and whether a contested block was observed. The final telemetry= JSON reports the transport: open, ready and acked segment counts; validReady, the ready segments that read back intact; invalidReady, each ready segment that does not, as {name, reason} naming the check it failed (a torn last row, a header or footer field, a frame out of sequence, a payload digest that no longer matches); reclaimable, the intact segments whose lake acknowledgement proves them kept; and legacy, the single-file telemetry an earlier layout left with its size. With --json the document is {policy: {autonomy, lexical, explicitCorrection, repair}, hooks: [{id, tier, mode, phase, baseline, openRun, source, contested}], telemetry}. The command is read-only and exits 0.

#Refusals and failures

Every failure is written as doctor: <reason> and exits 1. The reason names what could not be read:

• The adaptive policy (adaptive/policy.json) or the hook registry is missing, unreadable or not the declared shape, or a hook's tier is one the policy does not declare.
• A hook's adaptive state cannot be replayed from its journal.
• A segment folder, or a legacy telemetry file, cannot be examined.

A ready segment that cannot be read or is not intact, and a lake acknowledgement that cannot be read or does not prove its segment, are not failures of the command: each is listed under invalidReady with its reason, and the segment is kept.

Return to the adaptive command group or the complete CLI tree.