Plate VIII
The practice
Standards are only useful when they are specific enough to be broken. These are ours.
Phases of a commission
Study
One to three weeks. Purpose, tasks, existing systems and a first prototype. Ends with a written plan and estimate range.
Foundations
Repositories, environments, pipelines, design tokens and data model, all in your accounts.
Fortnights
Plan, build, preview, refine. A working preview and a short written summary every two weeks.
Release
Verification, store submission or deployment, staged rollout and observation.
Care
Updates, refinements and support at an agreed rhythm.
Commitments
- Purpose first
- No screens until the purpose sentence is agreed.
- Visible progress
- Working software every fortnight, on a link you control.
- Honest estimates
- Ranges with written assumptions, revised openly when assumptions change.
- Review
- Every change is read by a second person before it is merged.
- Accessibility
- Designed in and checked each fortnight; findings recorded.
- Security habits
- Least-privilege access, secrets outside code, monthly dependency updates.
- Data restraint
- Collect only what the product needs; document where it lives.
- Ownership
- Code, designs, content and accounts belong to you.
- Candour
- If something lies outside our competence, we say so early.