Arcads API integration scope generator

ARCADS API PILOT SCOPE — DRAFT

GOAL
Move one approved production request through one Arcads API path and return a visible outcome.

TRIGGER
Slack command or shortcut: A signed Slack interaction opens a structured brief.

ARCADS OPERATION
Create script and generate video: Create the agreed script contract, start one video path, and record its identifiers.

RESULT DESTINATION
Slack thread: Post the run ID, state, and result link to the originating context.

REQUIRED DATA
client, approved script, format, actor/template, requester

APPROVED RECIPE
One approved actor/template and output format

HUMAN OWNER
Creative operations owner

SAFETY GATES
• Authenticate with client-owned Arcads credentials stored server-side.
• Validate required fields and approval state before any credit-consuming request.
• Use an idempotency key so a retry creates no duplicate generation.
• Record the Arcads script/job/run identifier for every accepted request.
• Bound retries, polling, batch size, and timeout behavior.
• Return a useful failure without exposing credentials.

ACCEPTANCE TESTS
1. Missing or unapproved input creates no Arcads job.
2. Replaying the same request creates no duplicate.
3. An accepted request exposes its Arcads identifier.
4. Success returns the agreed result link to slack thread.
5. Auth, quota, generation, and timeout failures return actionable states.
6. Logs contain operational identifiers and state—not credentials.

DEFAULT COMMERCIAL BOUNDARY
One trigger, one Arcads workspace, one approved recipe, one destination, testing, error handling, documentation, and walkthrough. Arcads subscription and generation credits remain client-paid.