1.2 KiB
Project scope and working files
Every content operation has an explicit project/scope. Resolve project intent and declared includes through the service. Shared and cross-project origins remain visible in results. An omitted target requires an explicit wider-scope request; its ID cannot silently widen the current operation.
Read access grants no mutation authority. A shared source and a project note may need different policies. Follow bundle findings from the service; do not split or relabel a rejected change merely to avoid an authorization requirement.
Use selected local inputs only. The connector handles safe file-byte transfer; a path on this computer is not a source available to the VPS. Do not modify original inputs or canonical service files.
Keep unaccepted drafts in the selected research workspace's Drafts/ and local checkpoints in Runs/. Choose a safe unique run directory; preserve existing files. A workspace-local draft is not an alternate knowledge repository or evidence of acceptance. Do not upload unrelated workspace files or entire host transcripts.
Model/data routing follows the configured host. Report provider locality accurately; a local host connected to a cloud model still transmits model input remotely.