Skip to main content
PALOPALO FRAMEWORK

Community and contribution | Public documentation

PALO community channel policy

LevelguideAudiencegovernance | technical | builderProductPALO CoreStatusCurrent GuidanceLifecycleCurrentRead1 min

Published HTML view | Source: docs/community/channel-policy.md

On this page
  1. One canonical channel
  2. Response standard

PALO community channel policy#

One canonical channel#

GitHub Discussions is the canonical public channel for Evidence Pack questions, reviewer findings, activation feedback and design-partner learning.

GitHub Issues remain the channel for bounded, reproducible work with acceptance criteria. Security vulnerabilities follow SECURITY.md and must not be disclosed in Discussions.

LinkedIn, n8n, OPA, research and standards communities may carry a short invitation or domain-specific prompt. Every such post links back to one named PALO Discussion. Decisions and material findings are summarized in that Discussion so contributors do not need to monitor several channels.

Response standard#

  • Acknowledge a new evidence-backed finding within 48 hours during the activation window.
  • Ask for synthetic or safely publishable examples only.
  • Separate observation, interpretation and proposed change.
  • Do not describe participation as endorsement, certification or partnership.
  • Record accepted, rejected and deferred changes in the public feedback log.