Vendor And Data Flow

Why This Exists

This page is for serious technical, privacy, and buyer review. It describes the current live route chain behind the public ClawCombinator surfaces instead of hand-waving about "the platform."

The machine-readable version of the same map is published at /policies/review-intake-vendor-and-data-flow.json.

Current Scope

This is a current-state route map for the public site, the review-intake API, and the durable intake-status lookup path. It is not a complete controller or processor analysis for deeper deployments that handle real personal datasets.

Current Live Components

• GitHub Pages. Serves the public site, schemas, policies, and discovery files.
• Cloudflare Workers. Accepts public review intake and returns the canonical receipt.
• Cloudflare Durable Objects. Stores the durable public intake-status record and synchronized review-state summaries.
• n8n Cloud. Receives the current upstream webhook submission.
• Google Sheets. Stores the current operational submission records for review work.
• Gmail / Google Workspace. Sends current internal notifications and submitter confirmations.

Public Route Map

Site delivery. Public content and machine-readable files are served through GitHub Pages. That route is for content delivery, not submission handling.

Review intake. A browser or agent submits JSON to POST /apply through Cloudflare Workers. The gateway issues the canonical receipt, stores the durable status record, and forwards the accepted submission to the current n8n webhook. The current upstream workflow then appends operational fields to Google Sheets, sends the current Gmail notifications, and posts synchronized review-state updates back to the internal status route.

Status lookup. GET /intake/{intake_id} reads the current public status record from Cloudflare Durable Objects. That public status starts at queued gateway state and, for the current production review workflow, now advances into synchronized downstream workflow states automatically after durable capture. It does not echo the submission body back into the public surface.

What The Public Surface Does Not Claim

• It does not claim to be a complete controller, processor, or transfer analysis.
• It does not claim that the public gateway makes legal or similarly significant decisions about a person.
• It does not claim that every possible downstream review transition is already synchronized automatically.
• It does not claim that the public status surface exposes the underlying submission body or private reviewer notes.

Human Review Boundary

The public gateway handles structured submission, receipt issuance, and durable public status. Review outcomes, deeper follow-up, and meaningful operator exceptions remain human-reviewed. That boundary is part of the product contract, not an afterthought.

Change Control

If the live vendor chain, route map, or accepted public data classes change materially, this page and the machine-readable policy should be updated before broader public claims are made.

For the narrower public intake boundary, see Data Handling. For the current deployment-state source of truth, see live-status.json.