Govern customer-specific panels

Purpose and scope

Commission bespoke Firm or Enterprise panels through a reviewed component release rather than ungoverned customer code.

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

• A signed scope and contract reference.
• Named business owner and acceptance criteria.
• Data, role and lifecycle requirements.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For govern customer-specific panels, 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

• A versioned panel definition.
• Test and acceptance evidence.
• A controlled enable, update or retirement record.

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.