Truthful claims
Say what is known, name what is not, and do not inflate ordinary work into a larger promise.
MethodCo / Public operating commitments
The Standard
Everything MethodCo publishes, teaches, builds, serves, and sells should be useful, clearly presented, fairly offered, and reviewed before release.
Useful output
Publish, teach, build, serve, or sell something that makes a real task clearer or better.
Fair terms
Make price, access, cancellation, delivery, and important conditions understandable before commitment.
Clear scope
Define the result, boundaries, exclusions, ownership, and review points before work begins.
Quality control
Review material and systems before release, then maintain what remains public.
Responsible automation
Use automation to reduce repeat work while preserving review, accountability, privacy, and human judgment.
No pressure tricks
No false countdowns, manufactured urgency, hidden opt-ins, or shame-based persuasion.
No hidden fees
A stated price should not become a different obligation later through avoidable surprise charges.
No fake expertise
Do not claim credentials, authority, customers, results, or experience that do not exist.
No careless work
Do not release work merely because a tool made it fast. Speed does not replace review.
Honest limitations
Name unavailable features, uncertain timing, excluded work, and the boundary of support.
Corrections
Correct material errors plainly and improve the system that allowed them through.
Automation
Assistance can be automated. Responsibility stays visible.
Automated systems may organize, summarize, draft, check, route, or repeat agreed work.
Important claims, unusual requests, customer promises, sensitive information, and consequential decisions require an appropriate human review boundary.
When MethodCo is wrong
Corrections should be plain, proportionate, and useful.
Material public errors should be corrected where they appeared. Affected people should receive a direct explanation when appropriate, and the underlying process should be reviewed so the same failure is less likely to repeat.
Report a material issue