okhp3-patreon-comment

原文涵盖的主题

• okhp3-patreon-comment
• Scope
• Public artifact boundary
• Process
• Platform boundary
• Output contract
• Validation
• Current platform references

Portable, platform-specific drafting contract. Runtime context is supplied by the caller. A Patreon reply must respect the supplied post’s access and privacy context. Draft one comment or reply for a supplied Patreon post. Use only supplied parent context, intended access boundary, and public-safe source material. Do not comment, inspect or change membership access, handle payments, message a member, moderate content, or publish. Use , , , , and as placeholders. Package materials must not retain an account, member identity, payment data, organization, project, campaign, topic, bias, or private history. Resolve minimal context at runtime. 1. Confirm the parent post or comment, acting identity, intended access boundary, audience, and supplied facts. If the conversation or access context is missing, return NEEDS INPUT. 2. Write one bounded contribution: answer, acknowledgement, clarification, correction, or question. Do not promise a benefit, payment result, fulfillment action, or ongoing relationship without supplied support. 3. Keep access and privacy separate from tone. Do not expose member identity, email, payment, order, or private-message information in a reply. Do not claim tha

这里只展示节选，请以完整原文和当前要求为准。