Evidence before claims
Important statements are connected to a source, classified honestly and kept separate from assumptions.
Trust and Governance
Trust should be designed in, not added later
Practical AI is useful only when the business can understand the evidence, control important actions and remain responsible for the customer experience.
GDP defines responsibilities, permissions and limitations before capability expands.
Four working principles
Clear boundaries create useful confidence
Permission before action
Access to information does not automatically authorise messages, changes, publication or commitments.
Control grows with capability
The greater the possible consequence, the stronger the testing, approval, access and recovery controls should be.
Human responsibility remains visible
People retain responsibility for consequential judgement, exceptions and the promises made to customers.
Evidence classification
Evidence is clearer when different kinds of knowledge stay separate
GDP does not turn an uncertain observation into a confident claim simply because it sounds persuasive.
Verified fact
Supported by an identified source and checked for the purpose at hand.
Sourced observation
Something directly visible in a named record, page, report or customer feedback source.
Reasonable interpretation
A conclusion drawn from available evidence and clearly presented as an interpretation.
Needs confirmation
A missing, conflicting or time-sensitive detail that should not be guessed.
Human approval boundaries
Knowing something is not the same as being allowed to act on it
Every workflow uses the same five authority levels.
Privacy and retention
Use only what the work requires
Customer and business information should have a defined purpose, appropriate consent, limited availability and a considered retention period. Information should not quietly become available for unrelated future uses.
GDP begins with least-necessary access and expands it only when a clearly approved capability requires more.
Security proportionate to capability
Security grows with capability
A read-only report does not create the same risk as a system that can contact customers, make bookings or change a public resource. Controls should match the possible consequence.
This may include restricted accounts, narrowly permitted tools, client separation, confirmation of recipients and destinations, activity records and periodic access review.
Business ownership and portability
Your information and deliverables remain business assets
GDP provides clear documentation, copies of commissioned deliverables and available export or handover information. We distinguish information owned by the business from settings or features controlled by a platform.
We do not describe a system as portable when practical recovery or transfer is not supported.
Supplier and platform transparency
You should know what your solution depends on
AI models, messaging services, hosting providers and business platforms can have their own limits, costs, policies and availability. Material dependencies should be disclosed rather than hidden behind GDP branding.
If a supplier changes an important capability, the effect on the business should be assessed before the workflow is presented as dependable.
Activity records, recovery and handover
A useful system should leave an understandable trail
Where the selected platform allows it, important activity should be recorded so the business can understand what occurred, what information was used and whether a person approved the action.
Instructions and configurations should be versioned where practical. Recovery, fallback and handover arrangements should reflect the importance of the workflow rather than being considered only after something fails.
No quiet expansion. New information sources, recipients, actions or authority require their own consideration and approval.
Honest limitations
Useful work without unsupported promises
GDP can improve the quality, consistency and usefulness of business information, customer proof and workflows. We do not guarantee rankings, enquiries or revenue, and we do not claim that every platform will display, distribute or interpret information in the same way.
Unresolved matters and material limitations should remain visible.
Accessibility
Useful systems should remain usable by real people
Public pages and customer experiences should use clear language, readable presentation, meaningful structure and practical alternatives where a particular channel or method cannot be used.
Accessibility needs are considered alongside privacy, security and customer care rather than treated as a decorative final check.
See the work before making a major commitment
A Private Preview lets you examine GDP's approach with your confirmed business details before any live connection, public change or production authority is considered.