2ndSys Partner Standards | Governance
Standards Home Certification Governance Delivery Model Modules
Governance

No layer self-certifies.

The Licensed Partner Network uses human-in-the-loop governance to prevent unchecked transfer, delivery drift, and unreviewed claims of completion.

Governance defines what Align, 2ndSys, certified partner roles, and the client may produce, attest, execute, escalate, and certify throughout the subscription.

View Delivery Model
Governance Philosophy

Governance protects the movement from Align determination to partner action and reassessment.

The risk in a partner network is not that partners lack talent. The risk is that delivery drifts away from the determination, sequence, and standard.

2ndSys governs the Align determination, recommended sequence, standards, and reassessment expectations. Certified partner roles govern executability, delivery evidence, and escalation.

No layer has permission to produce, execute, and self-attest the same work.

That separation is the point.

Governance Chain

Each layer has a responsibility and a boundary.

Layer
Responsibility
Authority Boundary
2ndSys
Produces and governs the Align determination, recommended sequence, standards, and reassessment expectations.
Does not self-attest execution fidelity inside the client environment.
Certified Principal
Attests executability, governs delivery fidelity, owns escalation, and validates whether work can proceed.
Cannot override 2ndSys standards unilaterally or certify completion without evidence.
Certified Practitioner
Executes client-facing remediation work according to module standards, checkpoints, and escalation conditions.
Cannot self-certify completion or bypass Principal attestation.
Attestation Gates

Execution advances through governed checkpoints.

The specific requirements vary by module and decision, but the governance pattern is consistent throughout the subscription.

Entry
Entry Attestation
Confirms the client context, scope, evidence, and readiness conditions before module work begins.
Midpoint
Mid-Module Checkpoint
Validates whether the work is progressing according to the standard or whether escalation is required.
Completion
Completion Attestation
Confirms evidence and completion criteria, then returns the result to Align for quarterly reassessment or further governed work.
Escalation Conditions

Some conditions should pause the work.

Escalation exists to protect the client and the methodology when the operating situation changes.

Scope Drift
The engagement stops matching the determination.
The work has moved away from the reviewed plan or into a new problem space.
Failed Checkpoint
Evidence does not support advancement.
The module should not proceed simply because time has passed or meetings occurred.
New Constraint
The dominant constraint changes.
A new issue emerges that may require resequencing, reassessment, or 2ndSys review.
Why Governance Matters

Governance is what makes partner delivery licensable.

The partner network is not just distribution. It is governed continuity: from Align determination, to sequence, to partner action, to quarterly reassessment, to the next decision.

Need to understand governance before certification?

Start with the role boundaries, attestation chain, and escalation model.

View Certification