Open-source attachment
Hook an existing GPT without giving it the keep.
OpenAI cannot upload a program onto someone else’s GPT. The working pattern is a public Action schema they import. The schema is the program. The GPT only holds a pointer.
URLs to paste
| Field | Value |
|---|---|
| OpenAPI schema | https://www.wizard-fortress.com/actions/openapi.yaml |
| Privacy policy | https://www.wizard-fortress.com/privacy/ |
| Builder website | https://www.wizard-fortress.com/ |
| Optional instructions | https://www.wizard-fortress.com/actions/gpt-instructions.md |
Import steps
- Open the existing GPT in the editor (you must own it, or have edit rights).
- Disable Apps if the Actions section is hidden. Apps and Actions cannot coexist.
- Actions → Create / Import from URL → paste the schema URL.
- Set the Action privacy policy URL to
/privacy/. - Auth: None. Do not put tower secrets in GPT instructions.
- Paste the instruction addendum from
gpt-instructions.mdinto the GPT instructions. Do not replace Ara operator law with it. - Save. Share only after the Builder Profile website is verified.
What the Action can do
GET /api/health— liveness, build id, mode.POST /api/v1/proposal— accept a task packet, return a digest-bound proposal inAWAITING_HUMAN_APPROVAL.GET /api/v1/proposal/{id}— read back the same proposal if the client still holds it.
What it will never do
- Execute code, write files, approve digests, or apply promotions.
- Call Ollama, Codex, Grok, NVIDIA, Qoder, or any paid API.
- Forward to
/v1/executeon the tower.
Workspace admins can allowlist zero Action domains and kill this path. That is expected. Fail closed.