intake-boundary

Intake Boundary

Public/private boundary for visitor intake, human review and non-binding AI output.

boundary public intake

Public intake is non-binding. A visitor message can become an intake brief or proposal outline, but external follow-up, pricing, scheduling, legal terms and implementation commitments require human approval.

Allowed public source

PublicIntakeAgent may use approved public documentation only.

Blocked source

PublicIntakeAgent must not use Core documents, private workspace files, internal logs, secrets, mailbox data, calendar data or context graph data as a public answer source.

Visitor expectations

The public chat can help clarify a need. It cannot replace a signed agreement, human decision, security review or delivery plan.