PRISM v2.6.0 released

[Ronkupper]

PRISM v2.6.0 is released → https://github.com/Ronkupper/PRISM/releases/tag/v2.6.0

A MINOR over v2.5.2 that adds corpus-access dispatch (Phase 1) — a first-class investigation posture for sending PRISM to retrieve from a named source or document corpus, kept structurally separate from the framework's epistemic triangulation machinery.

Surface highlights

• Posture is now an Envelope field. The Execution Envelope (§3.2.1, the dispatch packet template) carries Posture: epistemic | investigation. Epistemic dispatch carries a dispatch shape; investigation dispatch carries none of {dispatch shape, vendor list, dispatch rationale}. This puts the SP-15 triangulation guardrail (the rule that single-vendor lookups don't earn a triangulation seat) into the structure of the Envelope itself.
• A corpus-access Envelope (new §4.13, the corpus-access dispatch section). Captures the source, its access path, the lookup driver, the fan, a reserved tools slot, the question, the extract, return form, archive request, and mandatory source-framing and temporal-frame caveats.
• Coverage fan, not triangulation. Fan: coverage (N) returns a recall-merge plus a retrieval-consistency note — never routed through §4.3 (Vendor Triangulation, the convergence machinery), which is now guarded to fire only on epistemic equivalence dispatch.
• Exhibits manifest (§3.2.3, the return contract). When you ask PRISM to archive what it found, the return bundles a signed Master with companion files under a mandatory provenance manifest — filename, source, capture date, query answered, and the framing + temporal caveat per item. SP-14 (the filename-discipline principle) gains a companion-file naming convention.

Phase status

Phase 1 makes the manual and vendor-executed lookup paths operational. The cowork-mcp path is defined but reserved, alongside auto_drive. Phase 2 (a lens-anchored auto-trigger) and Phase 3 (cowork-mcp auto-driven lookup) remain.

Worth reporting back

• Does Posture: read cleanly at dispatch time, or want a shorter default?
• Does the three-value lookup Driver: enum hold up once real lookups run?
• Do coverage-fan returns stay legibly separate from triangulated ones in the Master?
• Is per-entry exhibit provenance the right weight, or too heavy for small archives?

For where v2 sits relative to the v1.x surface, see Appendix D in PRISM.md (the v1.x → v2 surface-drift map). Design provenance (decisions D1–D12) lives in the private workshop repo at design/corpus_access_dispatch_dd_rev1.md.