Ownership
Use the app’s architecture contract and these source modules for exact current fields. The broader compatibility decoder is not the advertised current capability set.
Current tool surface
With all browser handlers bound, the current catalog exposes 13 primary definitions:
Tools can be absent when a handler, permission, source, model, or execution route is unavailable. Personal gateways have no local tool bridge. The old note/meal/biometric/supplement shortcuts and app-management definitions remain compatibility material, not additional current capabilities.
Read, project, review, commit
- Capture profile, conversation, provider/model/recipient, generation, and permission ownership.
- Read the exact permitted target. Return its current values, allowed fields and operations, and a snapshot identifier. A create read prepares the boundary for a new record.
- Validate a proposed semantic operation against that snapshot. Require supporting words from the accepted user message and a brief reason.
- Present native review cards with the before/after projection. A successful draft is still unsaved.
- On human Apply, revalidate permission, ownership, baseline and domain dependencies, then call the native persistence owner. Reject stale or unsupported operations rather than merging an arbitrary object patch.
Resource policy
getbased_read_data discovers the permitted saved-record models. Current health resources include profile facts, treatments, nutrition targets, meals, notes, manual readings, labs, genetics, Light & Sun facts and observations, and EMF records.
The current policy has 25 readable resource IDs and 22 draftable IDs. labReports, lightDevices, and lightAudits are read-only through this catalog. Whole lab-sample deletion is disallowed. Profile changes are restricted to name, sex, dob, height, and location; display-unit changes are not profile-fact edits. Nutrition presentation fields such as widgetNutrients and proteinBasis stay outside chat edits. Resource-specific validation narrows the common operations further.
The catalog does not grant application management: provider/model or profile switching, settings, backups, Sync, payments, connections, Knowledge Base administration, custom personas, live timer controls, hardware acquisition, and file selection remain native UI workflows. Retired management proposals can render as history but cannot Apply or Undo. Reading device specifications or completed sessions does not authorize device or timer administration.
Provider protocols and limits
direct-chat-tools.ts constructs the shared runtime and passes definitions through the provider facade. chat-tool-loop.ts bounds completion/tool rounds and validates native or structured tool responses. Venice’s encrypted route carries actions inside encrypted message content. A model without compatible tool or structured-output behavior can still fail; catalog presence is not live provider qualification.
Local CLI adapters carry the same definitions and return calls to the originating browser through the authenticated bridge. Schema negotiation, advertised image support, cancellation, provider errors, and stale-session rejection remain adapter responsibilities. See CLI agent providers.
If an answer affirmatively claims a prepared review without an actual turn-local draft, a bounded repair attempt can request a real proposal. Repeated unsupported claims become an explicit no-proposal result. Prose is never executed, and repair must not replay earlier successful tool calls or uncertain saves.