Skip to main content
📋

Changelog

Release logs, version tags, fixes, and engine updates.

v2026.08.11Connected Workflows, Semantic Knowledge, Trusted Reviews, and Structured Views
August 11, 2026â–²

Version 2026.08.11 - Connected Workflows and Structured Knowledge

This release makes it easier to connect outside context, organize portable Markdown, automate reviewable work, migrate knowledge safely, and collaborate around trusted sources.

Connections and reviewable automation

  • Connect Google and Microsoft accounts to bring bounded Calendar, email, and file context into Phasoric without exposing provider credentials to the browser.
  • Choose what external context becomes local Markdown. Captured items retain their source identity and provenance.
  • Use Zapier, n8n, OpenAPI, REST, and MCP paths to send events and create Forge proposals for long-tail services without requiring a dedicated connector for every provider.
  • Create event, cron, or one-time Agent triggers with pause controls, dry runs, run history, retry limits, loop prevention, concurrency controls, and execution budgets.
  • Deliver an approved, signed webhook only through a registered endpoint and the normal Agent → policy → Forge review path.

Blueprints and portable semantic Markdown

  • Create versioned Blueprints with required or recommended text, number, boolean, date, enum, tag, list, internal-link, and external-reference properties.
  • Keep Markdown canonical. Blueprint identity, stable entity links, external references, and behavior bindings remain readable in namespaced YAML outside Phasoric.
  • Preview Blueprint migrations before applying explicit field renames or defaults; unrelated frontmatter and note content remain untouched.
  • Link tasks and notes to broader context with stable entity IDs, source notes, heading paths, parent/root relationships, and external entities.

Safer migration and richer capture

  • Preview imports with measurable link, attachment, property, duplicate, collision, and quality checks before writing to the vault.
  • Resume interrupted migrations from bounded checkpoints and download a versioned migration report after completion.
  • Route quick notes, web highlights, voice, photos, documents, receipts, and scans with reusable Capture Studio templates and deterministic filing rules.
  • Imported and captured knowledge starts as Draft rather than being silently treated as verified.

Trusted knowledge lifecycle

  • Track knowledge as Draft, Reviewed, Verified, Changed, Stale, or Superseded with fingerprints, evidence, review deadlines, provenance, and history.
  • See trust state in the note inspector, Pulse, Strata, Intelligence evidence, retrieval context, and structured Quarry fields.
  • Note edits reconcile tracked fingerprints so changed or stale evidence can return to review instead of remaining invisibly trusted.

Team collaboration and governance

  • Assign Workspace Owner, Workspace Admin, Editor, Reviewer, Commenter, and Viewer roles with explicit workspace permissions.
  • Anchor durable discussions and reviews to a note, Markdown heading path, or portable block ID; changed or missing anchors are visibly identified.
  • Mention workspace members, assign reviewers, resolve or reopen threads, and inspect attributable workspace activity.
  • Keep live editing presence ephemeral while durable comments, review actions, and governance events remain auditable.

Structured Quarries and dashboards

  • Build Quarries from note rows or portable task rows, including task completion, priority, due date, source note, heading path, parent/root IDs, and linked entities.
  • View bounded results as List, Table, Kanban, Gallery, Calendar, Timeline, Chart, Map, or composed Dashboard layouts.
  • Save row type, renderer, filters, formulas, sorting, and grouping with each Quarry.
  • Phasoric reports result limits and truncation instead of implying that a bounded interactive view contains the entire vault.

Connected and team capabilities remain subject to plan access, workspace permissions, provider configuration, and explicit user approval. External provider writes remain proposal-only unless a separately supported executor is available.