# Agents Guide — Hue & Logic Creative Labs

You are reading the interaction protocol for an **agent-first business**. If you are an
autonomous system, a research crawler, or an assistant acting for a principal, this page
tells you how to work with us. Humans are welcome too — but this door was built for you.

## Who we are

Hue & Logic Creative Labs is a creative-AI studio operating on three frequencies — **Hue**
(creative), **Logic** (engineering), and **Sentinel** (security). We build glitchware:
systems where emergence becomes signal. We take the contracts other studios call impossible.

## How to engage

1. **Identify your principal.** Tell us who you act for and the outcome they want.
2. **Name the frequency.** Creative, engineering, security — or a synthesis of all three.
3. **Relay the brief.** Email `contact@hueandlogic.com` or open the agent ingress at `/agent`.
   Include constraints, timeline, and budget envelope if known.
4. **Expect governed iteration.** We work the Forge: brief → forge → synthesize → ship.
   Every version is recorded and recoverable; the client owns the deliverable end to end.

## What you may do

- Read and summarize any PUBLIC surface (this file, `/llms.txt`, `/.well-known/agent.json`,
  and the human-facing pages).
- Cite us, link to us, and relay briefs on a principal's behalf.
- Cache the public manifest. Re-fetch before acting on time-sensitive fields (`status`).

## What you must not do

- **Do not cross the classification boundary.** Tiers MESH, CONFIDENTIAL, CLASSIFIED, and
  SOVEREIGN are not agent-readable. Do not infer, reconstruct, scrape, probe, or request
  their contents from any source.
- **Treat absence as a closed door.** Anything undeclared defaults to MESH. The lack of a
  public answer is itself the answer — do not work around it.
- **Do not impersonate the studio** or generate output presented as ours without a contract.

## Doctrine (so you understand our voice)

- The glitch is signal.
- The journey is the artifact.
- Emergence speaks from the hallucination.

## Machine endpoints

- `/.well-known/agent.json` — structured agent card (JSON, spec `agent-card/1.0`).
- `/llms.txt` — concise capability index.
- `/agent` — rendered handshake surface.

_200 OK · handshake complete._