Agents are useful when they operate inside standing constraints. They become liabilities when they improvise standing. This concept page states the preferred pattern for agent use of accepted facts in Tinor's commercial and platform framing.

Read maintained presence first

Before answering, an agent should prefer the organization's maintained Business Presence (or equivalent Current projection) over opportunistic scraping of stale PDFs. Presence is not a brochure dump; it is a governed surface of capabilities, scopes, and statuses.

Respect disclosure audiences

Restricted diligence materials are not public capability summaries. An agent that cannot see audience tags will paraphrase annex language into open channels. That failure is catastrophic in B2B contexts. Disclosure is part of Operational State, not an afterthought filter.

Request missing materials; do not invent fillers

When evidence is absent, the correct move is often a request object — capture what was asked, by whom, for which scope — and route it through Reception. Inventing a plausible certificate number is fraud-adjacent behavior even when the model "means well."

Escalate commitments

Commercial promises, pricing, and binding language require human gates in many organizations. Business Response should make escalation the default for commitment-shaped intents, not an exception buried in a prompt paragraph.

Cite evidence class

Answers should show whether support is lab, issuer, self-declaration, or partner attestation. A single "verified" badge that collapses those classes trains partners to over-trust.

Distinguish Request Inbox from AI Reception

Signal includes Business Presence with a basic Request Inbox: humans handle intake. Pulse includes Business Response with AI-powered Reception & Response: the system assists intake and drafting under rules, still escalating where required. Conflating the two plans confuses buyers and implementers.

Inquiry boundary

Not every inbound message is a questionnaire to auto-complete. Some inquiries require refusing restricted audiences while still acknowledging the request. Some require conflict disclosure. Some require saying Unconfirmed. The inquiry boundary is part of Response design, not a prompt afterthought.

Closing pattern

Read Current → respect audience → request gaps → escalate commitments → cite evidence class. That pattern is how agents participate in commerce without rehearsing it.