agentkit-hybrid-cloud-demo

AgentKit Hybrid Cloud Demo

Operating contract

1. Treat README.md as the customer-facing source of truth. Read the requested step and its linked document before acting.
2. Start from a clean validation directory. Preserve unrelated or pre-existing changes.
3. Execute steps in README order unless the user names one specific step. Do not silently skip a failed prerequisite.
4. Prefer the repository scripts over reconstructed commands:
   • Human-guided Base Runtime: scripts/deploy_interactive.sh
   • Non-interactive/CI Base Runtime: scripts/deploy_hybrid.sh
   • Resource association and release: scripts/bootstrap_platform.py
   • Knowledge/Memory proof: scripts/verify_knowledge_memory.py
   • Local guide and Chat UI: scripts/run_local_ui.sh
5. Perform safe read-only discovery automatically. Stop for genuine human-only actions such as hosts/DNS changes requiring administrator access, console account switching, model selection, uploading documents, obtaining temporary credentials, or production authorization changes.
6. Never write or print AK/SK, passwords, Runtime API Keys, model keys, temporary Registry tokens, Bearer tokens, or injected component credentials. Use placeholders in docs and commands.
7. After each step, report:
   • action and evidence;
   • pass, fail, partial, or blocked;
   • required human action;
   • README/FAQ defect found and the minimal proposed update.

Mandatory safety and validation

• Verify ${AGENTKIT_OPENAPI_SCHEME:-http}://${AGENTKIT_OPENAPI_HOST}/ping before deployment. This delivered POC defaults to HTTP; honor an explicit HTTPS setting with normal certificate validation. Never make curl -k the customer solution, and clearly distinguish the POC HTTP default from a production HTTPS requirement.
• Default customer deployment to live. For the sample's default Ark profile, require MODEL_AGENT_API_KEY and resolve the documented default Model Name/API Base. For a custom or real environment, honor explicit API Base, Model Name, and API Key overrides. Inject all three resolved values during launch, fail clearly when the key is absent, and never silently downgrade to demo. Use AGENTKIT_DEPLOY_MODE=demo only when the user explicitly authorizes an infrastructure-only fallback, and label that result incomplete.
• Keep model values out of the public config, project .env, Git, Docker build context, logs, and prompts. Use the deployment script's transient 0600 config or a platform Runtime Secret.
• Do not manually docker pull or proactively require docker login. If agentkit launch actually returns token expired, unauthorized, invalid token claims, or authentication required, stop and explicitly guide the user to refresh the target Registry's temporary docker login, confirm Login Succeeded, and rerun launch. This manual login is the required recovery path after an observed authentication failure, not a prohibited action. Never ask the user to paste the token into chat or save it in the repository.
• Never silently reuse a global Region for Runtime creation. Require the user to confirm VOLCENGINE_REGION, preferably through scripts/deploy_interactive.sh; show any detected global value only as a hint.
• Before launch, detect an exact same-name Runtime in the confirmed Region. In an interactive session, ask whether to update that Runtime or enter a new unique name; check the new name before creation and never silently overwrite. In automation, require an explicit AGENTKIT_RUNTIME_ID or reuse authorization. Persist only the non-secret launch_types.hybrid.runtime_name and runtime_id after a successful launch so later runs update rather than hit InvalidParameter.DuplicateName; keep endpoint and API/model keys transient.
• Treat scripts/deploy_interactive.sh as the single first-deployment entry point for a human. It may reuse a confirmed existing CLI target or collect OpenAPI scheme/host, hidden AK/SK, Region, model profile, and hidden model key interactively. Do not require users to prepare exports or an Agent Prompt for this first deployment. After it succeeds, route later validation and capability work through the roadmap Prompts, which load this project Skill.
• Build and publish linux/amd64, including from Apple Silicon.
• Treat agentkit launch output as insufficient proof. Require Runtime Ready, service RUNNING, health Healthy, and a successful /invoke.
• Distinguish connection transport from Agent data mode: transport=remote, mode=demo proves the remote Runtime was called but still uses the deterministic demo; only transport=remote, mode=live proves the live Agent data plane handled the request.
• After runtime update, run runtime release and wait for Ready/Healthy.
• List platform resources with explicitly limited non-sensitive fields. Never dump full Tool JSON or environment variables.
• Do not delete, destroy, reset, or overwrite resources unless the user explicitly authorizes the exact target.