Repo and stack
The guidance reflects the application, framework, CI, release habits, and maintenance reality in front of the team.
Customer Front Door operating model
Make governed PR review the way your team works.
Customer Front Door adapts the governed PR spine to your repo, stack, review process, playbooks, gates, and risk profile after a useful Starter Front Door proof.
SDF structures evidence and review. Your team keeps approval, merge, deployment, and product judgement.
What it is
Customer Front Door is the local operating model for governed PR work.
Starter Front Door proves the workflow on one bounded PR. Customer Front Door keeps the useful parts and adapts them to how your team reviews, verifies, hands over, and decides on work.
The aim is a repeatable decision surface: intent, acceptance criteria, verification truth, evidence, risk, limits, and human review.
Review process
Reviewer expectations, approval paths, handoff notes, and merge ownership stay explicit.
Playbooks and overlays
Portable SDF guidance is layered with customer-specific engineering, product, security, and risk rules.
Gates and conventions
Acceptance criteria, verification expectations, evidence records, and PR body shape become repeatable.
Risk profile
Evidence depth scales with risk while the review gate and non-claims stay fixed.
Claim boundaries
The model records what was checked and what remains outside the claim.
After Starter Front Door
After one useful proof, keep what worked.
The first governed PR answers a practical question: can this team review AI-assisted work with enough context to decide well?
If yes, keep the useful parts, adapt the weak spots, and make the model visible enough that future PRs do not restart from scratch.
Keep the proof object
The governed PR becomes the reference for scope, evidence, verification truth, risks, limits, and reviewer focus.
Name the local rules
The customer-specific playbooks, overlays, gates, conventions, and handoff habits become explicit.
Set review expectations
Reviewers see what evidence to expect, what judgement remains theirs, and where approval or merge decisions sit.
Choose the next scope carefully
Expansion follows the evidence from the proof; it does not imply arbitrary repo coverage or automatic enforcement.
Where buyers enter
The path depends on what has already been proved.
Customer Front Door comes after a useful proof. Earlier buyers should go back to readiness, assessment, or one bounded Starter Front Door proof.
1
Not ready yet
Start with the free readiness check or paid readiness assessment when fit, scope, review ownership, or evidence is still unclear.
2
Ready to prove
Use Starter Front Door for one safe, bounded governed PR proof with acceptance criteria, verification truth, evidence, risk notes, limits, and human review.
3
Ready to adapt
When the proof is useful, shape Customer Front Door around the repo, stack, review process, playbooks, gates, conventions, and risk profile.
Recurring support
Keep the operating model useful as the repo and team change.
Governance gets stale if it is treated as a one-time setup. Recurring support keeps Customer Front Door aligned with real delivery work, new risks, and reviewer feedback.
Support is assisted and review-led. It keeps evidence and decisions visible; it does not approve, merge, deploy, repair, enforce, or optimise policy automatically.
Workflow support
Help teams keep governed PR habits usable inside their existing review rhythm.
Playbook updates
Refresh local overlays when the stack, product boundaries, or review expectations change.
Evidence review
Inspect whether PR evidence is still useful, honest, and proportionate to risk.
Assessment refreshes
Revisit readiness and blockers as the repo or team maturity changes.
Scoped onboarding
Bring additional repos or teams into the model only where evidence and review ownership support it.
Maturity progression
Turn reviewed lessons into clearer guidance without claiming autonomous learning or automatic governance.
Boundaries
Reviewable delivery, not automatic governance.
Customer Front Door is customer-specific operating guidance around the governed PR spine. It is not hosted enforcement, production governance, a self-serve scanner, or a shipped Managed SDF profile.
SDF records delivery evidence. It does not certify correctness, prove savings, provide billing-grade cost data, approve, merge, deploy, repair, or enforce automatically.
Customer-owned decisions
Humans decide whether to approve, merge, deploy, and expand the workflow.
Verification truth
Checks are reported as passed, failed, blocked, or unavailable. Evidence is not a guarantee of correctness.
Scoped expansion
New repos, teams, and risk areas are added only where the evidence and review ownership support it.
Next step
Start where the evidence says to start.
If you have not proved the workflow yet, begin with readiness.
If one bounded PR is already clear, the proof pilot can show whether Customer Front Door is worth shaping around your team.