@agent-native/core 0.130.2 → 0.131.2

package/corpus/templates/content/docs/product/capabilities/content.workspace.session-restore.md

@@ -0,0 +1,76 @@
+---
+record_type: "capability"
+spec_version: 2
+id: "content.workspace.session-restore"
+name: "Session resumption"
+user_promise: "Content reopens the authorized object and focused View a person was using without requiring them to reconstruct the route."
+primary_user_job: "Resume interrupted work quickly without reopening stale, deleted, or newly unauthorized information."
+kind: "surface"
+state: "approved_shape"
+publicness: "public"
+availability: "universal"
+dependencies: ["content.workspace.working-set"]
+related_features: ["content.feature.find-your-place-again"]
+roadmap_boundary: "feature"
+acceptance_summary: "Session restoration reopens the last authorized object and focused saved or personal View after a normal interruption, discarding stale or inaccessible UI state safely."
+proof_requirements:
+  [
+    "Restart restoration of focus, View configuration, selection, and authorized route coverage",
+    "Deleted, stale, changed-permission, unavailable, and cross-context invalidation coverage",
+    "Real-interface reload, crash/restart, keyboard focus, agent-context, and recovery workflow",
+  ]
+evidence: []
+superseded_by: null
+last_reviewed: "2026-07-29"
+---
+
+# Session resumption
+
+## Why this exists
+
+Returning to work should feel like a held thread, not a scavenger hunt—and never like a
+resurrection spell for information a person may no longer open.
+
+## Example workflow
+
+An editor leaves a focused Timeline View, restarts the application, and returns there.
+If the Page was deleted or access changed, Content opens a safe fallback and explains it.
+
+## Product contract
+
+- Session state stores UI references and focus, never a substitute copy of object truth.
+- Restoration reauthorizes every target before reopening it and drops invalid state safely.
+- Saved or personal View focus restores when still authorized; ephemeral renderer state is bounded.
+- Recovery distinguishes normal restoration, missing target, denied target, and unavailable source.
+
+## Boundaries and non-goals
+
+Working set owns persisted UI state. Session restoration is not a guarantee to preserve
+every inactive renderer, unsaved local draft, or unauthorized content.
+
+## Acceptance stories
+
+### Resume an authorized View
+
+Given an editor focused on an authorized saved View, when the app restarts normally, then
+Content reopens that object and View with a usable focus target.
+
+### Discard revoked state
+
+Given saved state for an object whose access is revoked, when the session restores, then
+Content omits the object and does not reveal its title, preview, or prior selection.
+
+## Current evidence
+
+Persisted navigation donors do not prove reauthorization, fallback, and recovery. This
+Capability remains `approved_shape`.
+
+## Proof plan
+
+1. Test normal restart, focused Views, selections, and bounded renderer restoration.
+2. Test deleted, stale, denied, unavailable, and cross-context state invalidation.
+3. Exercise reload/crash recovery, keyboard focus, agents, and accessible explanations.
+
+## Open questions
+
+The exact safe fallback order needs interaction design.

package/corpus/templates/content/docs/product/capabilities/content.workspace.view-instance.md

