AGENTS.md@examples/creative-director · git:20261008.32ddd82 · 2026-10-08 · sha256 f5fa3c8e52cf5bce

AGENTS.md@examples/creative-director git:20261008.32ddd82A

Immutable. This exact content never changes and is served at /api/v1/blob/f5fa3c8e52cf5bce.

# Creative director example: scoped execution

This directory is an operational example under the root AGENTS.md and CLAUDE.md. It is not a new SIP protocol or accepted portfolio policy.

Owner: Starlight shared reference; product implementation remains with the current Registry owner. Read the current Registry and quality decision before any cross-repository work.

- Keep the kernel pure and dependency-free. No provider calls, credentials, tenant corpora, spending or publication here.
- Label fixtures and estimates; never describe a draft plan as a completed media run.
- Keep world/CreatorPack revision and context/reference hashes in semantic inputs. Layout must not change semantic cache identity.
- Draft patches cannot promote canon or approve a Creator Mission.
- Production authentication, rights, approval, operation reservation, receipts and storage belong to existing domain services.
- Preserve native agent runtime boundaries. One supervisor owns each run; workers emit typed artifacts and evidence.
- Use existing product agent profiles; team.json is a capability-routing brief, not employment or a second agent registry.
- Required check: `node --test examples/creative-director/kernel.test.mjs`; meaningful regressions must accompany kernel changes.
- For a browser projection, read the owning site's nested instructions, tokens and visual gate. Compare three in-brand directions; capture and inspect real before/after at 375/768/1440 and supported themes.
- Keep generated projections bound to the kernel and fixture digests. Do not silently fork the kernel inside each brand.
- Before opening a PR with workflow or skill changes, run the estate-guard scanner and resolve findings attributable to the change.
- Record base/candidate SHA, PR, exact checks, environment, deployment/source binding and unresolved gates. An offline example is not an npm package export or a managed SaaS capability.