Hivy is ShardStitch's local verify engine. It helps surface drift and stale-path signals while the verified tier is rebuilt from current repository evidence.
A dead or stale AI session should not become the source of truth. Hivy helps ShardStitch keep repository-grounded facts separate from recovered session context, then surface stale branches and risky next moves before the next chat inherits them.
Hivy supports the trust layer. The core promise stays the same: ShardStitch reads disk truth, separates verified facts from inferred next steps, and hands the next AI a lean continuation packet. The verified record can be re-checked through Bedrock.
Hivy helps surface stale paths, drift signals, and mismatches between remembered context and current repository evidence. It is most useful before a tool handoff, after a failed recovery attempt, or when several branches of a debugging conversation look plausible.
Hivy highlights evidence for review; it does not make correctness claims without repository checks. Bedrock keeps the resulting record re-checkable so verified facts and inferred next steps remain distinct.
When Hivy marks a path, memory item, or proposed next move as stale or risky, open the referenced project evidence and decide whether the signal still applies to the current branch.
For example, a stale-path signal may point to a note naming src/old-router.py while the current tree contains src/router.py. Search the repository and inspect history before deleting the note: it may describe a deliberate rename or an unresolved migration. Record the evidence and resolution so the next handoff does not repeat the same guess.
A local signal is not proof that a file is wrong, a branch is stale, or a change is unsafe. Heuristics can miss context or raise a false positive. Resolve flags with source files, diffs, tests, and explicit project decisions.