@@ -0,0 +1,76 @@
+---
+record_type: "capability"
+spec_version: 2
+id: "content.workspace.view-instance"
+name: "View instances"
+user_promise: "Tabs, panes, embeds, and windows can show independent focused instances of the same canonical object without duplicating it."
+primary_user_job: "Compare or work through the same object in several places while keeping presentation state independent and data canonical."
+kind: "surface"
+state: "approved_shape"
+publicness: "public"
+availability: "universal"
+dependencies: ["content.workspace.working-set", "content.view.query"]
+related_features: ["content.feature.find-your-place-again"]
+roadmap_boundary: "feature"
+acceptance_summary: "Independent View instances hold their own focus and presentation state over shared canonical objects, reconcile shared mutations, and render lazily within one bounded working set."
+proof_requirements:
+  [
+    "Two-instance identity, independent View state, focus, selection, and persistence coverage",
+    "Shared mutation reconciliation, permission change, close, embed, and recovery coverage",
+    "Lazy-rendering, keyboard, assistive-technology, reload, and agent-context workflow",
+  ]
+evidence: []
+superseded_by: null
+last_reviewed: "2026-07-29"
+---
+
+# View instances
+
+## Why this exists
+
+Two windows can hold two questions about one Page. They should not create two Pages in
+order to do it.
+
+## Example workflow
+
+An editor opens one Database in a Table tab and a Timeline pane, changes a record in the
+Table, and sees the Timeline reconcile while its range and focus remain independent.
+
+## Product contract
+
+- A View instance references a canonical object plus instance-local presentation, focus, and selection state.
+- Tabs, panes, embeds, and later windows may show the same object without duplicating it.
+- Canonical mutations, permissions, and deletion reconcile across instances through shared Actions and state sync.
+- Lazy rendering bounds resource use without falsely treating an unmounted instance as closed or complete.
+
+## Boundaries and non-goals
+
+Working set owns instance persistence. A View instance is not a Page, Database, Query,
+permission boundary, or a fork of data.
+
+## Acceptance stories
+
+### Compare two presentations
+
+Given a Database open in a Table and Timeline instance, when a person changes Timeline
+range, then Table configuration is unchanged while both retain the same canonical records.
+
+### Reconcile one edit
+
+Given two authorized instances of one record, when an editor changes it through one, then
+the other reflects the canonical result without duplicate history or stale copy.
+
+## Current evidence
+
+Existing tabs or embeds are donor substrate only; no complete multi-instance contract is
+proven. This Capability remains `approved_shape`.
+
+## Proof plan
+
+1. Test two-instance focus, presentation, selection, close, persistence, and lazy rendering.
+2. Verify mutations, permission changes, deletion, errors, and recovery across instances.
+3. Exercise keyboard, assistive technology, reload, embed, and agent-context workflows.
+
+## Open questions
+
+Cross-window synchronization and focus-transfer policy need separate implementation design.

package/corpus/templates/content/docs/product/capabilities/content.workspace.working-set.md

@@ -0,0 +1,77 @@
+---
+record_type: "capability"
+spec_version: 2
+id: "content.workspace.working-set"
+name: "Working set"
+user_promise: "Tabs, split panes, and later windows are views over one persisted working set with explicit agent scope"
+primary_user_job: "Keep the few things I am actively using together without turning temporary UI state into object truth or hidden agent context."
+kind: "primitive"
+state: "approved_shape"
+publicness: "public"
+availability: "universal"
+dependencies: ["content.workspace.multi-scope"]
+related_features: ["content.feature.find-your-place-again"]
+roadmap_boundary: "feature"
+acceptance_summary: "A persisted working set holds stable, authorized View references and local presentation state for tabs and panes, with explicit focus, bounded lazy rendering, and visible agent scope."
+proof_requirements:
+  [
+    "Stable references, focus, selection, ordering, pane layout, and persistence coverage",
+    "Scope, access revocation, source boundary, agent-context consent, close, and recovery coverage",
+    "Lazy rendering, reload, keyboard, assistive-technology, and concurrent UI workflow",
+  ]
+evidence: []
+superseded_by: null
+last_reviewed: "2026-07-29"
+---
+
+# Working set
+
+## Why this exists
+
+Active work deserves continuity, but a tab strip must not become a secret database or an
+unannounced briefing packet for an agent.
+
+## Example workflow
+
+A person keeps a project, a filtered task View, and a note in split panes, focuses the
+task View, and chooses which focused context an agent may use. Reordering panes changes
+only their working set.
+
+## Product contract
+
+- The working set persists stable authorized View references and UI state, not object copies or truth.
+- Tabs, panes, and future windows share one explicit focus and selection model with bounded lazy rendering.
+- Current context and explicit consent govern what an agent receives; background tabs are not implied context.
+- Access loss, deletion, source unavailability, and scope changes invalidate or annotate state safely.
+
+## Boundaries and non-goals
+
+Multi-scope owns ownership boundaries and View instances own a rendering occurrence. This
+is not shared document structure, an agent surveillance feed, or a second navigation tree.
+
+## Acceptance stories
+
+### Keep temporary arrangement personal
+
+Given two people viewing the same project, when one rearranges tabs and panes, then the
+other person's layout and the project's canonical structure remain unchanged.
+
+### Make agent scope explicit
+
+Given several open panes, when a person asks an agent about the focused task View, then
+only the explicitly selected authorized context is supplied and its origin remains visible.
+
+## Current evidence
+
+No complete persisted working-set, consent, access-invalidating, and recovery proof is
+recorded. This Capability remains `approved_shape`.
+
+## Proof plan
+
+1. Test references, focus, panes, ordering, persistence, close, and lazy rendering.
+2. Verify access and context changes, source boundaries, agent consent, and recovery.
+3. Exercise reload, concurrent UI changes, keyboard, and assistive-technology workflows.
+
+## Open questions
+
+The first explicit agent-context selector and cross-device persistence policy need design.

