feat: pass candidate facets to Jev for review

2026-10-14 20:43:03 +08:00
2 changed files with 3 additions and 3 deletions
@@ -190,7 +190,7 @@
      "compatible_checkpoint_contracts": [
        "gewu.local-checkpoint@0.1.0"
      ],
-      "sha256": "b6193c5017a820fa6d50f1595bb40aa74f7439b98fa85082def1ca3991319c88",
+      "sha256": "3985cc41a7405ce9076f57229d63380cb18fb57c1c6b615a7014e717d6172eb6",
      "hash_encoding": "utf8-no-bom-lf"
    },
    {
@@ -516,6 +516,6 @@
  "snapshot": {
    "algorithm": "sha256",
    "scope": "modules array serialized as UTF-8 JSON with sorted keys and compact separators",
-    "digest": "279a2c16bb5e94110311fab44d9b2e79657342c49ab49b669e64298aaa5a37df"
+    "digest": "1f782aee6890de50e3928e7edc14eb2f959d8e0e05641cbd16d12b2edb3211d1"
  }
 }
@@ -8,6 +8,6 @@ Read the pack's [evidence](../../protocols/EVIDENCE.md), [scope](../../protocols
 Inputs are the selected source(s), explicit project and the user's research objective. Use `get_project_context` for the project's north star, key questions, watch list, taxonomy extensions, research lenses and saved ingest guidance. Every project defaults to four research lenses: technical, conceptual, cultural-historical and financial-market. Treat these as coverage prompts, not quotas. Verify the supported tool/schema contract, including `ingest_review_create` when borderline-review intake is available. Use the connector for local byte transfer; it returns a typed source metadata candidate without exposing the selected path or bytes. Selected `.vtt` and `.srt` files produce timestamped transcript cues; cite exact cue start/end times and the quote span. A declared NotebookLM export label is metadata only and is not export verification. For text explicitly pasted by the user, use `source_capture_text` with a stable capture ID and source key; it accepts UTF-8 plain text or Markdown up to 1 MB, archives and extracts it, and returns a typed candidate marked `capture_method=pasted-text`. Retry uncertain calls with the same capture ID and identical inputs; changed input under that ID conflicts. It does not register the candidate. `source_capture_url` fetches only operator-allowlisted public hosts and stages supported text, Markdown, HTML or PDF bytes; it also returns a source metadata candidate but does not register it. Submit candidates with the normal typed proposal flow, and use `capture-failed` candidates only as bookmarks, never as factual evidence. URL source IDs follow the sanitized URL; local source IDs follow the connector's configured file ID; pasted-text source IDs are derived from the supplied stable key and revision IDs include the content digest. PDF extraction currently requires Linux bubblewrap, Poppler and prlimit. Unsupported formats and unavailable parsers must be reported without inventing an extraction. If the service is unavailable, report the blocked stage and only prepare an unaccepted local draft when that work was requested.
-Extract useful atomic assertions, problems, techniques or cases with their conditions across all four lenses where the source contains relevant material. Consider cultural history, philosophical context and market/financial evidence as project data when they explain the project's origins, concepts, adoption, audience, costs or viability; they are not automatically peripheral. First try to connect uncertain material to the north star, a key question, a saved rule or one of the lenses. Exclude only clearly unrelated material, unavailable evidence, or material the user explicitly excluded. Do not defer a section merely because its relevance is indirect, non-technical or historical. Continue normal evidence-backed proposal evaluation/submission for all plausible useful findings. Also submit a bounded `ingest_review_create` follow-up flag with the exact extraction excerpt/locator, lens, summary and reason when a human should review the relevance or categorization; this flag is persisted for notification/filtering and must not block or change proposal submission. If available, the backend's Jev score is a relevance signal, not a gate or evidence assessment. When a reviewer decides, record the feedback and apply reusable project guidance only when the reviewer explicitly opts in. Preserve the service's exact source/extraction/location bindings. Map each factual field to evidence; assess semantic support separately. Record clear exclusions and genuinely skipped/deferred sections. Optimize for useful coverage rather than maximum note count.
+Extract useful atomic assertions, problems, techniques or cases with their conditions across all four lenses where the source contains relevant material. Consider cultural history, philosophical context and market/financial evidence as project data when they explain the project's origins, concepts, adoption, audience, costs or viability; they are not automatically peripheral. First try to connect uncertain material to the north star, a key question, a saved rule or one of the lenses. Exclude only clearly unrelated material, unavailable evidence, or material the user explicitly excluded. Do not defer a section merely because its relevance is indirect, non-technical or historical. Continue normal evidence-backed proposal evaluation/submission for all plausible useful findings. Also submit a bounded `ingest_review_create` follow-up flag with the exact extraction excerpt/locator, lens, summary and reason when a human should review the relevance or categorization; this flag is persisted for notification/filtering and must not block or change proposal submission. Include the same evidence-backed candidate `tags`, `audience`, `use_for` and `domain` labels you proposed for the associated knowledge, up to five per facet (20 total); reuse project vocabulary when suitable and omit uncertain candidates. If available, Jev assesses relevance, lens and each proposed facet label in one advisory call. Use these probabilities to focus human review; they are not a gate, evidence assessment, or instruction to silently rewrite accepted knowledge. When a reviewer decides, record the feedback and apply reusable project guidance only when the reviewer explicitly opts in. Preserve the service's exact source/extraction/location bindings. Map each factual field to evidence; assess semantic support separately. Record clear exclusions and genuinely skipped/deferred sections. Optimize for useful coverage rather than maximum note count.
 Submit bounded bundles under the affected project/shared policies. Repair actionable findings without weakening evidence, changing scope to evade policy or assuming owner authority. Resume uncertain calls through status lookup. Report accepted node IDs and receipts, pending/rejected work, archive/extraction limits and actual coverage. A successful upload or schema check is not a completed ingestion.