Start with the boundary and the evidence.

A useful support report identifies the exact version, environment, integration path, expected behavior and observed result without exposing secrets or private evidence.

For RuleOak v0.50.0

After the public repository is available, use GitHub Issues for reproducible bugs/documentation gaps and the compatibility-report template for integration-specific behavior. Design questions and Effect Profile proposals can use the public discussion channel if enabled.

Useful diagnostics

ruleoak --version
ruleoak protect check
ruleoak protect status
ruleoak effect pending
ruleoak record verify

For source checkouts, also run npm run check:source-manifest and the relevant focused test before assuming the defect is runtime logic.

Do not post

Credentials, access tokens, signing keys, private source, raw private evidence, customer data or unredacted sensitive logs.

Security issues

Use private vulnerability reporting rather than a public support issue. See Responsible Disclosure.