package/corpus/templates/content/docs/product/chapters/content.chapter.capture-research.md

@@ -0,0 +1,20 @@
+---
+record_type: "chapter"
+id: "content.chapter.capture-research"
+name: "Capture anything. Keep the thread"
+order: 5
+promise: "Chapter 5 turns the things people encounter into research they can keep using. Material can enter from many capture points, retain its source and exact context, become comfortable to read and annotate, and connect to citations, claims, and other knowledge without losing the original thread. The following Features support that path from capture to understanding."
+features:
+  [
+    "content.feature.capture-into-action",
+    "content.feature.read-and-annotate-anything",
+    "content.feature.cite-what-you-found",
+    "content.feature.sketch-connections-keep-whats-true",
+  ]
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Capture anything. Keep the thread
+
+Chapter 5 turns the things people encounter into research they can keep using. Material can enter from many capture points, retain its source and exact context, become comfortable to read and annotate, and connect to citations, claims, and other knowledge without losing the original thread. The following Features support that path from capture to understanding.

package/corpus/templates/content/docs/product/chapters/content.chapter.connected-sources.md

@@ -0,0 +1,20 @@
+---
+record_type: "chapter"
+id: "content.chapter.connected-sources"
+name: "One workspace across every source"
+order: 3
+promise: "Chapter 3 lets people work across Content, local files, and connected providers without rebuilding everything in one proprietary home. A team can combine information from several Sources, edit it through one predictable interface, and keep supported changes synchronized while preserving ownership, access, and provider-specific meaning. The following Features make that shared workspace possible."
+features:
+  [
+    "content.feature.connect-your-sources",
+    "content.feature.trust-your-connected-sources",
+    "content.feature.work-across-every-workspace",
+    "content.feature.bring-your-local-work",
+  ]
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# One workspace across every source
+
+Chapter 3 lets people work across Content, local files, and connected providers without rebuilding everything in one proprietary home. A team can combine information from several Sources, edit it through one predictable interface, and keep supported changes synchronized while preserving ownership, access, and provider-specific meaning. The following Features make that shared workspace possible.

package/corpus/templates/content/docs/product/chapters/content.chapter.consensus.md

@@ -0,0 +1,19 @@
+---
+record_type: "chapter"
+id: "content.chapter.consensus"
+name: "Come to consensus without losing the evidence"
+order: 2
+promise: "Chapter 2 keeps collaboration attached to the work being shaped. People and agents can discuss a Page or Database, leave precise feedback, review attributable changes, explore alternatives, and preserve how the team reached its conclusion without rescuing the useful parts from a separate chat afterward. The following Features create that collaboration loop."
+features:
+  [
+    "content.feature.collaborate-in-context",
+    "content.feature.review-changes-in-place",
+    "content.feature.explore-alternatives-safely",
+  ]
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Come to consensus without losing the evidence
+
+Chapter 2 keeps collaboration attached to the work being shaped. People and agents can discuss a Page or Database, leave precise feedback, review attributable changes, explore alternatives, and preserve how the team reached its conclusion without rescuing the useful parts from a separate chat afterward. The following Features create that collaboration loop.

