@agent-native/core 0.130.1 → 0.131.2

package/corpus/templates/content/docs/product/features/content.feature.build-living-dashboards.md

@@ -0,0 +1,34 @@
+---
+record_type: "feature"
+id: "content.feature.build-living-dashboards"
+number: 23
+name: "Build living dashboards"
+chapter: "content.chapter.working-systems"
+order: 23
+roadmap_status: "planned"
+summary: "Compose responsive Views, Charts, expressions, controls, and prose into durable operating surfaces."
+example_workflow: "A go-to-market lead assembles a responsive Page with pipeline Charts, filtered account Views, explanatory prose, and personal controls so people and agents can inspect the same operating picture and discuss it in context."
+works_today: "Pages can already combine prose, Blocks, references, expressions, and embedded Database Views, while saved Views provide reusable filtered presentations."
+remains: "Responsive Page columns, resizable View and Chart Blocks, dashboard controls, chart conformance, personal interaction state, presentation behavior, and export fidelity still need implementation."
+required_capabilities:
+  ["content.layout.responsive", "content.view.chart", "content.embed.surface"]
+enhancing_capabilities:
+  ["content.presentation.mode", "content.expression.language"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 23: Build living dashboards
+
+Compose responsive Views, Charts, expressions, controls, and prose into durable operating surfaces.
+
+## Product contract
+
+- **Ordinary Pages:** Serve as the dashboard canvas without introducing a separate dashboard datastore.
+- **Embedded Views and Charts:** Reference saved configurations while allowing each occurrence to override size and presentation.
+- **Responsive columns:** Arrange, resize, and reorder Blocks with a layout that linearizes coherently on smaller screens and in exports.
+- **Controls and Expressions:** Let viewers change authorized filters or inputs without mutating the shared default accidentally.
+- **Live context:** Keeps prose, decisions, metrics, and the underlying records together for people and agents.
+- **Presentation mode:** Reuses shared Slides primitives to present Pages or ordered records without inventing slide-only content.

package/corpus/templates/content/docs/product/features/content.feature.build-new-surfaces.md

@@ -0,0 +1,33 @@
+---
+record_type: "feature"
+id: "content.feature.build-new-surfaces"
+number: 20
+name: "Build new surfaces"
+chapter: "content.chapter.working-systems"
+order: 20
+roadmap_status: "partially_implemented"
+summary: "Create a one-off artifact, then promote it into a governed reusable Custom Block when it earns reuse."
+example_workflow: "An agent creates a one-off interactive calculator inside a Page; its owner inspects the source and rendered result, then promotes it to an approved Custom Block that coworkers can insert from the slash menu."
+works_today: "Sandboxed Extensions, local MDX components, HTML artifacts, executable-code foundations, and shared component toolkits already demonstrate several rendering and execution modes."
+remains: "These pieces need one Custom Block lifecycle with inspectable source, secure sandboxing, optional typed props, one-off artifacts, promotion, governed catalogs, source-backed origins, and slash-command discovery."
+required_capabilities:
+  ["content.renderer.artifact-block", "content.renderer.custom-block"]
+enhancing_capabilities: ["content.author.code", "content.renderer.typed"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 20: Build new surfaces
+
+Create a one-off artifact, then promote it into a governed reusable Custom Block when it earns reuse.
+
+## Product contract
+
+- **Artifact Block:** Stores Page-owned HTML, styles, and behavior without requiring props or a catalog entry.
+- **Source and rendered views:** Lets authors inspect the code underneath and the output it produces.
+- **Sandbox:** Denies network and application authority by default while enforcing time, memory, output, and asset limits.
+- **Save as Custom Block:** Promotes a useful one-off into a governed reusable definition with stable identity.
+- **Custom Blocks catalog:** Controls discovery, ownership, versions, permissions, compatibility, and typed props where useful.
+- **Source-backed origins:** Lets repository, Builder, or later Source adapters provide the implementation without creating another product identity.

package/corpus/templates/content/docs/product/features/content.feature.capture-into-action.md

@@ -0,0 +1,34 @@
+---
+record_type: "feature"
+id: "content.feature.capture-into-action"
+number: 24
+name: "Capture into action"
+chapter: "content.chapter.capture-research"
+order: 24
+roadmap_status: "partially_implemented"
+summary: "Resolve or create one canonical Page in the chosen Database, preserve provenance, and hand it to that Database's Rules and agents."
+example_workflow: "Someone shares a customer interview URL from their phone to the Research Database; Content reuses the canonical Source Page, preserves the transcript and provenance, and lets the Database's Rules extract companies and open questions."
+works_today: "Content can already import or create Pages from files, URLs, providers, local Sources, and Agent Actions, with useful provenance and Database destinations in several paths."
+remains: "Every entrance needs one Capture contract with remembered destination, canonical deduplication, idempotency, snapshot handling, Template application, receipts, and clean downstream enrichment."
+required_capabilities:
+  ["content.capture.enrich", "content.source.catalog", "content.job.durable"]
+enhancing_capabilities: ["content.rule.deterministic", "content.template.graph"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 24: Capture into action
+
+Resolve or create one canonical Page in the chosen Database, preserve provenance, and hand it to that Database's Rules and agents.
+
+## Product contract
+
+- **Many entrances:** Accepts browser capture, share sheets, Clips, URLs, files, email, identifiers, providers, and Agent Actions through one contract.
+- **Remembered destination:** Defaults to the last Database used for that entrance while keeping the destination easy to change.
+- **Idempotent resolution:** Finds an existing canonical Page or creates exactly one, with a deliberate-copy escape hatch.
+- **Provenance:** Preserves the original URL, identifier, provider identity, capture time, snapshot, and available representations.
+- **Database handoff:** Applies the destination's Template, defaults, memberships, validation, and permissions.
+- **Downstream enrichment:** Lets target-owned Rules and agents summarize, classify, extract, or route the record without making Capture wait for them.
+- **Receipts and repair:** Reports what Capture created or reused and allows failed later enrichment to retry independently.

package/corpus/templates/content/docs/product/features/content.feature.cite-what-you-found.md

@@ -0,0 +1,34 @@
+---
+record_type: "feature"
+id: "content.feature.cite-what-you-found"
+number: 26
+name: "Cite what you found"
+chapter: "content.chapter.capture-research"
+order: 26
+roadmap_status: "planned"
+summary: "Turn a link into one durable source-and-locator identity that can render in different citation styles."
+example_workflow: "A writer promotes an ordinary research link to a citation, adds a page locator, switches the article from author-date to footnote style, and watches the bibliography update without re-entering the source."
+works_today: "Content has ordinary links, Page references, source metadata, rich text, equations, and import and export machinery that can donate to citation rendering."
+remains: "First-class citation identity, locators, promote-to-citation, automatic bibliographies, selectable styles, Zotero interoperability, and semantic portability need implementation."
+required_capabilities: ["content.research.citation", "content.author.footnotes"]
+enhancing_capabilities:
+  ["content.portability.roundtrip", "content.source.adapters"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 26: Cite what you found
+
+Turn a link into one durable source-and-locator identity that can render in different citation styles.
+
+## Product contract
+
+- **Promote to citation:** Converts an ordinary link without losing its anchor or source identity.
+- **Source Page:** Resolves or creates the canonical record for the paper, book, website, video, dataset, or other source.
+- **Locators:** Preserve page, chapter, figure, timestamp, transcript range, or another precise place within the source.
+- **Style rendering:** Presents one semantic citation as a link, author-date reference, number, footnote, or bibliography entry.
+- **Bibliographies:** Recompute from the citations actually present rather than maintaining a second manual list.
+- **Zotero interoperability:** Uses Zotero identities and CSL styles instead of volunteering to personally maintain civilization's citation formats.
+- **Portability:** Keeps citation identity intact across supported imports and exports even when the destination renders it differently.

package/corpus/templates/content/docs/product/features/content.feature.collaborate-in-context.md

@@ -0,0 +1,59 @@
+---
+record_type: "feature"
+id: "content.feature.collaborate-in-context"
+number: 6
+name: "Collaborate in context"
+chapter: "content.chapter.consensus"
+order: 6
+roadmap_status: "partially_implemented"
+summary: "Comments, Discussion, messages, notifications, and history stay anchored to the Page or Database being shaped."
+example_workflow: "A teammate comments on an unclear paragraph, discusses the larger issue in the Page's Discussion, links the conversation to Slack, and returns later to see the Comment, replies, and resulting changes together."
+works_today: "Content supports anchored Comment threads, replies, resolution, mentions, notifications substrate, and document history. These already keep precise feedback closer to the artifact than an external chat can."
+remains: "Every Page and Database needs its universal Discussion, rich Blocks-field messages, stable permalinks, access-safe Slack continuation, and clearly attributable message revisions."
+required_capabilities:
+  [
+    "content.discussion.page",
+    "content.comment.page-owned",
+    "content.object.blocks-field",
+    "content.notification.source",
+    "content.event.committed",
+  ]
+enhancing_capabilities: ["content.agent.presence", "content.feedback.signal"]
+increments: ["decide-together"]
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 6: Collaborate in context
+
+Comments, Discussion, messages, notifications, and history stay anchored to the Page or Database being shaped.
+
+## Product contract
+
+- **Comments:** Attach precise feedback to text, Blocks, media, or other exact material and preserve the historical target if that material changes.
+- **Discussion:** Gives every Page and Database one continuing channel for collaboration about the whole artifact.
+- **Rich messages:** Use Blocks fields so messages and Comments can contain the same references, embeds, Expressions, and structured content as Pages.
+- **Threads and replies:** Keep focused sub-conversations understandable without infinite nesting.
+- **Permalinks:** Make every message and Comment addressable from Content, Slack, or another Page.
+- **Notifications:** Route attention through durable, queryable records without inventing another inbox engine.
+- **Attributable revisions:** Let message owners edit their work while preserving visible history instead of erasing what was said.
+
+## Increment: Decide together
+
+Polls and explicit outcome state deepen the same Discussion rather than creating a separate decision system.
+
+**Status:** Planned
+
+**Example workflow:** A team posts a Poll in the Database Discussion, allows each person to choose up to two priorities, closes voting on Friday, records the outcome, and links directly to that result from the resulting plan.
+
+**What works today:** Comments, reactions, rich content, Database Views, and permission-aware collaboration provide pieces of the eventual interaction.
+
+**What remains:** Poll messages, bounded multi-select, stable options, closing behavior, access-safe aggregates, featured Poll rendering, and superseding outcomes still need implementation.
+
+- **Poll messages:** Use the shared rich-message grammar and remain linkable like any other Discussion item.
+- **Single or bounded multi-select:** Lets the poll author decide whether responders may choose one answer or a fixed number.
+- **Stable options:** Preserves the meaning of existing responses when wording or presentation changes.
+- **Close and freeze:** Stops new responses at a deliberate boundary and keeps the resulting aggregate inspectable.
+- **Access-safe totals:** Never leak inaccessible participants through counts or aggregates.
+- **Outcome state:** Records the current conclusion and allows a later outcome to supersede it without manufacturing a Decision object.

package/corpus/templates/content/docs/product/features/content.feature.collect-structured-input.md

@@ -0,0 +1,38 @@
+---
+record_type: "feature"
+id: "content.feature.collect-structured-input"
+number: 21
+name: "Collect structured input"
+chapter: "content.chapter.working-systems"
+order: 21
+roadmap_status: "in_validation"
+summary: "Build Forms over the same schema, validation, and submission Actions as the Database they populate."
+example_workflow: "A research team publishes an intake Form that validates required fields, lets an external participant submit without reading the Database, creates exactly one record, and triggers the Database's enrichment Rule."
+works_today: "Content already has a Form View, ordered and required questions, schema-backed controls, and an atomic Action that creates and verifies an ordinary Database record."
+remains: "Content and Agent Native Forms need one shared engine, with polished public submission, richer validation, conditional behavior, permissions, spam protection, receipts, and dependable downstream Rule handoff."
+required_capabilities:
+  [
+    "content.form.shared-engine",
+    "content.property.constraints",
+    "content.agent.action-parity",
+    "content.event.committed",
+  ]
+enhancing_capabilities: ["content.rule.deterministic", "content.job.durable"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 21: Collect structured input
+
+Build Forms over the same schema, validation, and submission Actions as the Database they populate.
+
+## Product contract
+
+- **Form View:** Saves field selection, order, presentation, and submission behavior over one Database.
+- **Shared schema:** Reuses the same Property types and validation as Agent Native Forms and ordinary record editing.
+- **Conditional fields:** Shows or requires inputs through the typed expression language rather than custom form-only logic.
+- **Submission grants:** Allow a person to submit without silently granting broad access to the underlying Database.
+- **Idempotent submission:** Prevents duplicate records when a request retries or returns ambiguously.
+- **Receipts:** Records the submitted values, actor, resulting Page, and downstream Actions the submitter may inspect.

package/corpus/templates/content/docs/product/features/content.feature.connect-your-sources.md

@@ -0,0 +1,38 @@
+---
+record_type: "feature"
+id: "content.feature.connect-your-sources"
+number: 9
+name: "Connect your sources"
+chapter: "content.chapter.connected-sources"
+order: 9
+roadmap_status: "partially_implemented"
+summary: "Choose governed native and provider Sources, preserve their identity, and compose them through Queries and Views."
+example_workflow: "A content lead connects Builder blog articles and resources, aligns their compatible fields in one Query, and works from a shared editorial View without losing which provider owns each record."
+works_today: "Content already models source-backed Databases, source fields and rows, provenance, multi-source composition, and adapters for Builder, Notion, and local material."
+remains: "Sources need one governed catalog, Queries need to replace the confusing multi-source configuration surface, and field alignment, write routing, and access behavior need end-to-end proof."
+required_capabilities:
+  [
+    "content.source.catalog",
+    "content.source.adapters",
+    "content.view.source-query",
+    "content.query.object",
+  ]
+enhancing_capabilities: ["content.source.page-link", "content.property.catalog"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 9: Connect your sources
+
+Choose governed native and provider Sources, preserve their identity, and compose them through Queries and Views.
+
+## Product contract
+
+- **Sources catalog:** Lists approved personal, workspace, and organization connections with their capabilities and policy.
+- **Provider adapters:** Give Builder, Notion, Drive, Agent Native apps, and later providers one shared contract with independent certification.
+- **Item binding:** Maps each provider item to one stable Content identity without turning the provider into the Page's owner.
+- **Typed Queries:** Combine Databases, Sources, and other Queries through one visual selection and alignment model.
+- **Provenance:** Shows where each value or representation came from and which system owns changes to it.
+- **Access-safe results:** Evaluate every result and aggregate with the current viewer's authority rather than the Query owner's.

package/corpus/templates/content/docs/product/features/content.feature.data-that-keeps-itself-right.md

@@ -0,0 +1,45 @@
+---
+record_type: "feature"
+id: "content.feature.data-that-keeps-itself-right"
+number: 13
+name: "Data that keeps itself right"
+chapter: "content.chapter.working-systems"
+order: 13
+roadmap_status: "partially_implemented"
+summary: "Use typed defaults, formulas, validation, and rendering so ordinary data stays consistent."
+example_workflow: "An operations lead creates a request Database whose defaults fill the creator and timestamp, formulas calculate cost, validation rejects an impossible quantity, and a guarded budget change explains its consequences before committing."
+works_today: "Content has a broad typed Property system, formulas and computed fields, editable values, form-required fields, audit fields, and several useful validation donors."
+remains: "Defaults, formulas, validation, conditional rendering, guarded changes, typed errors, and time semantics need one expression language and one coherent configuration surface across every Property type."
+required_capabilities:
+  [
+    "content.property.typed",
+    "content.property.constraints",
+    "content.property.guarded-change",
+    "content.expression.language",
+    "content.time.types",
+  ]
+enhancing_capabilities:
+  [
+    "content.view.dynamic-create",
+    "content.property.actor",
+    "content.expression.cached-result",
+  ]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 13: Data that keeps itself right
+
+Use typed defaults, formulas, validation, and rendering so ordinary data stays consistent.
+
+## Product contract
+
+- **Typed Properties:** Give text, numbers, choices, dates, people, relationships, files, and rich Blocks explicit behavior.
+- **Creation defaults:** Evaluate one-time typed Expressions inside the successful creation transaction.
+- **Formulas:** Derive live values from the current row and related data without storing a second truth.
+- **Validation:** Reject invalid values consistently across the interface, Actions, API, agents, imports, and Forms.
+- **Safeguards:** Add customizable consequence text, confirmation, approval, or conditional authority before sensitive changes commit.
+- **Typed errors:** Keep null, error, unavailable, and stale cached values distinct and understandable.
+- **Time semantics:** Separate Dates from timezone-aware Instants and quarantine ambiguous legacy floating times honestly.

package/corpus/templates/content/docs/product/features/content.feature.durable-foundations.md

@@ -0,0 +1,48 @@
+---
+record_type: "feature"
+id: "content.feature.durable-foundations"
+number: 1
+name: "Durable foundations"
+chapter: "content.chapter.durable-home"
+order: 1
+roadmap_status: "in_validation"
+summary: "Pages, Blocks, Databases, Search, history, and recovery form one trustworthy material loop."
+example_workflow: "A teammate creates a project brief, turns its action items into Database records with owners and due dates, closes the app, finds the work again through Search, restores an accidentally deleted Block, and asks an agent to continue from the same durable context."
+works_today: "Content already has SQL-backed Pages, rich Blocks, Databases, Search, document snapshots, and a broad agent Action surface. People and agents can perform much of the ordinary creation and editing loop on the same durable objects."
+remains: "Stable Block identity, actor-aware history, dependable recovery across every object type, and complete end-to-end action parity still need to become one polished foundation."
+required_capabilities:
+  [
+    "content.object.page",
+    "content.object.block",
+    "content.object.blocks-field",
+    "content.object.database",
+    "content.knowledge.search",
+    "content.event.committed",
+    "content.history.queryable",
+    "content.agent.action-parity",
+  ]
+enhancing_capabilities:
+  [
+    "content.version.field-history",
+    "content.property.actor",
+    "content.author.document-editor",
+  ]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 1: Durable foundations
+
+Pages, Blocks, Databases, Search, history, and recovery form one trustworthy material loop.
+
+## Product contract
+
+- **Pages:** Hold durable identity, access, properties, rich content, and the context required to resume work.
+- **Blocks:** Give every editable rich-content body the same composable grammar, whether it belongs to a Page, Property, Comment, or message.
+- **Databases:** Govern writable collections, membership, typed Properties, validation, defaults, Rules, and the canonical path for creating records.
+- **Search:** Finds only what the current person can access and opens the exact object or context they were looking for.
+- **History:** Records attributable committed Events and logical Revisions without turning every keystroke into a fake milestone.
+- **Recovery:** Restores deleted or changed work without discarding the history that explains what happened.
+- **Agent parity:** Lets agents perform the same authorized operations through the same Action surface rather than a second, weaker API.

package/corpus/templates/content/docs/product/features/content.feature.evolve-systems-safely.md

@@ -0,0 +1,38 @@
+---
+record_type: "feature"
+id: "content.feature.evolve-systems-safely"
+number: 16
+name: "Evolve systems safely"
+chapter: "content.chapter.working-systems"
+order: 16
+roadmap_status: "planned"
+summary: "Review upstream changes to adopted systems, keep local work intact, and choose what to accept or detach."
+example_workflow: "A new version of the editorial Template adds one Property and changes a Rule; each Database owner sees the impact, accepts the Property, declines the Rule, preserves local changes, and stops seeing the same declined update."
+works_today: "Version history, diff donors, stable identifiers, Templates, and source change-review machinery provide the pieces needed to compare evolving systems."
+remains: "Governed building blocks need version pinning, affected-object previews, owner-scoped adoption, selective apply and reset, remembered declines, deprecation, and safe permanent divergence."
+required_capabilities:
+  [
+    "content.template.update",
+    "content.property.catalog",
+    "content.diff.in-place",
+  ]
+enhancing_capabilities:
+  ["content.template.governance", "content.event.committed"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 16: Evolve systems safely
+
+Review upstream changes to adopted systems, keep local work intact, and choose what to accept or detach.
+
+## Product contract
+
+- **Version pinning:** Keeps each adopted Template or Custom Property on the version its owner trusts.
+- **Impact preview:** Shows affected Databases, Views, Queries, formulas, Rules, Templates, and agent workflows before publication.
+- **Three-way comparison:** Distinguishes the old shared definition, the proposed update, and local changes.
+- **Selective adoption:** Lets each owner accept compatible changes, decline others, or apply a safe batch.
+- **Quiet decline memory:** Avoids repeatedly demanding review until the upstream change materially differs.
+- **Detach to local:** Ends the shared lineage without breaking the current system or losing provenance.

package/corpus/templates/content/docs/product/features/content.feature.explore-alternatives-safely.md

@@ -0,0 +1,39 @@
+---
+record_type: "feature"
+id: "content.feature.explore-alternatives-safely"
+number: 8
+name: "Explore alternatives safely"
+chapter: "content.chapter.consensus"
+order: 8
+roadmap_status: "planned"
+summary: "Create named Versions, compare them, selectively merge them, and promote one without losing the others."
+example_workflow: "A team keeps the published article canonical while creating a private rewrite, compares the two Versions in the normal editor, selectively merges the best changes, and promotes the rewrite only when it is ready."
+works_today: "Content preserves whole-document snapshots and can restore earlier revisions, while the broader event and diff architecture establishes the lower-level history foundation."
+remains: "Named Page Versions, Version-specific access, in-place comparison, selective merge, canonical promotion, and Version-aware collaboration are still planned."
+required_capabilities:
+  [
+    "content.version.branching",
+    "content.version.field-history",
+    "content.diff.in-place",
+    "content.access.row-private",
+  ]
+enhancing_capabilities:
+  ["content.diff.filtered-review", "content.research.annotation"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 8: Explore alternatives safely
+
+Create named Versions, compare them, selectively merge them, and promote one without losing the others.
+
+## Product contract
+
+- **One stable Page:** Keeps identity, title, top-level Properties, sharing, and Discussion common across its Versions.
+- **Named Versions:** Hold deliberate alternative bodies such as a published article and a new working draft.
+- **Version-specific access:** Allows a Version to be more private than its Page, but never more broadly shared.
+- **Compare and merge:** Shows differences in the ordinary Page interface and supports selective acceptance in either direction.
+- **Canonical promotion:** Makes any authorized Version current without destroying the Version it replaces.
+- **Version context:** Quietly anchors Comments, Discussion messages, Annotations, and execution receipts to the Version being viewed.

package/corpus/templates/content/docs/product/features/content.feature.find-your-place-again.md

@@ -0,0 +1,40 @@
+---
+record_type: "feature"
+id: "content.feature.find-your-place-again"
+number: 2
+name: "Find your place again"
+chapter: "content.chapter.durable-home"
+order: 2
+roadmap_status: "partially_implemented"
+summary: "Content makes arrival, navigation, and resumption feel dependable instead of asking people to remember where they left everything."
+example_workflow: "A new teammate follows an invitation, lands in the correct organization and Workspace, pins the project they care about, and later returns directly to the exact Database View they were using."
+works_today: "Content has Personal and organization-backed spaces, Workspace navigation, invitations, sidebar structure, and saved location state in varying degrees of maturity."
+remains: "Global Home, clearer context switching, intentional pinning and dynamic sidebar sections, and reliable resumption into the exact focused View need to work as one arrival experience."
+required_capabilities:
+  [
+    "content.source.spaces-files",
+    "content.workspace.multi-scope",
+    "content.home.global",
+    "content.navigation.sidebar",
+    "content.workspace.session-restore",
+  ]
+enhancing_capabilities:
+  ["content.workspace.working-set", "content.workspace.view-instance"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 2: Find your place again
+
+Content makes arrival, navigation, and resumption feel dependable instead of asking people to remember where they left everything.
+
+## Product contract
+
+- **Home:** Gives each person a top-level view across the Personal and organization contexts they can access.
+- **Workspaces:** Organize Pages and Databases beneath Personal or an Organization without becoming the permission model themselves.
+- **Sidebar:** Pins important Pages, Databases, and Queries while allowing dynamic sections such as Recent and Shared with me.
+- **Recent work:** Restores the objects and views a person was actually using, scoped by current access.
+- **Known links and invitations:** Land on the intended object with an honest access-denied state when permission is missing.
+- **Session resumption:** Reopens enough navigation and View state to pick up the work without reconstructing the route manually.

package/corpus/templates/content/docs/product/features/content.feature.keep-your-private-vault-private.md

@@ -0,0 +1,39 @@
+---
+record_type: "feature"
+id: "content.feature.keep-your-private-vault-private"
+number: 32
+name: "Keep your private vault private"
+chapter: "content.chapter.publishing-portability"
+order: 32
+roadmap_status: "paused"
+summary: "Add user-controlled encrypted custody without abandoning collaboration, recovery, or ordinary agent workflows."
+example_workflow: "A person enrolls a trusted laptop, opens an encrypted private vault locally, grants a local agent bounded access for one task, then revokes the device without exposing the vault to the service."
+works_today: "The private-vault lane has substantial research and fork implementation history around enrollment, encrypted custody, device authorization, fail-closed behavior, and cross-architecture verification."
+remains: "The complete user product still needs audited cryptographic integration, understandable recovery and revocation, collaboration, agent access boundaries, portable exit, current-main reconciliation, and production proof. Work remains deliberately paused."
+required_capabilities:
+  [
+    "content.security.private-vault",
+    "content.agent.resource-consent",
+    "content.portability.vault-export",
+  ]
+enhancing_capabilities:
+  ["content.source.local-bridge", "content.agent.audience-safe"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 32: Keep your private vault private
+
+Add user-controlled encrypted custody without abandoning collaboration, recovery, or ordinary agent workflows.
+
+## Product contract
+
+- **End-to-end encryption:** Keeps private content unreadable to the service outside explicitly authorized plaintext boundaries.
+- **Enrollment and recovery:** Gives people understandable key setup, device addition, rotation, revocation, and recovery ceremonies.
+- **Device authority:** Lets trusted local clients decrypt only the vaults and operations they are authorized to handle.
+- **Agent access:** Makes private-vault availability explicit and bounded rather than silently handing an agent plaintext.
+- **Collaboration:** Preserves sharing, Versions, comments, and revocation without weakening the custody promise.
+- **Portable exit:** Allows the owner to export readable authorized content and keys without permanent service dependence.
+- **Paused boundary:** Retains the existing E2EE research and implementation history without claiming the complete workflow is ready.

package/corpus/templates/content/docs/product/features/content.feature.living-references.md

@@ -0,0 +1,38 @@
+---
+record_type: "feature"
+id: "content.feature.living-references"
+number: 3
+name: "Living references"
+chapter: "content.chapter.durable-home"
+order: 3
+roadmap_status: "partially_implemented"
+summary: "Reuse canonical Pages and Blocks without producing copies that quietly drift apart."
+example_workflow: "The Docs team maintains one canonical product-description Block that appears across several guides and blog posts, edits it from any occurrence, and sees every authorized location update without copy and paste."
+works_today: "Content can reference Pages, embed ordinary Database Views, and preserve multi-membership without copying canonical records. Existing reference Blocks and source-aware identities provide useful substrate."
+remains: "Stable Block references, editable Synced Blocks, canonical Page embeds, a complete Connections surface, and typed relationship behavior still need to converge."
+required_capabilities:
+  [
+    "content.object.reference",
+    "content.object.transclusion",
+    "content.knowledge.links",
+    "content.relationship.edge",
+  ]
+enhancing_capabilities: ["content.object.block", "content.version.branching"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 3: Living references
+
+Reuse canonical Pages and Blocks without producing copies that quietly drift apart.
+
+## Product contract
+
+- **References:** Link to a Page or Block as a compact mention, card, or embedded preview.
+- **Synced Blocks:** Render one canonical Block in several places and allow authorized edits from any occurrence.
+- **Embedded Pages:** Place a canonical Page inside another surface while preserving its identity and access.
+- **Backlinks and forward links:** Show where an object is mentioned and what it intentionally references through Info → Connections.
+- **Typed Relationships:** Give important connections explicit meaning that Databases, Queries, Graphs, and agents can use.
+- **Graceful degradation:** Omit inaccessible references and preserve understandable broken or deleted-reference states.

package/corpus/templates/content/docs/product/features/content.feature.make-the-workspace-yours.md

@@ -0,0 +1,40 @@
+---
+record_type: "feature"
+id: "content.feature.make-the-workspace-yours"
+number: 4
+name: "Make the workspace yours"
+chapter: "content.chapter.durable-home"
+order: 4
+roadmap_status: "partially_implemented"
+summary: "Personal arrangements and private Views reshape shared work without changing it for everyone else."
+example_workflow: "A sales leader privately filters and groups the shared customer Database around this quarter's accounts, saves that arrangement as an Only-me View, and never changes what the rest of the company sees."
+works_today: "Saved Database Views already support filtering, sorting, grouping, density, and several renderers, while the data model supports Pages belonging to multiple Databases."
+remains: "Automatic personal overrides, named Only-me Views, reusable typed Queries, and predictable pinning and sharing behavior need complete product surfaces."
+required_capabilities:
+  [
+    "content.view.query",
+    "content.query.object",
+    "content.view.personal-state",
+    "content.share.views",
+    "content.object.multi-membership",
+  ]
+enhancing_capabilities:
+  ["content.navigation.sidebar", "content.expression.language"]
+increments: []
+feature_proof: null
+publicness: "public"
+last_reviewed: "2026-07-29"
+---
+
+# Feature 4: Make the workspace yours
+
+Personal arrangements and private Views reshape shared work without changing it for everyone else.
+
+## Product contract
+
+- **Personal View changes:** Remember one person's filters, sorting, grouping, density, and presentation over a shared View.
+- **Only-me Views:** Save named private Views over shared records without forking their data.
+- **Shared Views:** Give collaborators a dependable starting presentation while preserving personal exploration.
+- **Saved Queries:** Turn reusable selection and output logic into durable Content objects that can be linked and embedded.
+- **Multiple Database memberships:** Let one Page participate in several collections without gaining a primary Database identity.
+- **Pinned navigation:** Let each person choose the working set that deserves persistent space in the sidebar.