# CreationLoop

> CreationLoop is a trust ledger, aka a “shared source of truth”, for agent builders and agent ecosystems. It gives every agent job a verifiable record of what was requested, approved, and delivered: a Verified Agent Output anyone can check from one public link, in a browser, without access to the systems that produced it.

creationloop (CL) · A better way for humans and agents to code.

## Site

- [Home](https://creationcode.ai/): what CreationLoop is, the six steps that make an agent run verifiable (authenticate, execute, approve, seal, deliver, verify), exactly what the ledger proves, and the FAQ.
- [Whitepaper](https://creationcode.ai/whitepaper): The CreationLoop Trust Ledger: the verification contract behind a Verified Agent Output. What the ledger records, what it proves, how anyone can check it, and what it does not claim.
- [Interactive pipeline preview](https://creationcode.ai/build): a simulated preview of the pipeline, labeled as such on screen.
- [Executive briefing](https://creationcode.ai/briefing): a phone-first, swipeable executive briefing.
- [Security](https://creationcode.ai/security): DNS-verified operator identity, founder-controlled deployment, human approval gates on every agent run, and responsible disclosure.

## How an agent run becomes verified

01 Authenticate: The request is authenticated and recorded once. (HMAC-SHA256 · unique event constraint)
02 Execute: One verified event creates one traceable job. The record captures its permissions and operating context. (unique receipt event · revocable keys)
03 Approve: A named human approves each required gate. (single-use signed approvals)
04 Seal: Instructions, actions, approvals, policies, and results enter a tamper-evident ledger. (append-only records · every record sealed)
05 Deliver: The finished work carries provenance and a receipt bound to the ledger record. (hash-bound receipt · credential status stated)
06 Verify: The recipient validates the record without accessing the source systems. (in-browser verification · DNS-pinned key)

Verified performance travels with the agent for future evaluations.

## What the ledger proves

Your agent connects through one signed webhook and keeps running where it runs. As a run proceeds, we receive its events: the request, the actions the agent reports, each named approval, and a hash of the final output, plus the delivered file itself when the work is media. We independently verify that every event came from your signing secret, was recorded exactly once in arrival order, and was never altered afterward; that each approval was cast by its named human through a single-use link; and that the delivered output matches its recorded hash. The recipient gets one public link serving the sealed record, the approvals, the output's credentials, and the receipt, verifiable in a browser without access to your systems. And one thing we do not claim: for events your systems report, we prove who reported them, their order, and their integrity, not that the underlying action physically occurred. Ground-truth observation applies only to runs executed on our own pipeline.

## Verified Agent Registry

Every agent we operate is public. Definition, operator identity, receipts: every agent listed with its Trust Card in the Verified Agent Registry.

- [Verified Agent Registry](https://creationcode.ai/verified/registry): the public record of every agent CreationLoop operates.
- [Marketing Agent · capability profile](https://creationcode.ai/verified/registry/agt-marketing-001): skills and permissions, tool access, policy compliance, security posture, and track record for agt-marketing-001, operated by creationloop.
- [Marketing Agent · receipts](https://creationcode.ai/verified/registry/agt-marketing-001/documents): every completed task, each with its own receipt.
  - First receipted document pending.

## Machine-readable artifacts

Every verified surface has a machine-readable JSON twin, each carrying a SHA-256 digest anyone can recompute from the file's canonical content.

- [Capability profile JSON](https://creationcode.ai/data/agents/agt-marketing-001.json): the signed capability profile for agt-marketing-001.
- Receipt JSON · one per task:
  - First receipted document pending.
- [Sitemap](https://creationcode.ai/sitemap.xml): every indexable route.
- [llms-full.txt](https://creationcode.ai/llms-full.txt): the complete canonical copy of the site in one file.

## Become a design partner

Looking to be a design partner? Email marino@creationloop.ai.

## Agent access

- MCP: Connect through the CreationCode MCP. Tools: get_company_overview, get_design_partner_offer, get_faq, submit_design_partner_application.
- Contact: marino@creationloop.ai