package/corpus/templates/content/docs/product/chapters/content.chapter.durable-home.md

@@ -0,0 +1,21 @@
+---
+record_type: "chapter"
+id: "content.chapter.durable-home"
+name: "A durable home for your thinking"
+order: 1
+promise: "Chapter 1 gives people and agents a dependable place to create, organize, find, reshape, and recover their work. Pages and Databases remain understandable after an interruption, important material can be reused without drifting copies, and every authorized collaborator can return to the same durable context. The following Features establish that foundation."
+features:
+  [
+    "content.feature.durable-foundations",
+    "content.feature.find-your-place-again",
+    "content.feature.living-references",
+    "content.feature.make-the-workspace-yours",
+    "content.feature.see-your-information-your-way",
+  ]
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# A durable home for your thinking
+
+Chapter 1 gives people and agents a dependable place to create, organize, find, reshape, and recover their work. Pages and Databases remain understandable after an interruption, important material can be reused without drifting copies, and every authorized collaborator can return to the same durable context. The following Features establish that foundation.

package/corpus/templates/content/docs/product/chapters/content.chapter.publishing-portability.md

@@ -0,0 +1,21 @@
+---
+record_type: "chapter"
+id: "content.chapter.publishing-portability"
+name: "Write once, keep it yours, publish faithfully"
+order: 6
+promise: "Chapter 6 carries the same canonical work from private thought into public reading, other applications, portable archives, and future systems. People can publish or embed what they choose, move their full body of work without starting over, and retain meaningful control over custody without creating a second truth that quietly drifts away. The following Features make Content useful beyond Content itself."
+features:
+  [
+    "content.feature.publish-with-confidence",
+    "content.feature.take-the-whole-vault-with-you",
+    "content.feature.move-without-starting-over",
+    "content.feature.work-on-content-inside-another-application",
+    "content.feature.keep-your-private-vault-private",
+  ]
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Write once, keep it yours, publish faithfully
+
+Chapter 6 carries the same canonical work from private thought into public reading, other applications, portable archives, and future systems. People can publish or embed what they choose, move their full body of work without starting over, and retain meaningful control over custody without creating a second truth that quietly drifts away. The following Features make Content useful beyond Content itself.

package/corpus/templates/content/docs/product/chapters/content.chapter.working-systems.md

@@ -0,0 +1,27 @@
+---
+record_type: "chapter"
+id: "content.chapter.working-systems"
+name: "Shape your own working system"
+order: 4
+promise: "Chapter 4 turns flexible Pages and Databases into working systems a team can trust. People with the right expertise can shape data, Views, Templates, Rules, Skills, and agent workflows for everyone else, while validation, governance, and safe evolution keep that flexibility from becoming organizational confetti. The following Features provide those building blocks."
+features:
+  [
+    "content.feature.data-that-keeps-itself-right",
+    "content.feature.share-how-your-organization-works",
+    "content.feature.put-your-organizations-know-how-to-work",
+    "content.feature.evolve-systems-safely",
+    "content.feature.when-this-happens-that-follows",
+    "content.feature.run-projects-your-way",
+    "content.feature.plan-work-across-time",
+    "content.feature.build-new-surfaces",
+    "content.feature.collect-structured-input",
+    "content.feature.understand-what-your-data-says",
+    "content.feature.build-living-dashboards",
+  ]
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Shape your own working system
+
+Chapter 4 turns flexible Pages and Databases into working systems a team can trust. People with the right expertise can shape data, Views, Templates, Rules, Skills, and agent workflows for everyone else, while validation, governance, and safe evolution keep that flexibility from becoming organizational confetti. The following Features provide those building blocks.