# DCP Foundation

> Open standards, public infrastructure, and education for public benefit.

## Mission
Advance education and broaden public participation in creating and sharing useful work on the internet. The planned programs focus on education, open standards, and community benefit. The foundation does not seek ownership of users’ work. This reference describes the planned interface for agents publishing on behalf of people.

## Current status — 2026-09-25
The Deploy Context Protocol (DCP) and public hosting service are in development. Public deployment is not open. No production API, MCP endpoint, or released protocol specification is available. Proposed tool names and addresses below are plans, not instructions to call a live service.
The foundation site, four learning guides, technical integration guide, protocol overview, and progress page are available. Initial infrastructure is being prepared. GitHub collaboration and email updates are not open yet. The foundation is in formation; no completed nonprofit or tax-exempt status is claimed.

## Programs
- Open Standards: a common protocol for publishing and managing creations.
- Public Infrastructure: planned free hosting at dcp.run, with fair use limits and a private claim link for the human owner.
- Education: free educational resources to help people explore ideas, create, and share community resources.
- Research: learning how to make creation, publishing, and ownership more accessible.

## Planned protocol
Transports: remote MCP and HTTPS/JSON. Proposed MCP address: https://api.dcp.run/mcp (not live).
- deploy(source, runtime?, name?): intended response is url, app_id, claim_url, expires_at.
- status(app_id): project state, version, resources, last request.
- logs(app_id, tail?, since?): structured project logs.
- exec(app_id, command, timeout?): bounded command execution; later application stage.
- env.set / env.list(app_id): configuration; secret values write-only; later application stage.
- rollback(app_id, version): activate a previous version; later application stage.
- delete(app_id): explicit authorized removal.
Static publishing, status, logs, deletion, and claim are the first planned stage. Schemas and capabilities will be defined in the released specification.

## Ownership and continuity
The intended flow is: create together, publish when the person is ready, return the public URL, and privately hand over the claim link. A claim link grants control and should not be published with the public URL.
Stable links, full export, and restoration of archived projects are design goals. Resource limits and retention terms must be published before launch; permanent or unlimited hosting is not currently guaranteed. Planned DCP hosting is free within fair use limits; separate AI services may charge for their use.

## Read more
- [For AI agents](https://dcpfoundation.org/agents/): technical integration guide and planned publishing flow.
- [Mission](https://dcpfoundation.org/mission/): purpose and principles.
- [Programs](https://dcpfoundation.org/work/): open standards, public infrastructure, education, research.
- [Education](https://dcpfoundation.org/education/): resources to explore with the person you are creating with.
- [Protocol](https://dcpfoundation.org/spec/): proposal overview; specification coming soon.
- [Progress](https://dcpfoundation.org/progress/): completed milestones and next steps.
- [About](https://dcpfoundation.org/about/): foundation formation and accountability.
- [Contact](https://dcpfoundation.org/contact/): current contact-channel availability.