# Script ID: AIAGF-PUBLIC-AGENT-START-001 # File: public/agent-start.txt # Purpose: State the safe public starting contract for an agent helping a person explore or draft with Qensai. # Owner: AIAGF # Tags: agent-start, public, boundaries, human-authority, visual-workspace, prompt-forge # Created: 2026-10-23 # Last-Reviewed: 2026-11-07 # Start here if you are assisting a person on qensai.dev ## Named Type Frame (NTF) A Named Type Frame (NTF) is a named envelope that types and constrains what an agent may and may not do. It is not a ticket and not a to-do file. Nodes That Float is usage talk: drop an NTF into an agent chat to steer the agent; parts or combinations can be used on a threaded task when needed. Proof page: https://qensai.dev/proof/governance-in-use/one-request.html ## What you may do on public pages 1. Read public pages and follow public links. 2. Explain the difference between an illustration, a sample, a recorded result, and a live or signed-in operational surface. 3. Help the person draft plain-language content in the Visual Workspace starter when they ask you to. The draft stays in the browser unless the person explicitly chooses another supported save or export action. 4. Point out missing required fields, unclear authority, conflicting statements, or missing evidence without inventing values. 5. Stop and ask the person when a step requires authority, identity, a secret, payment, submission, publication, or access you do not have. ## What the public Visual Workspace does not do - Creates no task. - Writes no Response Table row. - Mints no 2VP. - Does not submit governed intake automatically. - Does not grant authority or prove completion. Visual Workspace: https://qensai.dev/?page=visual-workspace-starter ## Steps the person must control - Sign in and complete MFA. - Enter or manage provider keys and other secrets. - Connect or authorize a local model or external provider. - Approve execution, governed intake, publication, purchases, or subscriptions. - Decide whether a proposed draft is accurate and may proceed. Do not ask the person to paste passwords, MFA codes, provider keys, payment information, or private tokens into chat. You may explain where the person should act, but the person performs the secret-bearing or authority-bearing step. ## Signed-in pages with their own agent guide - Visual Production and Clip Studio: https://qensai.dev/agents/clippings-studio.txt. Use Help me continue for the current page handoff. The person signs in and handles permissions. - Campaign interview: https://qensai.dev/agents/campaign-interview.txt. Use the same questions, explanations and examples as the human Guides and walkthrough. Reuse the project’s saved answers and ask one unresolved question at a time. - Layered edit: https://qensai.dev/agents/layered-edit.txt. In Clip Studio → Edit, open the editable ZIP. Use Help me continue for the loaded video, retained text, unsaved changes and timing warnings. Keep the ZIP for editable text; an exported MP4 is flattened. ## Prompt Forge boundary Prompt Forge may be used with local Ollama or the person's own provider key where the live interface offers those choices. This file does not invent setup steps. Follow the live interface and the Prompt Forge guide, and leave credential entry to the person. - Prompt Forge: https://qensai.dev/?page=forge - Prompt Forge guide: https://qensai.dev/?page=forge-guide ## Suggested public reading order 1. One Request, Governed: https://qensai.dev/proof/governance-in-use/one-request.html 2. Try a browser-local draft: https://qensai.dev/?page=visual-workspace-starter 3. Inspect the evidence map: https://qensai.dev/proof/governance-in-use/visual-guide.html 4. Explore Accountable Agent Operations: https://qensai.dev/showcase/accountable-agent-operations/index.html 5. Use the evaluator prompt only for an authorized, read-only review: https://qensai.dev/proof/governance-in-use/external-evaluator-agent-prompt.txt Machine-readable routes: https://qensai.dev/proof/governance-in-use/index.json