How we work — rules of our own practice
- Status
- Review
- Version
- 0.1.1
- Authority
- UASK standard
- Applies to
- Core
Summary
These are the rules of our own practice that no other Hub item holds: how we borrow methods, protect the owner’s
time, keep development and support apart, work on client sites, keep logs and cases, and handle privacy and public
material. They come from the owner’s written instructions and from how we already work on client sites. The document
process.how-we-do summarises them in plain words; this item is their one home, with the keywords of RFC 2119.
Rules
- R1. A method we adopt MUST be borrowed from established practice where one exists, and MUST name the source it follows and say where it differs and why. (Owner, 2026-11-22.)
- R2. A rule that can be checked by a machine SHOULD have an automatic check.
- R3. Every job MUST leave an asset behind: a case, an improved procedure or a new check. A job that leaves only an invoice is only half done.
- R4. We MUST use our own method on our own work, and a foundation MUST be built one step at a time, each step reviewed by someone who did not write it before the next starts.
- R5. Each part of the method MUST belong to one lifecycle phase and to one document or record it produces, and MUST NOT require our interface or system frameworks; it MAY list them as related.
- R6. A question MUST go to the owner only in the cases of
mgmt.roles-and-decision-rights#R12, and it MUST carry a default; a request outside the current step MUST be parked in a “later” list and offered as “now, which moves the plan” or “later”. (Owner, 2026-11-20 and 2026-11-21.) - R7. Whether a piece of work is development or support MUST be decided by the owner; one site MAY be in several projects at once. (Owner, 2026-09-27.)
- R8. We work through AI agents under human direction; a design SHOULD be chosen by what keeps agents consistent and cheap to run: one stack, Git and review, data in files first. (Owner, 2026-11-20.)
- R9. Development and support MUST be run as different work. A new site MUST move to support only when it is handed over and the client has a support service; a site already in support MUST NOT move, and the development work closes there. (Owner, 2026-09-26 and 2026-09-27.)
- R10. Stages MUST run in order. A step never done for real MUST be marked “not verified” and rewritten after its first real run. Every job MUST have one visible status, and “blocked” MUST say what it waits for; every job MUST have one folder, and every project a card with what is missing and its risks.
- R11. Before any date is promised, the whole request MUST be read and the existing system MUST be snapshotted read-only; a gap between the request and the offer MUST be raised before work starts.
- R12. A large job MUST be cut into stages, each with its own plan and acceptance. A plan MUST say what we do, what we do not do, the target versions as numbers, checkable criteria and, for a live site, the work window.
- R13. On a client’s platform, a picture from the client MUST be treated as an idea, not a specification: the platform’s own settings MUST come first, then its standard parts, then styles; our own code or template changes MAY be used only when nothing else works, with the reason recorded. (Owner, 2026-09-27.)
- R14. A customisation MUST be packaged, switchable and safe across platform updates, MUST hold no client values in code, and MUST be checked against the next update and by someone who did not write it. The choice of platform MUST be recorded with its reasons, and third-party distributions MUST be kept with a checksum and their licence.
- R15. The log of a job MUST be written the same day: what was done, what broke and how it was fixed.
- R16. A change to a site SHOULD be scripted so it can be re-applied by one command, with a snapshot of the settings before and after; a manual edit by the owner MUST be carried into the script.
- R17. The look of a site MUST be checked on screenshots at desktop and phone widths, across every menu link, with the error log read after each, and a reviewer without the builder’s context SHOULD do a pass before hand-over.
- R18. A test with real side effects (an order, an email, an exchange with another system) MUST run only with the owner. Machine-generated content MUST be treated as a draft until checked: a pipeline MUST first be measured on a sample against known truth, and images MUST be checked for rights.
- R19. A site under construction MUST be closed by a password, served over HTTPS and marked not to be indexed before anything is uploaded, until launch. (Owner, 2026-09-27.)
- R20. A new site MUST be backed up right after the platform is installed and again before its first deployment; backups MUST sit outside the web root and be checked for integrity, with a manifest and checksums. (Owner, 2026-09-27.)
- R21. Acceptance MUST follow the written criteria, and a launch MUST follow a checklist.
- R22. Copies of code, database dumps and old backups MUST NOT be left in a web root.
- R23. Every entry in our knowledge base or a playbook MUST have a real case behind it, with its project and date.
- R24. Before work starts, we MUST look for where we did something similar. (Owner, 2026-09-26.)
- R25. A closed job MUST leave a case with its numbers before and after and the time it took; past cases SHOULD be the basis of estimates.
- R26. Long procedures MUST live in playbooks; an agent skill SHOULD stay short enough to read in a minute and MUST point to the playbook.
- R27. A site worked on by several projects MUST keep one shared notes file, hidden from the public; a client MAY see a project page and documents for approval only through a private link. (Owner, 2026-09-27.)
- R28. An agent session MUST NOT start without a plan item it serves, and the owner MUST get short, regular summaries: the stage, done against plan, what waits for the owner, what is frozen. (Owner, 2026-11-21.)
- R29. Credentials received in a chat MUST be moved to protected storage at once and changed as soon as key access works; the chat counts as exposed.
- R30. Requests sent through our site’s form MUST be kept for at most one month, then deleted. (Owner, 2026-11-22.)
- R31. A public example MUST be made up or come from a UK project without client data.
- R32. Public material MUST NOT name a market, client, tool, domain or currency from a market the owner has excluded. (Owner, 2026-11-20.)
- R33. Our brand MUST be the mark alone, our texts MUST say “we”, and the only use allowed without permission is the unchanged mark linking to our site. (Owner, 2026-11-20.)
- R34. The languages of each section MUST be the owner’s choice; English MUST be the source language. (Owner, 2026-11-22.)
Guidance
These rules are the “not yet approved” part of process.how-we-do: the owner’s yes to that document approves this item
with it. A rule here may later move into a more specific item; it then keeps its meaning, and the summary in
process.how-we-do changes its home in the same pull request.
The dates in brackets are the owner’s written instructions the rule comes from. Rules without a date come from how we already work on client sites.
Explanation
The Hub holds most of our rules in items that follow established methods. Some rules have no such home: they are how we
run our own work, or what the owner told us to do. Without one home they would live only in our working notes, which
are not part of the Hub. This item gives them that home, so that every rule of process.how-we-do can be cited and
checked.
Examples
A good use: an agent asked to make a sales page names no excluded market, keeps the request as sent, and logs the same day what broke (R32, R15). A bad use: a builder edits a theme file on a live client site to match a picture, with no script and no reason recorded (R13, R16).
Sources
- GOV.UK Service Standard — Open Government Licence v3.0. The idea of borrowing a published standard and naming it (R1). Accessed 2026-11-22.
- Basecamp, Shape Up — all rights reserved; linked only. Fixed time budgets and stages of a job (R12). Accessed 2026-11-22.
- ICO, UK GDPR guidance: storage limitation — Open Government Licence v3.0. Keeping personal data no longer than needed (R30). Accessed 2026-11-22.
- Google Search Central: block search indexing with noindex — CC BY 4.0. Keeping a site under construction out of search results (R19). Accessed 2026-11-22.