Use the documentation conventions

Purpose and scope

Navigate categories, search terms, versions, review dates, related guides, access labels and downloadable copies consistently.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• The task or subject being researched.
• The product and access context.
• The visible guide version and review date.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For use the documentation conventions, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• The correct guide and section.
• A reliable source reference.
• Feedback where content is unclear or stale.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.