Protected Staging Intake
Submit real text material into APCP's protected staging path, store it as a staged artifact, and receive a dry-run destination plan. Production is intentionally blocked for this flow until we choose to cross that boundary.
1Paste textMarkdown, text, JSON, or small code snippets up to 65536 bytes.
2Plan onlyTarget planning is dry-run and shows approvals plus setup gaps.
3Submit to stagingRequires MANIFEST_WRITE_TOKEN and stores text in R2 plus manifest state in D1.
4Attach afterOptional attachment upload is unlocked only after a staging manifest exists.
Material
This production Worker refuses real intake. Use https://agent-publish-control-plane-staging.fkurka.workers.dev/operator/intake.
Boundaries
production production hard stop
Requires MANIFEST_WRITE_TOKEN or a trusted Access membership with manifest write permission.
No publish runs are created. No provider is called. No here.now, GitHub release, social post, or deployment is triggered.
Text limit: 65536 bytes. Attachment limit: 2097152 bytes.
Result
No protected intake request has run.
Attachment After Text
Upload is disabled until a text intake manifest exists. This keeps file intake tied to a reviewed manifest record.
Submit text first, then select an attachment up to 2097152 bytes.
Target Plan
No target plan loaded yet.