Constraints and permissions
These rules apply to every harness, reader, capture adapter, and future integration.
Canonical sources: AGENTS.md, skill/SKILL.md, and authenticated sources
Non-negotiable rules#
- Preserve
inspect -> preview -> read. - Never read browser credentials, cookies, storage, or secrets.
- Never infer approval from an API key, backend choice, prior run, or browser permission.
- Keep local processing as the default.
- Require separate, current approvals for cloud transfer and a first model download.
- Use
read-videoonly as documented backward compatibility; new users start with Voidscape. - Preserve upstream attribution in
CREDITS.md. - Do not describe a design, local edit, or prototype as shipped.
Permission owners#
| Permission | Owner | Voidscape behavior |
|---|---|---|
| Browser site/tab access | Harness and user | Accept only the selected URL or saved local capture |
| OS screen recording | OS, user, optional capture tool | Read the resulting local file after normal preview |
| CLI account access | User | Read only the explicit READ_VIDEO_YTDLP_COOKIES file path when configured |
| Cloud transcription | Voidscape per-job gate | Stop until --allow-cloud is explicitly approved |
| Local model download | Voidscape per-job gate | Stop until --allow-model-download is explicitly approved |
| Installs | User/agent workflow | Report missing dependencies; do not silently install |
Browser approval never authorizes cloud spend or model downloads. CLI cookie configuration never authorizes the bridge or harness to inspect browser storage.
Data and citation honesty#
- Never expose secret values or private collection URLs in logs, docs, evidence, or tool results.
- Use a fresh, empty workdir for each evidence run; readers reject unsafe reuse.
- Cite
[image N],[MM:SS],[article N], or[entry N]exactly as the manifest defines. - Say when evidence is absent, static, incomplete, or lower-confidence.
- Do not claim to have watched or read material outside the produced bundle.
Explicitly unsupported#
- Automatic browser-cookie or storage export
- Raw browser
evalas a default integration tool - A production universal browser bridge
- A production MCP host
- An unattended scheduler or autonomous retry loop that adds approval flags
- Universal compatibility claims across all models or harnesses
Those items remain absent unless a later implementation and security review explicitly ships them.