docs(evidence): preserve Jev triage of the layered-memory reconcile #111
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/jev-layered-memory-evidence"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Moves the advisory Jev pass out of
/tmpinto the durable evidence tree.Follow-up to #110 (merged
afac8ef). The triage run for the layered-memorydocs/contract reconciliation lived only in
/tmp/jev-layered-memory-pass/;this preserves it under
docs/evidence/, matching the existingdocs/evidence/<name>/{packets,results}/convention.Added
docs/evidence/jev-layered-memory-reconcile/README.md— report + deterministic policy application (okf frontmatter)packets/layered-memory-reconcile.json— input packet (no credentials)results/layered-memory-reconcile.result.json— schema-validated typed answers, confidence, probabilities, usageresults/layered-memory-reconcile.raw.json— redacted raw gateway responseJSON files are verbatim copies of the local run (sha256-verified against the source).
Result recorded
status: ambiguous— relevancerelevant, prioritymedium,blocking
non_blocking;actionability(conf 0.47) andnext_action(conf 0.29, gap 0.09) trip the ambiguity rule;
safe_to_edit0.50 (<0.75) →false;
human_review0.67 → true. Transport: direct TypeSafejev-latest,caller_attribution: pi-deepseek, 1 attempt, cost not returned (usage 1570/282).Scope
Read-only evidence. The triage authorizes nothing — no implementation, merge,
publication, or credential change. No credentials or tokens are included.
Gates
check-formatpass ·check-dates --strictclean ·wiki-lint --strictclean(761/0) ·
check-okfadvisory exit 0.