Contributing diagnostic guides through OGO POD

The hosted OGO Studio is free to explore, but complete source and private repository access require verified onboarding. Apply from the OGO™ POD section on /open-source, complete identity and intended-use review, execute the applicable source-access and contributor terms, and receive the minimum required GitHub role.

Do not create a public fork, mirror, patch archive, or build from protected source unless the accepted Community Source rules and any separately required written terms permit it.

A guide should address one recognizable operating problem with a stable evidence path. Avoid a universal guide for an entire technology domain. The pain statement should include common operator language, alerts, and symptom examples without embedding customer data.

Each question should define the evidence being requested, answer options, and next target. Branches must resolve to another step or a complete resolution. Every answer should have a meaningful consequence; decorative questions increase operator effort without improving the boundary.

Identify who can provide the evidence, who authorizes change, who performs the action, who receives escalation, and who validates recovery. Commands must include purpose, expected signals, access, and safety classification.

Run schema, graph, domain-isolation, documentation, TypeScript, and test validation. Read the guide as an operator who did not author it. Confirm that current state, next owner, safety gate, and exit proof are always understandable.

Create one focused private branch, commit only the required guide, tests, and documentation, then open a pull request through the protected repository. Respond to domain, safety, documentation, security, and maintainer review. Do not push directly to the protected default branch.

A merged guide improves the shared approved knowledge base without exposing customer information, applicant data, private platform logic, proprietary vendor procedures, or unsafe automation. Contribution rights and distribution remain governed by the accepted Community Source rules and any separately required contributor terms.