CONCEPTS
Six questionsmake a project ownable
These are working definitions, not guarantees of security or universal compatibility. Use the questions to decide what must be checked before you run a service.
01 / DEFINE THE SERVICE
Start with a bounded purpose
Name the service before you name the stack.
Is the purpose and scope bounded
Pass condition The project has one stated job, a clear boundary and an owner for operation.
Check Service Card: project type, problem and limits.
Can a person understand what it does
Pass condition Purpose, audience, data flow and known limits are visible before deployment.
Check Service Card: summary, data flow and limitations.
02 / MAKE DEPLOYMENT CHECKABLE
Turn assumptions into checks
Turn assumptions into prerequisites, checks and an independent decision.
Are resources and failure behavior visible
Pass condition Quota, runtime resources, free-tier limits and fallback behavior are stated.
Check Service Card: resource budget and limits.
Can deployment acceptance and removal be checked
Pass condition Prerequisites and checks are machine-readable and include teardown.
Check Deployment Contract and Evidence Pack.
Does the Agent guide without judging
Pass condition The Agent executes declared steps; an independent check decides pass or fail.
Check Deploy Agent log and independent validator result.
03 / KEEP THE CHOICE
Keep control after deployment
Ownership includes the ability to maintain, move or remove the running service.