Forge 2.0 (Approval-First Execution Engine)

Forge 2.0 turns grounded intelligence, decision records, and Pulse change signals into safe, previewable actions. Built on an approval-first architecture, Forge ensures that AI and automated recipes never alter your vault or external tools without your explicit consent.

Action Lifecycle & Approval Model

Every Forge execution follows a deterministic, safe pipeline:

```text

proposed → previewed → edited → approved → applying → applied → undone

```

1. Proposal: Pulse signals, meeting summaries, or user prompts generate proposed actions.

2. Interactive Preview: Forge presents side-by-side diff previews and side-effect impact summaries.

3. User Editing & Customization: Modify targets, prompt inputs, or step boundaries before execution.

4. Approval: Click Approve (or perform a batch approval) to execute.

5. Execution & Audit: Actions run idempotently, writing outcome receipts to your workspace audit history.

6. Undo Support: Revert local file modifications directly from the execution history panel.

Core Action Recipes

Forge supports built-in local actions and reviewable proposals for connected external integration steps:

Core Local Actions

Note Management: Create new structured notes, append section summaries, or update frontmatter properties.
Task Extraction: Generate checklist tasks with due dates and tags directly in project notes.
Decision Registers: Convert confirmed Strata candidates into clean decision register notes.
Calendar Event Export: Generate downloadable .ics calendar files for scheduled commitments.
Draft Email Follow-ups: Formulate follow-up email drafts based on meeting decisions without sending them.

Connected External Proposals

Connected Calendars & Mail: Review proposals for calendar events and mail drafts. Direct provider execution is available only when a capability-specific Forge executor is installed and policy-approved.
Issue Trackers: Review GitHub, Linear, or Jira issue proposals arriving through the Automation Gateway. The proposal contract does not by itself claim a native write connector.
Cited Briefs: Publish live, branded cited briefs through Phasoric's supported local and hosted flow.

Developer & Agent Capabilities

REST & MCP Execution: Trigger Forge actions programmatically via REST API or hosted MCP server.
Hosted Dry-Run Transactions: Preview hosted-vault changes with explicit mapping IDs, idempotency keys, and expected-hash guards. Custom executable tool registration remains future work.
Zapier and n8n: Download versioned starter assets from /api/dev/automation/templates, import the n8n workflows, or configure the Zapier Webhooks recipe. These bridges cannot bypass approval.
Durable triggers: Five-field cron schedules and versioned events can create Forge proposals with persistent dedupe, cooldown, depth, concurrency, retry, and execution-budget records. A trigger does not approve its own proposal.
Signed webhook delivery: webhook.deliver proposals bind to a pre-registered encrypted destination. Explicit approval queues an idempotent signed request; Forge exposes retry and dead-letter state. This does not imply that calendar, mail, GitHub, Linear, or Jira proposal types have native executors yet.